asn.dev

Observed topology

AS297 AS297 - National Aeronautics and Space Administration

Upstreams 8 carry this network
Downstreams 7 this network carries
Adjacent (IPv4) 15
Adjacent (IPv6) 5

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS297: 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
AS209CenturyLink Communications, LLCResidentialIPv4714
AS2914NTT America, Inc.TransitIPv4436
AS6939Hurricane Electric LLCTransitIPv4 IPv6274
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4136
AS11537Internet2UnclassifiedIPv440
AS2497Internet Initiative Japan Inc.UnclassifiedIPv422
AS293ESnetUnclassifiedIPv420
AS38022REANNZ National Research and Education NetworkUnclassifiedIPv46

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.

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS270National Aeronautics and Space AdministrationUnclassifiedIPv410,990
AS10343National Aeronautics and Space AdministrationUnclassifiedIPv4190
AS21556National Aeronautics and Space AdministrationUnclassifiedIPv4 IPv695
AS31951NASA Deep Space Network (DSN)UnclassifiedIPv459
AS393594United States Naval ObservatoryUnclassifiedIPv458
AS24National Aeronautics and Space AdministrationUnclassifiedIPv455
AS1848National Aeronautics and Space AdministrationUnclassifiedIPv452

Adjacency

Adjacent networks

20 shown

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

ASNetworkTypeFamiliesPaths seen
AS270National Aeronautics and Space AdministrationUnclassifiedIPv411,633
AS209CenturyLink Communications, LLCResidentialIPv45,544
AS2914NTT America, Inc.TransitIPv4 IPv64,016
AS6939Hurricane Electric LLCTransitIPv4 IPv62,164
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv4 IPv61,187
AS11537Internet2UnclassifiedIPv4354
AS293ESnetUnclassifiedIPv4221
AS2497Internet Initiative Japan Inc.UnclassifiedIPv4202
AS10343National Aeronautics and Space AdministrationUnclassifiedIPv4190
AS38022REANNZ National Research and Education NetworkUnclassifiedIPv4 IPv6102
AS21556National Aeronautics and Space AdministrationUnclassifiedIPv4 IPv695
AS31951NASA Deep Space Network (DSN)UnclassifiedIPv459
AS393594United States Naval ObservatoryUnclassifiedIPv458
AS24National Aeronautics and Space AdministrationUnclassifiedIPv455
AS1848National Aeronautics and Space AdministrationUnclassifiedIPv452

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.

Interconnection

Exchange presence

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS297, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider to carry traffic between them, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's own page, with its peering LANs and every other network recorded on it. Recorded at 2 exchanges across 1 country and 1 region.

ExchangeLocationTheir addressMember ports
Equinix Internet Exchange AshburnAshburn, United States206.126.237.220388
Equinix Internet Exchange San Jose (Bay Area)San Jose, United States206.223.116.190193

Unlike the tables above, this is recorded rather than inferred. An address on a peering LAN is at that exchange by definition. Two carve-outs all the same. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. And an absent exchange means PCH has no record of it, not that the network is not there.

Provenance

Where this comes from

Derived from routing tables collected at 2026-08-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 74.02M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.

Exchange presence comes from a separate dataset: the directory collected 2026-08-08 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,327 exchanges and 93,137 recorded member ports, licensed CC BY-NC-SA 3.0.

PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.