Network · data from 2026-11-12
AS42393 SVYAZKONTRAKT-AS Svyaz-Kontrakt LLC
Registry name: SVYAZKONTRAKT-AS Svyaz-Kontrakt LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42393, 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.33.80.0/23 | No ROA | RIR databaseRIPE | 673 100% |
| 193.107.60.0/22 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS42393 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 4 are in fix.csv.
- ROA: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.33.80.0/23 | No ROA covers it. Add a ROA for AS42393, maxLength 23. |
| ROA: none | 193.107.60.0/22 | No ROA covers it. Add a ROA for AS42393, maxLength 22. |
Route objects not announced
Route objects with origin AS42393 whose prefix no peer sees AS42393 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.33.80.0/24 | RIPE | No ROA |
| 193.33.81.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.