Observed topology

AS11956 National Oceanic and Atmospheric Administration

Unclassified ARIN

Upstreams 0 carry this network

Downstreams 1 this network carries

Adjacent (IPv4) 5

Adjacent (IPv6) 4

Upstream graph Who carries AS11956, and who carries them, drawn as a map up to the transit-free core. 0 exchanges Where AS11956 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS11956: 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 AS11956 was observed as the last hop before the origin, meaning it appears to provide them transit.

AS	Network	Type	Families	Paths seen
AS3477	National Oceanic and Atmospheric Administration	Unclassified	IPv4 IPv6	5,773

Adjacency

Adjacent networks

observed

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

AS	Network	Type	Families	Paths seen
AS3477	National Oceanic and Atmospheric Administration	Unclassified	IPv4 IPv6	9,241
AS10886	University of Maryland	Education	IPv4 IPv6	5,618
AS14041	University Corporation for Atmospheric Research	Education	IPv4 IPv6	3,089
AS101	University of Washington	Unclassified	IPv4 IPv6	407
AS293	ESnet	Unclassified	IPv4	127

Provenance

Where this comes from

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