4 distinct campaigns affect this selection. Announcement dates below are different from vehicle model years. A campaign may cover multiple years.
25V063000 · Electrical System:Software | Equipment:Other:Owners/Service/Other Manual | Tires:Pressure Monitoring And Regulating Systems
Reported: 2025-02-06 (February 6, 2025) · Model years: 2025
Zeekr Technology US, LLC (Zeekr) is recalling one 2025 RT vehicle. The digital tire pressure monitoring system (TPMS) warning light may not flash long enough for the driver to notice. Additionally, the owner's manual may be missing information about the TPMS warning light. As such, this vehicle fails to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 138, "Tire Pressure Monitoring Systems."
Consequence: A TPMS warning light that fails to notify the driver of a problem increases the risk of a crash.
Remedy: Zeekr will update the display head unit software and add a correction to the owner's manual, free of charge. The vehicle was repaired on February 23, 2025. Owners may contact Zeekr customer service at 1-212-481-2050.
NHTSA campaign record ↗25V066000 · Air Bags:Side/Window:Curtain | Structure:Body:Roof And Pillars
Reported: 2025-02-07 (February 7, 2025) · Model years: 2025
Zeekr Technology US, LLC (Zeekr) is recalling one 2025 RT vehicle. The C-Pillar trim may catch the side curtain air bag, preventing the air bag from fully deploying. As such, this vehicle fails to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 226, "Ejection Mitigation."
Consequence: An air bag that deploys improperly increases the risk of ejection and injury during a crash.
Remedy: Zeekr will modify the C-Pillar chutes, free of charge. The vehicle was repaired on February 23, 2025. Owners may contact Zeekr customer service at 1-212-481-2050.
NHTSA campaign record ↗25V067000 · Air Bags: Air Bag/Restraint Control Module:Software | Air Bags:Sensor:Occupant Classification
Reported: 2025-02-07 (February 7, 2025) · Model years: 2025
Zeekr Technology US, LLC (Zeekr) is recalling one 2025 RT vehicle. The Occupant Weight Sensor (OWS) may misclassify the front passenger seat occupant or disable the air bag. As such, this vehicle fails to comply with Federal Motor Vehicle Safety Standard (FMVSS) 208, "Occupant Crash Protection."
Consequence: An air bag that deploys improperly or fails to deploy increases the risk of injury during a crash.
Remedy: Zeekr will update the OWS software, free of charge. The vehicle was repaired February 23, 2025. Owners may contact Zeekr customer service at 1-212-481-2050.
NHTSA campaign record ↗25V068000 · Air Bags:Frontal | Seats:Barriers | Air Bags:Frontal:Driver Side:Cushion
Reported: 2025-02-07 (February 7, 2025) · Model years: 2025
Zeekr Technology US, LLC (Zeekr) is recalling one 2025 RT vehicle. The seat position may prevent the side curtain and passenger air bag from providing adequate neck protection during a crash. As such, this vehicle fails to comply with Federal Motor Vehicle Safety Standard (FMVSS) 208, "Occupant Crash Protection."
Consequence: Inadequate neck protection increases the risk of injury.
Remedy: Zeekr will install a stop in the seat rail, free of charge. The vehicle was repaired February 23, 2025. Owners may contact Zeekr customer service at 1-212-481-2050.
Inspect model-year patterns, reported mileage, monthly activity and the evidence behind each signal.
Data completeness
6 unique complaints in this selection. Analysis snapshot: 2026-11-09.
0.0%Usable mileage0 / 6 records
100.0%Valid incident date6 / 6 records
100.0%Valid filing date6 / 6 records
100.0%Ordered incident and filing dates6 / 6 records
Missing, zero and invalid mileage is excluded. Dates after the snapshot are excluded. Examples are limited selections, not a representative sample.
Problems by model year
Model-wide comparison of the eight most reported components across the model. Cells show counts and shares within each model year. Open a cell for source examples.
Component complaint heatmap
Component
2025
2026
Steering
00.0%
No examples available for this selection.
240.0%ODI 11770568
I was waiting to turn left at an intersection with my left blinker on and my foot on the brakes. Waymo behind me went around on the left side and made a right turn cutting me off. When I saw the Waymo coming around my side I creeped forward a few times and turned my wheel to make it clear my vehicle wasn't disabled but it continued forward and completed its turn. An oncoming turning vehicle with the right of way had to slow down for the Waymo because there wasn't enough space for three vehicles across the intersection.
The car stopped suddenly (few yards before the destination) in the middle of a three lines street in Beverly Hills and as a consequence I had to get out from the car and put myself in danger when I had to cross the street.
Today I was trapped by 5 waymos on 15th between shotwell and south van ness in San Francisco. The first 3 stopped behind a delivery truck. I had to drive around the 4 vehicles to continue on 15th. As I passed another Waymo was in the oncoming lane, going around a delivery truck in the opposite direction (in my lane). The Waymo tried to back up, but another pulled up to get passengers, so waymos were taking up both lanes.
On Wednesday, XXX, at 11:05:48am I observed [XXX] CA license number [XXX], make an illegal right turn from [XXX] to [XXX]. It turned from the right through lane instead of the right curb lane traveling to the left of a car turning right legally. There were six Ojais turning right, so I was surprised that they didn't recognize each other and let this one into the curb lane. I have dashcam video of the incident. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
On XXX at ~7:20 PM, I took a ride in Waymo autonomous vehicle 0397N4. The navigation system and mobile application failed to identify a severe pedestrian hazard, indicating the drop-off required a routine 4-minute walk without disclosing that the destination was cut off by a barely lit, high-speed thoroughfare. Waymo zeroed out the fare, indicating an implicit internal system flag of a trip failure. The vehicle executed a drop-off in a residential cul-de-sac in [XXX] abutting [XXX]. While the vehicle parked safely, the location functioned as an…
Darker cells indicate a larger share of submitted complaints. Components overlap. This measures complaint composition, not failure probability.
Failure mileage by component
Median and middle 50% of usable owner-reported mileages. Ranges require at least five records.
Component failure mileage distribution
Component
Mileage range (25th–75th percentile)
Median
Usable records
Examples
No usable records for this analysis.
Complaint and recall timeline
Explore monthly filing activity alongside recall announcements. Up to ten years of monthly history is available.
Solid line: filed complaints. Dashed amber lines: recall announcement dates for this vehicle selection; markers include all recall components. The latest month is partial. Temporal proximity does not establish causation.
Monthly counts, recall campaigns and complaint examples
The car stopped suddenly (few yards before the destination) in the middle of a three lines street in Beverly Hills and as a consequence I had to get out from the car and put myself in danger when I had to cross the street.
On Wednesday, XXX, at 11:05:48am I observed [XXX] CA license number [XXX], make an illegal right turn from [XXX] to [XXX]. It turned from the right through lane instead of the right curb lane traveling to the left of a car turning right legally. There were six Ojais turning right, so I was surprised that they didn't recognize each other and let this one into the curb lane. I have dashcam video of the incident. INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)
On XXX at ~7:20 PM, I took a ride in Waymo autonomous vehicle 0397N4. The navigation system and mobile application failed to identify a severe pedestrian hazard, indicating the drop-off required a routine 4-minute walk without disclosing that the destination was cut off by a barely lit, high-speed thoroughfare. Waymo zeroed out the fare, indicating an implicit internal system flag of a trip failure. The vehicle executed a drop-off in a residential cul-de-sac in [XXX] abutting [XXX]. While the vehicle parked safely, the location functioned as an…
Complete months in the latest six months with at least 10 complaints, at least twice the preceding 12-month average, and at least three square-root deviations above that average.
This is a descriptive screening rule, not a statistical defect finding. Publicity and reporting changes can increase submissions.
No complete months meet the spike thresholds for this selection.
Equal-age model-year comparison
Model-wide cumulative reports during the first three or five calendar years, starting with the model year (age 0). Only fully elapsed windows are compared.
No selected model years have a complete observation window. Choose an eligible year or a shorter window.
Incident date is preferred when valid and no later than filing; otherwise filing date is used. Model year approximates age. Equal observation time does not adjust for sales, distance driven or reporting delays. One complaint linked to multiple model years can appear in each cohort.
Components reported together
Each cell counts unique complaints naming both components. Open a nonzero cell for examples.
Component co-occurrence matrix
Component
Steering
Unknown Or Other
Electrical System:Adas
Other/I Am Not Sure
Steering
—
0
0
0
Unknown Or Other
0
—
0
0
Electrical System:Adas
0
0
—
0
Other/I Am Not Sure
0
0
0
—
Co-reporting does not establish that one component caused another concern.
Recurring narrative patterns
Specific keyword mentions beyond broad component labels. Matching includes negations and comparisons and does not confirm a diagnosis.
1 patterns with matching reports.
Steering assistance concerns
1 mentions · 16.7% of complaints
Median mileage: Unavailable (0 usable records).
ODI 11774086
Safety complaint: Sudden loss of steering control , 2020 Chevrolet Silverado 1500 I own a 2020 Chevrolet Silverado 1500 with the 2.7L turbocharged four-cylinder engine. The truck had approximately 41,000 miles when this incident occurred. While driving and attempting to make a turn onto a side street, the steering suddenly locked up. I could not make the turn, creating a serious risk of a collision. Fortunately, there were no other vehicles on the road at that moment, and I avoided a crash. The truck was taken/towed to a Chevrolet dealership…