bgpreport

Network · data from 2026-11-12

AS63086 Uber Technologies Inc.

Registry name: UBER-PROD - Uber Technologies, Inc, US · PeeringDB

11IPv4 routes 100.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 11 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS63086, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63086, 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.
103.50.92.0/23 Valid None 673 100% 67
103.50.92.0/24 Valid None 673 100% 70
103.50.93.0/24 Valid None 673 100% 70
103.50.94.0/24 Valid None 673 100% 70
104.36.192.0/23 Valid None 673 100% 67
104.36.192.0/24 Valid None 673 100% 70
104.36.193.0/24 Valid None 673 100% 70
104.36.196.0/23 Valid None 673 100% 67
104.36.196.0/24 Valid None 673 100% 70
104.36.197.0/24 Valid None 673 100% 70
104.36.198.0/24 Valid None 673 100% 70

AS-SET

AS63086'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 11 are in fix.csv.

  • Route object: none11
ChangePrefix or setDetailFull-table peers
Route object: none103.50.92.0/23No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none103.50.92.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none103.50.93.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none103.50.94.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none104.36.192.0/23No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none104.36.192.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none104.36.193.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none104.36.196.0/23No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none104.36.196.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none104.36.197.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673
Route object: none104.36.198.0/24No route object for it. Add a route object with origin AS63086 in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS63086 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.