Rivian rearview-camera software recall across R1 and R2 (26V597)
Rivian recalled about 100,700 US and Canadian vehicles (98,828 in the US; R1S, R1T and the new R2) built from August 2021 through August 2026 because a software notification could block the rearview camera image; the company knew of no crashes or injuries and over 95% of vehicles already had the fix.
The damage was public. The root cause was preventable.
Rivian recalled about 100,700 US and Canadian vehicles (98,828 in the US; R1S, R1T and the new R2) built from August 2021 through August 2026 because a software notification could block the rearview camera image; the company knew of no crashes or injuries and over 95% of vehicles already had the fix.
What the software actually got wrong
A software prompt can overlay and briefly obstruct the rearview camera image, so the vehicles may not meet the federal rear-visibility standard (FMVSS 111); Rivian released a free over-the-air update, and it was the first recall to reach the R2.
A software prompt can overlay and briefly obstruct the...
A software prompt can overlay and briefly obstruct the rearview camera image, so the vehicles may not meet the federal rear-visibility standard (FMVSS 111)
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
Rivian released a free over-the-air update
Rivian released a free over-the-air update
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
It was the first recall to reach the R2
it was the first recall to reach the R2
Requs AI Edge Case and Software FMEA together treat this as a known, catalogued defect pattern — not a novel surprise — so it gets tested for deliberately rather than discovered after deployment.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.