Observed topology
AS42947 SKYNETLINK-AS
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS42947: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,291 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 833 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 575 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 226 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 138 |
| AS8637 | SpainWISP, S.L. | Unclassified | IPv4 | 133 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 88 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 88 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 88 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 88 |
Transit
Downstream networks
Networks for which AS42947 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS59885 | TELECUATRO C.B. | Unclassified | IPv4 | 176 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42947 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,329 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 854 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 613 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 235 |
| AS59885 | TELECUATRO C.B. | Unclassified | IPv4 | 176 |
| AS8637 | SpainWISP, S.L. | Unclassified | IPv4 | 145 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 144 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 91 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 91 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 91 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.