asn.dev

Observed topology

AS396955 INTERNET2-BLEND

Unclassified ARIN

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS396955: 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 IPv6777
AS1299Arelion Sweden ABTransitIPv4 IPv6272
AS11164Internet2EducationIPv4 IPv6152
AS11537Internet2UnclassifiedIPv4 IPv639

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS396961Internet2UnclassifiedIPv4 IPv6313
AS62775Internet2UnclassifiedIPv4 IPv6156
AS401950IPNSIG INC.UnclassifiedIPv4 IPv652
AS399855Keystone REN, LLCUnclassifiedIPv439
AS394088Agriculture Research ServiceUnclassifiedIPv438

Adjacency

Adjacent networks

observed

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

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,048
AS1299Arelion Sweden ABTransitIPv4 IPv6599
AS396961Internet2UnclassifiedIPv4 IPv6313
AS62775Internet2UnclassifiedIPv4 IPv6156
AS11164Internet2EducationIPv4 IPv6152
AS401950IPNSIG INC.UnclassifiedIPv4 IPv652
AS11537Internet2UnclassifiedIPv4 IPv639
AS399855Keystone REN, LLCUnclassifiedIPv439
AS394088Agriculture Research ServiceUnclassifiedIPv438

Provenance

Where this comes from

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