Network · data from 2026-11-12
AS48983 LETZI Artmotion AG
Registry name: LETZI Artmotion AG, CH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48983, 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.50.224.0/24 | Invalid: origin | RIR databaseRIPE | 81 12% |
| 185.50.224.0/22 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS48983 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 6 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.50.224.0/24 | ROAs covering it name AS24951, not AS48983. If AS48983 should announce it, add a ROA for AS48983. |
| ROA: none | 185.50.224.0/22 | No ROA covers it. Add a ROA for AS48983, maxLength 22. |
Route objects not announced
Route objects with origin AS48983 whose prefix no peer sees AS48983 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.198.6.0/24 | RIPE | No ROA |
| 185.50.225.0/24 | RIPE | Invalid: origin |
| 185.50.226.0/24 | RIPE | Invalid: origin |
| 185.50.227.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.