Network · data from 2026-11-12
AS203351 UBER-EMEA Uber International B.V.
Registry name: UBER-EMEA Uber International B.V., NL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203351, 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.137.208.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2a0c:4a00:c10::/44 | No ROA | Other IRR onlyRADB | 635 100% |
AS-SET
AS203351 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: none2
- Route object: RIR2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.137.208.0/24 | No ROA covers it. Add a ROA for AS203351, maxLength 24. |
| Route object: RIR | 185.137.208.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2a0c:4a00:c10::/44 | No ROA covers it. Add a ROA for AS203351, maxLength 44. |
| Route object: RIR | 2a0c:4a00:c10::/44 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS203351 whose prefix no peer sees AS203351 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.137.208.0/22 | RADB | No ROA |
| 185.137.209.0/24 | RADB | No ROA |
| 185.137.209.40/30 | RADB | No ROA |
| 2a0c:4a00::/29 | RADB | No ROA |
| 2a0c:4a00:c20::/44 | RADB | 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.