Network · data from 2026-11-12
AS50919 INTERWORKS
Registry name: INTERWORKS-AS INTERWORKS Single Member S.A., GR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50919, 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.
| 154.57.22.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 2a00:1f68::/32 | Valid | None | 633 100% |
| 82.29.50.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 89.116.175.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 178.23.72.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 188.164.200.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 194.62.224.0/22 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS50919's PeeringDB record names no 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 3 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 154.57.22.0/23 | No ROA covers it. Add a ROA for AS50919, maxLength 23. |
| Route object: RIR | 154.57.22.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: none | 2a00:1f68::/32 | No route object for it. Add a route object with origin AS50919 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS50919 is announced.
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.