Observed topology
AS3477 NOAA-NWAVE
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS3477: 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.
Transit
Downstream networks
Networks for which AS3477 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2648 | National Oceanic and Atmospheric Administration | Unclassified | IPv4 IPv6 | 1,040 |
| AS49 | National Institute of Standards and Technology | Unclassified | IPv4 IPv6 | 953 |
| AS5744 | United States Patent and Trademark Office | Unclassified | IPv4 IPv6 | 407 |
| AS30687 | National Weather Service Southern Region Headquarters | Unclassified | IPv4 | 300 |
| AS40623 | Office of Oceanic and Atmospheric Research - Geophysical Fluid Dynamics Laboratory | Unclassified | IPv4 IPv6 | 186 |
| AS16550 | Google LLC | Unclassified | IPv4 | 182 |
| AS12076 | Microsoft Corporation | Unclassified | IPv4 | 122 |
| AS3635 | U.S. Department of Commerce, Bureau of Economic Analysis | Unclassified | IPv4 IPv6 | 93 |
| AS6629 | National Oceanic and Atmospheric Administration | Unclassified | IPv4 IPv6 | 93 |
| AS33343 | U.S. Department of Commerce, HQ and ITA | Unclassified | IPv4 IPv6 | 93 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3477 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS11956 | National Oceanic and Atmospheric Administration | Unclassified | IPv4 IPv6 | 9,242 |
| AS2648 | National Oceanic and Atmospheric Administration | Unclassified | IPv4 IPv6 | 1,040 |
| AS49 | National Institute of Standards and Technology | Unclassified | IPv4 IPv6 | 953 |
| AS5744 | United States Patent and Trademark Office | Unclassified | IPv4 IPv6 | 407 |
| AS30687 | National Weather Service Southern Region Headquarters | Unclassified | IPv4 | 300 |
| AS26100 | National Oceanic and Atmospheric Administration | Unclassified | IPv4 IPv6 | 207 |
| AS40623 | Office of Oceanic and Atmospheric Research - Geophysical Fluid Dynamics Laboratory | Unclassified | IPv4 IPv6 | 186 |
| AS16550 | Google LLC | Unclassified | IPv4 | 182 |
| AS12076 | Microsoft Corporation | Unclassified | IPv4 | 122 |
| AS3635 | U.S. Department of Commerce, Bureau of Economic Analysis | Unclassified | IPv4 IPv6 | 93 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.