Observed topology
AS8943 JUMP
Hosting RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS8943: 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.
Transit
Downstream networks
Networks for which AS8943 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS43915 | TrueSpeed Communications Limited | Residential | IPv4 IPv6 | 371 |
| AS44671 | Skyline Networks & Consultancy Ltd | Unclassified | IPv4 IPv6 | 120 |
| AS8676 | PRT Systems Limited | Hosting | IPv4 | 99 |
| AS43950 | Terence Froy trading as "Spilsby Internet Solutions" | Unclassified | IPv4 IPv6 | 91 |
| AS200636 | Paravirt LTD | Unclassified | IPv4 | 59 |
| AS44934 | Arachsys Internet Services Ltd | Unclassified | IPv4 IPv6 | 17 |
| AS24865 | Keith Mitchell | Unclassified | IPv4 | 12 |
| AS51263 | County Broadband Ltd | Unclassified | IPv6 | 3 |
| AS210258 | Wildanet Ltd | Residential | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8943 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,354 |
| AS43915 | TrueSpeed Communications Limited | Residential | IPv4 IPv6 | 371 |
| AS8676 | PRT Systems Limited | Hosting | IPv4 | 146 |
| AS44671 | Skyline Networks & Consultancy Ltd | Unclassified | IPv4 IPv6 | 120 |
| AS200636 | Paravirt LTD | Unclassified | IPv4 | 117 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 98 |
| AS43950 | Terence Froy trading as "Spilsby Internet Solutions" | Unclassified | IPv4 IPv6 | 91 |
| AS44934 | Arachsys Internet Services Ltd | Unclassified | IPv4 IPv6 | 17 |
| AS24865 | Keith Mitchell | Unclassified | IPv4 | 12 |
| AS51263 | County Broadband Ltd | Unclassified | IPv6 | 3 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 16:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.19M 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.