There are 3 stored owner reports matching the driver assist & adas leading-label group for the 2021 Audi A6 in our NHTSA-sourced dataset. These are unverified consumer reports and may not reflect confirmed defects.
This group counts stored reports whose component label starts with one of this site's matching prefixes, ignoring case. Each matching report counts once within the group. Components mentioned later in the label or only in the narrative are not searched. How component counts work
Loaded 3 of 3 matching reports.
Open the full vehicle complaint log (all categories)The car has traffic sign recognition and uses it for "predictive control" where the vehicle will read traffic signs and adjust the adaptive cruise control setting to based on road signs. It had previously been working well but a software update was recently performed under TSB 2074688/3 on November 6th, 2025 and problems have shown up. Specifically, the system is incorrectly reading signs and sometimes appearing to make signs up out of nowhere. This has resulted in the car slowing down quickly on highways and nearly causing a couple of rear-end collisions due to the unexpected and erratic braking at highway speeds. The car will be going back to the dealer to be looked at, however this is unsafe because other drivers aren't prepared for a car randomly slowing down in front of them while on the highway for no reason. The car is also available to be inspected if needed. The issues first appeared within a week of having the TSB performed and has happened a number of times since. The following incidents have occurred: * Once on Highway 10 heading North/West between Big Lake and Elk River MN; the car was set to 60mph and hallucinated a 15mph speed limit sign. There was no speed limit sign on the road at all when this happened. This resulted in a near rear-end collision with the car behind. * Two times while on Highway 35E Southbound in the Minneapolis/St. Paul metro: 60mph to 40mph on clear roads. Once resulted in a near rear-end collision with the car behind. * Two times while on Highway 35E Northbound in the Minneapolis/St. Paul metro: 60mph to 40mph on clear roads * Once on Highway 35W Northbound in the Minneapolis/St. Paul metro: 60mph to 40mph on clear roads This software update is dangerous and should be updated or recalled, especially since the car did not have any issues of the sort prior to the update being performed.
The Audi Pre-sense is activated by weather. I was driving during a thunderstorm and Audi Presence activated causing the car to come to a hard stop due to precipitation. It happened again backing out of my driveway the Audi Pre-sense was activated and the car came to a hard stop. I thought I had back into another vehicle. This is very dangerous.
Today, I was in a protected left turn lane prior to making the turn. When oncoming traffic (4 lanes) cleared, I gently pressed the gas pedal to start the turn, but a red “pre-sense” error triggered and slammed on the brakes. I moved my foot to the brake and then back to the gas, and the error cleared, allowing me to continue the turn. This was dangerous as I could have stopped in front of oncoming traffic or been rear-ended by the car behind me. This is the first time I’ve had pre-sense braking engage, though I’ve gotten error messages while traveling at ~50mph in heavy traffic that’s it’s about to kick in. Several weeks ago, I made an appointment at my dealership to have the error messages looked at, but the first available appointment was about a month out, so I haven’t been able to take it in yet. In today’s incident, there was no warning before the braking engaged. I’m supportive of safety measures, but I am now scared of driving my car - I would rather have none of the fancy safety features than have false positives that put me in danger. This is like the Boeing 737 Max issue - why are cars with these issues allowed to be on the road??? Please make Audi fix this urgently, as message boards suggest it’s been an issue for at least five years!
Complaints are unverified consumer reports submitted to NHTSA. A high complaint count may reflect vehicle popularity, not defect severity. Data sourced from NHTSA public records.
NHTSA source checks for this vehicle year
Checks are recorded separately for each dataset, not for the whole page. Dates use UTC. A missing check date does not mean no records exist.
Vehicle import recorded: Aug 31, 2026. This is the stored import date, not confirmation that every source was successfully refreshed.