Network · data from 2026-11-12
AS51112 OSS-LTD-AS OSS Ltd
Registry name: OSS-LTD-AS OSS Ltd, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51112, 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.
| 178.217.76.0/24 | Valid | Nonecovered by 178.217.72.0/21 | 673 100% |
| 178.217.72.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 178.217.74.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS51112 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 178.217.76.0/24 | No route object for it. A route object for 178.217.72.0/21 with origin AS51112 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51112 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51112 whose prefix no peer sees AS51112 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 178.217.78.0/24 | RIPE | Valid |
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.