Observed topology
AS3580 PLANET - Planet Networks
Residential ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS3580: 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 | 178 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 113 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 96 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 84 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 30 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 19 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 11 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 11 |
| AS1836 | green.ch AG | Residential | IPv6 | 3 |
| AS9002 | RETN Limited | Unclassified | IPv6 | 3 |
Transit
Downstream networks
Networks for which AS3580 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS208951 | ITGLOBAL.COM NL B.V. | Unclassified | IPv4 | 289 |
| AS30144 | BQ Internet Corporation | Unclassified | IPv4 | 174 |
| AS396924 | Skylands Networks | Unclassified | IPv4 | 112 |
| AS26202 | Planet Networks | Residential | IPv4 | 95 |
| AS11981 | Yolo Risk Management LLC | Unclassified | IPv4 IPv6 | 91 |
| AS400068 | LION TECHNOLOGY INC | Unclassified | IPv4 | 46 |
| AS19865 | Icarz, Inc | Unclassified | IPv4 | 22 |
| AS15239 | Franklin Mutual Insurance Company | Unclassified | IPv4 | 9 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3580 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 408 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 297 |
| AS208951 | ITGLOBAL.COM NL B.V. | Unclassified | IPv4 | 289 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 239 |
| AS30144 | BQ Internet Corporation | Unclassified | IPv4 | 174 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 158 |
| AS396924 | Skylands Networks | Unclassified | IPv4 | 112 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 110 |
| AS26202 | Planet Networks | Residential | IPv4 | 95 |
| AS11981 | Yolo Risk Management LLC | Unclassified | IPv4 IPv6 | 91 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.