asn.dev

Observed topology

AS42947 SKYNETLINK-AS Telfy Telecom S.L.

Unclassified RIPE

Upstreams 31 carry this network
Downstreams 1 this network carries
Adjacent (IPv4) 30
Adjacent (IPv6) 14
Upstream graph Who carries AS42947, and who carries them, drawn as a map up to the transit-free core. 5 exchanges Where AS42947 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 31

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.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,222
AS6939Hurricane Electric LLCTransitIPv4 IPv6814
AS174Cogent Communications, LLCTransitIPv4 IPv6575
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6226
AS50304Blix Solutions ASUnclassifiedIPv4138
AS8637SpainWISP, S.L.UnclassifiedIPv4131
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv688
AS24482SG.GSHostingIPv4 IPv688
AS48185team.blue NVUnclassifiedIPv4 IPv688
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv688

All 31 upstreams →

Transit

Downstream networks

inferred

Networks for which AS42947 was observed as the last hop before the origin, meaning it appears to provide them transit.

ASNetworkTypeFamiliesPaths seen
AS59885TELECUATRO C.B.UnclassifiedIPv4171

Adjacency

Adjacent networks

All 33

Every AS seen directly next to AS42947 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3356Level 3 Parent, LLCTransitIPv4 IPv61,258
AS6939Hurricane Electric LLCTransitIPv4 IPv6835
AS174Cogent Communications, LLCTransitIPv4 IPv6613
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6235
AS59885TELECUATRO C.B.UnclassifiedIPv4171
AS50304Blix Solutions ASUnclassifiedIPv4144
AS8637SpainWISP, S.L.UnclassifiedIPv4143
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv691
AS24482SG.GSHostingIPv4 IPv691
AS48185team.blue NVUnclassifiedIPv4 IPv691

All 33 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-10 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 71.97M 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.