Project Kuiper is Amazon’s satellite internet constellation, built to deliver low-latency broadband from thousands of satellites in low Earth orbit, the same basic approach SpaceX’s Starlink pioneered at scale. Amazon has begun marketing the consumer service under the name Amazon Leo, though “Project Kuiper” remains the name most commonly used for the underlying satellite program and the one most searchers still use. As of 2026, Amazon has launched more than 392 production satellites, putting it in third place among active constellations, well behind Starlink but ahead of most other operators, while it works through a regulatory deadline dispute with the Federal Communications Commission (FCC) over how fast it must deploy the rest of its fleet.
What Project Kuiper Is Building
Project Kuiper is designed around the same low-orbit physics that made Starlink’s low latency possible: satellites flying a few hundred kilometers up complete an orbit quickly and are only in view of any single ground point for a few minutes, which requires a very large fleet to provide continuous coverage. Our LEO satellites explainer covers why that low-orbit tradeoff, more satellites needed, but far less delay, defines this whole category of constellation.
Amazon’s authorized license covers up to 3,236 satellites, and the company has since won approval for a much larger Gen2 expansion, bringing its total authorized fleet toward 7,727 satellites following FCC approval in January 2026. That scale positions Project Kuiper as a genuine long-term rival to Starlink in raw fleet size, even though its actual deployed satellite count remains far smaller today.
Deployment Progress and the FCC Deadline Fight
As of 2026, Amazon has launched more than 392 production satellites across 19 missions, a real but still early-stage build-out compared with Starlink’s thousands of operational satellites. That pace has put Amazon in direct conflict with its own regulatory obligations: the FCC’s original license required the company to have roughly half of its authorized 3,236-satellite constellation, about 1,618 satellites, in orbit by July 30, 2026.
Amazon has not kept pace with that requirement and has formally requested a deadline extension to 2028, telling regulators it expects only around 700 satellites in orbit by the original July 2026 date, well short of the 1,618-satellite milestone. That shortfall is a meaningful signal for anyone tracking the constellation’s progress: launch cadence, not satellite design, has been the binding constraint on how fast Project Kuiper can scale, and the FCC’s response to the extension request will shape how much regulatory pressure Amazon faces going forward.
Launch Vehicles
Amazon has deliberately spread Project Kuiper’s launches across a wide mix of rockets rather than relying on one provider, with more than 80 missions planned across Atlas V, Falcon 9, Ariane 6, Vulcan Centaur, and Blue Origin’s New Glenn. Notably, that mix includes Falcon 9 flights from SpaceX, Amazon’s most direct competitor in the satellite-broadband market, a pragmatic choice that trades some competitive awkwardness for launch-schedule flexibility. Our Vulcan rocket explainer covers how that vehicle in particular has become one of Kuiper’s primary launch partners, carrying a large share of its national-security-adjacent and commercial payload manifest.
Amazon has planned more than 20 Kuiper-related launches in 2026 alone and over 30 more in 2027, reflecting how much the constellation’s near-term growth depends on keeping multiple rockets flying in parallel rather than waiting on any single vehicle’s production and launch cadence.
Service Timeline
Amazon has targeted a mid-2026 launch for customer-facing Leo/Kuiper broadband service, though, as with Starlink’s own rollout, availability is expected to expand gradually rather than switch on everywhere at once. Coverage depends on having enough satellites overhead in a given region and on securing the local regulatory approvals a satellite internet service needs before it can legally operate in a given country, the same two constraints that shaped how unevenly Starlink’s own coverage map filled in over its first several years.
Project Kuiper vs. Starlink vs. OneWeb
| Provider | Orbit | Satellites in orbit (2026) | Position |
|---|---|---|---|
| Starlink | Low Earth orbit | Thousands, largest fleet | Established, serving consumers and enterprise worldwide |
| Project Kuiper (Amazon Leo) | Low Earth orbit | 392+ | Deploying, targeting mid-2026 service launch |
| OneWeb (Eutelsat) | Low Earth orbit | Established, smaller fleet | Enterprise and government focus |
Starlink’s multi-year head start and vastly larger deployed fleet give it a clear scale advantage today, but Amazon brings resources few competitors can match: its own cloud infrastructure through AWS and an enormous existing retail and logistics footprint that could accelerate customer acquisition once the constellation reaches meaningful coverage. OneWeb, now part of Eutelsat, has taken a narrower path, leaning toward enterprise and government customers rather than competing directly for consumer broadband subscribers the way both Starlink and Kuiper aim to.
Why Project Kuiper Matters Beyond Amazon
A second large-scale low-orbit broadband constellation, even one still building toward full deployment, changes the competitive and regulatory picture for satellite internet generally. It gives regulators and customers an alternative to a Starlink-dominated market, adds real demand for launch capacity across multiple rocket providers rather than concentrating it with one company, and tests whether a well-capitalized entrant with a different core business, cloud computing and retail rather than rockets, can execute a satellite megaconstellation on a comparable timeline. The FCC deadline dispute now underway is an early test of how much regulatory patience that kind of ambitious, resource-backed but behind-schedule build-out actually gets.