News
SpaceX Starship blew its top during rocket fueling test (updated)
Update: SpaceX has released an official statement indicating that Starship Mk1’s November 20th failure came after a decision to intentionally pressurize the rocket prototype to its limits. This likely means that the test was to max flight pressures and not an intentional burst test, so Starship’s dome failure is still a significant concern and was definitely not planned.
More importantly, SpaceX says that it had already decided to retire Starship Mk1 before any kind of flight testing, treating the vehicle as a pathfinder. Instead, SpaceX will build and use Starship Mk3 – the next Boca Chica prototype – for Starship’s first attempted skydiver-style landing and 20 km (12 mi) flight test.
SpaceX statement on the above test and incident: pic.twitter.com/r1ReRYhUhz— Michael Sheetz (@thesheetztweetz) November 21, 2019
SpaceX’s first full-scale Starship prototype has suffered a significant failure during testing, destroying or severely damaging large sections of the rocket. However, SpaceX CEO Elon Musk has already commented on the anomaly and is not all that concerned.
On November 20th, SpaceX – having canceled a planned road closure the day prior – unexpectedly requested a last-second road closure and entered into a much more serious round of testing with Starship Mk1, the rocket’s first full-scale prototype. This followed testing on November 18th that concluded with Starship Mk1’s very first ‘breath’ – some venting activity near the end of a tank proof test. SpaceX technicians spent the next 36 or so hours inspecting and working on Mk1, presumably looking for and patching minor leaks along its tank section.
The November 20th testing progressed far faster than the previous round of tests and Starship Mk1 was quickly venting again. Soon after that, frost began to appear on the exterior of its steel liquid oxygen and methane tanks, a telltale sign that some form of cryogenic testing was ongoing. Based on a distinct lack of activity at the nearby flare stack, SpaceX was using liquid oxygen (LOX) or liquid nitrogen (LN2) to verify that Starship performs as expected when filled with supercool propellant.
After initial venting and visible frost formation, SpaceX appeared to push forward, rapidly loading Starship Mk1 with LOX or LN2. This progress was easily visible thanks to the fact that the mass and pressure of all that cryogenic liquid made quick work of the slight imperfections on the exterior of Starship’s steel hull, turning the vehicle’s reflection from a speckled patchwork to an almost mirror-like finish. Roughly half an hour later, the otherwise peaceful scene was interrupted by the rapid failure of Starship Mk1’s upper LOX tank dome, instantly thrown several hundred feet into the air.
Seconds later, the crumpled upper half of Starship Mk1’s tank section appeared out of the clouds created and began hemorrhaging a huge volume of liquid oxygen, immediately boiling and vaporizing as it was exposed to the Earth’s comparatively white-hot atmosphere. Impressively, Starship appeared to remain functional after its top quite literally blew off, and the vehicle rapidly detanked and appeared to safe itself. Some ten minutes after the overpressure event, the freed liquid oxygen had boiled to nothing and Starship appeared to be quiet.





By all appearances, Starship Mk1 appeared to perform extremely well as an integrated system up to the point that its upper tank dome failed. The first frame from LabPadre’s stream with anything visibly amiss explicitly implicates the weld connecting the LOX dome to the cylindrical body of Starship’s LOX tank, point to a bad weld joint as the likeliest source of the failure. Although that hardware failure is unfortunate, Mk1’s loss will hopefully guide improvements in Starship’s design and manufacturing procedures.
Moving forward
Minutes after the anomaly was broadcast on several unofficial livestreams of SpaceX’s Boca Chica facilities, SpaceX CEO Elon Musk acknowledged Starship Mk1’s failure in a tweet, telegraphing a general lack of worry. Of note, Musk indicated that Mk1 was valuable mainly as a manufacturing pathfinder, entirely believable but also partially contradicting his September 2019 presentation, in which he pretty clearly stated that Mk1 would soon be launched to ~20 km to demonstrate Starship’s exotic new skydiver landing strategy.
Musk says that instead of repairing Starship Mk1, SpaceX’s Boca Chica team will move directly to Starship Mk3, a significantly more advanced design that has benefitted from the numerous lessons learned from building and flying Starhopper and fabricating Starship Mk1. The first Starship Mk3 ring appears to have already been prepared, but SpaceX’s South Texas focus has clearly been almost entirely on preparing Starship Mk1 for wet dress rehearsal, static fire, and flight tests. After today’s failure, it sounds like Mk1 will most likely be retired early and replaced as soon as possible by Mk3.
Above all else, the most important takeaway from today’s Starship Mk1 anomaly is that the vehicle was a very early prototype and SpaceX likely wants to have vehicle failures occur on the ground or in-flight. As long as no humans are at risk, pushing Starship to failure (or suffering unplanned failures like today’s) can only serve to benefit and improve the vehicle’s design, especially when the failed hardware can be recovered intact (ish) and carefully analyzed.
A step further, SpaceX is simultaneously building a second (and third) Starship prototype at its companion Cocoa, Florida facilities, and Starship Mk2 is nearly finished. Coincidentally, technicians installed its last tank dome – the same dome that failed on Mk1 – just days ago, and any insight that the Boca Chica team can gather from Mk1’s troubles will almost certainly be applied to Mk2, whether that means reinforcing its existing domes or fully replacing the upper dome with an improved design.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Lifestyle
Tesla’s mirrorless Cybercab will give riders a visibility upgrade
Tesla engineer confirms Cybercab update letting riders pull up rear and repeater cameras on demand.
Tesla is working on a Cybercab update that would let passengers pull up the vehicle’s rear and side cameras on demand, and the request came straight from a rider.
The exchange played out on X late Friday. Cybercab rider Dan Burkland shared photos of the two-seater’s cabin screen after an evening ride, praised the UI team’s work, and left one request: let riders open the rear and repeater cameras whenever they want, “especially for peace of mind.” Tesla UI software engineer Evan (@CarCoder) answered with two words: “In development.”
The Tesla UI team absolutely crushed it with the infotainment software. Nicely done @CarCoder!
One feature request: Allow folks to pull up the rear & repeater cameras on demand. This would be great especially for peace of mind. https://t.co/mNAOSLx6pE
— Dan Burkland (@DBurkland) October 10, 2026
The idea fits a pattern Teslarati has tracked since public rides began. Days after paid Cybercab service opened in Austin, Tesla sent riders a survey that asked them to rate the touchscreen, the app and the cabin, and to pick the features they wanted most. We reported on that survey in September, and a camera view is the kind of small software change Tesla can push quickly if riders keep asking.
It also speaks to something unique about the vehicle. With no steering wheel, no pedals and no driver, passengers have no mirror to check and no way to see behind them. The hardware is clearly built for camera awareness, from the repeater cameras to the rear camera. Letting a passenger look through those same cameras would give a nervous first time rider a way to confirm what is around the car.
The timing matters because the fleet is growing fast. Tesla’s Robotaxi account said on Saturday that more than 300 Cybercabs are now serving Austin, an eightfold increase in 30 days, and Tesla AI chief Ashok Elluswamy named Dallas as the next city. More cars and more cities mean more people riding in a driverless vehicle for the first time, which is exactly when small trust features carry weight.
For now, the feature is confirmed only as in development. If Tesla follows its usual pattern with Cybercab software, riders could see it appear in a point release without any announcement, and Teslarati will watch for it.
News
Tesla’s Cybercab fleet jumped 8x in a month, with Dallas up next
Tesla confirms its first official Cybercab fleet number as Austin scales fast and Dallas looms.
Tesla says more than 300 Cybercabs are now serving Austin, the first time the company has put an official number on its active Cybercab fleet. The figure came from the Robotaxi account on X on Saturday, which wrote that one month after launch the service had “scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days.”
Ashok Elluswamy, Tesla’s head of AI software, quoted the post with a line that carried the bigger news. “Two years since the 10/10 Cybercab WeRobot event, the cabs are everywhere in Austin now. Dallas soon,” he wrote. It is the first time Tesla has named the next city for public Cybercab rides.
One month after launch, we’ve scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days https://t.co/EagJy2JAsm
— Robotaxi (@robotaxi) October 10, 2026
Tesla opened Cybercab rides to the public in Austin on September 4, as Teslarati reported, a day after an invite only launch event. The ramp since then has been steep. Our September 28 report had the fleet at well over 100 units after availability jumped from 58 to 125 in a single week. On Thursday, Tesla added 150 Cybercabs to the Texas automated vehicle registry, lifting its registered count to 319 from 169. The first seven appeared on the registry on August 31.
RobotaxiTracker, a community site that counts vehicles from sightings and state records, listed 275 vehicles in unsupervised service in Austin on Saturday, 105 of them Cybercabs, which is well below Tesla’s figure. Tracker counts can lag official numbers, though Sawyer Merritt noted that Cybercab wait times in Austin stayed short on Saturday evening even with more than 2,000 fans in town for X Takeover.
Regulators are watching the rollout. NHTSA opened an audit query into Tesla’s certification that the Cybercab meets federal safety standards, and sworn answers are due October 30. Tesla reports third quarter earnings on October 21, which gives the company a natural venue to define its fleet numbers and put a date on Dallas.
Elon Musk
Elon Musk roasts India’s billionaire Mukesh Ambani as Starlink fight heats up
Elon Musk sarcastically calls Mukesh Ambani ‘Prime Minister’ as the Starlink India standoff escalates again.
Elon Musk escalated his public fight over Starlink’s launch in India on Friday, addressing Reliance chairman Mukesh Ambani as “Prime Minister Ambani” in a sarcastic post on X. “Please accept my humble apologies for not realizing that you are the real boss of India,” Musk wrote, before accusing Ambani of “monopolistic exploitation” and asking whether he would “consider allowing Starlink to compete.” In follow up posts, he said Starlink has proven essential during natural disasters and would help parts of India with no internet access.
The post came two days into a fight that Musk sparked up on Wednesday, when he said Starlink was “being blocked by certain oligarchs in order to maintain their monopolistic chokehold on the Indian people.” He called it “a crime against the people of India” and left the names out, adding only, “You can guess who they are.” Jio and Airtel together hold more than 80% of India’s telecom market. On Thursday, Musk asked whether Ambani is “the real boss of India” and said Starlink has spent five years complying with “every single law and requirement” of the Indian government.
Dear Prime Minister Ambani,
Please accept my humble apologies for not realizing that you are the real boss of India.
Naturally, you would prefer to maintain your monopolistic exploitation of the great people of India, but would you nonetheless consider allowing Starlink to compete?
There are many areas of India, as there are in all countries, with no Internet access, which denies children the opportunity for education and for small businesses the opportunity to sell their goods to a global market. Starlink would change their lives for the better.
Thank you 🙏
— Elon Musk (@elonmusk) October 9, 2026
India’s government has pushed back each time. The Ministry of Communications called the suggestion that its framework is unfair or discriminatory “baseless and misconceived.” Communications Minister Jyotiraditya Scindia said Friday that three companies hold satcom licenses: Starlink, Jio Satellite Communications, and Bharti backed Eutelsat OneWeb. Amazon’s Kuiper, now Amazon Leo, is still going through the process. None can launch until regulators finalize satellite spectrum pricing and the Home Ministry signs off on each company’s security compliance. Scindia said the telecom regulator and the Department of Telecommunications are close to a decision on pricing, The Hindu reported. Bharti chairman Sunil Mittal also said OneWeb is still waiting on approvals.
Starlink received its operator license in 2025 after a three year wait, and the space regulator IN-SPACe granted what industry executives called the last approval needed in July. The holdup since then centers on security, particularly concern that foreign operators could bypass Indian gateways.
Musk and Ambani have been on opposite sides of this before. In late 2024, Ambani argued for auctioning satellite spectrum, which Musk criticized as out of step with the rest of the world, and India chose administrative allocation instead. By March 2025, the two sides had signed a deal to sell Starlink devices in Reliance stores, and Starlink secured its telecom license that June. That partner is now also a competitor. Jio is reportedly weighing a constellation of 1,600 to 1,650 satellites costing an estimated $10 billion to $15 billion, while Akash Ambani has told shareholders Jio plans to lease capacity from global providers to move quickly.