Observed topology
AS8888 XTOM xTom Pty Ltd
Hosting RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS8888: 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 |
|---|---|---|---|---|
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 3,957 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,135 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 322 |
| AS9312 | xTom | Hosting | IPv4 IPv6 | 208 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 100 |
| AS931 | Hyonix | Hosting | IPv4 IPv6 | 95 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 56 |
| AS38001 | NewMedia Express Pte Ltd | Hosting | IPv4 IPv6 | 55 |
| AS64073 | Vetta Group | Unclassified | IPv4 IPv6 | 42 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 28 |
Transit
Downstream networks
Networks for which AS8888 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43357 | Owl Limited | Unclassified | IPv4 IPv6 | 8,886 |
| AS43959 | xTom GmbH | Unclassified | IPv6 | 540 |
| AS23959 | Owl Limited | Unclassified | IPv4 IPv6 | 220 |
| AS141776 | Baoshuo Network | Unclassified | IPv4 IPv6 | 130 |
| AS17243 | Byte Node LLC | Unclassified | IPv4 | 120 |
| AS949 | xTom | Hosting | IPv4 IPv6 | 95 |
| AS25737 | Jone Broadband LLC | Unclassified | IPv4 IPv6 | 95 |
| AS212164 | Jiaxian He | Unclassified | IPv6 | 68 |
| AS397668 | Infocrest Systems LLC | Unclassified | IPv4 | 61 |
| AS399737 | Etherware Solutions LLC | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8888 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43357 | Owl Limited | Unclassified | IPv4 IPv6 | 8,886 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 7,934 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 4,139 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 858 |
| AS931 | Hyonix | Hosting | IPv4 IPv6 | 687 |
| AS43959 | xTom GmbH | Unclassified | IPv6 | 540 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 373 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 338 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 291 |
| AS213241 | TECHIT.BE SRL | Residential | IPv4 IPv6 | 269 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.