A software issue blocking the rearview camera image prompted Rivian to recall almost 100,000 vehicles
- A fault with the company’s rear-view camera is behind the recall.
- A total of 98,828 Rivian R1S, R1T, and R2 models are impacted.
- Rivian says most models have already been fixed.
Customer deliveries of the Rivian R2 started only three months ago, and already, the electric SUV has been caught up in its first recall. It’s not the only Rivian model impacted either, as tens of thousands of R1S and R1T models are also being recalled over the same issue.
The recall notice says that a software issue in the R1S, R1T, and R2 models falls foul of Federal Motor Vehicle Safety Standards. On the face of it, that sounds quite troubling, but it isn’t overly significant and certainly isn’t something Rivian owners should be losing sleep over.
The company says that if the stability control system is disabled in one of the different drive modes, a safety alert will appear on the infotainment screen, asking whether the driver would like to return to a mode where the ESC is enabled. If a driver then puts the vehicle into reverse without making a selection, this notification will remain on screen, overlapping the rear-view camera image, which is a no-no according to safety standards.
A total of 98,828 Rivian models are impacted. These start with 2,481 examples of the 2027 R2, manufactured between April 23, 2026, and August 10, 2026. In addition, 62,259 Rivian R1S models built from March 30, 2022, to August 6, 2026, through the 2022-2027 model years are involved, as are 34,088 Rivian R1Ts built from August 23, 2021, to July 6, 2026.
Rivian says it discovered the issue during internal testing from July through September and adds that before the recall notice was even issued, an over-the-air software update had already rectified the fault in most models. In fact, it says the update has already been rolled out to 96 percent of the R2s involved, as well as 95 percent of R1S and R1T models. Chances are, if you own an impacted model, it was already updated and fixed before the recall.
