Network · data from 2026-11-12
AS202999 VTEL-AS Vostok Telecom LLC
Registry name: VTEL-AS Vostok Telecom LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202999, 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.
| 193.233.57.0/24 | Valid | None | 2 0%low visibility |
| 193.233.9.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.233.56.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.233.58.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.233.59.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS202999 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.
- Route object: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 193.233.57.0/24 | No route object for it. Add a route object with origin AS202999 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202999 whose prefix no peer sees AS202999 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.233.57.0/27 | RIPE | Valid |
| 193.233.57.32/27 | RIPE | Valid |
| 193.233.57.64/27 | RIPE | Valid |
| 193.233.57.96/27 | RIPE | Valid |
| 193.233.57.128/27 | RIPE | Valid |
| 193.233.57.160/27 | RIPE | Valid |
| 193.233.57.192/27 | RIPE | Valid |
| 193.233.57.224/27 | 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.