Network · data from 2026-11-12
AS201250 ZT-LPT-AS OOO SET
Registry name: ZT-LPT-AS OOO SET, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS201250, 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.
| 91.190.64.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 213.59.132.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 213.59.155.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 213.59.158.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 217.107.196.0/22 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS201250 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 5 are in fix.csv.
- ROA: none5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.190.64.0/20 | No ROA covers it. Add a ROA for AS201250, maxLength 20. |
| ROA: none | 213.59.132.0/22 | No ROA covers it. Add a ROA for AS201250, maxLength 22. |
| ROA: none | 213.59.155.0/24 | No ROA covers it. Add a ROA for AS201250, maxLength 24. |
| ROA: none | 213.59.158.0/24 | No ROA covers it. Add a ROA for AS201250, maxLength 24. |
| ROA: none | 217.107.196.0/22 | No ROA covers it. Add a ROA for AS201250, maxLength 22. |
Route objects not announced
Every route object with origin AS201250 is announced.
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.