Network · data from 2026-11-12
AS9202 ZSSM-AS GYUSS PKF LTD
Registry name: ZSSM-AS GYUSS PKF LTD, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS9202, 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.
| 109.235.8.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 212.8.32.0/19 | No ROA | RIR databaseRIPE | 671 100% |
| 109.235.15.0/24 | No ROA | RIR databaseRIPE | 668 99% |
AS-SET
AS9202 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 9 are in fix.csv.
- ROA: none3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.235.8.0/21 | No ROA covers it. Add a ROA for AS9202, maxLength 21. |
| ROA: none | 212.8.32.0/19 | No ROA covers it. Add a ROA for AS9202, maxLength 19. |
| ROA: none | 109.235.15.0/24 | No ROA covers it. Add a ROA for AS9202, maxLength 24. |
Route objects not announced
Route objects with origin AS9202 whose prefix no peer sees AS9202 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.235.14.0/24 | RIPE | No ROA |
| 212.8.52.0/23 | RIPE | No ROA |
| 212.8.54.0/24 | RIPE | No ROA |
| 212.8.55.0/24 | RIPE | No ROA |
| 212.8.56.0/24 | RIPE | No ROA |
| 212.8.57.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.