Polestar 2 rearview camera FMVSS 111 software recalls
- Manufacturer
- Polestar
- Model
- Polestar 2
- Years affected
- 2021–2025
- Risk type
- Software/visibility
- Issue
- A multi-year sequence of three NHTSA campaigns addressing the same underlying defect — the rearview camera image may fail to display when the Polestar 2 is placed in reverse, violating Federal Motor Vehicle Safety Standard No. 111 ('Rear Visibility'). RP1016 (NHTSA 24V477, August 2024) was the first remedy. RP1056 (NHTSA 25V280, June 2025) followed when the first fix proved insufficient. RP1069 (NHTSA 25V615, September 2025) is the current third remedy attempt — replaces both prior campaigns. Affects all 2021-2025 Polestar 2 vehicles. Vehicles previously repaired under 24V477 or 25V280 must have the new RP1069 remedy completed.
Summary
The Polestar 2 rearview camera recall is one of the most-instructive software-defined-vehicle reliability stories on the EV market. The same FMVSS 111 'Rear Visibility' defect — the rearview camera failing to display when the vehicle is placed in reverse — has now been the subject of three separate NHTSA campaigns: RP1016 (August 2024), RP1056 (June 2025), and the current RP1069 (September 2025). Each campaign identified that the prior remedy did not fully resolve the underlying defect.
Timeline
August 2024 (RP1016 / 24V477): Initial recall covering 2021-2024 Polestar 2 vehicles. Polestar released an OTA software update to the Infotainment Head Unit (IHU). Owner notification letters mailed August 9, 2024.
June 2025 (RP1056 / 25V280): Second recall expanded scope to 2021-2025 vehicles after the RP1016 fix proved insufficient. Required dealer software update (not OTA this time) for vehicles previously repaired under 24V477.
September 2025 (RP1069 / 25V615): Third recall replaces both 24V477 and 25V280. Vehicles previously repaired under either prior campaign must have the new RP1069 remedy completed. Interim notification letters mailed November 7, 2025. The actual software remedy is anticipated late Q1 / early Q2 2026 — meaning owners notified in late 2025 should not expect to receive the fix for several months. VINs searchable on NHTSA.gov beginning September 17, 2025.
Consumer impact
The pattern of three consecutive remedy attempts for the same defect carries practical implications for both current owners and used buyers. For current owners: if the rearview camera is currently working reliably, no immediate action is required, but expect dealer or OTA notification when the RP1069 remedy ships in 2026. For used buyers: verifying recall completion via NHTSA VIN lookup is critical — and a 'completed' status on RP1069 is more meaningful than a 'completed' status on the prior 24V477 or 25V280 campaigns, which proved insufficient. Polestar's customer service line is 1-800-806-2504. The pattern itself — three OTA-deliverable recalls for one defect — is a meaningful data point in evaluating any software-defined-vehicle ownership proposition, regardless of brand.
Help other owners — file with the regulator
If your vehicle is affected by this defect, filing a complaint with NHTSA, Transport Canada, DVSA, or your regional regulator helps build the data record. Each report contributes to pattern detection that can trigger formal investigations and recalls — protecting other owners of the same vehicle, not just you.
You can file at any time, even if your dealer or manufacturer is already handling repairs. The regulatory complaint is a separate channel that helps every owner of your vehicle.
Campaign codes across affected model years
The manufacturer internal campaign codes and NHTSA campaign numbers we have on file for every affected model year. Multiple codes on a single vehicle reflect successive campaigns — sometimes a new campaign supersedes an earlier repair that did not resolve the issue.
| Mfr. code | NHTSA # | Announced | Model year | Description |
|---|---|---|---|---|
| R10079 | 21V338 | 2021 | 2021 | BECM software defect causes high-voltage system disconnect, leading to loss of drive power. OTA software remedy. |
| RP1069 | 25V615 | 2025 | 2021 | Rearview camera image may not display when in reverse. Third remedy attempt for FMVSS 111 violation. Replaces 24V477 and 25V280. Software fix anticipated late Q1 / early Q2 2026. |
| RP1063 | 25V452 | 2025 | 2021 | One-pedal-drive coast brake-loss. Loss of brake function during downhill OPD coasting. Software remedy. |
| R10245 | 23V569 | 2023 | 2023 | Front lower ball joint may have been incorrectly installed. Narrow batch (~12 vehicles). |
| RP-FSAB | 25V020 | 2025 | 2024 | Driver-side inner far side air bag module clamp crimping defect. Narrow batch. |
Always verify open status by VIN with the regulator in your region:
This table is editorial reference, not a regulatory record. Regulators outside of NHTSA generally require a VIN or registration-plate lookup flow instead of a per-model URL.
Verify your vehicle with the regulator
The regulator in your jurisdiction is always the authoritative source for whether your specific VIN is affected by an open safety campaign. Check the database below using your vehicle identification number.
- United States — NHTSA (US)
- Canada — Transport Canada
- Transport Canada — Transport Canada defects and recalls
- DVSA (UK) — DVSA vehicle recall check (UK)
- EU Safety Gate — EU Safety Gate
- KBA (Germany) — KBA recalls database (Germany)
EV Risk Index editorializes around public recall data; we do not replace regulatory guidance. If you believe your vehicle is affected by a safety recall, contact the manufacturer and check the regulator database for your jurisdiction using your VIN.