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.
Tesla is bolstering its Cybercab fleet with the State of Texas’s regulatory bodies ahead of the planned launch of the all-electric ride-hailing vehicle this Thursday.
Seven purpose-built Tesla Cybercabs have been added to Texas’s official automated vehicle registry, appearing in the Texas Motor Carrier Credentialing System (TxMCCS) public lookup just three days before Tesla’s invite-only Cybercab launch event in Austin on September 3.
The records, visible through TxDMV’s Motor Carrier and Automated Motor Vehicle Operator Lookup, list seven 2026 Tesla Cybercabs under Tesla Robotaxi, LLC. Their VINs begin with the 5YJA prefix, distinct from the 7SAYG Model Y robotaxis that already dominate Tesla’s Texas fleet.
Community trackers that scrape the same public database recorded the new entries on August 31, bringing Tesla’s authorized Texas robotaxi total to 276 vehicles: 269 Model Ys and the seven Cybercabs:
🚨 There are now SEVEN Tesla Cybercabs registered with the state of Texas
We are just three days from Cybercab! pic.twitter.com/ndwhuFYsep
— TESLARATI (@Teslarati) August 31, 2026
Texas Senate Bill 2807, which took effect in late May 2026, created a self-certification framework for commercial Level 4 operations. Operators file through TxMCCS, attest to SAE Level 4 capability, maintain insurance, and keep an active vehicle list.
Tesla completed that process months earlier for its existing Model Y Robotaxi service, which has carried paying passengers in Austin, Dallas, Houston and other markets. Adding the Cybercabs to the same authorization means the new two-seat, steering-wheel-free vehicles are now legally recognized for commercial use on Texas roads.
The timing is deliberate as Tesla scheduled the September 3 event at its Austin campus after sending invitations to selected Robotaxi riders and other guests. The company has described the evening as a chance to “experience the future of full autonomy” and plans to livestream it.
Production Cybercabs, which lack pedals and a steering wheel, have been rolling off the Giga Texas line for months; some earlier examples still carried temporary driver controls for data collection. Registering a small fleet of the finished design immediately before the public event signals that Tesla intends to move the purpose-built vehicle from factory and test tracks into the same Robotaxi app already used by Model Y passengers.
The seven units remain a tiny fraction of Tesla’s overall Texas authorization and far smaller than competing fleets. Registration does not automatically equal unsupervised public rides; it is the legal prerequisite.
Still, the sudden appearance of Cybercab VINs in the state’s lookup system, after a year of Model Y-only listings, is the clearest official confirmation yet that Tesla’s dedicated robotaxi hardware is entering the regulatory pipeline at the same moment the company is preparing to show it to invited guests and a global livestream audience.
Whether those seven vehicles appear at the September 3 event or begin carrying passengers shortly afterward, their presence in TxMCCS marks a concrete regulatory step that has been anticipated since the Cybercab concept was first revealed.
Tesla has expanded the operational geofence for its driverless Robotaxi service in Austin, Texas, marking the first such increase in some time. The updated Service Area for Robotaxi in Austin now spans about 288 square miles and is roughly 9 percent larger than the previous boundary.
This incremental growth adds approximately 24 square miles of coverage, bringing the prior zone of roughly 264 square miles into a broader footprint that better serves northern suburbs.
The expansion extends the geofence northward toward Pflugerville along the US 183 corridor, incorporating additional neighborhoods north of the Domain and areas such as Mesa Park. These additions include higher-end residential and commercial districts that previously sat just outside the allowed operating zone.
Riders can now request unsupervised trips that begin or end in these newly included locations, provided the entire route remains inside the digital boundary:
Tesla has just expanded its Robotaxi service area in Austin, Texas for the first time in 10 months.
The new service area is roughly 9% larger than the old one, and is about 288 square miles in total. pic.twitter.com/i4oBM1KfWS
— Sawyer Merritt (@SawyerMerritt) August 31, 2026
Tesla first launched public Robotaxi operations in Austin in mid-2025 with a modest initial zone of about 20 square miles. Subsequent enlargements in 2025 and early 2026 steadily grew the map until it covered much of the metropolitan area.
After the last major update roughly ten months earlier, the company held the boundary steady while it collected additional miles and refined the FSD suite.
The modest nine percent increase still matters for daily utility. Longer trips become possible, more residents gain access, and the fleet can accumulate more diverse real-world data across new road types and traffic patterns. Observers note that the added territory aligns with existing Tesla service infrastructure, which could support more efficient vehicle staging in the North end of Austin.
Although the geofence has grown, Tesla continues to operate a relatively small unsupervised fleet in the city. The company has emphasized safety and software readiness over rapid geographic scaling. This latest map update signals that Tesla remains committed to expanding Robotaxi availability in its home market as it prepares for further software improvements and potential Cybercab deployments.
The 288-square-mile zone now gives Austin riders one of the larger driverless service areas currently available in the United States.
Tesla’s 2026 Summer Update turns Grok from a talking companion into a true in-car controller, with considerably expanded capabilities. Where the assistant once answered questions and handled navigation, it can now operate hardware and software through ordinary speech, including several requests at the same time.
Grok has become incredibly robust over the past few quarters, and this new ability that Tesla has included with its Summer Update is perhaps the clearest sign of just how capable it has become.
You can issue many commands to Grok at once, and each will be taken care of: anything from headlight control to climate adjustments to mirror folding can now all be taken care of with a simple sentence spoken toward Grok:
This is cool, you can now give Grok a ton of commands at once in your Tesla and it’ll do them all together.
The commands I gave:
• Fold mirrors
• Turn on wipers to fastest setting
• Change temp to 65°
• Open self-driving app
• Open gloveboxComes with Tesla’s 2026 Summer… pic.twitter.com/drZxoHrknv
— Sawyer Merritt (@SawyerMerritt) August 26, 2026
Here’s another example I used in my Model Y:
🚨 Using Grok to control the cabin temperature and turn on headlights in 2026 Model Y on FSD v14.3.8 and 2026.26.6.5 pic.twitter.com/7clgQkGABk
— TESLARATI (@Teslarati) August 27, 2026
Tesla’s official Release Notes list the core powers of Grok’s new capabilities: Grok can place phone calls from a paired phone, search a streaming service and queue music, adjust climate, and search the Controls panel. Drivers can also ask it questions about the vehicle or the latest features included in a recent software update.
It can also take care of driving settings, dynamics, and other relevant preferences that deal with how the car operates and handles.
Tesla Summer Update begins rolling out: a look at the new features
It’s also more of a use case than a novelty feature. Grok was great for learning about something that was being pondered while Full Self-Driving was taking care of the major automotive responsibilities, but it did have some useful functionality when it came to navigation.
Another less-noted improvement is the swift transition that Grok has from thinking of its answer to giving you one. In the past, it would take a few seconds for Grok to truly come up with a valuable response. It now seems that it is improving, at least slightly.
Tesla Cybercab fleet grows in Austin ahead of launch event
Tesla expands driverless Robotaxi geofence in Austin
