Skip to main content

AS218444

AS218444

Root Web TR

Registry

Authoritative registration data

AS number
218444
Name
AS218444
Organisation
Root Web TR
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

4

Total announced

5

Announced prefixes

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

Prefixes announced by AS218444
199.201.237.0/24 IPv4 /24 not checked
2602:f86f:50::/44 IPv6 /44 not checked
2602:f86f:52::/48 IPv6 /48 not checked
2602:f86f:53::/48 IPv6 /48 not checked
2602:f86f:58::/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 AS218444
Address families
INTERIX 1,000 Mbps IPv4 · IPv6
LOCIX DUSSELDORF: Peering LAN 1,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 AS218444 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS218444 in AS paths

Observed upstreams
Families
AS212895 ROUTE64_ORG 189 283
v4 v6
AS34872 Servperso_Systems 150 202
v4 v6
AS47272 HYEHOST 146 176
v6
AS6939 HURRICANE 91 120
v4 v6
AS197324 Vladyslav 45 56
v4 v6
AS41051 FREETRANSIT 20 27
v4 v6
AS8772 NLineLLC 9 11
v6
AS56630 MELBICOM-EU-AS 5 7
v6
AS29632 NASSIST-AS 3 3
v6
AS25091 IP-Max 2 3
v4 v6
AS401753 BIXCE 1 2
v4 v6
AS211358 AS-IPV6GO 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS218444 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 4
v4 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.