Network · data from 2026-11-12
AS211056 KhalijServer Amir Hosein Maaref
Registry name: KhalijServer Amir Hosein Maaref, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS211056, 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.
| 94.184.14.0/24 | Invalid: origin | Other origin only | 39 6%low visibility |
| 94.184.8.0/24 | Invalid: origin | Other origin only | 35 5%low visibility |
| 185.201.49.0/24 | Valid | None | 671 100% |
| 85.133.249.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 85.133.193.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.47.197.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.47.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.47.201.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 92.114.50.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 89.47.202.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.81.16.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.81.17.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.81.18.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.81.19.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 89.47.198.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS211056 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 12 are in fix.csv.
- ROA: origin2
- Route object: none3
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 94.184.14.0/24 | ROAs covering it name AS6736, AS34837, AS211421, not AS211056. If AS211056 should announce it, add a ROA for AS211056. |
| Route object: none | 94.184.14.0/24 | Route objects for it name AS6736, AS211421. Add a route object with origin AS211056 in the RIR database for the space. |
| ROA: origin | 94.184.8.0/24 | ROAs covering it name AS6736, AS34837, AS216061, not AS211056. If AS211056 should announce it, add a ROA for AS211056. |
| Route object: none | 94.184.8.0/24 | Route objects for it name AS6736, AS216061. Add a route object with origin AS211056 in the RIR database for the space. |
| Route object: none | 185.201.49.0/24 | No route object for it. Add a route object with origin AS211056 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS211056 whose prefix no peer sees AS211056 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.81.16.0/23 | RIPE | No ROA |
| 94.184.15.0/24 | RIPE | Invalid: origin |
| 94.184.23.0/24 | RIPE | Invalid: origin |
| 2a01:5500:ffff::/48 | RIPE | Valid |
| 2a03:9381::/48 | RIPE | Valid |
| 2a03:9381:5::/48 | RIPE | Valid |
| 2a03:9381:6::/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.