bgpreport

Network · data from 2026-11-12

AS1070 AS-PRP-001 - Peel Regional Police

Registry name: AS-PRP-001 - Peel Regional Police, CA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS1070, 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.
204.138.80.0/24 No ROA Nonecovered by 204.138.80.0/21 671 100% 68
204.138.84.0/24 No ROA Other origin onlycovered by 204.138.80.0/21 671 100% 68
204.138.85.0/24 No ROA Other origin onlycovered by 204.138.80.0/21 671 100% 68
204.138.86.0/24 No ROA Other origin onlycovered by 204.138.80.0/21 671 100% 68
204.138.87.0/24 No ROA Other origin onlycovered by 204.138.80.0/21 671 100% 68

AS-SET

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

  • ROA: none5
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none204.138.80.0/24No ROA covers it. Add a ROA for AS1070, maxLength 24.671 of 673
Route object: none204.138.80.0/24No route object for it. A route object for 204.138.80.0/21 with origin AS1070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1070 in the RIR database for the space.671 of 673
ROA: none204.138.84.0/24No ROA covers it. Add a ROA for AS1070, maxLength 24.671 of 673
Route object: none204.138.84.0/24Route objects for it name AS812, AS26788. A route object for 204.138.80.0/21 with origin AS1070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1070 in the RIR database for the space.671 of 673
ROA: none204.138.85.0/24No ROA covers it. Add a ROA for AS1070, maxLength 24.671 of 673
Route object: none204.138.85.0/24Route objects for it name AS812, AS26788. A route object for 204.138.80.0/21 with origin AS1070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1070 in the RIR database for the space.671 of 673
ROA: none204.138.86.0/24No ROA covers it. Add a ROA for AS1070, maxLength 24.671 of 673
Route object: none204.138.86.0/24Route objects for it name AS812. A route object for 204.138.80.0/21 with origin AS1070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1070 in the RIR database for the space.671 of 673
ROA: none204.138.87.0/24No ROA covers it. Add a ROA for AS1070, maxLength 24.671 of 673
Route object: none204.138.87.0/24Route objects for it name AS812. A route object for 204.138.80.0/21 with origin AS1070 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1070 in the RIR database for the space.671 of 673

Route objects not announced

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

204.138.80.0/21ARINNo 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.