asn.dev

Observed topology

AS999 CORIX-999

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS999: 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
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6278
AS174Cogent Communications, LLCTransitIPv4 IPv6190
AS22356Durand do Brasil LtdaUnclassifiedIPv4 IPv6132
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv625
AS28663FLYS INTERATIVA LTDAUnclassifiedIPv611
AS3303Swisscom (Schweiz) AGResidentialIPv41
AS24482SG.GSHostingIPv41
AS35280F5 Networks SARLHostingIPv61

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS20253Qwilt Inc.UnclassifiedIPv4455

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv4 IPv6527
AS20253Qwilt Inc.UnclassifiedIPv4455
AS174Cogent Communications, LLCTransitIPv4 IPv6278
AS22356Durand do Brasil LtdaUnclassifiedIPv4 IPv6230
AS6939Hurricane Electric LLCTransitIPv4 IPv6130
AS28663FLYS INTERATIVA LTDAUnclassifiedIPv4 IPv631
AS1031PEER 1031 LLCUnclassifiedIPv4 IPv627
AS3303Swisscom (Schweiz) AGResidentialIPv41
AS24482SG.GSHostingIPv41
AS35280F5 Networks SARLHostingIPv61

Provenance

Where this comes from

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