bgpreport

Network · data from 2026-11-12

AS201540 PJCO Pishgaman Toseeh Fanavari Etelaat Va Ertebatat Jonoub (Joint Stock Company)

Registry name: PJCO Pishgaman Toseeh Fanavari Etelaat Va Ertebatat Jonoub (Joint Stock Company), IR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS201540, 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.71.192.0/23 Valid RIR databaseRIPE 671 100% 67
185.71.194.0/23 Valid RIR databaseRIPE 671 100% 67
185.109.60.0/24 Valid RIR databaseRIPE 671 100% 66
185.109.61.0/24 Valid RIR databaseRIPE 671 100% 66
185.109.62.0/23 Valid RIR databaseRIPE 671 100% 67
185.109.72.0/24 Valid RIR databaseRIPE 671 100% 67
185.109.73.0/24 Valid RIR databaseRIPE 671 100% 67
185.109.74.0/24 Valid RIR databaseRIPE 671 100% 67
185.109.75.0/24 Valid RIR databaseRIPE 671 100% 67
185.111.8.0/22 Valid RIR databaseRIPE 671 100% 67
185.111.12.0/22 Valid RIR databaseRIPE 671 100% 67
185.111.64.0/23 Valid RIR databaseRIPE 671 100% 67
185.111.136.0/22 Valid RIR databaseRIPE 671 100% 67
185.112.168.0/22 Valid RIR databaseRIPE 671 100% 67
185.120.192.0/22 Valid RIR databaseRIPE 671 100% 66
185.120.196.0/22 Valid RIR databaseRIPE 671 100% 67
185.120.200.0/24 Valid RIR databaseRIPE 671 100% 67
185.120.201.0/24 Valid RIR databaseRIPE 671 100% 67
185.120.202.0/24 Valid RIR databaseRIPE 671 100% 67
185.120.203.0/24 Valid RIR databaseRIPE 671 100% 67
185.120.208.0/22 Valid RIR databaseRIPE 671 100% 67
185.120.216.0/22 Valid RIR databaseRIPE 671 100% 67
185.120.224.0/22 Valid RIR databaseRIPE 671 100% 67
185.120.232.0/22 Valid RIR databaseRIPE 671 100% 67
185.120.240.0/22 Valid RIR databaseRIPE 671 100% 67
185.109.80.0/23 Valid RIR databaseRIPE 670 100% 66
185.109.82.0/23 Valid RIR databaseRIPE 670 100% 66
2a03:3b60::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

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

  • Route object: not announced56

Route objects not announced

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

185.71.192.0/24RIPEInvalid: maxLength
185.71.193.0/24RIPEValid
185.71.194.0/24RIPEInvalid: maxLength
185.71.195.0/24RIPEValid
185.109.62.0/24RIPEInvalid: maxLength
185.109.63.0/24RIPEInvalid: maxLength
185.109.80.0/24RIPEInvalid: maxLength
185.109.81.0/24RIPEInvalid: maxLength
185.109.82.0/24RIPEInvalid: maxLength
185.109.83.0/24RIPEInvalid: maxLength
185.111.8.0/24RIPEInvalid: maxLength
185.111.9.0/24RIPEInvalid: maxLength
185.111.10.0/24RIPEInvalid: maxLength
185.111.11.0/24RIPEInvalid: maxLength
185.111.12.0/24RIPEInvalid: maxLength
185.111.13.0/24RIPEInvalid: maxLength
185.111.14.0/24RIPEInvalid: maxLength
185.111.15.0/24RIPEInvalid: maxLength
185.111.64.0/24RIPEInvalid: maxLength
185.111.65.0/24RIPEInvalid: maxLength
185.111.136.0/24RIPEInvalid: maxLength
185.111.137.0/24RIPEInvalid: maxLength
185.111.138.0/24RIPEInvalid: maxLength
185.111.139.0/24RIPEInvalid: maxLength
185.112.168.0/24RIPEInvalid: maxLength
185.112.169.0/24RIPEInvalid: maxLength
185.112.170.0/24RIPEInvalid: maxLength
185.112.171.0/24RIPEInvalid: maxLength
185.120.192.0/24RIPEInvalid: maxLength
185.120.193.0/24RIPEInvalid: maxLength
185.120.194.0/24RIPEInvalid: maxLength
185.120.195.0/24RIPEInvalid: maxLength
185.120.196.0/24RIPEInvalid: maxLength
185.120.197.0/24RIPEInvalid: maxLength
185.120.198.0/24RIPEInvalid: maxLength
185.120.199.0/24RIPEInvalid: maxLength
185.120.208.0/24RIPEInvalid: maxLength
185.120.209.0/24RIPEInvalid: maxLength
185.120.210.0/24RIPEInvalid: maxLength
185.120.211.0/24RIPEInvalid: maxLength
185.120.216.0/24RIPEInvalid: maxLength
185.120.217.0/24RIPEInvalid: maxLength
185.120.218.0/24RIPEInvalid: maxLength
185.120.219.0/24RIPEInvalid: maxLength
185.120.224.0/24RIPEInvalid: maxLength
185.120.225.0/24RIPEInvalid: maxLength
185.120.226.0/24RIPEInvalid: maxLength
185.120.227.0/24RIPEInvalid: maxLength
185.120.232.0/24RIPEInvalid: maxLength
185.120.233.0/24RIPEInvalid: maxLength
185.120.234.0/24RIPEInvalid: maxLength
185.120.235.0/24RIPEInvalid: maxLength
185.120.240.0/24RIPEInvalid: maxLength
185.120.241.0/24RIPEInvalid: maxLength
185.120.242.0/24RIPEInvalid: maxLength
185.120.243.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.