Network · data from 2026-11-12
AS48359 Hesabgar Pardaz Gharb
Registry name: Hesabgar-AS Hesabgar Pardaz Gharb PJSC, IR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48359, 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.
| 2a04:acc4::/30 | No ROA | Nonecovered by 2a04:acc0::/29 | 634 100% |
| 91.213.172.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.47.48.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.47.49.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.47.50.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.47.51.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.82.64.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.82.65.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.82.66.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.82.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.121.56.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.121.57.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.121.58.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.121.59.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.125.20.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.125.21.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.125.22.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.125.23.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.137.60.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.137.61.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.137.62.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.137.63.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.92.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.93.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.94.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.95.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.124.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.125.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.126.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.142.127.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.212.192.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.212.193.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.212.195.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.221.192.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.221.194.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.221.195.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.238.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.238.45.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.238.46.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.238.47.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.246.174.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.246.175.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.246.200.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 193.246.201.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.8.112.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.8.114.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.191.22.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.191.23.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.191.44.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.191.45.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.230.97.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.155.192.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.155.193.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.155.194.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.155.195.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS48359'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 19 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a04:acc4::/30 | No ROA covers it. Add a ROA for AS48359, maxLength 30. |
| Route object: none | 2a04:acc4::/30 | No route object for it. A route object for 2a04:acc0::/29 with origin AS48359 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48359 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48359 whose prefix no peer sees AS48359 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.232.5.0/24 | RIPE | Valid |
| 185.47.50.0/23 | RIPE | Valid |
| 185.126.41.0/24 | RIPE | Invalid: origin |
| 185.126.42.0/23 | RIPE | Valid |
| 185.129.184.0/22 | RIPE | Invalid: origin |
| 185.129.184.0/24 | RIPE | Valid |
| 185.129.185.0/24 | RIPE | Valid |
| 185.129.186.0/24 | RIPE | Valid |
| 185.129.187.0/24 | RIPE | Valid |
| 185.129.198.0/24 | RIPE | Valid |
| 185.129.201.0/24 | RIPE | Valid |
| 185.129.228.0/23 | RIPE | Invalid: origin |
| 185.129.228.0/24 | RIPE | Valid |
| 185.129.229.0/24 | RIPE | Valid |
| 185.169.38.0/24 | RIPE | Invalid: origin |
| 185.169.39.0/24 | RIPE | Invalid: origin |
| 2a04:acc0::/29 | 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.