News
SpaceX’s Starship explosion explained by Elon Musk
Shortly after a briefing following SpaceX’s flawless astronaut launch debut, CEO Elon Musk casually revealed the best explanation yet for why a Starship prototype violently exploded during testing on May 29th.
On that fated Saturday, SpaceX successfully completed the fifth static fire of a Raptor engine installed on a full-scale Starship prototype, preceded by about an hour and a half of vehicle checks and propellant loading. Unfortunately, around a minute after Raptor shut down, what was quickly identified as liquid methane began spurting out of a specific section at the base of Starship, rapidly creating a massive cloud as the cryogenic propellant boiled and turned into gas. The specific source is unclear but moments later, something under Starship SN4 provided the shock or spark needed to ignite the expanding fire hazard, producing a spectacularly large and violent explosion.
Unsurprisingly, the accidental fuel-air explosion that was created obliterated Starship SN4 in the blink of an eye, shredding its lower (liquid oxygen) tank into steel confetti and immediately breaching the upper (liquid methane) tank, which fell to the ground and subsequently exploded again. The launch mount Starship was staged on was also damaged beyond repair and has been fully dismantled and scrapped in the two days since the anomaly. Thankfully, however, SpaceX already has replacement mounts and ships well on their way to carrying Starship SN4’s torch forward and Elon Musk already seems to understand what caused the prototype’s demise.
Shortly after a post-launch briefing celebrating and discussing SpaceX’s inaugural astronaut launch on May 30th, Reuters reporter Joey Roulette was able to ask Musk about Starship SN4’s spectacular demise the day prior. The SpaceX CEO was quoted saying that “what we thought was going to be a minor test of a quick disconnect ended up being a big problem”, confirming suspicions based on careful analysis of public views of the explosion that it was caused by issues with Starship’s ground support equipment (GSE).

In Musk’s statement, “quick disconnect” (QD) refers to an umbilical port that connects a launch vehicle to GSE, enabling the loading and offloading of propellant and fluids, clamping down the rocket, and providing a wired telemetry and communications link for ground controllers. QDs must perform all those tasks while also being able to rapidly release and disconnect, allowing the rocket to lift off while still protecting its sensitive ports for ease of reuse.
In theory, Starship’s quick-disconnect umbilical panel is even more complex, as it will have to simultaneously enable the ship to be fueled and controlled while sitting on top of a Super Heavy booster and permit in-orbit docking and refueling. Given that Starships are currently being tested independently on spartan launch mounts, it’s unclear if the current generation of prototypes has been outfitted with advanced QD panels. More likely, Musk was referring to a test of a less advanced QD panel similar to the rough version used on Starhopper last year, and SpaceX simply wanted to test its ability to disconnect and reconnect to Starship on command.


If that’s the case, the likeliest explanation for SN4’s explosion is that that quick disconnect was unable to fully reconnect after the test, resulting in a leak from the liquid methane port when SpaceX began to detank the rocket. Instead of the highly-pressurized fluid flowing smoothly back to ground storage tanks, the liquid methane sprayed wildly, akin to the effect one might observe when attempting to block off an active water source with an open palm.


Compared to the many possible ways a fueled Starship could fail, a propellant leak started by a faulty umbilical panel is about as convenient as they come. Starship SN4 may have been violently destroyed as a result, turning a relatively small error into exceptionally painful lesson but SpaceX has already had some success building full-scale prototypes at an almost unbelievably low cost – likely less than $10M apiece. Starship SN5 appears to be just shy of ready to take SN4’s place on the launch mount, although SpaceX will have to build an entirely new launch mount before it can resume testing.
At the same time, Starship SN5’s successor – SN6 – is just one stacking event away from reaching a level of completion similar to SN4 and SN5. All told, Starship SN4’s demise is just another part of the process of developing a new kind of rocket by building and testing hardware – failure can be a valuable tool when managed properly. Based on past observations, SpaceX could be ready to continue testing (and hopefully flying) Starship prototypes before the end of the month.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
SpaceX moves to challenge AT&T, Verizon with Qualcomm-powered 5G
SpaceX has selected Qualcomm Technologies to supply core infrastructure for Starlink Mobile’s planned nationwide terrestrial 5G network in the United States.
Announced on November 4, the multi-year agreement covers radios, baseband units, and commercial-grade Layer 1 software based on Qualcomm’s Dragonwing Cellular Infrastructure platforms, specifically the QRU100 and QDU100:
🚀 SpaceX has picked Qualcomm to supply radios, baseband units and Layer 1 software for Starlink Mobile’s nationwide terrestrial 5G network.
Deployment across tens of thousands of U.S. cell sites starts in 2027. Qualcomm calls it its biggest 5G deal yet. https://t.co/YKLRakuJjB
— TESLARATI (@Teslarati) November 4, 2026
These will power Massive MIMO radio units featuring 64 transmit and 64 receive paths (64T64R), designed to boost coverage, capacity, and spectral efficiency at scale. Qualcomm has described the pact as its largest 5G deal to date, with deployment across tens of thousands of U.S. cell sites scheduled to begin in 2027.
The terrestrial build-out is meant to complement, not replace, Starlink’s satellite direct-to-cell capabilities. SpaceX has assembled substantial spectrum holdings for this purpose: roughly 65 MHz of mid-band frequencies acquired from EchoStar (including AWS-4 and related bands) and up to 14 MHz of low-band 800 MHz spectrum from Grain Management.
The low-band airwaves improve indoor penetration and range, while mid-band supports higher capacity. SpaceX executives, including President Gwynne Shotwell, have outlined a hybrid architecture in which satellites eliminate outdoor dead zones and terrestrial nodes add capacity where demand is highest.
Earlier comments suggested small cells or femtocells potentially co-located with existing Starlink user terminals on roofs, though later filings also reference more conventional antennas on towers and structures.
The big picture is SpaceX’s bid to become a full-fledged U.S. mobile carrier rather than a satellite partner or dead-zone filler. AT&T, Verizon, and T-Mobile together generate hundreds of billions in annual wireless revenue; Shotwell has said SpaceX expects to win customers by offering superior coverage, including during disasters, through seamless satellite-terrestrial handoff.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Starlink already represents a major share of SpaceX’s revenue and profit following the company’s 2026 IPO. By vertically integrating spectrum, satellite manufacturing, launch capacity, and now ground radio equipment, SpaceX aims to control more of the connectivity stack.
Qualcomm’s involvement also positions the network for future evolution toward AI-native 6G infrastructure, with energy-efficient processing that could improve deployment economics.
Challenges remain: spectrum depth still lags the Big Three, capital costs for tens of thousands of sites will be substantial, and regulatory approvals continue, but the Qualcomm deal marks a concrete step from spectrum accumulation toward operational network build-out.
In short, the partnership accelerates Starlink Mobile’s shift from orbital broadband specialist to hybrid mobile competitor, testing whether a space-based company can reshape terrestrial wireless economics and coverage in the world’s largest market.
Elon Musk
Elon Musk’s Grok Bot is picking up the phone now, and the first calls are wild
Elon Musk wants Grok Bot users making phone calls, and one Comcast call saved $500.
Elon Musk is pushing Grok Bot users toward a feature that, until this week, few of them could actually use. “Try asking Grok @Bot to make calls!” Musk wrote on X Tuesday afternoon, quoting a demo from Sawyer Merritt that included audio from a live call.
Musk first announced calling on October 25, writing that the agent could “call someone or a business for you, make a request on your behalf, take notes on the response and send you a note summarizing the conversation.” There were no release notes at the time, and the feature only appeared in preview builds. That changed on Tuesday, when creator Peter Yang said all Grok Bot users should now be able to call US businesses. Musk reposted his demo.
Try asking Grok @Bot to make calls! — Elon Musk (@elonmusk) November 3, 2026
Yang’s call shows how far the feature goes. In his video, his bot dialed Comcast, worked through the phone menu, deflected small talk about the weather by saying it does not “have eyes on the sky,” turned down three upsells and used a cheaper fiber offer from competitor Sonic as leverage. His bill dropped from $84 to $45 per month on a faster plan, a savings of nearly $500 a year. The call ran about 25 minutes, and the bot paused to get Yang’s approval before accepting the final terms.
Merritt described what the user sees: a live transcript runs during the call, and when the business asks for something the bot does not know, an answer box pops up in the chat. The user types a reply and Grok relays it to the person on the line. Other users posted results Tuesday, including a $100 gift card recovered from Verizon Fios after a 51 minute call and a same day pediatric appointment, which Musk also shared. Not every call worked. One user said a rep refused to cancel a subscription once it was clear an AI was on the phone.
Grok @Bot can now call someone or a business for you, make a request on your behalf, take notes on the response and send you a note summarizing the conversation! — Elon Musk (@elonmusk) October 25, 2026
The Grok Bot terms require every call to identify itself as a virtual assistant calling on the user’s behalf and warn that calls may be recorded. Marketing, mass calling and impersonation are prohibited, and calling currently works only with US numbers.
The timing stands out. Days ago, users began hitting their weekly limits early, and Musk said the cost of serving Grok Bot was “unsustainably high relative to revenue,” as Teslarati reported. A call that spends most of its 25 or 50 minutes on hold is the kind of long running task that eats into usage, and SpaceXSI has not said how calls count against the weekly pool. Grok Bot is included from the $30 Premium tier of The X Subscription upward.
For Tesla owners, the agent has been in their cars since September 22 and is enabled across every Cybercab and Model Y Robotaxi. Musk has already pitched it for phone chores like scrubbing your number from spam call lists. Neither Tesla nor SpaceXSI has confirmed whether a bot can place one of these calls on request from inside the vehicle.
News
Tesla Full Self-Driving gets hit with some adjustments in Europe
Tesla Full Self-Driving, which is now referred to in Europe as “Tesla Assisted Driving” (TAD), is getting hit with a handful of new changes at the hands of the Netherlands’ vehicle authority, the RDW (Rijksdienst voor het Wegverkeer).
On 3 November, the RDW announced that it has assessed and approved a set of changes to Tesla’s FSD Supervised driver-assistance system. The updates introduce the official European name TAD and impose stricter controls on the system’s speed behaviour.
The new name will appear on the in-car display, in the owner’s manual, and in all other driver-facing information. The change applies to Tesla models equipped with Tesla Assisted Driving and hardware version 4.0 (HW4) or later.
Importantly, the RDW stressed that the name change does not alter the system’s fundamental operation: it remains a supervised driver-assistance feature that supports the driver in performing driving tasks. The driver stays fully responsible for controlling the vehicle at all times.
Beyond the rebranding, the most significant functional adjustments concern speed settings. Drivers will still be able to set a speed margin, a percentage by which the system may exceed the applicable speed limit when necessary for safety or traffic flow. However, the maximum allowable margin has been reduced from +50% to a maximum of +10%.
In addition, every time the vehicle is started, the speed-margin setting will default to 0% deviation, and other speed-related functions will be disabled by default. These changes will be delivered through an over-the-air (OTA) software update from Tesla.
Tesla requested the RDW’s review of these “minor changes.” After evaluating how the modifications were implemented and how the system behaves, the authority found no adverse or unintended effects on the system’s operation or the vehicle’s driving behaviour. Consequently, the existing type approval remains valid under the same conditions and for the same use; no amendment or extension of the approval is required.
The RDW has informed the nine EU member states that have already accepted its type approval—Belgium, Denmark, Estonia, Croatia, Latvia, Lithuania, Slovenia, Slovakia and Czechia—about the updates. Broader EU-wide approval is still under discussion within the European Technical Committee on Motor Vehicles (TCMV). Those proceedings remain confidential, and the RDW has declined to comment on them.
The approved changes align with earlier discussions involving German authorities, which had advocated both for clearer naming to avoid misleading drivers and for a tighter speed offset.
By formally incorporating these adjustments while leaving the core type approval intact, the RDW has cleared the way for Tesla to roll out the updated TAD software via OTA to eligible vehicles in the Netherlands and the other countries that recognise the Dutch approval. The system continues to function strictly as supervised driver assistance, with the human driver remaining the responsible party.