A United Launch Alliance Vulcan rocket carrying 40 Amazon Leo broadband satellites failed about 10 minutes after lifting off from Cape Canaveral, Florida, on Sunday, November 15, 2026, and never delivered its payload to orbit. All 40 satellites — hardware intended for the network Amazon is building to compete with SpaceX’s Starlink — were lost, and Reuters reported it was the launch company’s first mission failure in 20 years of operations.
Key facts
- 12:40 p.m. ET: the rocket lifted off from Space Launch Complex 41 at Cape Canaveral Space Force Station, according to Primetimer.
- About 10 minutes in: the vehicle suffered an anomaly and failed to reach orbit.
- Roughly 50 minutes after liftoff: ULA confirmed the failure, Primetimer reports.
- The flight was the first of 38 Vulcan launches Amazon had purchased from ULA, according to the Free Press Journal. Amazon referred to it as LV-01.
- The exact cause of the malfunction is unknown and under investigation.
Why it matters
Amazon Leo, previously known as Project Kuiper, is the service Amazon is assembling to challenge Starlink in consumer and enterprise satellite broadband. Every lost launch pushes back the point at which a second large low Earth orbit network can offer customers an alternative.
The gap is wide. Наша Ніва reports that Starlink has more than 11,000 satellites and millions of customers, against 398 Amazon Leo satellites in space — a lead detailed in Starlink’s own constellation and subscriber totals.
There is also a structural difference the sources highlight. Наша Ніва notes that SpaceX launches its satellites on its own rockets, flying Starlink missions often enough to make up 85 percent of SpaceX’s launches this year, while Amazon must buy launches from other companies and absorb their schedules and setbacks.
Investigation and fallout
What ULA has said
ULA, a joint venture between Boeing and Lockheed Martin, said in a statement posted on X and quoted by The Verge that the Vulcan vehicle suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit. The company said it was unclear what caused the failure and pledged transparency as the investigation continues.
“Since the anomaly just occurred, we do not yet have specific information to understand what happened,” the company said in remarks carried by Наша Ніва. The Free Press Journal reports ULA will work with Amazon and other organisations to find the cause and apply corrective measures before flying again.
A troubled return to flight
Sunday’s mission was Vulcan’s fifth flight since the rocket debuted in 2024 — Primetimer dates the first flight to January 2024 — and its first launch after a hiatus of roughly nine months.
Primetimer reports that two earlier Vulcan flights had problems with the rocket’s solid rocket boosters, with part of a booster nozzle burning through and falling off around 30 seconds after liftoff. In both cases the payloads still reached orbit. Before the November launch, ULA said it had changed the nozzle design and production process.
The Free Press Journal adds that Vulcan had also faced technical concerns involving its BE-4 engines, supplied by Jeff Bezos-owned Blue Origin, and that investigators had not established whether the earlier problems contributed to Sunday’s failure.
The Pentagon angle
Наша Ніва reports that the Pentagon was awaiting the outcome of this flight before recertifying Vulcan to launch national security satellites. Primetimer adds that the US Space Force had paused national security launches on Vulcan until ULA fixed the booster nozzle problem, and that ULA had hoped Sunday’s mission would demonstrate the rocket was ready to fly again. None of the sources say what the Space Force will now require.
Where Amazon Leo stands
The sources differ slightly on Amazon’s tally. The Free Press Journal, citing Reuters, says Amazon had deployed 398 satellites across 14 launches since 2025. Primetimer puts it at around 400 satellites across 15 missions. Both agree Sunday was Amazon’s first Leo mission on Vulcan.
It is not the first launch-side blow this year. Наша Ніва reports that in May, Blue Origin’s New Glenn rocket exploded during testing just days before a scheduled launch of Leo satellites. Even so, Amazon has kept selling the network ahead of full coverage, winning its first big airline customer before the Vulcan loss.
What to watch next
No source identifies the cause of the anomaly, gives a date for the investigation’s findings, or says when the next Vulcan flight or Amazon Leo launch will take place. Three markers will show how long the setback lasts: ULA’s first substantive update on the anomaly, which the company has promised but not scheduled; whether the Space Force restates its conditions for recertifying Vulcan for national security missions; and whether Amazon shifts satellites onto its Falcon 9, Ariane 6 or New Glenn contracts rather than waiting out a Vulcan grounding that Наша Ніва says could run months. The sources do not address availability or pricing for Amazon Leo in any African market.
Frequently Asked Questions
How many satellites does Amazon still need for global coverage?
Amazon needs 3,236 satellites for its planned global coverage, according to Reuters as cited by the Free Press Journal. Against the 398 launched so far, that is roughly one-eighth of the planned total based on Reuters’ two figures.
Which rockets have carried Amazon Leo satellites so far?
Atlas V, Falcon 9 and Ariane 6, with November 15 marking the first Amazon low Earth orbit launch on Vulcan, Primetimer reports. The Free Press Journal adds that Amazon also holds launch agreements with SpaceX, Blue Origin and Europe’s Arianespace.
How long could Vulcan be grounded after the failure?
Several months, Наша Ніва reports, if the investigation drags on. ULA has committed only to working with Amazon and other relevant organisations to identify the cause and apply corrective measures before resuming launches, according to the Free Press Journal.
How did Amazon respond to losing its satellites?
Amazon called ULA a trusted partner it believes will learn from the mission, in a post on X reported by The Verge. The company added that there is risk with any launch, especially inaugural missions like LV-01.













