Network · data from 2026-11-12

AS200370 FPCC-AS Farzanegan Pars Communications Company PJS

Registry name: FPCC-AS Farzanegan Pars Communications Company PJS, IR · not in PeeringDB

16IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 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

0Route objects not announced registered with origin AS200370, seen from no peer

Announced routes

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


95.142.231.0/24	Valid	RIR databaseRIPE	670 100%	67
95.142.232.0/24	Valid	RIR databaseRIPE	670 100%	67
95.142.238.0/24	Valid	RIR databaseRIPE	670 100%	67
95.142.239.0/24	Valid	RIR databaseRIPE	670 100%	67
193.56.59.0/24	Valid	RIR databaseRIPE	670 100%	67
193.56.61.0/24	Valid	RIR databaseRIPE	670 100%	67
193.56.107.0/24	Valid	RIR databaseRIPE	670 100%	67
193.56.118.0/24	Valid	RIR databaseRIPE	670 100%	67
194.60.208.0/24	Valid	RIR databaseRIPE	670 100%	67
194.60.209.0/24	Valid	RIR databaseRIPE	670 100%	67
194.60.210.0/24	Valid	RIR databaseRIPE	670 100%	67
194.60.211.0/24	Valid	RIR databaseRIPE	670 100%	67
45.8.160.0/24	Valid	RIR databaseRIPE	669 99%	67
45.8.161.0/24	Valid	RIR databaseRIPE	669 99%	67
45.8.162.0/24	Valid	RIR databaseRIPE	669 99%	67
45.8.163.0/24	Valid	RIR databaseRIPE	669 99%	67
2a05:cac0::/29	Valid	RIR databaseRIPE	633 100%	67
2a0f:51c0::/29	Valid	RIR databaseRIPE	633 100%	67
2a12:93c0::/29	Valid	RIR databaseRIPE	631 99%	67

AS-SET

AS200370 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS200370 is announced.

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.