Network · data from 2026-11-12
AS203849 UMICORE Umicore NV
Registry name: UMICORE Umicore NV, BE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203849, 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.120.164.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.120.165.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.120.167.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 185.120.166.0/24 | No ROA | RIR databaseRADB, RIPE | 672 100% |
AS-SET
AS203849 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 7 are in fix.csv.
- ROA: none4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.120.164.0/24 | No ROA covers it. Add a ROA for AS203849, maxLength 24. |
| ROA: none | 185.120.165.0/24 | No ROA covers it. Add a ROA for AS203849, maxLength 24. |
| ROA: none | 185.120.167.0/24 | No ROA covers it. Add a ROA for AS203849, maxLength 24. |
| ROA: none | 185.120.166.0/24 | No ROA covers it. Add a ROA for AS203849, maxLength 24. |
Route objects not announced
Route objects with origin AS203849 whose prefix no peer sees AS203849 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 153.254.102.0/26 | NTTCOM | Valid |
| 165.254.191.0/26 | NTTCOM | Valid |
| 185.120.164.0/22 | 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.