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.
Tesla has expanded the operational geofence for its driverless Robotaxi service in Austin, Texas, marking the first such increase in some time. The updated Service Area for Robotaxi in Austin now spans about 288 square miles and is roughly 9 percent larger than the previous boundary.
This incremental growth adds approximately 24 square miles of coverage, bringing the prior zone of roughly 264 square miles into a broader footprint that better serves northern suburbs.
The expansion extends the geofence northward toward Pflugerville along the US 183 corridor, incorporating additional neighborhoods north of the Domain and areas such as Mesa Park. These additions include higher-end residential and commercial districts that previously sat just outside the allowed operating zone.
Riders can now request unsupervised trips that begin or end in these newly included locations, provided the entire route remains inside the digital boundary:
Tesla has just expanded its Robotaxi service area in Austin, Texas for the first time in 10 months.
The new service area is roughly 9% larger than the old one, and is about 288 square miles in total. pic.twitter.com/i4oBM1KfWS
— Sawyer Merritt (@SawyerMerritt) August 31, 2026
Tesla first launched public Robotaxi operations in Austin in mid-2025 with a modest initial zone of about 20 square miles. Subsequent enlargements in 2025 and early 2026 steadily grew the map until it covered much of the metropolitan area.
After the last major update roughly ten months earlier, the company held the boundary steady while it collected additional miles and refined the FSD suite.
The modest nine percent increase still matters for daily utility. Longer trips become possible, more residents gain access, and the fleet can accumulate more diverse real-world data across new road types and traffic patterns. Observers note that the added territory aligns with existing Tesla service infrastructure, which could support more efficient vehicle staging in the North end of Austin.
Although the geofence has grown, Tesla continues to operate a relatively small unsupervised fleet in the city. The company has emphasized safety and software readiness over rapid geographic scaling. This latest map update signals that Tesla remains committed to expanding Robotaxi availability in its home market as it prepares for further software improvements and potential Cybercab deployments.
The 288-square-mile zone now gives Austin riders one of the larger driverless service areas currently available in the United States.
Tesla’s 2026 Summer Update turns Grok from a talking companion into a true in-car controller, with considerably expanded capabilities. Where the assistant once answered questions and handled navigation, it can now operate hardware and software through ordinary speech, including several requests at the same time.
Grok has become incredibly robust over the past few quarters, and this new ability that Tesla has included with its Summer Update is perhaps the clearest sign of just how capable it has become.
You can issue many commands to Grok at once, and each will be taken care of: anything from headlight control to climate adjustments to mirror folding can now all be taken care of with a simple sentence spoken toward Grok:
This is cool, you can now give Grok a ton of commands at once in your Tesla and it’ll do them all together.
The commands I gave:
• Fold mirrors
• Turn on wipers to fastest setting
• Change temp to 65°
• Open self-driving app
• Open gloveboxComes with Tesla’s 2026 Summer… pic.twitter.com/drZxoHrknv
— Sawyer Merritt (@SawyerMerritt) August 26, 2026
Here’s another example I used in my Model Y:
🚨 Using Grok to control the cabin temperature and turn on headlights in 2026 Model Y on FSD v14.3.8 and 2026.26.6.5 pic.twitter.com/7clgQkGABk
— TESLARATI (@Teslarati) August 27, 2026
Tesla’s official Release Notes list the core powers of Grok’s new capabilities: Grok can place phone calls from a paired phone, search a streaming service and queue music, adjust climate, and search the Controls panel. Drivers can also ask it questions about the vehicle or the latest features included in a recent software update.
It can also take care of driving settings, dynamics, and other relevant preferences that deal with how the car operates and handles.
Tesla Summer Update begins rolling out: a look at the new features
It’s also more of a use case than a novelty feature. Grok was great for learning about something that was being pondered while Full Self-Driving was taking care of the major automotive responsibilities, but it did have some useful functionality when it came to navigation.
Another less-noted improvement is the swift transition that Grok has from thinking of its answer to giving you one. In the past, it would take a few seconds for Grok to truly come up with a valuable response. It now seems that it is improving, at least slightly.
Tesla Full Self-Driving is set to get a major fix with pothole avoidance, a feature that CEO Elon Musk said recently was “coming soon.” The feature has been included within the FSD v14 release notes for some time as an upcoming improvement.
Potholes come in all shapes and sizes, but one thing is universal about them, and that is the fact that every driver wants to avoid them. Driving into or over a pothole can cause tire and wheel damage, alignment issues, and even, in some more severe instances, injury to occupants or major damage to a vehicle in despair.
Tesla Cybercab uses a unique strategy for picking up the right rider
Musk said late last night in a post that pothole avoidance while utilizing the Full Self-Driving suite is “coming soon.”
Coming soon
— Elon Musk (@elonmusk) August 31, 2026
Full Self-Driving, even in its most recent and robust forms, still has its shortcomings. While the suite has performed exceptionally well with avoiding on-road obstacles like cardboard boxes, horse droppings, car parts, and other debris, it still seems to struggle with recognizing certain things.
Potholes and other abrupt changes in a road’s layout are things that FSD still tends to struggle with. Perhaps the suite’s 3D modeling is still in need of some additional data or some sort of script that will help it to avoid a potentially destructive pothole or bump in the road that would be easily recognizable by the human eye.
Musk has mentioned pothole avoidance for some time, with the initial idea coming in April 2019 when an owner first requested the feature. Musk said that Tesla would “definitely” develop pothole avoidance.
In August 2020, Musk said Tesla was in the process of labeling bumps and potholes so cars can either slow down or steer around them altogether.
Tesla to utilize micro maps for pothole-detection in future update
Avoiding major disturbances in the road is a necessary feature for Full Self-Driving to have, especially as Tesla is working toward a fully autonomous program that will eventually allow every occupant in the vehicle to sleep, work, or enjoy leisure time while traveling.
That truly begins this week with the launch of Cybercab on Thursday.
Tesla expands driverless Robotaxi geofence in Austin
Elon Musk’s Grok can basically control anything in your Tesla now
