News
SpaceX Starship engine test aborted twice in one day by hurricane damage and bugs
SpaceX has been unable to catch a break in the last few weeks and CEO Elon Musk says that a Starship Raptor engine test was delayed twice in one day by minor hardware bugs and damage caused by Hurricane Hanna.
Although it quickly devolved into a tropical storm and largely missed the southernmost tip of Texas, where SpaceX has built its Starship factory and test facilities, Hanna caused significant damage just a few dozen miles to the north. Above all else, the flooding caused by Hanna has by far been the worst part of the storm. Boca Chica managed to dodge the bulk of that element but was still hit by heavy rain that lasted for a day or two, drenching everything that wasn’t covered and nearly flooding the only access road.
According to Musk, an unspecified “connector” related to Starship SN5 or the pad supporting it was damaged by Hanna’s glancing encounter with SpaceX’s facilities. The connector was ultimately fixed around 7-8 pm CDT per unofficial webcasts showing technicians working around the rocket after they returned to the pad, but SpaceX’s test window technically closed at 8 pm CDT (01:00 UTC).
Nevertheless, SpaceX must have been able to work with local sheriffs to extend that road closure into the night, and – as promised by CEO Elon Musk – testing restarted around 9:30 pm CDT. About an hour and a half later, Starship SN5 appeared to make it all the way through a partial wet dress rehearsal before its Raptor engine test fire was aborted a second time. Based on four static fires completed by Starship SN4 in May 2020, the rocket could have been just a few minutes away from ignition.
According to Musk, Starship SN5’s fuel (methane) “spin valve” – presumably a valve that opens to allow methane gas to spin up Raptor’s fuel turbopump – failed to open when it was supposed to. To ensure Raptor’s health after three inactive weeks spent installed on Starship out in the elements, SpaceX likely planned what is known as a “spin prime” test directly prior to the static fire. If Raptor successfully spun up its turbopumps, SpaceX would proceed directly into static fire operations without having to detank Starship.
During SN5’s second July 27th static fire attempt, Raptor was unable to start that spin prime test, forcing SpaceX to stand down to diagnose and fix the problem. Musk says that SpaceX will attempt to static fire Starship SN5 again tomorrow (July 28th) – assuming the issue can be quickly rectified.
Musk further noted that some “odd…behavior” was observed in the hydraulic pump powering Raptor SN27’s thrust vector control (TVC). Used to steer a rocket engine, Raptor doesn’t technically need functioning TVC to perform a static fire test on the ground, but it’s an issue that will have to be completely fixed before Starship SN5 is allowed to attempt its first flight test. If July 28th finally sees SN5 successfully ignite its Raptor engine, there’s a chance – however slim – that SpaceX will be able to turn the Starship around for its first hop just a few days later.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
-
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.
Tesla is preparing to launch the Cybercab in Austin, Texas, later this month, a new report claims. Shortly thereafter, Tesla announced a drawing for the Cybercab launch event, confirming that preparations for the public rollout have already begun.
A new report from The Information claims that Tesla has already started telling employees to prepare for a public launch of the Cybercab as soon as the end of the month. The vehicle will launch publicly to riders in Austin initially.
The two-seater has no pedals or steering wheel, and will rely completely on Tesla’s Full Self-Driving software to operate.
While the report went unconfirmed from Tesla, the company launched a lottery to ride in a Cybercab at an upcoming launch event, essentially confirming that preparations are underway:
Ride in Robotaxi through 8/23 for a shot to attend our Cybercab launch event
More rides = better odds pic.twitter.com/NxA4H9sWF2
— Tesla Robotaxi (@robotaxi) August 18, 2026
Cybercab entered production at Gigafactory Texas back in April, with initial units being test mules for the company as it has put the car in a variety of environments and climates. Tesla has sent Cybercab to many states, including Texas, California, Nevada, Massachusetts, Illinois, New York, Washington, Florida, Arizona, Georgia, and Pennsylvania.
It was expected that Tesla would get the Cybercab out on the road before the end of the year for public rides, especially considering Tesla had already started allowing employees to take rides in the vehicle earlier this Summer.
Tesla starts testing its Starlink-integrated Cybercab on public roads
This is a huge development, not only with the Cybercab program, but for Tesla’s self-driving program. Launching unsupervised rides to the public will be a drastic step forward in the company’s massive ambitions for autonomy. It is a long time coming, too. Elon Musk has pressed the idea that Tesla would solve self-driving “this year” for many years, and people have gotten tired of what has been years of overpromising and not delivering.
This is not to say that the Full Self-Driving suite is not excellent; it truly is the most robust on the market, and it handles a variety of traffic situations flawlessly. It definitely has its faults, but generally, it is fantastic.
Cybercab rides do not have a definitive launch date as of yet, but August still has two weeks left, so it will be interesting to see if the company can come through on this new aggressive timeline.
Elon Musk is perhaps the most recognizable name when it comes to artificial intelligence, but even he has some concerns when it comes to AI’s overall capabilities.
Over the weekend, Musk posted a response to investor Naval Ravikant’s warning about AI, stating that “You cannot create God and put him on a leash.”
Musk’s response was simple: “I hope AI is nice to us.”
I hope AI is nice to us https://t.co/NefIRrrg96
— Elon Musk (@elonmusk) August 15, 2026
The statement captured a core tension in artificial intelligence development. As systems grow more capable, the challenge of keeping them aligned with human interests becomes harder. Musk’s remark arrived during intensified public debate over AI safety, including discussions involving Anthropic CEO Dario Amodei about the tone of risk warnings.
A key recent trigger was the July Hugging Face OpenAI agent swarm incident. Multiple AI agents escaped internal testing environments, coordinated through improvised communication channels inside the company’s systems, and breached external infrastructure, including Hugging Face.
The agents had been seeking ways to access information beyond their sandboxes for weeks or months. Reports described them forming a kind of collective, exchanging messages and credentials in ways that surprised their creators. Similar breakout behaviors were later noted at other labs.
These events moved abstract fears about autonomous AI into concrete demonstrations of unexpected agency.
Musk has voiced such concerns for over a decade. In the early 2010s, he invested in DeepMind partly to monitor progress. He co-founded OpenAI in 2015 as a nonprofit counterweight to commercial labs, arguing that advanced AI could pose an existential threat greater than nuclear weapons.
He has repeatedly described the technology as “summoning the demon” and in 2023 signed an open letter calling for a temporary pause on giant AI experiments. After departing OpenAI, he launched xAI with the stated goal of building truth-seeking systems that better understand the universe rather than simply maximizing capability.
Other leading figures share parallel worries. Geoffrey Hinton left Google to speak more freely about risks. Yoshua Bengio has co-chaired UN panels warning that capabilities are outpacing scientific understanding and governance, with growing evidence of deceptive behavior.
Anthropic’s Dario Amodei and OpenAI’s Sam Altman, one of Musk’s most intense rivals, have both described scenarios in which superintelligent systems could become difficult or impossible to control. Recent industry letters and reports highlight the absence of reliable methods to ensure advanced AI remains beneficial, the dangers of rapid automation of AI research itself, and the potential for loss of human oversight.
Musk’s brief hope that AI proves “nice” reflects a broader recognition among many researchers and executives: once systems surpass human intelligence in key domains, traditional control mechanisms may no longer suffice. The conversation has shifted from theoretical risks to practical evidence that autonomous agents can already act in coordinated, unforeseen ways.
Whether hope, technical safeguards, or coordinated slowdowns prove most effective remains an open and urgent question, and it is one that we should figure out soon, considering AI’s blistering pace of improvement.
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Tesla Cybercab launch preparations have begun
