bgpreport

Network · data from 2026-11-12

AS43395 Pooya Parto Qeshm Cooperative

Registry name: Ertebatat-Doorbord-Fars Pooya Parto Qeshm Cooperative Company, IR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43395, 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.46.108.0/22 Invalid: origin None 80 12% 35
89.221.84.0/22 Invalid: origin Other origin only 2 0%low visibility 2
46.148.38.0/24 Valid RIR databaseRIPE 672 100% 66
46.148.43.0/24 Valid RIR databaseRIPE 672 100% 66
46.148.44.0/24 Valid RIR databaseRIPE 671 100% 66
164.138.203.0/24 Valid RIR databaseRIPE 671 100% 67
46.148.34.0/24 Valid RIR databaseRIPE 670 100% 66
46.148.35.0/24 Valid RIR databaseRIPE 670 100% 66
46.148.36.0/24 Valid RIR databaseRIPE 670 100% 66
46.148.40.0/24 Valid RIR databaseRIPE 670 100% 66
46.148.42.0/24 Valid RIR databaseRIPE 670 100% 66
46.148.45.0/24 Valid RIR databaseRIPE 670 100% 66
46.148.46.0/24 Valid RIR databaseRIPE 670 100% 66
46.148.47.0/24 Valid RIR databaseRIPE 670 100% 66
95.130.225.0/24 Valid RIR databaseRIPE 670 100% 66
176.101.40.0/21 Valid RIR databaseRIPE 670 100% 66
185.66.224.0/24 Valid RIR databaseRIPE 670 100% 66
185.66.225.0/24 Valid RIR databaseRIPE 670 100% 66
185.66.226.0/24 Valid RIR databaseRIPE 670 100% 66
185.110.219.0/24 Valid RIR databaseRIPE 670 100% 66
185.140.232.0/24 Valid RIR databaseRIPE 670 100% 66
185.140.233.0/24 Valid RIR databaseRIPE 670 100% 66
185.140.234.0/24 Valid RIR databaseRIPE 670 100% 66
185.140.235.0/24 Valid RIR databaseRIPE 670 100% 66
185.145.184.0/22 Valid RIR databaseRIPE 670 100% 66
185.186.48.0/24 Valid RIR databaseRIPE 670 100% 66
185.186.49.0/24 Valid RIR databaseRIPE 670 100% 66
185.186.50.0/24 Valid RIR databaseRIPE 670 100% 66
185.186.51.0/24 Valid RIR databaseRIPE 670 100% 66
194.33.104.0/24 Valid RIR databaseRIPE 670 100% 66
45.9.144.0/24 Valid RIR databaseRIPE 669 99% 66
45.9.145.0/24 Valid RIR databaseRIPE 669 99% 66
45.9.146.0/24 Valid RIR databaseRIPE 669 99% 66
45.9.147.0/24 Valid RIR databaseRIPE 669 99% 66
45.86.4.0/24 Valid RIR databaseRIPE 669 99% 66
45.86.5.0/24 Valid RIR databaseRIPE 669 99% 66
45.86.6.0/24 Valid RIR databaseRIPE 669 99% 66
45.86.7.0/24 Valid RIR databaseRIPE 669 99% 66
45.148.248.0/24 Valid RIR databaseRIPE 669 99% 66
45.148.249.0/24 Valid RIR databaseRIPE 669 99% 66
45.148.250.0/24 Valid RIR databaseRIPE 669 99% 66
45.148.251.0/24 Valid RIR databaseRIPE 669 99% 66
94.127.17.0/24 Valid RIR databaseRIPE 668 99% 67
185.166.3.0/24 Valid RIR databaseRIPE 668 99% 67
212.108.125.0/24 Valid RIR databaseRIPE 668 99% 67
2a05:7a80:fffd::/48 Valid RIR databaseRIPE 634 100% 68

AS-SET

AS43395'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 23 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
ROA: origin185.46.108.0/22ROAs covering it name AS62132, not AS43395. If AS43395 should announce it, add a ROA for AS43395.80 of 673
Route object: none185.46.108.0/22No route object for it. Add a route object with origin AS43395 in the RIR database for the space.80 of 673
ROA: origin89.221.84.0/22ROAs covering it name AS62442, not AS43395. If AS43395 should announce it, add a ROA for AS43395.2 of 673
Route object: none89.221.84.0/22Route objects for it name AS62442. Add a route object with origin AS43395 in the RIR database for the space.2 of 673

Route objects not announced

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

5.160.62.0/23RIPEInvalid: origin
5.160.63.0/24RIPEInvalid: origin
5.160.158.0/23RIPEInvalid: origin
46.143.224.0/20RIPEValid
46.148.44.0/23RIPENo ROA
77.237.92.0/24RIPEInvalid: origin
81.12.65.0/24RIPEInvalid: origin
81.12.90.0/23RIPEValid
176.101.40.0/24RIPEValid
176.101.41.0/24RIPEValid
176.101.42.0/24RIPEValid
176.101.43.0/24RIPEValid
176.101.44.0/24RIPEValid
176.101.45.0/24RIPEValid
176.101.46.0/24RIPEValid
176.101.47.0/24RIPEValid
185.110.218.0/24RIPEValid
2a09:2e00::/29RIPENo ROA
2a0a:2440::/32RIPENo 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.