News
SpaceX Starship booster heads to launch pad for the fifth time
For the fifth time in five months, SpaceX has transported its most advanced Starship booster prototype from the Starbase factory to the launch pad, setting the stage for another round of testing.
Super Heavy Booster 7 (B7) returned to the factory for the fourth time on August 12th after becoming the first prototype of any kind to perform a static fire engine test while installed on SpaceX’s orbital Starship launch mount. In the days prior, the booster completed two back-to-back static fire tests with one of the 20 Raptor engines installed on the rocket, both of which apparently gave SpaceX enough confidence to prepare for the next phase of testing.
That relatively cautious progress only came after SpaceX attempted to test all 33 of the prototype’s Raptors at once during its first engine test. Whether it was the fault of overzealous managers or executives or a genuine oversight is not clear, but the combined behavior of Super Heavy and the orbital launch pad was not properly characterized before testing began. As a result, the cloud of flammable gas the rocket released during its attempted 33-engine ‘spin-prime’ test found an ignition source and violently exploded on July 11th, causing damage throughout Booster 7’s aft engine section that required several weeks of repairs between July 15th and August 6th.
When the Super Heavy rolled to the pad for the fourth time on August 6th, it was missing all 13 center Raptors, leaving only the outer ring of 20 Raptor Boost engines partially installed for the tests that followed. Thankfully, things went much better on the second try and Booster 7 completed two spin-prime tests with a single Raptor engine, followed by two successful static fire tests on August 9th and 11th. The latter test was the longest Starbase static fire ever (by a factor of ~3) and lasted about 20 seconds, allowing SpaceX to test Booster 7’s autogenous pressurization. That system pressurizes Super Heavy’s tanks by turning small quantities of cryogenic liquid propellant into gas, ensuring that its tanks remain stable as they’re rapidly drained of thousands of tons of propellant.
On August 12th, Booster 7 returned to the factory, where workers installed the rocket’s 13 center engines for the second time. Booster 7 headed back to the orbital launch site (OLS) on August 23rd and the pad’s robotic launch tower used a pair of arms to lift the rocket off its transport stand and place it on the launch mount by the end of the day.
In addition to readying Booster 7 for its next phase of static fire testing, teams of SpaceX workers took advantage of the unplanned lull in testing to modify the orbital launch mount. It’s impossible to know what exactly was done without official confirmation, but it’s likely that SpaceX was attempting to quickly fix the shortcoming(s) that allowed the July 11th explosion to happen. Without a fix, it’s unlikely that SpaceX would want to proceed with plans to ignite large numbers of Raptor engines simultaneously – a series of tests that must be completed before Starship can safely attempt its first orbital launch.


It’s unclear what exactly that fix entails, but it could involve a system to constantly flood the engine section with fire-stopping nitrogen gas or potentially take the shape of a system of vents that will connect to every Raptor engine and remove methane gas before it can turn into flammable clouds.
It’s possible that Booster 7 has returned to the launch pad solely for fit checks or some other basic proof-of-concept testing. It’s also possible that the returns signifies that SpaceX is confident in its quick launch mount fix and ready to restart static fire testing.
As Booster 7 prepares for that next phase of testing, SpaceX may also be ready to restart static fire testing with Starship S24, which paused shortly before Super Heavy returned to the factory. SpaceX appears to be modifying the suborbital launch mount and test stand Ship 24 is installed on, which could explain the lack of ship testing since August 11th. SpaceX has 12-hour test windows tentatively scheduled on August 24th and 25th, either of which could be used to test either or both prototypes.
If all goes to plan, Ship 24 and Booster 7 will eventually complete all the qualification testing SpaceX can throw at them and be ready to support Starship’s first orbital launch attempt sometime before the end of 2022.
News
Tesla reveals plans for Robotaxi charging hub in Austin
Tesla has revealed plans through permit submissions for a massive Robotaxi charging hub in Austin, Texas.
Tesla plans to build the Supercharger hub in multiple phases, with the second phase potentially introducing wireless induction charging, something the company has been developing for the Robotaxi fleet.
Initially, 48 Tesla Robotaxi-geared Superchargers will be built on a lot just across from the St. Elmo, Texas, Service Center. There are about 80 additional spots that will not be impacted by phase 1 of the construction process.
Filings show that the second phase of the project will turn those 80 additional spots into wireless charging for Robotaxi, but it might be an error. The Key Notes state that item 3 is listed as “V4 Charging Cabinet to Support 80 Wireless Chargers in Phase 2. However, the drawings point to V3 Cabinets that are already tied to Superchargers:

There are roughly 128 total spots in the lot, but it is unclear if they will all be used for charging based on what appears to be some sort of typo in the blueprint.
A new Robotaxi fleet charging hub is coming soon to Austin, Texas!!
Permits have been filed for the installation of 48 (V3) stalls in a vehicle storage lot across the road from Tesla’s St Elmo service center. pic.twitter.com/xwRgSWDqht
— MarcoRP (@MarcoRPi1) August 18, 2026
This is among the first Robotaxi charging hubs Tesla has started to develop, as it currently has four others planned throughout various areas: one in Phoenix, one in San Antonio, another in Irving, which will serve the Dallas-Fort Worth area, and another in Las Vegas.
These projects are necessary as Tesla expands its Robotaxi program. Now that preparations have started for the public launch of Cybercab, Robotaxi will likely be expanding aggressively, especially over the next two to three years.
Last night, The Information reported that Tesla was planning to launch Cybercab as soon as the end of August. Hours later, Tesla then announced it was launching a competition for fans to potentially ride in Cybercab during its first public rides.
Tesla’s plan to expand its charging infrastructure in the regions where Robotaxi will initially operate is great preparation for the expanding service. There is still a lot to do, including launching the Cybercab on time.
News
Tesla Semi gets its largest order yet
Tesla got its largest order for the all-electric Class 8 Semi yet, a 500-unit order from Einride AB, a Swedish trucking company.
Einride made the announcement this morning following its second-quarter earnings call. The company said it plans to use 500 Tesla Semi units on its fleet intelligence platform, called Saga AI. The deployments will serve large companies like Amazon and will extend Einride’s electric freight network across logistics routes in California, New Jersey, Texas, Illinois, and Georgia.
🚨 Tesla has received a MASSIVE order from Swedish freight company Einride AB, which placed an order for 500 Tesla Semi trucks
Tesla’s biggest order for the Semi yet! pic.twitter.com/PrtLp5yzvh
— TESLARATI (@Teslarati) August 18, 2026
The deployment is being carried out in several phases over the next two years as Tesla ramps production of the Semi at its dedicated production facility in Sparks, Nevada. Einride will receive its first Semi units in September.
Saga AI
Saga AI is Einride’s dedicated fleet intelligence platform. It enables scaled adoption of electric trucks for freight use and allows shippers to integrate electric capacity without the operational burden or capital risks of managing a fleet. This helps integrate cost-efficient logistics and makes budgeting and forecasting much more accurate.
Tesla Semi’s Adoption
The Tesla Semi is now gathering large-scale clients past those who have helped the company operate a Pilot Program to gain initial information and feedback from real-world drivers.
Perhaps the biggest and most notable is that of Frito-Lay and PepsiCo., who have worked with Tesla for the past several years to dial in the finer details of the truck, including its efficiency and operation-related components.
Tesla Semi gets strange-but-understandable comparison from Jay Leno
There has been tremendous progress in that time, and it even catalyzed Tesla to make some design changes, which were unveiled earlier this year.
But Einride CEO Roozbeh Charli says his company’s partnership with Tesla will continue to push those things forward:
“This deployment is yet another proof point that we can execute at the scale our customers demand. Working closely with Tesla to bring next-generation Semis into active operations quickly and at scale is a testament to the strength of that partnership, and how quickly this technology is maturing from promise to daily operations.”
Additionally, Dan Priestley, the Director of the Semi Program at Tesla, said the partnership is ideal due to Einride’s focus on sustainable transport:
“Einride is at the forefront of sustainable freight, and we are thrilled to deepen our relationship with them through this order of 500 Semis. EV heavy trucks provide lower costs per mile from fuel savings, reduced maintenance, and better uptime over diesel trucks. These savings increase further through operational efficiency when deploying EV trucks at scale, and we are excited that Einride recognizes this and look forward to supporting their deployments.”
Elon Musk
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Elon Musk says X now exposes government censorship, but India’s secrecy laws complicate that promise.
Elon Musk’s promise to make government censorship requests on X “clearly visible” is running into a wall in India, where the law forbids the very disclosure Musk is promising.
On August 15, Musk responded to an update from X’s open-source algorithm team by writing “Any censorship required by governments is now clearly visible.” The claim referred to a change X pushed two days earlier to its public xai-org/x-algorithm repository, which now includes a controversial filter written directly into the code. The filter suppresses posts from 665 accounts flagged by Brazil’s Superior Electoral Court from appearing in the For You feed of any viewer located in Brazil, unless the viewer already follows the account. The election tied to the filter is scheduled for October 4.
India’s government wasn’t as impressed, and responded on Monday that “X will have to follow the law of the land,” in response to Musk’s transparency push covered by the Times of India. The problem is structural rather than political. India issues content blocking orders under Section 69A of its IT Act, and Rule 16 of the accompanying 2009 Blocking Rules requires those orders to stay confidential. Publishing an India equivalent of the Brazil filter, naming specific accounts and citing specific government orders, would itself violate Indian law. Government use of Section 69A has grown from roughly 6,000 orders a year between 2018 and 2023 to about 24,300 in 2025, according to a Tech Times report.
The contrast puts Musk’s transparency pledge in an odd spot. It works largely as advertised in Brazil, where electoral law requires disclosure and X can point to specific account IDs and a specific court order in public code. It cannot work the same way in India, where the law requires the opposite. X users in India will keep seeing content disappear from search and their feeds without any public accounting of why, even as X tells the rest of the world that its censorship compliance is now inspectable.
This isn’t the first time X’s fights with a national government have shaped how the platform operates. Brazil’s Supreme Court ordered X to suspend the accounts of sitting lawmakers and journalists in 2024, a standoff that cost X its Brazilian revenue for months and froze Starlink’s local accounts before the investigation into Musk and X was closed in March with no evidence of wrongdoing found. X also sued California over a state law requiring moderation disclosures, arguing the mandate itself violated the First Amendment.
Whether India’s government pursues anything beyond a public statement remains to be seen. For now, the mismatch between what X can legally publish and what different governments legally allow it to publish is the real story behind Musk’s seven word claim.