Network · data from 2026-11-12
AS38928 GLONASS JSC GLONASS
Registry name: GLONASS JSC GLONASS, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS38928, 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.
| 193.232.47.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 62.76.137.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 62.76.138.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.232.77.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS38928 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: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.232.47.0/24 | No ROA covers it. Add a ROA for AS38928, maxLength 24. |
| ROA: none | 62.76.137.0/24 | No ROA covers it. Add a ROA for AS38928, maxLength 24. |
| ROA: none | 62.76.138.0/24 | No ROA covers it. Add a ROA for AS38928, maxLength 24. |
| ROA: none | 193.232.77.0/24 | No ROA covers it. Add a ROA for AS38928, maxLength 24. |
Route objects not announced
Route objects with origin AS38928 whose prefix no peer sees AS38928 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.192.84.0/22 | RIPE | No ROA |
| 212.192.152.0/23 | 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.