bgpreport

Network · data from 2026-11-12

AS26673 CORPIT-AS - Uber Technologies, Inc

Registry name: CORPIT-AS - Uber Technologies, Inc, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26673, 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.
207.231.168.0/22 No ROA Nonecovered by 207.231.168.0/21 673 100% 67
207.231.169.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.231.170.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.231.172.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.231.173.0/24 No ROA Other IRR onlyRADB 673 100% 67
207.231.168.0/21 No ROA Other IRR onlyRADB 672 100% 67
207.231.174.0/24 No ROA Other IRR onlyRADB 672 100% 67
2620:1b2:c40::/44 No ROA Other IRR onlyRADB 635 100% 67
207.231.168.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 3
207.231.171.0/24 No ROA Other IRR onlyRADB 2 0%low visibility 2
2620:1b2:c50::/44 No ROA Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS26673 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 29 are in fix.csv.

  • ROA: none11
  • Route object: none1
  • Route object: RIR10
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none207.231.168.0/22No ROA covers it. Add a ROA for AS26673, maxLength 22.673 of 673
Route object: none207.231.168.0/22No route object for it. A route object for 207.231.168.0/21 with origin AS26673 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26673 in the RIR database for the space.673 of 673
ROA: none207.231.169.0/24No ROA covers it. Add a ROA for AS26673, maxLength 24.673 of 673
Route object: RIR207.231.169.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.231.170.0/24No ROA covers it. Add a ROA for AS26673, maxLength 24.673 of 673
Route object: RIR207.231.170.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.231.172.0/24No ROA covers it. Add a ROA for AS26673, maxLength 24.673 of 673
Route object: RIR207.231.172.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.231.173.0/24No ROA covers it. Add a ROA for AS26673, maxLength 24.673 of 673
Route object: RIR207.231.173.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none207.231.168.0/21No ROA covers it. Add a ROA for AS26673, maxLength 21.672 of 673
Route object: RIR207.231.168.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none207.231.174.0/24No ROA covers it. Add a ROA for AS26673, maxLength 24.672 of 673
Route object: RIR207.231.174.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2620:1b2:c40::/44No ROA covers it. Add a ROA for AS26673, maxLength 44.635 of 636
Route object: RIR2620:1b2:c40::/44Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none207.231.168.0/24No ROA covers it. Add a ROA for AS26673, maxLength 24.2 of 673
Route object: RIR207.231.168.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none207.231.171.0/24No ROA covers it. Add a ROA for AS26673, maxLength 24.2 of 673
Route object: RIR207.231.171.0/24Route object only in RADB. Add it in the RIR database for the space.2 of 673
ROA: none2620:1b2:c50::/44No ROA covers it. Add a ROA for AS26673, maxLength 44.1 of 636
Route object: RIR2620:1b2:c50::/44Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

207.231.175.0/24RADBNo ROA
2620:1b2::/36RADBNo ROA
2620:1b2:c10::/44RADBNo ROA
2620:1b2:c20::/44RADBNo ROA
2620:1b2:c30::/44RADBNo ROA
2620:1b2:cb0::/44RADBNo ROA
2620:1b2:cc0::/44RADBNo 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.