Network · data from 2026-11-12
AS213861 Vostrik-AS Vostrikov Rodion
Registry name: Vostrik-AS Vostrikov Rodion, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213861, 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.
| 2a12:a340::/32 | No ROA | None | 2 0%low visibility |
| 2a12:a342::/32 | No ROA | None | 1 0%low visibility |
| 2a13:93c6::/32 | No ROA | None | 1 0%low visibility |
| 2a0f:c084::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 2a12:cc02::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 45.14.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.137.85.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 45.149.146.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 103.114.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.147.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.147.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.244.175.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.3.19.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 84.21.191.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 207.89.19.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a09:a503::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a0d:fcc4::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a12:3bc1::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a14:7b83::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a14:a406::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a14:a083::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS213861 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: none5
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a12:a340::/32 | No ROA covers it. Add a ROA for AS213861, maxLength 32. |
| Route object: none | 2a12:a340::/32 | No route object for it. Add a route object with origin AS213861 in the RIR database for the space. |
| ROA: none | 2a12:a342::/32 | No ROA covers it. Add a ROA for AS213861, maxLength 32. |
| Route object: none | 2a12:a342::/32 | No route object for it. Add a route object with origin AS213861 in the RIR database for the space. |
| ROA: none | 2a13:93c6::/32 | No ROA covers it. Add a ROA for AS213861, maxLength 32. |
| Route object: none | 2a13:93c6::/32 | No route object for it. Add a route object with origin AS213861 in the RIR database for the space. |
| ROA: none | 2a0f:c084::/32 | No ROA covers it. Add a ROA for AS213861, maxLength 32. |
| ROA: none | 2a12:cc02::/32 | No ROA covers it. Add a ROA for AS213861, maxLength 32. |
Route objects not announced
Route objects with origin AS213861 whose prefix no peer sees AS213861 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a14:a086::/32 | 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.