Mercedes-Benz infotainment-reset instrument-cluster blackout recall (26V281)
Mercedes-Benz USA recalled 144,049 2024-2026 vehicles (AMG GT, C-, E-, SL-, CLE- and GLC-Class and others) whose digital instrument cluster could go blank while driving, hiding the speedometer and warning lights; no crashes or injuries were reported, but the company acknowledged numerous warranty claims.
The damage was public. The root cause was preventable.
Mercedes-Benz USA recalled 144,049 2024-2026 vehicles (AMG GT, C-, E-, SL-, CLE- and GLC-Class and others) whose digital instrument cluster could go blank while driving, hiding the speedometer and warning lights; no crashes or injuries were reported, but the company acknowledged numerous warranty claims.
What the software actually got wrong
The infotainment control unit could trigger an increased number of system resets as an intended fallback behavior, briefly blanking the instrument cluster; the problem traced to software Mercedes pushed in August 2025 to improve display robustness, and only about 62% of vehicles had received the corrective over-the-air update when the formal recall was filed.
The infotainment control unit could trigger an increased number...
The infotainment control unit could trigger an increased number of system resets as an intended fallback behavior, briefly blanking the instrument cluster
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.
The problem traced to software Mercedes pushed in August...
the problem traced to software Mercedes pushed in August 2025 to improve display robustness
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.
Only about 62% of vehicles had received the corrective...
only about 62% of vehicles had received the corrective over-the-air update when the formal recall was filed
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.