Network · data from 2026-11-12
AS216363 Istra.net
Registry name: istra-dot-net-as OOO Istra.net, RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216363, 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.94.182.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 2a13:c9c0::/32 | No ROA | RIR databaseRIPE | 635 100% |
| 212.59.104.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 212.59.104.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 212.59.106.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 212.59.110.0/23 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS216363'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 8 are in fix.csv.
- ROA: none2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.94.182.0/24 | No ROA covers it. Add a ROA for AS216363, maxLength 24. |
| ROA: none | 2a13:c9c0::/32 | No ROA covers it. Add a ROA for AS216363, maxLength 32. |
Route objects not announced
Route objects with origin AS216363 whose prefix no peer sees AS216363 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.59.104.0/24 | RIPE | Invalid: maxLength |
| 212.59.105.0/24 | RIPE | Invalid: maxLength |
| 212.59.106.0/24 | RIPE | Valid |
| 212.59.107.0/24 | RIPE | Valid |
| 212.59.110.0/24 | RIPE | Valid |
| 212.59.111.0/24 | 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.