Network · data from 2026-11-12
AS50656 Optix-Software-ASN Optix Software Ltd
Registry name: Optix-Software-ASN Optix Software Ltd, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50656, 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.
| 77.73.169.0/24 | Valid | Other origin onlycovered by 77.73.168.0/21 | 672 100% |
| 77.73.168.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS50656 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 4 are in fix.csv.
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 77.73.169.0/24 | Route objects for it name AS34555. A route object for 77.73.168.0/21 with origin AS50656 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50656 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50656 whose prefix no peer sees AS50656 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.73.168.0/21 | RIPE | No ROA |
| 77.73.173.0/24 | RIPE | No ROA |
| 77.73.174.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.