Observed topology
AS25460 TNP-AS
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS25460: 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 | 153 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 110 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 108 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 28 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 18 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 18 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 10 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 10 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 10 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 10 |
Transit
Downstream networks
Networks for which AS25460 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59619 | Blackpool Borough Council | Unclassified | IPv4 | 118 |
| AS198142 | Warrington Borough Council | Unclassified | IPv4 | 118 |
| AS30847 | Lancaster University Network Services Limited | Unclassified | IPv4 IPv6 | 96 |
| AS35832 | Birmingham City Council | Unclassified | IPv4 | 79 |
| AS202206 | FAT MEDIA LTD | Unclassified | IPv4 | 70 |
| AS25585 | Kencomp Internet Ltd | Unclassified | IPv4 | 60 |
| AS49049 | Bath North East Somerset Council | Unclassified | IPv4 | 59 |
| AS211438 | Shetland Islands Council | Unclassified | IPv4 | 27 |
Adjacency
Adjacent networks
Every AS seen directly next to AS25460 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 | 272 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 249 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 220 |
| AS59619 | Blackpool Borough Council | Unclassified | IPv4 | 118 |
| AS198142 | Warrington Borough Council | Unclassified | IPv4 | 118 |
| AS30847 | Lancaster University Network Services Limited | Unclassified | IPv4 IPv6 | 96 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 80 |
| AS35832 | Birmingham City Council | Unclassified | IPv4 | 79 |
| AS202206 | FAT MEDIA LTD | Unclassified | IPv4 | 70 |
| AS25585 | Kencomp Internet Ltd | Unclassified | IPv4 | 60 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.