Observed topology
AS18530 ISOMEDIA-1
Hosting ARIN Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS18530: 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 |
|---|---|---|---|---|
| AS209 | CenturyLink Communications, LLC | Residential | IPv4 IPv6 | 1,811 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,685 |
| AS11404 | Wave Broadband | Residential | IPv4 IPv6 | 857 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 228 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 118 |
| AS21859 | Zenlayer Inc | Hosting | IPv4 IPv6 | 89 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 84 |
| AS3130 | RGnet OU | Unclassified | IPv4 | 59 |
| AS7575 | Australian Academic and Research Network AARNet | Education | IPv4 | 59 |
| AS24482 | SG.GS | Hosting | IPv4 | 59 |
Transit
Downstream networks
Networks for which AS18530 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS10557 | Connect Northwest Internet Services, LLC | Unclassified | IPv4 | 4,778 |
| AS399310 | South Sound 911 | Unclassified | IPv4 | 882 |
| AS397731 | EliteWork LLC | Unclassified | IPv4 | 480 |
| AS400699 | KitsapWiFi | Residential | IPv4 IPv6 | 102 |
| AS18849 | Richesin Engineering, LLC | Unclassified | IPv4 | 86 |
| AS53340 | VegasNAP, LLC | Hosting | IPv4 | 43 |
| AS16652 | Riseup Networks | Hosting | IPv4 | 42 |
| AS30170 | Isomedia, Inc. | Unclassified | IPv4 IPv6 | 35 |
| AS22030 | Zipcon LLC | Hosting | IPv4 | 10 |
| AS399524 | SoundLine Communications | Unclassified | IPv4 | 7 |
Adjacency
Adjacent networks
Every AS seen directly next to AS18530 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209 | CenturyLink Communications, LLC | Residential | IPv4 IPv6 | 4,879 |
| AS10557 | Connect Northwest Internet Services, LLC | Unclassified | IPv4 | 4,778 |
| AS11404 | Wave Broadband | Residential | IPv4 IPv6 | 2,775 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,512 |
| AS399310 | South Sound 911 | Unclassified | IPv4 | 882 |
| AS397731 | EliteWork LLC | Unclassified | IPv4 | 480 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 312 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 228 |
| AS30170 | Isomedia, Inc. | Unclassified | IPv4 IPv6 | 210 |
| AS7575 | Australian Academic and Research Network AARNet | Education | IPv4 | 183 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.