Observed topology
AS2516 KDDI KDDI CORPORATION
Mobile DROP-listed space ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS2516: 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 | 8,414 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,059 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 3,525 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,265 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 2,810 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 2,235 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 | 1,660 |
| AS577 | Bell Canada | Mobile | IPv4 | 1,114 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 565 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 559 |
Transit
Downstream networks
Networks for which AS2516 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS20940 | Akamai International B.V. | Hosting | IPv4 IPv6 | 8,537 |
| AS38631 | LY Corporation | Hosting | IPv4 IPv6 | 6,804 |
| AS9824 | JCOM Co., Ltd. | Residential | IPv4 IPv6 | 5,587 |
| AS55374 | FUJITSU LIMITED | Unclassified | IPv4 IPv6 | 3,504 |
| AS131932 | JR East Information Systems Company | Unclassified | IPv4 | 2,741 |
| AS54994 | Meteverse Limited. | Unclassified | IPv4 IPv6 | 2,299 |
| AS7687 | TOYOTA SYSTEMS CORPORATION | Unclassified | IPv4 | 2,075 |
| AS59107 | Hachinohe Cable Television Co. | Residential | IPv4 | 1,803 |
| AS7479 | KDD HONG KONG LIMITED | Unclassified | IPv4 | 1,566 |
| AS132203 | Tencent Building, Kejizhongyi Avenue | Hosting | IPv4 IPv6 | 1,180 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2516 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 24,628 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 24,061 |
| AS20940 | Akamai International B.V. | Hosting | IPv4 IPv6 | 15,962 |
| AS9824 | JCOM Co., Ltd. | Residential | IPv4 IPv6 | 15,210 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 13,963 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 13,689 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 13,373 |
| AS38631 | LY Corporation | Hosting | IPv4 IPv6 | 6,804 |
| AS577 | Bell Canada | Mobile | IPv4 IPv6 | 5,074 |
| AS2152 | CENIC | Unclassified | IPv4 | 4,643 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.