asn.dev

Observed topology

AS210000 TwentyWAN-Networks TwentyWAN MB

Hosting RIPE Network Services

Upstreams 4 carry this network
Downstreams 3 this network carries
Adjacent (IPv4) 6
Adjacent (IPv6) 6
Upstream graph Who carries AS210000, and who carries them, drawn as a map up to the transit-free core. 1 exchange Where AS210000 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS210000: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6447
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4 IPv6171
AS36530IDC CubeUnclassifiedIPv459
AS60011Mythic Beasts LtdHostingIPv4 IPv614

Transit

Downstream networks

inferred

Networks for which AS210000 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS201217RADISHCLOUD TECHNOLOGY LLCHostingIPv4 IPv6246
AS36530IDC CubeUnclassifiedIPv636
AS57406Zero Distance Internet LLCUnclassifiedIPv635

Adjacency

Adjacent networks

observed

Every AS seen directly next to AS210000 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6871
AS6424EDGOO NETWORKS UNIPESSOAL LDAHostingIPv4 IPv6622
AS36530IDC CubeUnclassifiedIPv4 IPv6589
AS201217RADISHCLOUD TECHNOLOGY LLCHostingIPv4 IPv6246
AS7480Tsung-Yi YuUnclassifiedIPv466
AS57406Zero Distance Internet LLCUnclassifiedIPv635
AS60011Mythic Beasts LtdHostingIPv4 IPv616

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.