Observed topology
AS8801 AS-ROCKET United Kingdom
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8801: 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 |
|---|---|---|---|---|
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 95 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 87 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 62 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 30 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 23 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 16 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 9 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 9 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 9 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 9 |
Transit
Downstream networks
Networks for which AS8801 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16353 | Merula Limited | Hosting | IPv4 IPv6 | 1,009 |
| AS59778 | Synextra Limited | Unclassified | IPv4 | 726 |
| AS203649 | GO INTERNET LTD | Residential | IPv4 IPv6 | 352 |
| AS215262 | Cloud Nord Limited | Unclassified | IPv4 IPv6 | 294 |
| AS59455 | Clearstream Technology ltd | Unclassified | IPv4 IPv6 | 189 |
| AS212174 | Jola Cloud Solutions Ltd | Unclassified | IPv4 | 130 |
| AS60255 | Internetty Ltd | Residential | IPv4 IPv6 | 128 |
| AS212815 | Dyjix SAS | Residential | IPv4 | 75 |
| AS200581 | TfW Fibre Ltd | Unclassified | IPv4 IPv6 | 68 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8801 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 1,252 |
| AS16353 | Merula Limited | Hosting | IPv4 IPv6 | 1,175 |
| AS212815 | Dyjix SAS | Residential | IPv4 IPv6 | 883 |
| AS59778 | Synextra Limited | Unclassified | IPv4 | 726 |
| AS215262 | Cloud Nord Limited | Unclassified | IPv4 IPv6 | 354 |
| AS203649 | GO INTERNET LTD | Residential | IPv4 IPv6 | 352 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 338 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 338 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 337 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 294 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.