bgpreport

Network · data from 2026-11-12

AS212714 CANALPOZUELOASN Canal Pozuelo S.L.

Registry name: CANALPOZUELOASN Canal Pozuelo S.L., ES · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS212714, 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.

45.11.64.0/24 Invalid: origin Nonecovered by 45.11.64.0/22 83 12% 40
45.11.65.0/24 Invalid: origin Nonecovered by 45.11.64.0/22 83 12% 40
45.11.66.0/23 Invalid: origin Nonecovered by 45.11.64.0/22 83 12% 40
185.152.172.0/22 Valid RIR databaseRIPE 673 100% 67
2a11:180::/29 Valid RIR databaseRIPE 631 99% 67

AS-SET

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

  • ROA: origin3
  • Route object: none3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin45.11.64.0/24ROAs covering it name AS29119, not AS212714. If AS212714 should announce it, add a ROA for AS212714.83 of 673
Route object: none45.11.64.0/24No route object for it. A route object for 45.11.64.0/22 with origin AS212714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212714 in the RIR database for the space.83 of 673
ROA: origin45.11.65.0/24ROAs covering it name AS29119, not AS212714. If AS212714 should announce it, add a ROA for AS212714.83 of 673
Route object: none45.11.65.0/24No route object for it. A route object for 45.11.64.0/22 with origin AS212714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212714 in the RIR database for the space.83 of 673
ROA: origin45.11.66.0/23ROAs covering it name AS29119, not AS212714. If AS212714 should announce it, add a ROA for AS212714.83 of 673
Route object: none45.11.66.0/23No route object for it. A route object for 45.11.64.0/22 with origin AS212714 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212714 in the RIR database for the space.83 of 673

Route objects not announced

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

45.11.64.0/22RIPEInvalid: origin

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.