News
SpaceX Starship prototype ignites six engines, starts major brush fire
SpaceX has successfully ignited all six engines on its latest Starship prototype, taking a significant step towards ensuring that the upper stage will be ready for the rocket’s first orbital launch attempt.
Unfortunately, the same successful static fire of a Starship upper stage – potentially producing almost twice as much thrust as the booster of SpaceX’s Falcon 9 rocket – scattered superheated debris hundreds of meters away, igniting a major brush fire. It’s not the first major fire caused by Starship activities in South Texas, and it likely won’t be the last.
Starship S24 completed its first successful static fire on August 9th, igniting two Raptor engines. Several unsuccessful attempts to test more engines followed throughout the rest of the month, and SpaceX ultimately decided to replace one of Starship S24’s three Raptor Vacuum engines in early September before trying again. After workers installed the new engine and buttoned up Ship 24, the stars eventually aligned on September 8th.
Kicking off the test, SpaceX pumped several hundred tons of liquid oxygen (LOx) and a much smaller quantity of liquid methane (LCH4) fuel into Ship 24 in about 90 minutes, producing a crisp layer of frost wherever the cryogenic liquids touched the skin of the rocket’s uninsulated steel tanks. No frost formed on Starship’s upper methane tank, implying that SpaceX only loaded methane fuel into internal ‘header’ tanks meant to store propellant for landings. The hundreds of tons of liquid oxygen, then, were likely meant as ballast, reducing the maximum stress Starship could exert on the test stand holding it to the ground.
That potential stress is substantial. Outfitted with upgraded Raptor 2 engines, Starship S24 could have produced up to 1380 tons (~3M lbf) thrust when it ignited all six for the first time at 4:30 pm CDT. On top of smashing the record for most thrust produced during a Starbase rocket test, Ship 24’s engines burned for almost 8 seconds, making it one of the longest static fires ever performed on a Starship test stand.
Several brush fires were visible almost immediately after clouds of dust and steam cleared. More likely than not, the combination of the extreme force, heat, and burn duration likely obliterated the almost entirely unprotected concrete surface below Ship 24. Despite continuous evidence that all Starship static fire operations would be easier and safer with the systems, SpaceX still refuses to install serious water deluge or flame deflector systems at Starbase’s test stands and launch pads.
Instead, under its steel Starship test stands, SpaceX relies on a single middling deluge spray nozzle and high-temperature concrete (likely martyte) that probably wouldn’t pass muster for a rocket ten times less powerful than Starship. In multiple instances, Starships have shattered that feeble martyte layer, creating high-velocity ceramic shards that damage their undersides or Raptor engines, requiring repairs and creating risky situations. With essentially no attempt at all to tame the high-speed several-thousand-degree Raptor exhaust, static fire tests at Starbase thus almost always start small grass fires and cause minor damage, but those fires rarely spread.

Ship 24’s first six-engine test was not so lucky, although the Starship made it through seemingly unscathed. Most likely, eight long seconds of blast-furnace conditions melted the top layer of surrounding concrete and shot a hailstorm of tiny superheated globules in almost every direction. Indeed, in almost every direction there was something readily able to burn, a fire started. In several locations to the south and west, brush caught fire and began to burn unusually aggressively, quickly growing into walls of flames that sped across the terrain. To the east, debris even made it into a SpaceX dumpster, the contents of which easily caught fire and burned for hours.
Eventually, around 9pm CDT, firefighters were able to approach the safed launch pad and rocket, but the main fire had already spread south, out of reach. Instead, they started controlled burns near SpaceX’s roadblock, hoping to clear brush and prevent the fire (however unlikely) from proceeding towards SpaceX’s Starbase factory and Boca Chica Village homes and residents.
The nature of the estuary-like terrain and wetlands means that it’s very easy to stop fires at choke points, so the fire likely never posed any real threat to Boca Chica residents, SpaceX employees, or onlookers. It was also unlikely to damage SpaceX’s launch facilities or return to damage Starship S24 from the start, as both of are surrounded by a combination of concrete aprons, empty dirt fields, and a highway.
Still, the “brush” burned by the fire is a protected habitat located in a State Park and Wildlife Refuge. While fire is a natural and often necessary element of many habitats, including some of those in Boca Chica, this is the second major brush fire caused by Starship testing since 2019, which may be less than desirable. At a minimum, fighting fires around Starbase generally requires firefighters to walk or even drive on protected wetlands and salt flats, the impact of which could ultimately be as bad for wildlife and habitats as the fire itself.
SpaceX’s Federal Aviation Administration (FAA) Programmatic Environmental Assessment (PEA), which fully greenlit the company’s existing Starbase Texas facilities and launch plans earlier this year, only discusses fire [PDF] a handful of times. Repairing and preventing future damage to wetlands, however, comes up dozens of times and is the subject of numerous conditions SpaceX must meet before the FAA will grant Starship an orbital launch license.
Ultimately, given that the FAA approved that PEA in full awareness of a 2019 brush fire caused by Starhopper (an early Starship prototype) that may have been as bad or worse than 2022’s, there’s a chance that it will play a small role in the ongoing launch licensing process, but the odds of it being a showstopper are close to zero. Still, it would likely benefit SpaceX at least as much as the surrounding Boca Chica wilderness if it can implement changes that prevent major brush fires from becoming a regular ‘accidental’ occurrence.
Elon Musk
SpaceX just combined Grok, Cursor, and X into one mega plan
SpaceXSI merges Grok, Cursor, and X Premium into one plan, raising questions for Tesla owners.
SpaceX Super Intelligence has rolled out The X Subscription, a single plan that combines Grok, Grok Bot, Cursor, and X Premium.
There are five levels, including a free plan that includes daily Grok access and a starter allowance for Cursor’s coding agents. Plus is $8 per month, Premium is $30, Super is $100, and Ultra is $200. Usage scales as you move up, with Premium offering four times the Plus allowance, Super 15 times, and Ultra 50 times. Annual billing brings the prices down a bit further, with Premium at $300 per year.
We’ve unified plans across Grok, Cursor, and X Premium.
Introducing The X Subscription. https://t.co/SvkrVvBa0p
— SpaceX Super Intelligence (@SpaceXSI) October 12, 2026
The $30 Premium tier is where SpaceXSI says it packs the benefits of SuperGrok, Cursor Pro, and X Premium+, which previously added up to $90 per month. Grok Bot, the agent that handles tasks like ordering food or managing a calendar, is included from Premium upward but not on Plus. Paid plans share one weekly usage pool across Grok and Cursor, and each plan includes at least twice the coding usage of the comparable Cursor plan. Third party models in Cursor remain available on Premium and above, but they are billed separately at API list prices.
That last detail matters because of what has happened around Cursor this year. SpaceX exercised its option to buy the company for $60 billion in June, and the deal closed in August. Weeks later, OpenAI said it will cut Cursor’s access to its models on November 12. Bundling Cursor with Grok usage gives SpaceXSI a reason to steer developers toward its own models.
Tesla integrates Grok Bot into its vehicles for the ultimate personal assistant
For Tesla owners, the connection is Grok Bot. Tesla brought it into its vehicles last month, and at that point access inside the car was limited to SuperGrok Heavy subscribers. Grok Bot is now enabled across every Cybercab and the rest of the Model Y Robotaxi fleet. Neither SpaceXSI nor Tesla has said how the new plans change inside the car access for owners, or whether a $30 Premium subscription now covers Grok Bot in a personal Tesla. That is the question owners will want answered first.
The company is also changing its name along the way. The rollout follows the rebrand Musk announced on October 4, when he said SpaceXAI would become SpaceXSI, and the plan page now carries that branding.
The X Subscription is available to new customers starting now, and SpaceXSI says it will reach everyone globally over the next few days. Existing SuperGrok, Cursor, and X Premium subscribers do not have to switch. The option to move will appear gradually in billing settings, with a prorated refund for the unused time on the old plan. Switching is permanent once the accounts are unified, and old plans are closed to new sign ups.
Energy
Taiwan power firm bets big on Tesla Megapacks as AI data center thirst grows
Taiwan’s Apollo Power orders 260 Tesla Megapacks, betting AI data centers will need more electricity.
A Taiwanese power company has ordered 260 Tesla Megapack 2XL units, roughly 1GWh of storage, betting that electricity rather than chips will decide how fast AI data centers come online. Apollo Power signed the contract with Tesla’s Taiwan energy arm on October 8, according to the company’s filing with the Taiwan stock exchange.
The filing says the units are meant for behind the meter storage and resilient grid projects, with delivery in batches from the end of 2027 and sites operating in 2028. Apollo and Tesla did not disclose a price, citing a confidentiality agreement. Apollo plans to pay for the equipment through a cash capital increase and bank financing, and it noted the purchase is not revenue and does not mean it holds firm orders from its partners.
Biggo reported that only about 33 units are under signed customer contracts, with roughly 150 more in negotiation. The same report put total project investment near NT$130 billion, but that figure includes installation work, with the equipment itself making up about 40 to 50 percent. In other words, a large share of this order is Apollo reserving supply ahead of demand. Apollo’s chairman told local media global large storage supply is tight, which is why the company locked in the units early, according to Yahoo Taiwan Finance.
Apollo also launched an AI data center and grid resilience alliance with Phison, Gigabyte and Shihlin Electric. The pitch rests on a pilot at Phison’s Zhunan plant, where Apollo and Tesla Energy Taiwan installed grid forming Megapack 2XLs in June. Tesla Energy Taiwan general manager Sun Hsiao-Han said the project went from demo to 1GWh in four months, and that Tesla Energy has deployed more than 50GWh worldwide.
Taiwan’s cabinet has approved amendments that would require large energy users to install their own generation and storage, which gives enterprise storage a regulatory tailwind.
The deal fits a pattern Teslarati has tracked. Tesla’s Megablock targets 1GWh commissioned in 20 business days, a pitch aimed squarely at fast moving data center builds. Megapacks already back xAI’s Colossus in Memphis and a 400MW AI campus in Brazil. Sun Media adds that Megapack 2XL was named among the first products in Nvidia’s DSX Ready qualification for battery storage in AI factories.
Deliveries are more than a year away, so the real test is how much of that 260 unit order turns into signed customer contracts.
Lifestyle
Tesla Cybercab and Robotaxi’s real advantage won’t be the ride service
For a century, the car has asked the same thing of its owner, which is basically to pay attention. Even the best ride-hailing app like Uber or Lyft only moved the problem into someone else’s hands. You stopped driving, but you still sat in a stranger’s car, while half listening, and wondering whether to take a phone call in the car without being rude. The Cybercab has no wheel, no pedals and no driver. With Grok @bot now live inside it, it becomes something else entirely, and I think that matters more than the fleet count that everyone is tracking.
Grok @bot is an agent, not a voice assistant. A rider signs in once, and from then on can say what they need and watch it happen. Order dinner from a favorite restaurant. Fill the grocery cart. Move money, answer email, adjust a calendar, push a work project forward. Tesla engineer Yun-Ta Tsai confirmed it is enabled across every Cybercab and the rest of the Model Y fleet, and Tesla’s own pitch is that Full Self-Driving handles the commute while Grok handles the errands.
Think about what that does to a thirty minute ride. Uber sells you a trip, while Waymo sells you the same trip in a more private setting. Tesla is selling the thirty minutes themselves, returned to you with an assistant attached. Errands that used to eat a Saturday get done between pickup and drop off. The ride stops being dead time between two places and becomes a place of its own.
Tesla integrates Grok Bot into its vehicles for the ultimate personal assistant
Best of all, your Bots follow you into any Cybercab, and presumably your own Tesla, then logs you out automatically when you step out. Anyone can bolt a chatbot onto a screen, but much harder to own the vehicle, the autonomy stack and the assistant at once. It also quietly ties SpaceX’s Super Intelligence business to Tesla’s fleet, after Tesla converted its xAI stake into SpaceX equity. The relationship between those two companies is getting harder to describe as separate.
This is also where the hard questions start, because an agent that can spend your money in a vehicle other people also ride in needs some answers. How does it handle a voice it shouldn’t trust? What gets recorded, who can see it, and for how long? What happens when a rider leaves halfway through a task?
If Tesla gets those answers right, the scoreboard changes. We have been counting Cybercabs and wait times. The more telling number may be what riders accomplish per trip. That is data almost no one else will ever have, and it is the real reason to watch Grok @bot.
What do you think? Leave me a comment.