Observed topology
AS25160 VORBOSS Vorboss Limited
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS25160: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 453 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 348 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 240 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 136 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 103 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 66 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 63 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 37 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 37 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 37 |
Transit
Downstream networks
Networks for which AS25160 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50056 | Vorboss Limited | Unclassified | IPv4 | 780 |
| AS48273 | ESSENSYS (UK) Ltd. | Unclassified | IPv4 | 420 |
| AS210054 | NCG Energy Ltd | Unclassified | IPv4 IPv6 | 237 |
| AS206392 | Hackworth Ltd | Unclassified | IPv4 IPv6 | 126 |
| AS215287 | Secure Digital Apps CO WLL | Unclassified | IPv4 | 120 |
| AS24894 | Tag Europe Ltd | Unclassified | IPv4 | 59 |
| AS203416 | I.T Communications Limited | Hosting | IPv4 IPv6 | 51 |
| AS212286 | LonConnect Ltd | Unclassified | IPv4 | 40 |
| AS31050 | The Framestore Limited | Unclassified | IPv4 | 34 |
| AS206573 | London Systems UK Limited | Unclassified | IPv4 | 24 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25160 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 832 |
| AS50056 | Vorboss Limited | Unclassified | IPv4 | 780 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 629 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 453 |
| AS48273 | ESSENSYS (UK) Ltd. | Unclassified | IPv4 | 420 |
| AS210054 | NCG Energy Ltd | Unclassified | IPv4 IPv6 | 237 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 231 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 208 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 | 148 |
| AS206392 | Hackworth Ltd | Unclassified | IPv4 IPv6 | 126 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.