Network · data from 2026-11-12
AS43395 Pooya Parto Qeshm Cooperative
Registry name: Ertebatat-Doorbord-Fars Pooya Parto Qeshm Cooperative Company, IR · PeeringDB
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% |
| 89.221.84.0/22 | Invalid: origin | Other origin only | 2 0%low visibility |
| 46.148.38.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.148.43.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 46.148.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 164.138.203.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 46.148.34.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.148.35.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.148.36.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.148.40.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.148.42.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.148.45.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.148.46.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 46.148.47.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 95.130.225.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 176.101.40.0/21 | Valid | RIR databaseRIPE | 670 100% |
| 185.66.224.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.66.225.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.66.226.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.110.219.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.140.232.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.140.233.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.140.234.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.140.235.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.145.184.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 185.186.48.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.186.49.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.186.50.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.186.51.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 194.33.104.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.9.144.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.9.145.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.9.146.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.9.147.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.86.4.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.86.5.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.86.6.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.86.7.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.148.248.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.148.249.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.148.250.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.148.251.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 94.127.17.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 185.166.3.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 212.108.125.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a05:7a80:fffd::/48 | Valid | RIR databaseRIPE | 634 100% |
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
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.46.108.0/22 | ROAs covering it name AS62132, not AS43395. If AS43395 should announce it, add a ROA for AS43395. |
| Route object: none | 185.46.108.0/22 | No route object for it. Add a route object with origin AS43395 in the RIR database for the space. |
| ROA: origin | 89.221.84.0/22 | ROAs covering it name AS62442, not AS43395. If AS43395 should announce it, add a ROA for AS43395. |
| Route object: none | 89.221.84.0/22 | Route objects for it name AS62442. Add a route object with origin AS43395 in the RIR database for the space. |
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/23 | RIPE | Invalid: origin |
| 5.160.63.0/24 | RIPE | Invalid: origin |
| 5.160.158.0/23 | RIPE | Invalid: origin |
| 46.143.224.0/20 | RIPE | Valid |
| 46.148.44.0/23 | RIPE | No ROA |
| 77.237.92.0/24 | RIPE | Invalid: origin |
| 81.12.65.0/24 | RIPE | Invalid: origin |
| 81.12.90.0/23 | RIPE | Valid |
| 176.101.40.0/24 | RIPE | Valid |
| 176.101.41.0/24 | RIPE | Valid |
| 176.101.42.0/24 | RIPE | Valid |
| 176.101.43.0/24 | RIPE | Valid |
| 176.101.44.0/24 | RIPE | Valid |
| 176.101.45.0/24 | RIPE | Valid |
| 176.101.46.0/24 | RIPE | Valid |
| 176.101.47.0/24 | RIPE | Valid |
| 185.110.218.0/24 | RIPE | Valid |
| 2a09:2e00::/29 | RIPE | No ROA |
| 2a0a:2440::/32 | RIPE | No 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.