Observed topology
AS20860 IOMART-AS IOMART CLOUD SERVICES LIMITED
Hosting DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS20860: 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 | 3,209 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 3,110 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,877 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 567 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 378 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 189 |
| AS3741 | Dimension Data | Unclassified | IPv4 | 189 |
| AS4637 | Telstra Global | Unclassified | IPv4 | 189 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 189 |
| AS24482 | SG.GS | Hosting | IPv4 | 189 |
Transit
Downstream networks
Networks for which AS20860 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS200876 | Evolving Networks Limited | Unclassified | IPv4 | 2,092 |
| AS47264 | Iomart Managed Services Limited | Unclassified | IPv4 IPv6 | 2,011 |
| AS35425 | Iomart Managed Services Limited | Hosting | IPv4 IPv6 | 1,404 |
| AS199542 | Iomart Managed Services Limited | Unclassified | IPv4 | 1,197 |
| AS50957 | MEMSET Ltd | Hosting | IPv4 IPv6 | 496 |
| AS51320 | Wireless Logic Limited | Unclassified | IPv4 | 464 |
| AS201715 | Ineedbroadband Ltd | Unclassified | IPv4 | 227 |
| AS208621 | LogicForge Limited | Hosting | IPv4 IPv6 | 215 |
| AS206078 | UltraNetworks Limited | Residential | IPv4 | 204 |
| AS206332 | Arrow Business Communications Limited | Unclassified | IPv4 | 171 |
Adjacency
Adjacent networks
Every AS seen directly next to AS20860 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 6,244 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 5,765 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,278 |
| AS200876 | Evolving Networks Limited | Unclassified | IPv4 | 2,092 |
| AS47264 | Iomart Managed Services Limited | Unclassified | IPv4 IPv6 | 2,068 |
| AS35425 | Iomart Managed Services Limited | Hosting | IPv4 IPv6 | 1,404 |
| AS199542 | Iomart Managed Services Limited | Unclassified | IPv4 | 1,197 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 1,008 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 670 |
| AS50957 | MEMSET Ltd | Hosting | IPv4 IPv6 | 496 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.