Observed topology
AS2497 IIJ Internet Initiative Japan Inc.
Unclassified DROP-listed space APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS2497: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,753 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 2,200 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,900 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,844 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,380 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 702 |
| AS5511 | Orange S.A. | Transit | IPv4 IPv6 | 624 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 538 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 527 |
| AS1257 | Tele2 Sverige AB | Mobile | IPv4 IPv6 | 269 |
Transit
Downstream networks
Networks for which AS2497 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2907 | Research Organization of Information and Systems, National Institute of Informatics | Unclassified | IPv4 IPv6 | 24,830 |
| AS9605 | NTT DOCOMO, INC. | Mobile | IPv4 IPv6 | 14,880 |
| AS4694 | IDC Frontier Inc. | Hosting | IPv4 IPv6 | 10,650 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 | 10,385 |
| AS9824 | JCOM Co., Ltd. | Residential | IPv4 IPv6 | 7,091 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 5,032 |
| AS59109 | Hitachi,Ltd., Managed & Platform Services Business Division | Unclassified | IPv4 | 3,835 |
| AS6327 | Shaw Communications | Residential | IPv4 | 3,829 |
| AS17514 | Otsuka Corp. | Hosting | IPv4 | 3,599 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 | 3,507 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2497 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 179,656 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 146,093 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 118,372 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 100,786 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 91,106 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 78,774 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 53,878 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 | 43,639 |
| AS2907 | Research Organization of Information and Systems, National Institute of Informatics | Unclassified | IPv4 IPv6 | 41,705 |
| AS58453 | China Mobile International Limited | Unclassified | IPv4 | 32,937 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-23 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.15M 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.