bgpreport

Network · data from 2026-11-12

AS57910 Soluciones Corporativas IP (SCIP)

Registry name: SCIP-AS Soluciones Corporativas IP, SL, ES · PeeringDB

107IPv4 routes 99.1% RPKI valid · 100.0% with a route object
12IPv6 routes 100.0% RPKI valid · 16.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 10 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
16Route objects not announced registered with origin AS57910, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS57910, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.

195.93.208.0/24 No ROA RIR databaseRIPE 673 100% 66
2a02:2110:2::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:3::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:4::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:5::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:6::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:7::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:8::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:9::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a02:2110:a::/48 Valid Nonecovered by 2a02:2110::/32 635 100% 69
2a0c:7a04::/30 Valid Nonecovered by 2a0c:7a00::/29 634 100% 69
2a00:b5c0:fff1::/48 Valid Other IRR onlyRADB 633 100% 70
31.214.176.0/24 Valid RIR databaseRIPE 673 100% 66
31.214.177.0/24 Valid RIR databaseRIPE 673 100% 66
31.214.178.0/24 Valid RIR databaseRIPE 673 100% 66
31.214.179.0/24 Valid RIR databaseRIPE 673 100% 66
31.214.180.0/24 Valid RIR databaseRIPE 673 100% 66
31.214.181.0/24 Valid RIR databaseRIPE 673 100% 66
31.214.191.0/24 Valid RIR databaseRIPE 673 100% 66
37.152.88.0/24 Valid RIR databaseRIPE 673 100% 66
37.152.89.0/24 Valid RIR databaseRIPE 673 100% 66
37.152.91.0/24 Valid RIR databaseRIPE 673 100% 66
37.152.93.0/24 Valid RIR databaseRIPE 673 100% 66
82.198.48.0/20 Valid RIR databaseRIPE 673 100% 66
87.117.96.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
87.117.97.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
87.117.100.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.101.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.102.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.103.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.104.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.105.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.106.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.107.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.108.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.109.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.110.0/24 Valid RIR databaseRIPE 673 100% 66
87.117.111.0/24 Valid RIR databaseRIPE 673 100% 66
91.132.116.0/24 Valid RIR databaseRIPE 673 100% 66
91.132.117.0/24 Valid RIR databaseRIPE 673 100% 66
91.132.118.0/24 Valid RIR databaseRIPE 673 100% 66
91.132.119.0/24 Valid RIR databaseRIPE 673 100% 66
95.214.0.0/24 Valid RIR databaseRIPE 673 100% 66
95.214.1.0/24 Valid RIR databaseRIPE 673 100% 66
95.214.2.0/24 Valid RIR databaseRIPE 673 100% 66
95.214.3.0/24 Valid RIR databaseRIPE 673 100% 66
109.69.48.0/24 Valid RIR databaseRIPE 673 100% 66
109.69.50.0/24 Valid RIR databaseRIPE 673 100% 66
109.69.51.0/24 Valid RIR databaseRIPE 673 100% 66
109.69.52.0/24 Valid RIR databaseRIPE 673 100% 66
109.69.53.0/24 Valid RIR databaseRIPE 673 100% 66
109.69.54.0/24 Valid RIR databaseRIPE 673 100% 66
109.69.55.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.236.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.237.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.238.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.239.0/24 Valid RIR databaseRIPE 673 100% 66
185.161.14.0/24 Valid RIR databaseRIPE 673 100% 66
185.161.15.0/24 Valid RIR databaseRIPE 673 100% 66
185.226.236.0/24 Valid RIR databaseRIPE 673 100% 66
185.226.237.0/24 Valid RIR databaseRIPE 673 100% 66
185.226.238.0/24 Valid RIR databaseRIPE 673 100% 66
194.56.236.0/24 Valid RIR databaseRIPE 673 100% 66
194.56.237.0/24 Valid RIR databaseRIPE 673 100% 66
194.56.239.0/24 Valid RIR databaseRIPE 673 100% 66
194.127.158.0/24 Valid RIR databaseRIPE 673 100% 66
194.127.159.0/24 Valid RIR databaseRIPE 673 100% 66
194.127.162.0/24 Valid RIR databaseRIPE 673 100% 66
31.214.176.0/20 Valid RIR databaseRIPE 672 100% 67
37.10.73.0/24 Valid RIR databaseRIPE 672 100% 66
37.10.74.0/24 Valid RIR databaseRIPE 672 100% 66
37.10.75.0/24 Valid RIR databaseRIPE 672 100% 66
37.152.88.0/21 Valid RIR databaseRIPE 672 100% 67
45.149.228.0/24 Valid RIR databaseRIPE 672 100% 66
45.149.229.0/24 Valid RIR databaseRIPE 672 100% 66
45.149.230.0/24 Valid RIR databaseRIPE 672 100% 66
45.149.231.0/24 Valid RIR databaseRIPE 672 100% 66
46.18.72.0/24 Valid RIR databaseRIPE 672 100% 66
46.18.74.0/24 Valid RIR databaseRIPE 672 100% 66
46.18.75.0/24 Valid RIR databaseRIPE 672 100% 66
46.18.76.0/24 Valid RIR databaseRIPE 672 100% 66
46.18.77.0/24 Valid RIR databaseRIPE 672 100% 66
46.18.78.0/24 Valid RIR databaseRIPE 672 100% 66
46.18.79.0/24 Valid RIR databaseRIPE 672 100% 66
193.57.37.0/24 Valid RIR databaseRIPE 672 100% 66
31.214.182.0/24 Valid RIR databaseRIPE 671 100% 66
31.214.183.0/24 Valid RIR databaseRIPE 671 100% 66
31.214.184.0/24 Valid RIR databaseRIPE 671 100% 66
31.214.185.0/24 Valid RIR databaseRIPE 671 100% 66
31.214.187.0/24 Valid RIR databaseRIPE 671 100% 66
31.214.188.0/24 Valid RIR databaseRIPE 671 100% 66
31.214.189.0/24 Valid RIR databaseRIPE 671 100% 66
31.214.190.0/24 Valid RIR databaseRIPE 671 100% 66
37.152.90.0/24 Valid RIR databaseRIPE 671 100% 66
37.152.92.0/24 Valid RIR databaseRIPE 671 100% 66
37.152.94.0/24 Valid RIR databaseRIPE 671 100% 66
37.152.95.0/24 Valid RIR databaseRIPE 671 100% 66
62.81.173.0/24 Valid RIR databaseRIPE 671 100% 66
87.117.98.0/24 Valid RIR databaseRIPE 671 100% 66
87.117.99.0/24 Valid RIR databaseRIPE 671 100% 66
109.69.49.0/24 Valid RIR databaseRIPE 671 100% 66
185.161.12.0/24 Valid RIR databaseRIPE 671 100% 66
185.161.13.0/24 Valid RIR databaseRIPE 671 100% 66
185.226.239.0/24 Valid RIR databaseRIPE 671 100% 66
194.56.238.0/24 Valid RIR databaseRIPE 671 100% 66
194.127.163.0/24 Valid RIR databaseRIPE 671 100% 66
212.95.210.0/24 Valid RIR databaseRIPE 671 100% 66
213.201.70.0/24 Valid RIR databaseRIPE 671 100% 66
37.10.72.0/24 Valid RIR databaseRIPE 670 100% 66
37.10.76.0/24 Valid RIR databaseRIPE 670 100% 66
37.10.77.0/24 Valid RIR databaseRIPE 670 100% 66
37.10.78.0/24 Valid RIR databaseRIPE 670 100% 66
37.10.79.0/24 Valid RIR databaseRIPE 670 100% 66
46.18.73.0/24 Valid RIR databaseRIPE 670 100% 66
193.57.36.0/24 Valid RIR databaseRIPE 670 100% 66
193.57.38.0/24 Valid RIR databaseRIPE 670 100% 66
193.57.39.0/24 Valid RIR databaseRIPE 670 100% 66
31.214.186.0/24 Valid RIR databaseRIPE 668 99% 66
2a00:b5c0::/32 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS57910: AS-SCIP. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS57910 isn't in the set, or no route object for AS57910 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS57910 in itNot covered
AS-SCIP RIPE 11125 Yes 0

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 28 are in fix.csv.

  • ROA: none1
  • Route object: none10
  • Route object: RIR1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none195.93.208.0/24No ROA covers it. Add a ROA for AS57910, maxLength 24.673 of 673
Route object: none2a02:2110:2::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:3::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:4::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:5::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:6::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:7::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:8::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:9::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a02:2110:a::/48No route object for it. A route object for 2a02:2110::/32 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.635 of 636
Route object: none2a0c:7a04::/30No route object for it. A route object for 2a0c:7a00::/29 with origin AS57910 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57910 in the RIR database for the space.634 of 636
Route object: RIR2a00:b5c0:fff1::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

Route objects with origin AS57910 whose prefix no peer sees AS57910 announce. Many are kept on purpose (backup routes, space announced only in some places).

37.10.72.0/21RIPEValid
45.149.228.0/22RIPEValid
46.18.72.0/21RIPEValid
87.117.96.0/20RIPEValid
91.132.116.0/22RIPEValid
95.214.0.0/22RIPEValid
109.69.48.0/21RIPEValid
185.11.236.0/22RIPEValid
185.161.12.0/22RIPEValid
185.226.236.0/22RIPEValid
193.57.36.0/22RIPEValid
194.56.236.0/22RIPEValid
194.127.158.0/23RIPEValid
194.127.162.0/23RIPEValid
2a02:2110::/32RIPEValid
2a0c:7a00::/29RIPEValid

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.