asn.dev

Observed topology

AS1000 CORIX NETWORKS

Unclassified ARIN NSP

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS1000: 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.

No upstream observed. Typical for a tier-1 network that buys transit from nobody.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS268737CONECT TELECOM COMUNICACAO LTDAUnclassifiedIPv4 IPv6136
AS263258INTERLIG TELECOMUnclassifiedIPv4 IPv6107
AS264329ESTRATEGIA REDES DE TELECOMUNICACOES LTDA.UnclassifiedIPv4 IPv692
AS262972Info Sete TelecomunicacoesHostingIPv442

Adjacency

Adjacent networks

All 11

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

ASNetworkTypeFamiliesPaths seen
AS264329ESTRATEGIA REDES DE TELECOMUNICACOES LTDA.UnclassifiedIPv4 IPv61,618
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,286
AS6939Hurricane Electric LLCTransitIPv4 IPv6676
AS268737CONECT TELECOM COMUNICACAO LTDAUnclassifiedIPv4 IPv6180
AS263258INTERLIG TELECOMUnclassifiedIPv4 IPv6149
AS262972Info Sete TelecomunicacoesHostingIPv484
AS47065USC / UFMG PEERING Research TestbedEducationIPv458
AS24482SG.GSHostingIPv4 IPv650
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv616
AS6453TATA COMMUNICATIONS (AMERICA) INCTransitIPv42

All 11 adjacent →

Provenance

Where this comes from

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