Network · data from 2026-11-12
AS57531 REGIONINFOCOM-AS RegionInfoCom LLC
Registry name: REGIONINFOCOM-AS RegionInfoCom LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57531, 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.160.36.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.160.39.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 91.232.188.0/24 | No ROA | RIR databaseRIPE | 284 42% |
| 185.160.37.0/24 | No ROA | RIR databaseRIPE | 86 13% |
| 185.160.38.0/24 | No ROA | RIR databaseRIPE | 78 12% |
AS-SET
AS57531 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 6 are in fix.csv.
- ROA: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.160.36.0/24 | No ROA covers it. Add a ROA for AS57531, maxLength 24. |
| ROA: none | 185.160.39.0/24 | No ROA covers it. Add a ROA for AS57531, maxLength 24. |
| ROA: none | 91.232.188.0/24 | No ROA covers it. Add a ROA for AS57531, maxLength 24. |
| ROA: none | 185.160.37.0/24 | No ROA covers it. Add a ROA for AS57531, maxLength 24. |
| ROA: none | 185.160.38.0/24 | No ROA covers it. Add a ROA for AS57531, maxLength 24. |
Route objects not announced
Route objects with origin AS57531 whose prefix no peer sees AS57531 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.160.36.0/22 | 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.