bgpreport

Network · data from 2026-11-12

AS9165 Prosodie Iberica

Registry name: PROSODIEIBERICA-AS PROSODIE IBERICA SL, ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS9165, 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.
62.97.128.0/19 No ROA None 671 100% 67
62.97.136.0/21 No ROA None 671 100% 67
62.97.128.0/21 Valid RIR databaseRIPE 669 99% 67
62.97.144.0/21 Valid RIR databaseRIPE 669 99% 67
212.101.64.0/19 Valid RIR databaseRIPE 669 99% 67

AS-SET

AS9165's PeeringDB record names no 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 8 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none62.97.128.0/19No ROA covers it. Add a ROA for AS9165, maxLength 19.671 of 673
Route object: none62.97.128.0/19No route object for it. Add a route object with origin AS9165 in the RIR database for the space.671 of 673
ROA: none62.97.136.0/21No ROA covers it. Add a ROA for AS9165, maxLength 21.671 of 673
Route object: none62.97.136.0/21No route object for it. Add a route object with origin AS9165 in the RIR database for the space.671 of 673

Route objects not announced

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

62.97.136.0/23RIPENo ROA
62.97.138.0/23RIPENo ROA
62.97.142.0/23RIPENo ROA
62.97.152.0/21RIPENo ROA

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.