asn.dev

Observed topology

AS57910 SCIP-AS Soluciones Corporativas IP SCIP

Residential RIPE

Upstreams 12 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 12
Adjacent (IPv6) 7
Upstream graph Who carries AS57910, and who carries them, drawn as a map up to the transit-free core. 3 exchanges Where AS57910 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 12

Networks observed carrying traffic for AS57910: 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
AS59908BalaLink S.A.UnclassifiedIPv4 IPv62,145
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv61,515
AS8637SpainWISP, S.L.UnclassifiedIPv4 IPv61,211
AS6939Hurricane Electric LLCTransitIPv4943
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6327
AS12357VODAFONE ESPANA S.A.U.MobileIPv4202
AS59432GINERNET S.L.UnclassifiedIPv4118
AS24482SG.GSHostingIPv4 IPv6117
AS33891Core-Backbone GmbHHostingIPv4 IPv6117
AS37721Virtual Technologies & SolutionsResidentialIPv4105

Transit

Downstream networks

inferred

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

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 12

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

ASNetworkTypeFamiliesPaths seen
AS59908BalaLink S.A.UnclassifiedIPv4 IPv62,145
AS29119AIRE NETWORKS DEL MEDITERRANEO SL UNIPERSONALUnclassifiedIPv4 IPv61,515
AS8637SpainWISP, S.L.UnclassifiedIPv4 IPv61,211
AS6939Hurricane Electric LLCTransitIPv4943
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv6327
AS12357VODAFONE ESPANA S.A.U.MobileIPv4202
AS59432GINERNET S.L.UnclassifiedIPv4118
AS24482SG.GSHostingIPv4 IPv6117
AS33891Core-Backbone GmbHHostingIPv4 IPv6117
AS37721Virtual Technologies & SolutionsResidentialIPv4105

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-21 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.