News
SpaceX hit by back to back Falcon 9 and Starship rocket delays
SpaceX has been hit by multiple back-to-back Falcon 9 launch and Starship test delays in a period of a few days, ending the company’s second attempt at a potentially record-breaking month.
Originally scheduled to launch no earlier than (NET) June 22nd, give or take, SpaceX’s own Starlink-9 satellite mission kicked off the misfortune and has suffered the most. After SpaceX announced an indefinite delay on July 11th to allow for “more time for checkouts”, Starlink-9 is not expected to launch for several more days at best. On July 13th, SpaceX announced that another summer mission targeting a NET July 14th launch had also been delayed indefinitely to allow teams to inspect the Falcon 9 rocket’s upper stage and potentially replace hardware.
Those two delays have had follow-on effects on subsequent launches planned in late July and early August but the actual end-results will be hard to determine until SpaceX has settled on alternate launch dates for Starlink-9 and ANASIS II. Meanwhile, all throughout those orbital-class launch delays, the first Raptor engine test with SpaceX’s fifth full-scale Starship has been consistently delayed and is now expected no earlier than this week (roughly July 15-19). The swath of delays have been so pronounced and oddly simultaneous that CEO Elon Musk even weighed in on Twitter yesterday, shedding a bit of light on the situation.
On July 13th, in response to a Spaceflight Now article detailing a few of those setbacks, Musk revealed that SpaceX is “being extra paranoid” – presumably the cause of most of the recent delays. Per Musk, “maximizing [the] probability of [a] successful launch is paramount” to SpaceX – not exactly a shocking revelation but still good to hear. Over the last six or so weeks, SpaceX has attempted to substantially ramp its launch cadence, targeting an unprecedented four launches in June 2020.
Delays reared their head, however, beginning with Starlink-9 around the last week of the month. SpaceX simply carried its four-launch-month ambitions into July, although that goal has already been pushed out of reach before the first launch of the month. As of July 1st, SpaceX has completed 11 launches in 2020 and has at least another 16 within tentative launch targets in the second half of the year. To complete all 16, the company would have to average almost three launches per month for the rest of 2020, a cadence it’s only managed to sustain for two or so months at a time.
Before ANASIS II’s indefinite delay was announced, Falcon 9 booster B1058 was on track to smash the world record for the fastest turnaround of an orbital class rocket, beating NASA’s Space Shuttle by ~20% (9 days). Somewhat ironically, some concerns surrounding the unflown upper stage have triggered said delay, while the record-breaking B1058 booster was apparently ready for launch. Like Starlink-9, ANASIS II’s delay is indefinite, meaning that it could last just a few days or stretch weeks into the future. If SpaceX manages to turn around for a second launch attempt before July 26th, though, B1058 still has a shot at becoming the world’s most rapidly reusable orbital-class rocket.
Meanwhile, Starship SN5 has been slowly wading through delay after delay as SpaceX’s South Texas team prepares the rocket for its first wet dress rehearsals (WDRs) with live propellant and its first Raptor engine ignition tests (i.e. static fires). As few as a few days after that test is complete, SpaceX wants to launch the massive steel rocket on the first full-scale hop test, potentially reaching 150m (500 ft) or higher before attempting to land nearby.
Prior to numerous delays, Starship SN5’s first static fire was expected to occur as early as late June or early July. As of now, SpaceX appears to be targeting the first wet dress rehearsal (WDR) with live methane and oxygen propellant (a precursor to any flight test) no earlier than (NET) July 15th to test SN5’s “fuel pump.” If successful, SpaceX would presumably move into static fire operations within a few days, followed another few days later by the first hop test attempt if the static fire was also successful.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.
Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.
Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
