asn.dev

Observed topology

AS7500 M-ROOT-DNS WIDE Project

Hosting APNIC

Upstreams 28 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 26
Adjacent (IPv6) 15
Upstream graph Who carries AS7500, and who carries them, drawn as a map up to the transit-free core. 33 exchanges Where AS7500 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 28

Networks observed carrying traffic for AS7500: 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 IPv6191
AS3257GTT Communications Inc.TransitIPv421
AS2516KDDI CORPORATIONMobileIPv413
AS3356Level 3 Parent, LLCTransitIPv4 IPv612
AS2497Internet Initiative Japan Inc.UnclassifiedIPv410
AS2200RenaterEducationIPv4 IPv66
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63
AS4608Asia Pacific Network Information CentreUnclassifiedIPv43
AS24482SG.GSHostingIPv4 IPv63
AS38001NewMedia Express Pte LtdHostingIPv4 IPv63

All 28 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS23634WIDE ProjectUnclassifiedIPv4 IPv682
AS112DNS-OARCUnclassifiedIPv41

Adjacency

Adjacent networks

All 31

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6254
AS23634WIDE ProjectUnclassifiedIPv4 IPv682
AS3257GTT Communications Inc.TransitIPv421
AS3356Level 3 Parent, LLCTransitIPv4 IPv616
AS2516KDDI CORPORATIONMobileIPv413
AS2200RenaterEducationIPv4 IPv611
AS2497Internet Initiative Japan Inc.UnclassifiedIPv411
AS24482SG.GSHostingIPv4 IPv65
AS50628Leonix Telecom SASUnclassifiedIPv4 IPv65
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv63

All 31 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-22 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.12M 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.