News
SpaceX fires up Starship and Super Heavy booster hours apart
SpaceX appears to have successfully fired up a Starship and Super Heavy booster hours apart, testing a total of three new Raptor 2 engines on the two rockets.
SpaceX says it completed a two-engine static fire with Starship 24 less than three hours after the company successfully ignited a Raptor 2 engine installed on a rocket prototype for the first time. That earlier test, performed by Super Heavy Booster 7, was also the first time SpaceX used its new Starbase orbital launch site to support a static fire test and the second-ever static fire of a Starship booster prototype. Had the company called it quits after Booster 7 survived its first intentional trial by fire, it would have still been an exceptionally successful day.
But SpaceX wasn’t done.
Instead, after Booster 7’s seemingly flawless single-Raptor static fire at 5:25 pm CDT, SpaceX loaded Starship 24 with a small amount of liquid oxygen and methane propellant and ignited two of the ship’s six engines around 8:18 pm. It was not initially clear how many engines were involved but a tweet from SpaceX later confirmed it was two. More likely than not, one of those engines was a sea level-optimized Raptor with a smaller bell nozzle and the other was a vacuum-optimized Raptor with a much larger nozzle.
Almost ten months ago, Starship 20 – SpaceX’s first potentially orbital-class Starship prototype – began static fire testing in a somewhat similar way. Its first day of static fires began with a single Raptor Vacuum engine and ended with a simultaneous RVac and sea-level Raptor test in October 2021. In some ways, SpaceX has been a bit less cautious with Starship 24, which is the second potentially orbital-class prototype to begin proof testing. Ship 24 already has all six Raptors installed, whereas Ship 20 only had four of six engines installed during its first static fire tests. SpaceX also took about three weeks to progress from Ship 20’s first static fire test to its first static fire of all six engines, whereas it appears that Ship 24 could potentially attempt its first six-engine test just a few days to a week later.
On the other hand, Ship 24’s path to its first static fire was substantially longer than Ship 20’s. Ship 20 completed its first static fire test(s) just 25 days after its first proof test, referring to the process of verifying that the prototype was in good working order before moving on to riskier testing with flammable propellant and intentional ignitions. Ship 20 also completed its first six-engine static fire 46 days after testing began. Ship 24, meanwhile, took 75 days to go from its first proof test to its first static fire – almost three times slower than Ship 20, a prototype that was essentially the first of its kind.
It’s possible that Ship 24’s upgraded Raptor 2 engines are partially or fully to blame. Instead of jumping straight into ‘hot’ Raptor testing like Ship 20, which began that particular campaign with a partial-ignition preburner test, SpaceX put Ship 24 through seven ‘spin-prime’ tests before its first static fire. For Raptor, spin-primes test the ignition step before preburner ignition, which is itself a step before main combustion chamber ignition (where the engine starts to produce meaningful thrust). Raptor startup procedures likely involve flowing high-pressure gaseous helium, nitrogen, or propellant (oxygen/methane) through the engine to spin up its turbopumps, ‘priming’ them for preburner and main combustion chamber ignition.
On Raptor 1, the preburners would ignite once a high enough flow rate was achieved, producing hot gas that the main combustion chamber would mix and ignite one last time to start the engine. In a recent interview with Tim Dodd (“The Everyday Astronaut”), CEO Elon Musk revealed that SpaceX was able to “remove torch igniters” from Raptor 2’s main combustion chamber (MCC). It’s unclear if that means that Raptor 2 now has zero MCC igniters, but a major change in the overall ignition process could explain why the start of Ship 24 and Booster 7 engine testing was so sluggish. So could the unintended explosion Booster 7 caused when SpaceX attempted to spin-prime all 33 of its Raptor 2 engines at once.
Regardless, SpaceX has finally crossed that particular Rubicon and, with any luck, Raptor 2 testing will begin to speed up on both Starship 24 and Super Heavy Booster 7. SpaceX has test windows scheduled on August 11th, 15th, and 16th. A warning distributed to Boca Chica, Texas residents on August 10th confirmed that the company intends to perform at least one more static fire test on the 11th.
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.
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.
SpaceX moves to challenge AT&T, Verizon with Qualcomm-powered 5G
Elon Musk’s Grok Bot is picking up the phone now, and the first calls are wild
