bgpreport

Network · data from 2026-11-12

AS134135 UBER-AS-AP - Uber Technologies

Registry name: UBER-AS-AP - Uber Technologies, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134135, 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.

82.152.71.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.152.127.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.152.61.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.72.0/24 Valid Other IRR onlyRADB 673 100% 68
82.152.92.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.41.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.42.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.53.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.58.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.80.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.86.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.90.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.91.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.144.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.155.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.180.0/24 Valid Other IRR onlyRADB 673 100% 68
82.153.203.0/24 Valid Other IRR onlyRADB 673 100% 68
82.163.15.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.49.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.64.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.70.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.71.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.73.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.74.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.77.0/24 Valid Other IRR onlyRADB 673 100% 68
89.213.79.0/24 Valid Other IRR onlyRADB 673 100% 68
212.134.106.0/24 Valid Other IRR onlyRADB 673 100% 68
212.134.107.0/24 Valid Other IRR onlyRADB 673 100% 68
212.134.108.0/24 Valid Other IRR onlyRADB 673 100% 68
212.134.109.0/24 Valid Other IRR onlyRADB 673 100% 68
43.245.118.0/24 Valid RIR databaseAPNIC 673 100% 69
64.69.105.0/24 Valid RIR databaseARIN, RADB 673 100% 66
64.69.106.0/24 Valid RIR databaseARIN, RADB 673 100% 66
95.155.160.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
95.155.161.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
95.155.162.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
95.155.163.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
95.155.164.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
95.155.165.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
95.155.166.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
95.155.167.0/24 Valid RIR databaseRADB, RIPE 673 100% 66
205.196.129.0/24 Valid RIR databaseARIN, RADB 673 100% 66
205.196.130.0/24 Valid RIR databaseARIN, RADB 673 100% 66
205.196.149.0/24 Valid RIR databaseARIN, RADB 673 100% 66
205.196.150.0/24 Valid RIR databaseARIN, RADB 673 100% 66
212.134.32.0/22 Valid RIR databaseRADB, RIPE 673 100% 66

AS-SET

AS134135 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 41 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: RIR28
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin82.152.71.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS134135. If AS134135 should announce it, add a ROA for AS134135.2 of 673
Route object: none82.152.71.0/24Route objects for it name AS834. Add a route object with origin AS134135 in the RIR database for the space.2 of 673
ROA: origin82.152.127.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS134135. If AS134135 should announce it, add a ROA for AS134135.2 of 673
Route object: none82.152.127.0/24Route objects for it name AS834. Add a route object with origin AS134135 in the RIR database for the space.2 of 673
Route object: RIR82.152.61.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.72.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.152.92.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.41.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.42.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.53.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.58.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.80.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.86.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.90.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.91.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.144.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.155.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.180.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.203.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.163.15.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.49.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.64.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.70.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.71.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.73.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.74.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.77.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR89.213.79.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR212.134.106.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR212.134.107.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR212.134.108.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR212.134.109.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS134135 whose prefix no peer sees AS134135 announce. Many are kept on purpose (backup routes, space announced only in some places).

106.0.60.0/24APNICInvalid: origin
106.0.61.0/24APNICInvalid: origin
212.134.40.0/22RIPEInvalid: origin
212.134.48.0/22RIPEInvalid: origin
212.134.100.0/22RIPEInvalid: origin
212.134.112.0/22RIPEInvalid: origin
212.134.120.0/22RIPEInvalid: origin
212.134.132.0/22RIPEInvalid: origin
212.134.140.0/22RIPEInvalid: origin

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.