Skip to main content

AS44530

HOPUS

HOPUS SAS

Registry

Authoritative registration data

AS number
44530
Name
HOPUS
Organisation
HOPUS SAS
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS44530
37.77.32.0/20 IPv4 /20 not checked
2a02:e5c::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS44530
Address families
Hopus 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS44530 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS44530 in AS paths

Observed upstreams
Families
AS20766 GITOYEN-MAIN-AS 163 6,432
v4 v6
AS34019 HIVANE 197 2,672
v4 v6
AS41327 FIBERTELECOM-AS 4 1,843
v4 v6
AS3320 DTAG 164 667
v4 v6
AS3303 SWISSCOM 96 287
v4 v6
AS6830 LibertyGlobal 75 230
v4 v6
AS35661 VIRTUASYS-EU 12 46
v6
AS1273 CW 21 37
v4 v6
AS25091 IP-Max 6 8
v6
AS8218 NEO-ASN 2 6
v6
AS35280 F5 4 5
v6
AS29222 Infomaniak-AS 2 4
v4 v6
AS3215 AS3215 2 3
v4
AS30972 BEDROCK 2 2
v4
AS215596 Kissgroup 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

31 networks seen after AS44530 in AS paths

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS50628 Leonix-Telecom 1 1
v6
AS56987 AS-ABACLOUDA 1 1
v6
AS209823 ENKI-AS 1 1
v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.