Network · data from 2026-11-12
AS208502 DSC-AS Data Storage Center JSC
Registry name: DSC-AS Data Storage Center JSC, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208502, 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.
| 185.129.206.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.129.207.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a00:9720::/32 | No ROA | RIR databaseRIPE | 636 100% |
| 185.129.205.0/24 | No ROA | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS208502 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 7 are in fix.csv.
- ROA: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.129.206.0/24 | No ROA covers it. Add a ROA for AS208502, maxLength 24. |
| ROA: none | 185.129.207.0/24 | No ROA covers it. Add a ROA for AS208502, maxLength 24. |
| ROA: none | 2a00:9720::/32 | No ROA covers it. Add a ROA for AS208502, maxLength 32. |
| ROA: none | 185.129.205.0/24 | No ROA covers it. Add a ROA for AS208502, maxLength 24. |
Route objects not announced
Route objects with origin AS208502 whose prefix no peer sees AS208502 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 92.242.58.0/24 | RIPE | No ROA |
| 92.242.59.0/24 | RIPE | No ROA |
| 185.129.204.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.