Observed topology
AS17511 OPTAGE OPTAGE Inc.
Residential APNIC Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS17511: 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 |
|---|---|---|---|---|
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 IPv6 | 1,057 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 980 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 571 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 IPv6 | 265 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 264 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 256 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 83 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 68 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 66 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 | 66 |
Transit
Downstream networks
Networks for which AS17511 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS24270 | CRC Solutions Corp., | Hosting | IPv4 IPv6 | 212 |
| AS24282 | KAGOYA JAPAN Inc. | Hosting | IPv4 IPv6 | 79 |
| AS131924 | Kansai Airports | Unclassified | IPv4 IPv6 | 60 |
| AS9358 | OPTAGE Inc. | Unclassified | IPv4 | 59 |
| AS151379 | OPTAGE Inc. | Unclassified | IPv4 | 58 |
| AS63402 | Universal Orlando | Unclassified | IPv4 | 52 |
| AS4711 | INTEC Inc. | Unclassified | IPv4 IPv6 | 49 |
| AS59118 | NRI SecureTechnologies, Ltd. | Unclassified | IPv4 | 44 |
| AS38633 | Value Core Inc. | Unclassified | IPv4 | 16 |
| AS59124 | KYOTO Prefectural Government | Unclassified | IPv4 | 6 |
Adjacency
Adjacent networks
Every AS seen directly next to AS17511 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS2497 | Internet Initiative Japan Inc. | Unclassified | IPv4 IPv6 | 1,260 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 980 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 627 |
| AS4637 | Telstra Global | Unclassified | IPv4 IPv6 | 365 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 329 |
| AS2516 | KDDI CORPORATION | Mobile | IPv4 IPv6 | 318 |
| AS24270 | CRC Solutions Corp., | Hosting | IPv4 IPv6 | 212 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 101 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 100 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 94 |
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.