Network · data from 2026-11-12
AS9147 JN-AS Homaye Jahan Nama Co. ( Private Joint Stock)
Registry name: JN-AS Homaye Jahan Nama Co. ( Private Joint Stock), IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9147, 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.176.56.0/24 | Valid | Other origin only | 671 100% |
| 185.176.57.0/24 | Valid | Other origin only | 671 100% |
| 185.176.58.0/24 | Valid | Other origin only | 671 100% |
| 185.176.59.0/24 | Valid | Other origin only | 671 100% |
| 185.176.56.0/22 | Valid | Other origin only | 670 100% |
| 212.86.64.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 212.86.67.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.70.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.72.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.73.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.74.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.80.0/20 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.87.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.88.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.91.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.92.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.94.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.95.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 212.86.64.0/19 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.64.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.65.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.66.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.68.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.69.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.71.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.75.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.76.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.77.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.78.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.79.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.80.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.81.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.82.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.83.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.84.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.85.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.86.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.89.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.90.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 212.86.93.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS9147 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 5 are in fix.csv.
- Route object: none5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.176.56.0/24 | Route objects for it name AS206635. Add a route object with origin AS9147 in the RIR database for the space. |
| Route object: none | 185.176.57.0/24 | Route objects for it name AS206635. Add a route object with origin AS9147 in the RIR database for the space. |
| Route object: none | 185.176.58.0/24 | Route objects for it name AS206635. Add a route object with origin AS9147 in the RIR database for the space. |
| Route object: none | 185.176.59.0/24 | Route objects for it name AS206635. Add a route object with origin AS9147 in the RIR database for the space. |
| Route object: none | 185.176.56.0/22 | Route objects for it name AS206635. Add a route object with origin AS9147 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS9147 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.