Network · data from 2026-11-12
AS197628 SUDAK-NET Sudak-Net LLC
Registry name: SUDAK-NET Sudak-Net LLC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197628, 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.
| 2.59.76.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 45.11.4.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 45.149.40.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 91.224.168.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 91.225.228.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 146.19.115.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 193.168.188.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 195.191.246.0/23 | No ROA | RIR databaseRIPE | 672 100% |
| 185.92.144.0/22 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS197628 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 8 are in fix.csv.
- ROA: none8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2.59.76.0/22 | No ROA covers it. Add a ROA for AS197628, maxLength 22. |
| ROA: none | 45.11.4.0/22 | No ROA covers it. Add a ROA for AS197628, maxLength 22. |
| ROA: none | 45.149.40.0/22 | No ROA covers it. Add a ROA for AS197628, maxLength 22. |
| ROA: none | 91.224.168.0/23 | No ROA covers it. Add a ROA for AS197628, maxLength 23. |
| ROA: none | 91.225.228.0/22 | No ROA covers it. Add a ROA for AS197628, maxLength 22. |
| ROA: none | 146.19.115.0/24 | No ROA covers it. Add a ROA for AS197628, maxLength 24. |
| ROA: none | 193.168.188.0/22 | No ROA covers it. Add a ROA for AS197628, maxLength 22. |
| ROA: none | 195.191.246.0/23 | No ROA covers it. Add a ROA for AS197628, maxLength 23. |
Route objects not announced
Every route object with origin AS197628 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.