Network · data from 2026-11-12
AS214922 FanAvaran_Mihan_Mizban FanAvaran Mihan Mizban PJSC
Registry name: FanAvaran_Mihan_Mizban FanAvaran Mihan Mizban PJSC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS214922, 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.
| 5.160.226.0/24 | Valid | None | 670 100% |
| 87.236.208.0/24 | Valid | None | 2 0%low visibility |
| 5.160.131.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 62.60.163.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.184.23.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 62.60.184.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.60.193.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.60.195.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.60.221.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.60.222.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 62.60.223.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.104.95.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.81.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.82.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 87.107.83.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 94.184.6.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 94.184.11.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 94.184.12.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.14.160.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 5.160.77.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 5.160.252.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.237.90.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.12.54.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 81.12.56.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 85.133.202.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 62.60.188.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 2a03:9381:b::/48 | Valid | RIR databaseRIPE | 634 100% |
| 2a03:9381:c::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS214922 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 3 are in fix.csv.
- Route object: none2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.160.226.0/24 | No route object for it. Add a route object with origin AS214922 in the RIR database for the space. |
| Route object: none | 87.236.208.0/24 | No route object for it. Add a route object with origin AS214922 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS214922 whose prefix no peer sees AS214922 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a03:9381:a::/48 | RIPE | Valid |
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.