Network · data from 2026-11-12
AS210346 phoenix Phoenix Technologies AG
Registry name: phoenix Phoenix Technologies AG, CH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210346, 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.
| 185.250.224.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 192.122.254.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.135.63.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.135.100.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.144.75.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a12:1740::/29 | No ROA | RIR databaseRIPE | 632 99% |
AS-SET
AS210346 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: none6
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.250.224.0/22 | No ROA covers it. Add a ROA for AS210346, maxLength 22. |
| ROA: none | 192.122.254.0/24 | No ROA covers it. Add a ROA for AS210346, maxLength 24. |
| ROA: none | 192.135.63.0/24 | No ROA covers it. Add a ROA for AS210346, maxLength 24. |
| ROA: none | 192.135.100.0/24 | No ROA covers it. Add a ROA for AS210346, maxLength 24. |
| ROA: none | 192.144.75.0/24 | No ROA covers it. Add a ROA for AS210346, maxLength 24. |
| ROA: none | 2a12:1740::/29 | No ROA covers it. Add a ROA for AS210346, maxLength 29. |
Route objects not announced
Route objects with origin AS210346 whose prefix no peer sees AS210346 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.193.20.0/22 | RIPE | No ROA |
| 178.250.24.0/21 | RIPE | No ROA |
| 2a05:51c0::/29 | 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.