bgpreport

Network · data from 2026-11-12

AS207251 Caspel

Registry name: caspel CASPEL LLC, AZ · PeeringDB

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

Announced routes

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

185.161.224.0/24 No ROA Nonecovered by 185.161.224.0/22 673 100% 66
185.161.225.0/24 No ROA Nonecovered by 185.161.224.0/22 673 100% 66
185.161.226.0/24 No ROA Nonecovered by 185.161.224.0/22 673 100% 66
185.161.227.0/24 No ROA Nonecovered by 185.161.224.0/22 673 100% 66
185.161.224.0/22 No ROA RIR databaseRIPE 673 100% 66
31.171.104.0/22 Valid RIR databaseRIPE 673 100% 66
85.132.32.0/22 Valid RIR databaseRIPE 673 100% 66
85.132.42.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.45.0/24 Valid RIR databaseRIPE 673 100% 66
109.235.194.0/23 Valid RIR databaseRIPE 673 100% 66
109.235.196.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS207251'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 17 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none185.161.224.0/24No ROA covers it. Add a ROA for AS207251, maxLength 24.673 of 673
Route object: none185.161.224.0/24No route object for it. A route object for 185.161.224.0/22 with origin AS207251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207251 in the RIR database for the space.673 of 673
ROA: none185.161.225.0/24No ROA covers it. Add a ROA for AS207251, maxLength 24.673 of 673
Route object: none185.161.225.0/24No route object for it. A route object for 185.161.224.0/22 with origin AS207251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207251 in the RIR database for the space.673 of 673
ROA: none185.161.226.0/24No ROA covers it. Add a ROA for AS207251, maxLength 24.673 of 673
Route object: none185.161.226.0/24No route object for it. A route object for 185.161.224.0/22 with origin AS207251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207251 in the RIR database for the space.673 of 673
ROA: none185.161.227.0/24No ROA covers it. Add a ROA for AS207251, maxLength 24.673 of 673
Route object: none185.161.227.0/24No route object for it. A route object for 185.161.224.0/22 with origin AS207251 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207251 in the RIR database for the space.673 of 673
ROA: none185.161.224.0/22No ROA covers it. Add a ROA for AS207251, maxLength 22.673 of 673

Route objects not announced

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

31.171.104.0/24RIPEInvalid: maxLength
31.171.105.0/24RIPEInvalid: maxLength
31.171.106.0/24RIPEInvalid: maxLength
31.171.107.0/24RIPEInvalid: maxLength
85.132.32.0/24RIPEInvalid: maxLength
85.132.33.0/24RIPEInvalid: maxLength
85.132.34.0/24RIPEInvalid: maxLength
85.132.35.0/24RIPEInvalid: maxLength

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.