Observed topology
AS2518 BIGLOBE BIGLOBE Inc.
Residential APNIC NSP
Transit
Upstream networks
Networks observed carrying traffic for AS2518: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 961 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 294 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 194 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 139 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 118 |
| AS4635 | Hong Kong Internet Exchange--Route Server 1 | Unclassified | IPv4 | 65 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 35 |
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 | 33 |
| AS4657 | StarHub Ltd | Residential | IPv4 | 33 |
| AS20485 | Joint Stock Company TransTeleCom | Unclassified | IPv4 | 33 |
Transit
Downstream networks
Networks for which AS2518 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS10010 | TOKAI Communications Corporation | Residential | IPv4 | 1,228 |
| AS18068 | Dream Wave Shizuoka Co. Ltd. | Unclassified | IPv4 IPv6 | 647 |
| AS23629 | Obihiro City Cable Co.,Ltd. | Residential | IPv4 | 503 |
| AS4711 | INTEC Inc. | Unclassified | IPv4 IPv6 | 462 |
| AS7524 | ITEC HANKYU HANSHIN CO.,LTD. | Residential | IPv4 | 344 |
| AS17961 | mitene internet co., ltd. | Unclassified | IPv4 IPv6 | 307 |
| AS9354 | Community Network Center Inc. | Residential | IPv4 | 299 |
| AS7511 | SYNAPSE Co.,Ltd. | Residential | IPv4 IPv6 | 281 |
| AS23661 | CLARA, Inc. | Hosting | IPv4 IPv6 | 218 |
| AS9621 | Okinawa Telecommunication Network Co.,Inc | Residential | IPv4 IPv6 | 200 |
Adjacency
Adjacent networks
Every AS seen directly next to AS2518 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,670 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 IPv6 | 3,334 |
| AS59105 | Home NOC Operators Group | Unclassified | IPv4 IPv6 | 2,783 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,714 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,802 |
| AS9354 | Community Network Center Inc. | Residential | IPv4 IPv6 | 1,259 |
| AS10010 | TOKAI Communications Corporation | Residential | IPv4 | 1,228 |
| AS18068 | Dream Wave Shizuoka Co. Ltd. | Unclassified | IPv4 IPv6 | 689 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 571 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 515 |
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.