asn.dev

Observed topology

AS40498 ABQG

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS40498: 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
AS3356Level 3 Parent, LLCTransitIPv4 IPv6383
AS174Cogent Communications, LLCTransitIPv4228
AS2152CENICUnclassifiedIPv4 IPv684
AS3912CHECSEducationIPv440
AS11537Internet2UnclassifiedIPv4 IPv634
AS2153CENICUnclassifiedIPv429
AS11164Internet2EducationIPv62

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS11570Eastern New Mexico UniversityEducationIPv4654
AS3912CHECSEducationIPv4372
AS17153New Mexico TechUnclassifiedIPv4315
AS3388University of New MexicoEducationIPv4112
AS40586University of New Mexico Health Sciences CenterUnclassifiedIPv426
AS11996Lobo Internet Services, LtdUnclassifiedIPv4 IPv65

Adjacency

Adjacent networks

All 13

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,206
AS3912CHECSEducationIPv4 IPv61,038
AS174Cogent Communications, LLCTransitIPv4804
AS11570Eastern New Mexico UniversityEducationIPv4658
AS17153New Mexico TechUnclassifiedIPv4315
AS2152CENICUnclassifiedIPv4 IPv6267
AS11537Internet2UnclassifiedIPv4 IPv6153
AS3388University of New MexicoEducationIPv4112
AS2153CENICUnclassifiedIPv475
AS293ESnetUnclassifiedIPv430

All 13 adjacent →

Provenance

Where this comes from

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