Network · data from 2026-11-12
AS200982 ZT-TOMSK-AS OOO SET
Registry name: ZT-TOMSK-AS OOO SET, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS200982, 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.
| 81.177.196.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 213.59.136.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 213.59.138.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 213.59.139.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 213.59.156.0/23 | No ROA | RIR databaseRIPE | 671 100% |
| 81.20.205.0/24 | No ROA | RIR databaseRIPE | 670 100% |
AS-SET
AS200982 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: none6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 81.177.196.0/23 | No ROA covers it. Add a ROA for AS200982, maxLength 23. |
| ROA: none | 213.59.136.0/22 | No ROA covers it. Add a ROA for AS200982, maxLength 22. |
| ROA: none | 213.59.138.0/24 | No ROA covers it. Add a ROA for AS200982, maxLength 24. |
| ROA: none | 213.59.139.0/24 | No ROA covers it. Add a ROA for AS200982, maxLength 24. |
| ROA: none | 213.59.156.0/23 | No ROA covers it. Add a ROA for AS200982, maxLength 23. |
| ROA: none | 81.20.205.0/24 | No ROA covers it. Add a ROA for AS200982, maxLength 24. |
Route objects not announced
Route objects with origin AS200982 whose prefix no peer sees AS200982 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 213.59.136.0/23 | RIPE | No ROA |
| 213.59.185.0/24 | RIPE | No ROA |
| 2a03:aa00:1003::/48 | 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.