There are 2 stored owner reports matching the speed control & cruise leading-label group for the 2017 Toyota Yaris 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 2 of 2 matching reports.
Open the full vehicle complaint log (all categories)I RECENTLY BOUGHT THE CAR FROM THE DEALER AND I TOOK IT BACK TO THEN 4 TIMES FOR THE SAME ISSUE AND THEY SAY IT IS NORMAL. SO MY ISSUE IS WHEN I'M AT A LIGHT AND I'M IN DRIVE OR REVERSE YOU CAN SEE THE RPM JUMP AROUND TO ABOUT 400 TO 700 AND THE CAR STARTS TO VIBRATE SHAKING THE CAR. THE CAR ONLY HAS 23,XXX MILES ON IT.
TL* THE CONTACT OWNS A 2017 TOYOTA YARIS. WHILE MERGING ONTO THE EXPRESSWAY AT APPROXIMATELY 25 MPH, THE VEHICLE DID NOT ACCELERATE AND ALMOST CAUSED A CRASH. THE ACCELERATOR PEDAL WAS DEPRESSED ALL THE WAY DOWN TO THE FLOORBOARD. AFTER APPROXIMATELY 30 SECONDS, THE VEHICLE FINALLY ACCELERATED. THE CONTACT STATED THAT THE VEHICLE ONLY EXHIBITED THE FAILURE WHEN TRAVELING ON AN INCLINE. THE VEHICLE WAS TAKEN TO THE DEALER (COUNTRY TOYOTA IN WESTPORT, CONNECTICUT) WHERE IT WAS DIAGNOSED THAT THE VEHICLE WAS PERFORMING ACCORDING TO STANDARDS. THE FAILURE OCCURRED THREE TIMES IN TWO MONTHS. THE MANUFACTURER WAS NOTIFIED OF THE FAILURE AND PROVIDED CASE NUMBER: 1708151519. THE VEHICLE WAS NOT REPAIRED. THE APPROXIMATE FAILURE MILEAGE WAS 8,431.
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: Apr 29, 2026. This is the stored import date, not confirmation that every source was successfully refreshed.