Tesla FSD version 10.69.2.3 rolled out shortly after AI Day. The latest update of Tesla’s Full Self Driving software delivers minor bug fixes. Some testers have received v10.69.2.3 and shared their observations with Teslarati.
As previously noted, 10.69.2.3 is a relatively small update that addresses some minor bugs in FSD Beta. As it sometimes goes with software bug fixes, some Beta testers mentioned a new issue in the latest version that appeared to be a step or two backward.
Road Obstacle Detection Issues
A few testers in Tesla’s FSD Beta Program reported experiencing road obstacle detection issues when their vehicles would not register particular objects in their path or directly ahead.
For instance, beta tester Jonathan shared that his vehicle did not recognize or avoid dead animals on the road. Another beta tester experienced similar issues with gates in his community.
“One day coming back from work I decided to see if it can get me close to the proximity of my house. I live in a gated community. The vehicle made the turn into the drive entry of the community which has two swing gates. Vehicle was almost going to go through the closed gates,” FSD Beta user Sean shared with Teslarati. “I had to tap the breaks and override the system to make it stop. It didn’t see the gates as obstacles or road blocks. I have tried this a couple of times during daylight and night time and result is the same.”
After Tesla released v10.69.2.2, a few beta testers observed that their vehicles recognized and avoided construction work sites and similar obstacles on the road.
Left and Right Turns
A couple of beta testers mentioned issues with left and right turns, specifically during intersections. The most prominent issue FSD Tesla drivers raised about turns was their cars’ hesitation during intersections. Testers highlighted that their cars’ hesitation during intersections isn’t really a big issue until they consider the other drivers on the road.
“Hesitates too long at intersections presumably trying to determine if/when it’s safe to proceed. This only matters to me when there are cars behind me. I feel intense pressure to push the car through (and I do). Humans do not have patience to wait on its time-table,” noted Terry, another FSD Beta tester.
FSD Beta user Dr. Rahaman made similar observations. He noted that his Tesla would creep forward after stopping at an intersection on a red light and would take a left or right turn too slowly, sometimes irritating the drivers behind him. Dr. Rahaman specifically observed that his car entered left turn lanes late without a signal. In the past, the Tesla owner has noted that the car’s turn signals sporadically turn off and on at some intersections or turns.
Lane Selection Issues
Tesla FSD v.10.69.2.3 doesn’t appear to address the largest issue multiple testers have pointed out over the past few weeks: lane selection. One beta tester seemed to sum up the sentiments most drivers in the Tesla FSD program have regarding lane selection.
“Lane selection sometimes just plain wrong and dumb. Causes driving task to be harder for itself than it needs to be because it realizes (eventually, usually) it’s in the wrong lane too late and then has to get over which is harder with traffic and unlike a human who can gesture, the car can give no such signals as to its self-made predicament,” the tester commented.
“Also, it sometimes gets into turn lane just late enough that cars behind me assume I’m continuing straight and swoop in behind me and get over immediately causing it to be even harder for my car to get over into that lane now because all slots are occupied and the road is about to end at a light,” he added.
Other Issues
Some other less prominent issues that a few FSD Beta testers have noted are listed below.
1. Lane Positioning – The car hugs the double yellow lines too closely on narrow roads or sticks to the middle of the road when no lines are present.
2. Wide turns – The Tesla car takes wide turns, far from the curb. One tester observed that his car risked hitting the guard rails and other obstacles with its wide turn.
3. Turn Lane Issues – The car still mistakes turn lanes for driving lanes
Some testers still report experiencing phantom braking and jerkiness while taking turns. However, the one observation that seems to stick out among others came from beta tester Neeraj.
“Drives as if everyone is going to follow the rules 100% and is not accommodating or accounting for those who may not be going 100% as they should,” he said about FSD Beta.
FSD Beta still has a ways to go before 100% autonomous version rolls out to the general public. Observations and tests from beta testers help Tesla improve FSD. Elon Musk teased more significant improvements in the next update, 10.69.3. Tesla hopes to release a ‘supervised’ FSD version by the end of the year.
Have you tried out FSD Beta 10.69.2.3 yet? I’d like to hear from you! Contact me at maria@teslarati.com or via Twitter @Writer_01001101.
News
Tesla’s Cybercab fleet just had its biggest day ever
Tesla registered a record 200 Cybercabs in one day, and Dallas could be next up.
Tesla added a record 200 Cybercabs to its Texas Robotaxi fleet in a single day, pushing the purpose-built two-seater past 750 registered units in the state. The batch landed on the Texas Department of Motor Vehicles automated vehicle register at 3:45 p.m. CT on November 17 and included 200 Cybercabs and one Model Y. Tesla’s Cybercab count had sat at 573 since late October before the jump.
The additions also put Tesla back ahead of Waymo on the register. Tesla now has 1,507 vehicles registered for driverless operation in Texas against Waymo’s 1,321, a lead of 186. Waymo had been ahead by 15 vehicles before the batch arrived. Tesla first passed Waymo on November 10, as Teslarati reported, before Waymo briefly moved back in front.
🚨 There are more CYBERCABS in the Tesla Robotaxi fleet in Texas than Model Y! https://t.co/BdRK2LnnAP — TESLARATI (@Teslarati) November 18, 2026
Cybercabs now make up 51.3 percent of Tesla’s registered Texas fleet, at 773 units against 734 Model Ys. Waymo’s fleet in the state is split between 874 Jaguar I-PACEs and 447 Ojai vehicles.
The register does not say where vehicles will operate, and registration does not mean a car is carrying riders. Still, the timing lines up with Tesla’s plans for Dallas. On the company’s third quarter earnings call in October, AI chief Ashok Elluswamy said, “next month, we’ll be launching in Dallas,” and a video posted over the weekend showed more than 50 Cybercabs parked in rows at a Dallas lot, with more on a car carrier nearby. Tesla has not announced a start date.
Dallas is already one of Tesla’s busiest Robotaxi markets. Model Y Robotaxis there have run without anyone in the driver’s seat around the clock since November 11, and the city logged 608,130 miles with no safety monitor between January 22 and October 18, second only to Austin, according to Tesla’s first Robotaxi Safety Report. Public Cybercab rides have been limited to Austin since the vehicle joined the service in September.
The fleet growth comes as Tesla shifts more of its factory capacity toward the Cybercab. The company is winding down Cybertruck production at Giga Texas by the end of summer 2027 to make room, and announced this week a €3 billion expansion of Giga Berlin with a new building designed to produce up to 1 million Cybercabs a year starting in 2029, as Teslarati covered.
Some Cybercabs will soon go to private owners too. Tesla began inviting select customers to buy the vehicle for personal use last week at $29,990 with a required $299 monthly Autonomy Subscription, with deliveries targeted for December in the same five Texas cities where Robotaxi operates.
News
Tesla Robotaxi takes over for Uber credits and loaners at Service locations
Tesla is now utilizing its in-house Robotaxi platform to give those waiting for their vehicles during Service visits rides instead of offering Uber credits or Loaner vehicles.
Tesla owners in Austin who bring vehicles in for service are receiving in-app prompts to use the company’s Robotaxi network while their cars are being worked on.
One recent notification, sent during a frunk repair, carried the heading “Try Robotaxi During Your Service Visit” and stated that while the vehicle is being serviced, the customer can take an autonomous Robotaxi ride to the next destination in Austin and download the Robotaxi app to get started.
Interesting. While my frunk gets fixed Tesla suggests taking a Robotaxi 😇 https://t.co/QiUbAmrp4a
— Wadesmith (@LanceWade) November 17, 2026
The suggestion arrives as Tesla has long relied on two main ways to keep customers mobile during longer service visits. Service centers have typically offered loaner vehicles drawn from a limited fleet; when those vehicles were unavailable, centers have issued Uber or Lyft credits. Uber credits were widely eliminated years ago, but some locations will still give them out.
Both approaches carry costs: loaner cars occupy inventory that could otherwise be sold, and third-party credits generate recurring expense.
Code discovered in Tesla app version 4.60.5 in September 2026 already listed “sv_transport_robotaxi” among the transportation options available for service appointments, alongside paid loaners and other alternatives, indicating the company had been preparing to route customers through its own autonomous fleet.
Your Tesla could be in the Robotaxi fleet next month, Elon Musk claims
Austin provides the clearest early example. The city remains Tesla’s primary Robotaxi market, with unsupervised Model Y and Cybercab vehicles operating across an expanded zone of roughly 400–440 square miles and running 24/7 since November 11. Public driverless service is also live in Dallas, Fort Worth, Houston, San Antonio, Miami, Orlando, and Tampa.
Directing service customers into this network keeps the vehicles utilized and reduces reliance on external rideshare credits, while giving owners practical experience with the Robotaxi app and vehicles during the repair window. Once service is complete, the same network can be used for the return trip without a staffed loaner handoff.
The Austin notification is the first public instance of the capability the September app code previewed. As Robotaxi expands into additional U.S. markets and the fleet grows, service centers in those cities are positioned to follow the same pattern, presenting autonomous rides as a primary transportation option during the service appointment rather than defaulting to loaner vehicles or third-party credits.
For customers, the change preserves mobility without the logistics of arranging a temporary car; for Tesla, it links the service operation more tightly to the expanding Robotaxi business.
Elon Musk
Sean Duffy fires back at Elon Musk over free Starlink
Sean Duffy says the FAA picked a ground network over Starlink, and Musk isn’t impressed.
Transportation Secretary Sean Duffy has responded to Elon Musk’s claim that the Federal Aviation Administration turned down free Starlink terminals before last week’s nationwide ground stop, saying the department chose a ground-based network after running into problems with an earlier version of the satellite service. Musk’s reply was a single emoji: “🤦♂️.”
Speaking at a press conference, Duffy said Starlink had been useful in some parts of the system. “I’ve worked well with Elon, and he, Starlink was a great solution for some of our assets in Alaska, but we sent Starlink, in one of its prior iterations, to our tech lab, and, there was some issues that we had to navigate, and we thought that the best method is to have a network that’s based on the ground,” Duffy said, according to a transcript published by ZeroHedge. “Now, I think what he’s doing with Starlink and the speed is remarkable, but, our airspace is very big. We have assets everywhere. And so, again, we used him for different parts of the airspace.”
Duffy did not dispute that the offer was made. He also did not say what problems the FAA found during testing.
The exchange started Monday, when Musk wrote on X, “Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” as Teslarati reported. That post came three days after the FAA grounded departures nationwide on November 13, when its legacy equipment became unstable as data flooded its telecommunications network at 1,000 connection attempts every four to five seconds. The FAA traced the flood to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where L3Harris had been installing a new router. Roughly 12,462 flights were canceled that day.
As I was saying …
Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were.
— Elon Musk (@elonmusk) November 16, 2026
Duffy has also signaled frustration with L3Harris, which runs the FAA’s current network. “I want to get away from L3Harris and get to a new one, but they own the network,” he said. “I can’t cancel the network that they own.” He has asked Congress for $50 billion to modernize air traffic control, arguing against “a patchwork, a fix to a system that’s critical for every single family.”
The FAA’s position on satellite links predates this week. In a July 2025 letter to lawmakers, FAA Administrator Bryan Bedford said the agency “would not use Starlink (or any satellite service) as the sole communications technology” for safety-critical air traffic services. Reuters reported at the time that the FAA was not considering replacing its L3Harris and Verizon contracts with Starlink. Verizon’s FAA Enterprise Network Services contract, awarded in 2023, is valued at up to $2.4 billion over 15 years.
Musk first pressed the issue in February 2025, while he was leading the Department of Government Efficiency, writing that “the Verizon system is not working and so is putting air travelers at serious risk” before correcting himself days later to blame L3Harris. SpaceX said at the time it was supplying Starlink kits to the FAA at no cost and had no intent to take over any existing contract.