Network · data from 2026-11-12
AS212264 ZOLOTAYA-KORONA Closed joint stock company "ZOLOTAYA KORONA"
Registry name: ZOLOTAYA-KORONA Closed joint stock company "ZOLOTAYA KORONA", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS212264, 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.
| 195.208.103.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 193.232.20.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.232.94.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.85.18.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.190.85.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.226.243.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 194.85.113.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 195.208.110.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS212264 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 6 are in fix.csv.
- ROA: none6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.208.103.0/24 | No ROA covers it. Add a ROA for AS212264, maxLength 24. |
| ROA: none | 193.232.20.0/24 | No ROA covers it. Add a ROA for AS212264, maxLength 24. |
| ROA: none | 193.232.94.0/24 | No ROA covers it. Add a ROA for AS212264, maxLength 24. |
| ROA: none | 194.85.18.0/24 | No ROA covers it. Add a ROA for AS212264, maxLength 24. |
| ROA: none | 194.190.85.0/24 | No ROA covers it. Add a ROA for AS212264, maxLength 24. |
| ROA: none | 194.226.243.0/24 | No ROA covers it. Add a ROA for AS212264, maxLength 24. |
Route objects not announced
Every route object with origin AS212264 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.