bgpreport

Network · data from 2026-11-12

AS60508 PinosPuente-AS T.V.C. PINOS PUENTE SL

Registry name: PinosPuente-AS T.V.C. PINOS PUENTE SL, ES · not in PeeringDB

11IPv4 routes 81.8% RPKI valid · 81.8% with a route object
0IPv6 routes
2RPKI invalid 0 origin · 2 maxLength
0No ROA 2 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS60508, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS60508, 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.
93.90.78.0/24 Invalid: maxLength RIR databaseRIPE 14 2%low visibility 15
93.90.79.0/24 Invalid: maxLength RIR databaseRIPE 14 2%low visibility 15
93.90.76.0/24 Valid Nonecovered by 93.90.76.0/23 669 99% 67
93.90.77.0/24 Valid Nonecovered by 93.90.76.0/23 669 99% 67
84.236.183.0/24 Valid RIR databaseRIPE 671 100% 67
84.236.207.0/24 Valid RIR databaseRIPE 671 100% 67
88.148.102.0/24 Valid RIR databaseRIPE 671 100% 67
89.45.242.0/24 Valid RIR databaseRIPE 671 100% 67
93.90.76.0/22 Valid RIR databaseRIPE 671 100% 67
176.227.153.0/24 Valid RIR databaseRIPE 671 100% 67
178.156.25.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS60508 isn't in PeeringDB, where networks name their AS-SET.

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 6 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength93.90.78.0/24ROA 93.90.76.0/22 AS60508 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 93.90.78.0/24.14 of 673
ROA: maxLength93.90.79.0/24ROA 93.90.76.0/22 AS60508 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 93.90.79.0/24.14 of 673
Route object: none93.90.76.0/24No route object for it. A route object for 93.90.76.0/23 with origin AS60508 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60508 in the RIR database for the space.669 of 673
Route object: none93.90.77.0/24No route object for it. A route object for 93.90.76.0/23 with origin AS60508 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60508 in the RIR database for the space.669 of 673

Route objects not announced

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

93.90.76.0/23RIPEInvalid: maxLength
212.163.60.0/22RIPEValid

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.