News
SpaceX still an option for future Amazon internet satellite launches, says Senior VP
An Amazon executive says that the company could still call on SpaceX to launch some of its Project Kuiper internet satellites after two of the three unproven rockets it purchased announced launch delays days apart.
Amazon began work on Project Kuiper in 2018. When SpaceX CEO Elon Musk fired several senior employees overseeing the company’s Starlink satellite internet program for being overly cautious, at least two of those employees immediately landed in senior positions at Project Kuiper. Four years later and more than two years after Amazon received an FCC license to deploy its 3,236-satellite Project Kuiper constellation, which aims to compete directly with SpaceX’s Starlink, the company’s first prototype satellite launch has changed rockets and slipped from late 2022 to early 2023.
Of the 77 firm launch contracts Amazon has signed since April 2021, only nine are for a rocket – United Launch Alliance’s (ULA) Atlas V – that has already successfully flown. The remaining 68 (and another 15 exercisable options) are spread among ULA’s Vulcan Centaur, Arianespace’s Ariane 6, and Blue Origin’s New Glenn, all of which are months away from their first launch attempts.
On October 10th, ULA CEO Tory Bruno told reporters that Vulcan Centaur’s launch debut had slipped from its latest late-2022 target to no earlier than (NET) “early 2023.” Garnering 38 of 77 firm contracts, Vulcan is the single most important rocket for Amazon’s Project Kuiper plans and is likely expected to launch close to half of all Kuiper satellites.
Nine days later, Ariane Group and the European Space Agency (ESA) announced that Ariane 6’s launch debut had also slipped from a late-2022 target. Unlike Vulcan’s gentle early-2023 slip, Ariane 6’s debut was pushed to late 2023 at the earliest, and ESA and Ariane officials frankly admitted that that could easily become 2024. Excluding options, Ariane 6 won 18 Project Kuiper launch contracts and is the constellation’s second most important rocket.
Because Amazon applied for its Project Kuiper license so early, a six-year countdown started when the FCC approved its license in July 2020. If Amazon fails to launch half of its 3,236 satellites within six years of that receipt, the FCC could revoke Kuiper’s constellation license. While it’s unlikely that the FCC would actually revoke the license of a constellation that’s close to achieving its deployment milestones, the deadline still emphasizes just how far Amazon and its suppliers are falling behind.
Vulcan, Ariane 6, and Project Kuiper prototype launch delays have only worsened an already challenging situation. In addition to the rocket’s long-awaited debut, ULA has major obligations to NASA and the US military, who expect Vulcan to complete up to four more launches in 2023. Unless ULA pulls off a minor miracle, it’s unlikely that Vulcan will be able to launch five times in its first year of service. Respectively, ULA’s Atlas V and Delta IV rockets took 2.5 and 3.5 years to reach that milestone. If ULA’s past record serves as a reasonable guide for its future, it’s possible that Vulcan Centaur won’t have the spare capacity to begin Project Kuiper launches until 2025.
The same is arguably true for Ariane 6, which has an even busier manifest – all of which may be delayed to 2024. Of Arianespace’s two most recent rockets, Ariane 4 took 14 months and Ariane 5 took 53 months to complete their first five fully successful launches. Ariane 6 borrows heavily from Ariane 5’s design. Unless Arianespace gets off to a record-breaking start or prioritizes Amazon over ESA and other European operators, an almost unthinkable scenario, it’s difficult to imagine that Ariane 6 will have the spare capacity to begin Project Kuiper launches before 2025 or 2026.
Blue Origin’s New Glenn rocket, which is years behind schedule and unlikely to debut before late 2023 or 2024, might ironically be Amazon’s best bet for the first dedicated Project Kuiper launch, but only if its debut is near-flawless and doesn’t slip any further. Given that New Glenn will be Blue Origin’s first orbital rocket of any kind, more delays and issues (if not an outright failure) on the first launch are likely. New Glenn is thus also unlikely to be ready to launch large batches of Project Kuiper satellites until 2024 or 2025. Given the record of its suborbital New Shepard rocket, the odds are also against Blue Origin quickly ramping up the cadence of a far more complex orbital launch vehicle.
Only Atlas V appears to have any significant chance of beginning large-scale Project Kuiper launches before 2025. But ULA is shutting down Atlas V production to transition to Vulcan, so it’s impossible for Amazon to order more than nine of the rockets, as ULA.
Unfortunately for Amazon, in addition to the many rocket-side issues facing Project Kuiper, its satellite prototype delays will make it even harder for the company to begin large-scale launches sooner than later. SpaceX, now the proud owner of a majority of all working satellites in orbit, took around 21 months to go from launching its first two prototypes to its first batch of 60 operational Starlink satellites. The satellite design it settled on was almost nothing like the first two prototypes.
If Amazon’s first prototypes launch on Vulcan’s early-2023 debut, perform excellently, meet or exceed expectations after just a few months of testing, and are close to the final satellite design, Project Kuiper may still have a shot at manufacturing enough satellites to fill one or more launches in 2024. But if its first satellites run into major issues, Amazon’s decision to “[bring] up manufacturing of…production satellites [in parallel with prototype development]” could set it back months if it’s forced to redesign its satellites, find new suppliers, or significantly change the factory it’s already building.
Combined, Project Kuiper finds itself in an unenviable position. It’s thus unsurprising that as of October 2022, an Amazon executive appears to have changed their tune about using SpaceX rockets. Over the last ~13 months, SpaceX has become the single most productive launch provider in the world, besting the entire nation of China. On a quarterly basis, SpaceX now launches more useful mass to orbit than the rest of the world combined. It’s also the only launch provider on Earth that can create spare capacity for last-minute customers by shuffling its own internal launch demands.
According to Dave Limp, senior vice president of devices and services at Amazon, Project Kuiper is willing to consider taking advantage of some of SpaceX’s unprecedented capabilities after it shunned the company entirely in earlier contracts and statements. Speaking in a Washington Post Live interview, Limp says that Amazon is “open to contracting with anyone” and understands “that heavy launch capacity is [and will likely remain] pretty constrained” for years to come.
Unfortunately, Limp began by falsely asserting that Falcon 9 was too small to have warranted earlier launch contracts, stating that it’s “probably at the low end of…the capacity that we need.” In an expendable configuration, Falcon 9 can launch more than 22 tons (~48,500 lb) to low Earth orbit (LEO), while Ariane 6 is quoted at [PDF] 21.7 tons (~47,800 lb). While it hasn’t flown, SpaceX also offers an extended payload fairing that should more or less match Vulcan and Ariane 6’s largest fairings.
But Limp expressed interest in SpaceX’s Falcon Heavy rocket, which could likely match or come close to the payload volume of Ariane 6 and Vulcan and far exceed either rocket’s performance to LEO. In a configuration that would allow SpaceX to recover all three of Falcon Heavy’s boosters, almost guaranteeing that it would cost less than Vulcan or Ariane 6, the rocket would likely be able to launch around 40-50 tons (90,000-110,000 lb) to LEO. The Amazon executive even brought up SpaceX’s next-generation Starship rocket as a more desirable option for future Project Kuiper launches. Starship is designed to launch anywhere from 100 to 150 tons to LEO, should cost even less than Falcon 9 or Falcon Heavy, and will eventually feature a payload bay that dwarfs even New Glenn’s massive fairing.
Nonetheless, despite the promise of SpaceX, Amazon appears to be in no rush to hedge its bets on Vulcan, Ariane 6, and New Glenn. Only time will tell if its multi-billion-dollar gamble pays off.
Tesla has confirmed today that its steering wheel-less and pedal-less Cybercab, the vehicle geared toward launching the company’s autonomous ride-hailing hopes, has officially entered production at its Giga Texas production facility outside of Austin.
The Cybercab is a sleek two-door, two-passenger coupe engineered from the ground up as an electric self-driving vehicle. It features no steering wheel or pedals, relying instead on Tesla’s advanced vision-only Full Self-Driving system powered by multiple cameras and artificial intelligence.
Purpose-built for autonomy
Cybercab in production now at Giga Texas pic.twitter.com/Y9qG3KyWBa
— Tesla (@Tesla) April 23, 2026
The minimalist cabin centers on a large display screen that serves as the primary interface for passengers, creating an open, futuristic space optimized for comfort during unsupervised rides. A compact 35-kilowatt-hour battery pack delivers exceptional efficiency at 5.5 miles per kilowatt-hour, providing an estimated 200-mile range.
Additional innovations include inductive charging compatibility and a lightweight design that enhances aerodynamics and performance.
Production at Giga Texas builds on earlier prototypes and initial units completed earlier in 2026. The facility, already a hub for Model Y and Cybertruck assembly, now ramps up dedicated lines for the Cybercab.
This shift to volume manufacturing reflects Tesla’s strategy to scale affordable autonomous vehicles rapidly.
By focusing on a dedicated platform rather than adapting existing models, the company aims to keep costs low while prioritizing safety and reliability through continuous AI improvements.
The Cybercab’s debut in production carries broad implications for urban mobility. As the cornerstone of Tesla’s Robotaxi network, it promises on-demand, driverless rides that could slash transportation expenses, reduce traffic accidents caused by human error, and lower emissions through its all-electric powertrain.
Accessibility features, such as space for service animals or assistive devices, further broaden its appeal. Regulators and cities worldwide will soon evaluate its deployment, but the vehicle’s design already addresses key hurdles in scaling unsupervised autonomy.
Challenges persist, including full regulatory clearance and building charging infrastructure. Yet this production launch signals momentum. With Cybercabs poised to roll out in increasing numbers, Tesla edges closer to a future where personal ownership meets shared fleets of intelligent vehicles.
The start of Cybercab production is more than just a new vehicle entering mass manufacturing for Tesla, as it’s a signal autonomy is near. Being developed without manual controls is such a massive sign by Tesla that it trusts its progress on Full Self-Driving.
While the development of that suite continues, Tesla is making a clear cut statement that it is prepared to get its fully autonomous vehicle out in public roads as it prepares to revolutionize passenger travel once and for all.
News
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.
Tesla Full Self-Driving v14.3.2 began rolling out to some owners earlier this week, and there are some notable improvements that came with this update.
There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.
Overall operation saw a handful of slight improvements, especially with parking performance, which has been the most notable difference with the arrival of FSD v14.3. However, there are still some very notable shortcomings, most notably with region-specific signage and navigation.
Tesla Assisted Smart Summon (ASS) improvements
There are noticeable improvements to ASS operation, which has definitely been inconsistent in terms of performance. Tesla wrote in the release notes for v14.3.2:
“Unified the model between Actually Smart Summon, FSD, and Robotaxi for more capable and reliable behavior.”
As recently as this month, I used Summon with no success. It had pulled around the parking lot I was in incorrectly, leaving the range at which Summon can be operated and losing a signal while moving in the middle of the lot.
This caused me to sprint across the lot to retrieve the vehicle:
It was pouring when I left the gym so I tried to Summon my Model Y
It turned the opposite way and drove out of range, stopping here and forcing me to walk even further across the lot in the rain for it 🤣One day pic.twitter.com/iD10c8sriB
— TESLARATI (@Teslarati) April 5, 2026
Unfortunately, Summon was not dependable or accurate enough to use regularly. It appears Tesla might have bridged the gap needed to make it an effective feature, as two tests in parking lots proved that Summon was more responsive and faster to navigate to the location chosen.
It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:
🚨 Tesla FSD v14.3.2 ASS testing part 1
This was a significant improvement than recent tries using ASS. The parking lot was pretty empty but getting it to come to my location in one singular motion and maneuver was encouraging. https://t.co/vF7TS48GGV pic.twitter.com/sYt8tyHgNn— TESLARATI (@Teslarati) April 23, 2026
Tesla Full Self-Driving v14.3.2 ASS testing part 2 https://t.co/lxfWfnLUxf pic.twitter.com/2R0r3ohI3M
— TESLARATI (@Teslarati) April 23, 2026
I plan to test this more thoroughly and regularly through the next few weeks, and I avoided using it in a congested parking lot initially because I have not had overwhelming success with Summon in the past. I wanted to set a low baseline for it to see if it could simply pull up to the place I pinned in the Tesla app.
It was two for two, which is a big improvement because I don’t think I ever had successful Summon attempts back-to-back. It just seems more confident than ever before.
New Disengagement Categories
This is a really good idea from Tesla, but there are some issues with it. The categories you can select are Critical, Comfort, Preference, and Other.
I think the reasons why people choose to take over would be a better way to prompt drivers, like, “Traveling Too Fast,” “Incorrect Maneuver,” “Navigation Error,” would be more beneficial.
I say this because it seems that how we each categorize things might be different. For example, I shared a video of an intervention because the car had navigated to an exit to a parking lot and put its left blinker on, despite left turns not being allowed there.
I disengaged and chose Critical as the reason; it’s not a comfort issue, it’s not a preference, it’s quite literally an illegal turn, and it’s also dangerous because it cuts across several lanes of traffic and is 180 degrees.
I chose to label this Navigation error as “Critical” while testing FSD v14.3.2
Here’s why:
✅ This intervention wasn’t “preference,” as the maneuver FSD routed was illegal
✅ If a police officer saw this maneuver, it would result in a ticket https://t.co/znhHb4haAo pic.twitter.com/bZOiLwWmQa— TESLARATI (@Teslarati) April 23, 2026
Some said I should not have labeled this as Critical, but that’s the description I best characterized the disengagement as.
Categorizing interventions is a good thing, but it’s kind of hard to determine how to label them correctly.
Inconsistency with Regional Traffic Patterns
Tesla Full Self-Driving is pretty inconsistent with how it handles regional or local traffic patterns and road rules. The most frequent example I like to use is that of the “Except Right Turn” stop sign, which has become a notorious sighting on our social media platforms.
In the initial rollout of v14.3, my Model Y successfully navigated through one of these stop signs with no issues. However, testing at two of these stop signs yesterday proved it is still not sure how to read signs and navigate through them properly.
🚨 Tesla FSD v14.3.2 attempts the “Except Right Turn” stop sign: https://t.co/W5MjAybaNK pic.twitter.com/P6oeUsk4PN
— TESLARATI (@Teslarati) April 23, 2026
Off camera, I approached another one of these signs and felt the car coming to a stop, so I nudged it forward with the accelerator pedal pressed.
This helped the car go through the sign without stopping, but I could feel the bucking of the vehicle as the car really wanted to stop.
Musk said on the earnings call earlier this week that unsupervised FSD would probably be available in some regions before others, including a state-to-state basis in the U.S.
“It’s difficult to release this like to everyone everywhere all at once because we do want to make sure that they’re not unique situations in a city that particularly complex intersection or — actually, they tend to be places where people get into accidents a lot because they’re just — perhaps there’s — and like I said, an unsafe intersection or bad road markings or a lot of weather challenges. So I think we would release unsupervised gradually to the customer fleet as we feel like a particular geography is confirmed to be safe.”
This could be one of those examples that Tesla just has to figure out.
Highway Operation
Full Self-Driving is already pretty good at routine roadway navigation, so I don’t have too much to report here.
However, I was happy with FSD’s decision-making at several points, including its choice not to pass a slightly slower car and remain in the right lane as we approached the off-ramp:
🚨 Tesla FSD v14.3.2 highway operation: generally happy with the performance here, especially behavior near the exit
Love that the car got over in the right lane after its final pass, and stayed there as the off ramp was approaching https://t.co/qVRVhg6XGR pic.twitter.com/1ELwHf2XKS— TESLARATI (@Teslarati) April 23, 2026
Better Maneuvering at Stop Signs
Many FSD users report some strange operations at stop signs, especially four-way intersections where there is a stop sign and a line on the road, and they’re not even with one another.
I experienced this quite frequently and found that FSD would actually double stop: once at the stop sign and again at the line.
This created some interesting scenarios for me and I had many cars honk at me when the second stop would happen. Other vehicles that had waved me on to proceed through the intersection would become frustrated at the second stop.
FSD seems to have worked through this particular maneuver:
🚨 Tesla FSD v14.3.2 with a singular stop at the correct spot
No double stopping anymore in my experience https://t.co/Wd0TaNjc1R pic.twitter.com/CdQPvJHaAM
— TESLARATI (@Teslarati) April 23, 2026
FSD should know to go to the more appropriate location (whichever provides better visibility), and proceed when it is the car’s turn to move. The double stop really ruined the flow of traffic at times and generally caused some frustration from other drivers.
News
Tesla plans to resolve its angriest bunch of owners: here’s how
Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.
Tesla has a plan to make Hardware 3 owners whole after CEO Elon Musk admitted that those with that self-driving chip in their cars will not have access to unsupervised Full Self-Driving.
The company’s strategy is so crazy that it is sort of hard to believe.
Since the rollout of the AI4 chip in Tesla vehicles, owners with the last generation self-driving chip, known as Hardware 3, have been persistent in their quest for a solution to their issue: they were told their cars were capable of unsupervised Full Self-Driving. It turns out the cars are not.
Tesla owners with HW3 finally get their answer: https://t.co/CSZTKKkWXx
— TESLARATI (@Teslarati) April 22, 2026
During the Tesla Q1 earnings call on Wednesday, Musk finally clarified what the company’s plans are for Hardware 3 owners, what they will be offered, and what Tesla will have to do internally to prepare for it.
The answer was somewhat mind-boggling.
Musk said:
“Unfortunately, Hardware 3 — I wish it were otherwise, but Hardware 3 simply does not have the capability to achieve unsupervised FSD. We did think at one point it would have that, but relative to Hardware 4, it has only 1/8 of the memory bandwidth of Hardware 4. And memory bandwidth is one of the key elements needed for unsupervised FSD.”
He continued, stating that HW3 owners would have the opportunity to trade their cars in at a discounted rate in order to get the AI4 chip:
“So for customers that have bought FSD, what we’re offering is essentially a trade-in — like a discounted trade-in for cars that have AI4 hardware, and we’ll also be offering the ability to upgrade the car, to replace the computer. And you also need to replace the cameras, unfortunately, to go to Hardware 4.”
Obviously, Tesla has a lot of people to work with and make this whole thing right. Musk was adamant that HW3 would be capable of FSD, and now that the company has finally admitted that it is not, there are some things that could come of this.
There has been open talk about some sort of class action lawsuit against Tesla. The promises that Tesla made previously could be considered a breach of contract or even false advertising, and that’s according to Grok, Musk’s own AI program.
Musk went on to say that Tesla would likely have to establish new microfactories to effectively and efficiently replace HW3 computers and cameras:
…So to do this efficiently, we’re going to have to set up, like kind of micro factories or small factories in major metropolitan areas in order to do it efficiently. Because if it’s done just at the service center, it is extremely slow to do so and inefficient. So we basically need like many production lines to make the change.”
This is going to be an extremely costly process, especially if Tesla has to buy real estate, properties, and equipment to complete this work. Additionally, there was no wording on pricing, but Musk never said it would be free. It will likely come with some kind of price tag, and HW3 owners, after being left hanging for so long, will have something to say about that.
Tesla confirms Cybercab with no steering wheel enters production
Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much
