Network · data from 2026-11-12
AS57574 AGRIBANK-AS Agriculture Bank PJSC
Registry name: AGRIBANK-AS Agriculture Bank PJSC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57574, 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.
| 164.215.63.0/24 | No ROA | Nonecovered by 164.215.62.0/23 | 671 100% |
| 164.215.56.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 164.215.56.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 164.215.60.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 164.215.61.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS57574 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 9 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 164.215.63.0/24 | No ROA covers it. Add a ROA for AS57574, maxLength 24. |
| Route object: none | 164.215.63.0/24 | No route object for it. A route object for 164.215.62.0/23 with origin AS57574 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57574 in the RIR database for the space. |
| ROA: none | 164.215.56.0/21 | No ROA covers it. Add a ROA for AS57574, maxLength 21. |
Route objects not announced
Route objects with origin AS57574 whose prefix no peer sees AS57574 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 164.215.58.0/23 | RIPE | No ROA |
| 164.215.58.0/24 | RIPE | Valid |
| 164.215.59.0/24 | RIPE | Valid |
| 164.215.60.0/23 | RIPE | Valid |
| 164.215.62.0/23 | RIPE | No ROA |
| 2a06:9d80::/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.