Observed topology
AS42831 UKSERVERS-AS UK Dedicated Servers, Hosting and Co-Location
Hosting DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS42831: 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 |
|---|---|---|---|---|
| AS35200 | TransitX Ltd | Unclassified | IPv4 | 4,720 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 3,721 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 3,096 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,264 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 IPv6 | 260 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 260 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 260 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 260 |
| AS37100 | SEACOM Limited | Unclassified | IPv4 | 243 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 212 |
Transit
Downstream networks
Networks for which AS42831 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS64080 | SYN LTD | Unclassified | IPv4 IPv6 | 1,289 |
| AS200260 | Debugged Ltd | Hosting | IPv4 | 724 |
| AS7489 | HostUS | Hosting | IPv4 IPv6 | 591 |
| AS206074 | F.N.S. HOLDINGS LIMITED | Unclassified | IPv6 | 224 |
| AS46261 | QuickPacket, LLC | Unclassified | IPv4 | 219 |
| AS59676 | Network Services Ltd. | Unclassified | IPv4 IPv6 | 184 |
| AS47625 | Paul David Hughes | Unclassified | IPv4 | 174 |
| AS205072 | Layershift Limited | Unclassified | IPv4 | 174 |
| AS216382 | LAYER MARKETING SERVICES L.L.C | Unclassified | IPv4 IPv6 | 126 |
| AS64245 | DigitalFyre Internet Solutions, LLC. | Unclassified | IPv4 IPv6 | 125 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42831 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35200 | TransitX Ltd | Unclassified | IPv4 IPv6 | 7,817 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 6,581 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 5,223 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 4,243 |
| AS64080 | SYN LTD | Unclassified | IPv4 IPv6 | 1,289 |
| AS200260 | Debugged Ltd | Hosting | IPv4 | 724 |
| AS7489 | HostUS | Hosting | IPv4 IPv6 | 591 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 467 |
| AS37100 | SEACOM Limited | Unclassified | IPv4 | 398 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 355 |
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.