bgpreport

Network · data from 2026-11-12

AS201167 Caspian Telecom

Registry name: castel-as Caspian Telecom LLC, AZ · PeeringDB

16IPv4 routes 75.0% RPKI valid · 75.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
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
1Route objects not announced registered with origin AS201167, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201167, 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.43.188.0/24 No ROA Nonecovered by 185.43.188.0/22 673 100% 66
185.43.189.0/24 No ROA Nonecovered by 185.43.188.0/22 673 100% 66
185.43.190.0/24 No ROA Nonecovered by 185.43.188.0/22 673 100% 66
185.43.191.0/24 No ROA Nonecovered by 185.43.188.0/22 673 100% 66
2a01:49e0::/32 No ROA RIR databaseRIPE 635 100% 70
62.212.235.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.8.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.9.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.10.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.11.0/24 Valid RIR databaseRIPE 673 100% 66
85.132.97.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.42.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.52.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.96.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.97.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.98.0/24 Valid RIR databaseRIPE 673 100% 66
94.20.99.0/24 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS201167'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 10 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.43.188.0/24No ROA covers it. Add a ROA for AS201167, maxLength 24.673 of 673
Route object: none185.43.188.0/24No route object for it. A route object for 185.43.188.0/22 with origin AS201167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201167 in the RIR database for the space.673 of 673
ROA: none185.43.189.0/24No ROA covers it. Add a ROA for AS201167, maxLength 24.673 of 673
Route object: none185.43.189.0/24No route object for it. A route object for 185.43.188.0/22 with origin AS201167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201167 in the RIR database for the space.673 of 673
ROA: none185.43.190.0/24No ROA covers it. Add a ROA for AS201167, maxLength 24.673 of 673
Route object: none185.43.190.0/24No route object for it. A route object for 185.43.188.0/22 with origin AS201167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201167 in the RIR database for the space.673 of 673
ROA: none185.43.191.0/24No ROA covers it. Add a ROA for AS201167, maxLength 24.673 of 673
Route object: none185.43.191.0/24No route object for it. A route object for 185.43.188.0/22 with origin AS201167 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201167 in the RIR database for the space.673 of 673
ROA: none2a01:49e0::/32No ROA covers it. Add a ROA for AS201167, maxLength 32.635 of 636

Route objects not announced

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

185.43.188.0/22RIPENo 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.