Network · data from 2026-11-12
AS51464 IBANK2RU MITIGATOR CLOUD LLC
Registry name: IBANK2RU MITIGATOR CLOUD LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51464, 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.
| 109.232.252.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 109.232.253.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 109.232.254.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 109.232.255.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.6.47.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 109.232.248.0/21 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS51464 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 8 are in fix.csv.
- ROA: none6
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.232.252.0/24 | No ROA covers it. Add a ROA for AS51464, maxLength 24. |
| ROA: none | 109.232.253.0/24 | No ROA covers it. Add a ROA for AS51464, maxLength 24. |
| ROA: none | 109.232.254.0/24 | No ROA covers it. Add a ROA for AS51464, maxLength 24. |
| ROA: none | 109.232.255.0/24 | No ROA covers it. Add a ROA for AS51464, maxLength 24. |
| ROA: none | 185.6.47.0/24 | No ROA covers it. Add a ROA for AS51464, maxLength 24. |
| ROA: none | 109.232.248.0/21 | No ROA covers it. Add a ROA for AS51464, maxLength 21. |
Route objects not announced
Route objects with origin AS51464 whose prefix no peer sees AS51464 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.232.254.0/23 | RIPE | No ROA |
| 185.6.44.0/24 | 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.