Skip to main content

AS211360

AS-HATHOST

+------------------------------------+

Registry

Authoritative registration data

AS number
211360
Name
AS-HATHOST
Organisation
+------------------------------------+
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

5

Total announced

6

Announced prefixes

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

Prefixes announced by AS211360
193.84.108.0/24 IPv4 /24 not checked
2a10:ba80::/31 IPv6 /31 not checked
2a06:a005:a90::/44 IPv6 /44 RPKI valid
2a06:a005:aa0::/44 IPv6 /44 RPKI valid
2a06:a005:ac0::/44 IPv6 /44 RPKI valid
2a06:a005:1f::/48 IPv6 /48 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 AS211360
Address families
EVIX: Peering LAN 1,000 Mbps IPv6
MINAP Milan: MINAP 40,000 Mbps IPv4 · IPv6
PCIX 10,000 Mbps IPv4 · IPv6
VSIX: Primary 10,000 Mbps IPv4 · IPv6
ixFabric - Frankfurt 1,000 Mbps 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 AS211360 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS211360 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 481 1,936
v4 v6
AS5405 INTERDOTLINK 512 1,521
v4 v6
AS211509 RUDAKI-AS 6 18
v6
AS14840 ASN14840 2 5
v4
AS1267 ASN-WINDTRE 1 1
v4
AS9498 BBIL-AP 1 1
v4
AS263444 ASN263444 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS211360 in AS paths

Observed downstreams
Families
AS56781 AS-ASNETPROIT 262 1,080
v6
AS57698 AS-HATHOST 261 359
v6

No rows match “”.

Showing – of

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

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.