Observed topology
AS8758 IWAY
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8758: 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 |
|---|---|---|---|---|
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 IPv6 | 833 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 518 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 338 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 269 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 198 |
| AS15576 | NTS workspace AG | Unclassified | IPv4 IPv6 | 54 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 53 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 53 |
| AS49432 | Dominic Schallert trading as schallert.com e.U. | Unclassified | IPv4 IPv6 | 53 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 53 |
Transit
Downstream networks
Networks for which AS8758 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204478 | EW Hoefe AG | Unclassified | IPv4 | 240 |
| AS209886 | LAKE Solutions AG | Unclassified | IPv4 IPv6 | 178 |
| AS29691 | Nine Internet Solutions AG | Hosting | IPv4 IPv6 | 165 |
| AS215217 | Vadian.Net AG | Unclassified | IPv4 IPv6 | 133 |
| AS207733 | Iway AG | Unclassified | IPv4 IPv6 | 130 |
| AS206492 | Nexphone AG | Unclassified | IPv4 | 118 |
| AS199403 | DR. BAEHLER DROPA AG | Unclassified | IPv4 | 95 |
| AS215044 | OBT AG | Unclassified | IPv4 IPv6 | 91 |
| AS20612 | SwissIX Internet Exchange | Hosting | IPv4 IPv6 | 89 |
| AS211174 | St. Gallisch-Appenzellische Kraftwerke AG | Unclassified | IPv4 IPv6 | 89 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8758 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS8220 | COLT Technology Services Group Limited | Hosting | IPv4 IPv6 | 1,443 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 1,108 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 898 |
| AS29691 | Nine Internet Solutions AG | Hosting | IPv4 IPv6 | 739 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 486 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 303 |
| AS204478 | EW Hoefe AG | Unclassified | IPv4 | 240 |
| AS209886 | LAKE Solutions AG | Unclassified | IPv4 IPv6 | 178 |
| AS211664 | Q-MEX Networks GmbH | Unclassified | IPv4 | 137 |
| AS215217 | Vadian.Net AG | Unclassified | IPv4 IPv6 | 133 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-13 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.22M 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.