On a Sunday afternoon at Cape Canaveral, a Vulcan rocket carrying forty satellites for Amazon's Leo network fell silent ten minutes into its climb, and the satellites never reached the orbit they were built for. It is the first failure in the two-decade history of United Launch Alliance, a young enterprise that now carries the weight of a rival's ambitions and its own hopes for a steady cadence of flights. The cause remains unknown, and in the way of all new machines, each loss is also a lesson written in data not yet read. For Amazon, the sky has become a crowded, uncertain place, where its a
Amazon Loses 40 Leo Satellites as ULA's Vulcan Rocket Fails Ten Minutes After Florida Launch
Forty satellites, ten minutes, and a first failure in two decades
Forty satellites gone in one flight. Why does this one land so hard for Amazon?
Because it was the biggest batch Amazon had tried to launch at once, and Vulcan was supposed to carry nearly half of the first-generation network of 3,232 satellites.
And ULA itself? This is described as a first.
Worth being precise: it's the first mission failure for the company in about two decades, per the reporting. That's a record the source states, not something I can verify beyond that.
The company's own wording is careful too. It says the anomaly came ten minutes in and the Amazon mission wasn't delivered to orbit.
Do we know what went wrong?
No. ULA said outright it has no specific data yet. Anything about the cause right now would be guesswork.
What are Amazon's other ways up?
Blue Origin's New Glenn has been grounded since a May test explosion. Arianespace is set to fly 36 satellites on an Ariane 6 no earlier than November 23.
Note the phrase no earlier than. That's a target, not a commitment, and the reporting doesn't say whether this failure affects it.
And the Starlink comparison?
SpaceX deployed 26 Starlink satellites on a Starship test flight the day before and caught a spacecraft with tower arms. The timing makes the contrast stark.
Though that was a test flight, and the article doesn't say how Amazon's 2026 service timeline changes. That's still unanswered.
El Pulso
- A Vulcan rocket carrying 40 Amazon Leo satellites broke apart in the air ten minutes after leaving Florida, and the payload never reached orbit.
- ULA, a company about twenty years old, faces its first mission failure just as it was trying to settle into a steady launch rhythm.
- Amazon has been waiting since July to resume launches, and the loss of its largest-ever batch deepens the gap in its planned constellation.
- With New Glenn grounded after a May test explosion, Amazon is leaning on an Ariane 6 launch set for November 23 to keep its schedule alive.
- Engineers have not yet identified the cause, and the answer will determine how quickly Vulcan can fly again.
On a Sunday afternoon at Cape Canaveral, a Vulcan rocket carrying forty satellites for Amazon's Leo network fell silent ten minutes into its climb, and the satellites never reached the orbit they were built for. It is the first failure in the two-decade history of United Launch Alliance, a young enterprise that now carries the weight of a rival's ambitions and its own hopes for a steady cadence of flights. The cause remains unknown, and in the way of all new machines, each loss is also a lesson written in data not yet read. For Amazon, the sky has become a crowded, uncertain place, where its answer to Starlink must now wait on delayed rockets and a distant launch from French Guiana.
At 12:40 pm on Sunday, a Vulcan rocket lifted off from Space Launch Complex 41 at Cape Canaveral, carrying 40 satellites meant to expand Amazon's Leo internet network. Ten minutes into the flight, something went wrong, and the satellites never reached orbit.
United Launch Alliance, the company that runs the rocket and is jointly owned by Boeing and Lockheed Martin, confirmed the anomaly. Its Launch Director had received data showing the vehicle had failed to deliver the mission, but the company said it did not yet know why. It described every flight as a source of learning, even when the lesson comes at a painful price.
For Amazon the loss is serious. The company had bought 38 launches from ULA and expected Vulcan to carry nearly half of the first generation of its planned 3,232-satellite network. This was the largest batch it had ever attempted on one flight, and Amazon had not launched anything since July. Its commercial service was supposed to begin in 2026.
Amazon's response was measured. It acknowledged that every launch carries risk, especially inaugural ones, and expressed confidence that ULA would learn and deliver on Vulcan's long-term promise.
The company's alternatives are limited. Blue Origin's New Glenn has been grounded since a test explosion in May, and Arianespace is set to launch 36 Amazon satellites on an Ariane 6 from Kourou no earlier than November 23. The contrast with Starlink sharpened the moment, since SpaceX had deployed 26 large satellites on a Starship test flight just one day earlier.
Now attention turns to what ULA's data reveals and whether the Ariane 6 launch holds its date.
At 12:40 pm local time on Sunday, a Vulcan rocket left Space Launch Complex 41 at Cape Canaveral, Florida, carrying 40 satellites for Amazon's Leo internet network. About ten minutes later, something went wrong, and the satellites never reached orbit.
United Launch Alliance, the company that operates the rocket, confirmed the failure in a statement. Based on data received by its Launch Director, ULA said, the Vulcan vehicle suffered an anomaly ten minutes into the flight and failed to deliver the Amazon mission to orbit. The company said it did not yet know why. Because the anomaly had only just happened, it said, it had no specific data to explain what occurred, adding that every flight generates data and teaches the company something.
The failure is the first for ULA, a company about two decades old and jointly owned by Boeing and Lockheed Martin. It is also a setback for Vulcan, its flagship rocket, as ULA tries to settle into a regular launch rhythm for Amazon's growing constellation.
The stakes for Amazon are considerable. According to Agence France-Presse, the company has bought 38 launches from ULA, and Vulcan was expected to carry nearly half of the first generation of Leo satellites, a network planned at 3,232. The lost flight was the largest batch Amazon had ever tried to put up on a single mission. Since April 2025, the company has deployed around 400 satellites, though it had not launched any since July. Amazon had planned to start its commercial internet service, Amazon Leo, in 2026.
In a post on X, Amazon Leo struck a measured tone. There is risk with any launch, it wrote, especially on inaugural missions, and it said it believed ULA would learn from this one and deliver on its long-term plans for Vulcan.
Amazon does not depend on Vulcan alone, but its other options are constrained. Blue Origin, founded by Jeff Bezos, builds the New Glenn rocket, which is also expected to carry Amazon satellites. New Glenn has been grounded since an explosion during a test in May. Amazon is also a major commercial customer of the French company Arianespace, which is scheduled to launch 36 Amazon satellites on an Ariane 6 rocket from Kourou, French Guiana, no earlier than November 23.
The timing sharpens the contrast with Amazon's chief rival. Amazon competes with Elon Musk's Starlink in satellite internet, and the Vulcan failure came one day after SpaceX deployed 26 large Starlink satellites during a test flight of its Starship rocket. That flight also achieved the first-ever catch of a spacecraft using mechanical arms on its launch tower, a step toward reusable rockets.
What to watch now is what ULA's data reveals about the cause, and whether the Ariane 6 launch holds its November 23 target at the earliest.
Citas Notables
Since the anomaly just occurred, we don't have any specific data yet to understand what occurred today.— United Launch Alliance statement
There is risk with any launch, and that's especially true for inaugural missions.— Amazon Leo, post on X