Published
As of Nov 3, 2026, Amazon hasn’t named any US state, region or date for its first Amazon Leo service. It has said only that service will begin in northern and southern latitudes and expand gradually toward the Equator.
That sentence has started a lot of guessing, especially in northern states. The orbits behind it are real, but they describe where satellites crowd, not where Amazon will sell.
What Amazon said, Feb 12 to Oct 29, 2026
Amazon Leo (formerly Project Kuiper) first tied its rollout to latitude on Feb 12, 2026, said “certain latitudes” and “initial latitude bands” in July, then switched to “certain locations later this year” in September; none of those statements names a latitude, a country or a US state. Our initial-service explainer quotes each one with its date.
Why satellites bunch up near their orbit’s tilt
Every satellite shell has an inclination, the tilt of its orbit against the Equator. A satellite in a 51.9-degree orbit swings between 51.9 degrees north and 51.9 degrees south on every pass.
It doesn’t spend equal time at every latitude. It crosses the Equator at a steep angle and moves on quickly, then turns at the top and bottom of its path, where it travels nearly east to west for a while. Put dozens of satellites in the same shell and they crowd together near those turning points and spread thin over the Equator. So the latitudes just below a shell’s tilt get the most satellites overhead, and the tropics get the fewest.
Amazon’s first-generation network, as listed in the FCC’s Feb 10, 2026 grant, has these shells:
- 630 km at 51.9 degrees
- 610 km at 42 degrees
- 590 km at 33 degrees and 30 degrees
By tracker data from late October 2026, every Leo satellite launched so far is in the 51.9-degree shell. That fits Amazon’s “northern and southern latitudes” wording: today’s satellites are densest at the higher mid-latitudes, north and south of the Equator alike.
How far each shell can reach depends on how low in the sky a terminal can still connect. Amazon’s 2019 filing gives that as 35 degrees above the horizon. At that angle, the calculated northern edge of each shell is roughly 36.4 degrees north for the 30-degree shell, 39.4 for the 33-degree shell, 48.6 for the 42-degree shell and 58.7 for the 51.9-degree shell. Those are geometry, not service promises, and coverage right at an edge comes and goes. Amazon’s filing claims continuous coverage only to about 56 degrees.
Coverage first, capacity later
Being under the densest part of a shell helps with one thing: having a satellite overhead often enough for a steady connection. It doesn’t guarantee room on the network. Each satellite can serve only so many homes at once, and Amazon has about a quarter of the 1,616 satellites its licence originally required by July 2026. The FCC let the licence continue anyway, and all 3,232 first-generation satellites are now due by Jul 30, 2029.
Amazon’s own wording reflects that order of events. On Sep 22, 2026 it said it would “begin rolling out initial service in certain locations later this year, and will expand coverage as we launch more satellites and add coverage and capacity to the network.” Coverage and capacity grow with each launch, and no Leo launch has happened since Jul 2, 2026. The next with an announced date is LV-01 on Vulcan, targeted for Nov 13.
The lower shells change the picture over time. The 42-degree shell would thicken coverage across the middle of the lower 48, and the 33- and 30-degree shells would do the same farther south. None of those shells has satellites yet, and Amazon hasn’t published a schedule for filling them.
What Amazon’s 2019 FCC plan said
People often quote one line from Amazon’s 2019 technical filing (FCC application SAT-LOA-20190704-00057): “During deployment, full-time commercial service will initially be available between 39°N-56°N and 39°S-56°S latitudes.” The FCC’s 2020 order summarized the same application as saying “service will begin once the first 578 satellites are launched”, and the filing’s first phase put all 578 in the 630 km, 51.9-degree shell.
Treat it as history. It’s a 2019 plan for a network Amazon has since changed. Amazon now says nearly 400 satellites are enough to begin, not 578. And Amazon hasn’t restated the 39-to-56-degree band in 2026, or said its “initial latitude bands” follow it. It’s the clearest public hint of how Amazon once thought about rollout, not a map of where service starts.
Where the lower 48 sit on that map
For orientation only, here’s where some US places fall against those lines, using Census latitudes. This is not a service map, and no place on it is marked as first.
| Reference line or place | Latitude (north) | Note |
|---|---|---|
| Continuous-coverage limit in Amazon’s 2019 filing | 56 | Most of Alaska lies north of it |
| Seattle | 47.62 | |
| Fargo | 46.87 | |
| Minneapolis | 44.96 | |
| Chicago | 41.84 | |
| Denver | 39.76 | |
| Baltimore | 39.30 | |
| 2019 filing’s initial full-time band, southern edge | 39 | A 2019 plan, not a 2026 promise |
| Washington, DC | 38.90 | |
| St. Louis | 38.64 | |
| Dallas | 32.79 | |
| Miami | 25.78 | |
| Honolulu | 21.32 | Inside the designed coverage area, far from the 2019 initial band |
Two cautions. First, latitude alone doesn’t decide who gets service. Capacity, ground stations, licences in each country, and where Amazon chooses to sell all matter, and Amazon has published none of that for the US. Second, “northern and southern latitudes” applies to the whole planet. Amazon’s partners include Australia’s nbn, which expects customers to begin moving over from around mid-2027, and providers in Europe and Africa. Amazon hasn’t said the US is in its first group.
Alaska and the 56-degree edge
Alaska is the one US case where the answer is clearer, and it’s mostly no for now. The FCC’s 2020 order, describing Amazon’s own design, says: “Given the proposed design of the Kuiper system, service cannot be provided to the majority of Alaska.” By our computation from 2020 Census blocks, about 96% of Alaskans live north of 56 degrees.
What could change that is the polar system the FCC approved on Feb 10, 2026: 1,292 satellites at 66 to 82 degrees. None of those satellites has launched, and half aren’t due until Feb 10, 2032. Our Alaska page covers the details.
Hawaii and the US territories sit inside the network’s designed coverage area but well south of the 2019 initial band. The FCC’s 2020 order describes the design as “serving the contiguous United States, Hawaii, U.S. territories, and other world regions.” Puerto Rico and the US Virgin Islands lie near 18 degrees north, Guam near 13 degrees and American Samoa near 14 degrees south, all far from the shells where today’s satellites are densest. Amazon’s household sign-up form lists those territories as separate entries in its country menu, but Amazon has given no date for any of them, and leo.amazon.com has no coverage map or address check to look a place up.
What this means if you’re deciding where you live
If you’re in a northern state, Amazon’s wording fits where today’s satellites are densest, and that’s as far as it goes. Amazon hasn’t said the US is in the first bands, it hasn’t named a state, and it has no US price or order page. If you’re in the South or Southwest, the 2019 plan suggests later phases, but that plan is seven years old.
For your address, the latitude question will be settled by a list of named places, not by orbital geometry. Until Amazon publishes one, no latitude chart, including this one, can tell you when Leo reaches you.
Common questions
Which states get Amazon Leo first?
Will northern states get Amazon Leo before southern states?
How far north can Amazon Leo's first satellites reach?
How these facts were checked
Every claim in this post comes from the sources listed below, each read on the date shown, and Amazon Leo items say how sure they are (announced, reported, not announced). This post was drafted with AI assistance from those sources; the site owner checked each number, date and quote against them before it went up. Read the editorial policy.
Where each fact comes from
- Amazon: first Ariane 64 mission (northern and southern latitudes) · checked
- Amazon: South Africa, Herotel (certain latitudes) · checked
- Amazon: direct-to-device explained (initial latitude bands) · checked
- nbn: a major step closer to nbn LEO (Australia, from around mid-2027) · checked
- Vodafone and Amazon Leo agreement (Europe and Africa) · checked
- FCC 20-102: Kuiper Systems authorization (Jul 30, 2020) · checked
- Amazon: Amazon Leo in Uzbekistan (certain locations, coverage and capacity) · checked
- Amazon Leo mission updates (LV-01 date) · checked
- FCC DA 26-553 (1,616 and 3,232 milestones) · checked
- Amazon Leo US site (Join the list, no coverage map) · checked
- Census 2024 Gazetteer, places (latitudes) · checked
- Census 2020 redistricting file, Alaska (population by latitude) · checked

