Summary

  • Amazon reports peak downloads above 400 Mbps in a Leo Pro demonstration. That is evidence of a working connection, not a promise of continuous service at that speed.
  • The FCC has kept the constellation's deployment authority from automatically shrinking at its interim deadline, but retained conditions on priority, the bond and the final milestone.

A laptop is a useful antidote to a satellite presentation. Either the data arrives or it does not. In a recent demonstration hosted by DEVCOM C5ISR in Aberdeen, Maryland, Amazon says a Leo Pro terminal and laptop exchanged data through passing satellites, reaching peak downloads above 400 Mbps. More than 30 U.S. Army attendees watched the demonstration, according to the company's October 13 announcement.

That is a meaningful result for Amazon Leo. It brings the project down from launch schedules to something a prospective user can try. But the question changes when the laptop belongs to a paying customer: what connection will be available tomorrow, at a particular location, for the hours the customer needs?

The reported peak does not answer that. Amazon describes further work on higher speeds, mobility and integration. Its account supports the demonstration and an ongoing partnership; it does not establish a new procurement award or the terms of an Army service commitment. Nor does the absence of those terms from this announcement establish that no contract exists.

Three counters, three different jobs

Amazon said it had manufactured more than 1,000 satellites and had nearly 400 in low Earth orbit. The first number records factory output; the second records spacecraft in space. Neither, on its own, tells a customer how much usable capacity is available at a given place and time.

The distinction becomes unusually clear in the next mission's description. In its October 14 update, Amazon schedules LE-04 no earlier than November 23, with 36 satellites aboard Ariane 64. They are to separate at roughly 465 kilometres, establish contact and undergo health checks before moving to a 630-kilometre operational orbit. A successful release is an important step. It is not the last step.

There is work on the ground too. Amazon's system description identifies ground infrastructure, satellites and customer terminals as its three main components. Gateways connect the satellite system to internet, cloud and private networks. For a customer, all of that has to work together; the most photogenic component is not necessarily the one that determines whether a service can be supplied.

Even the speed numbers have different meanings. Leo Pro is advertised with download speeds up to 400 Mbps. The demonstration announcement reports a peak above that figure. A product specification and a reported test peak are not interchangeable with an average, a minimum or a contractual guarantee.

A waiver with conditions attached

The regulatory story has a similar temptation: compress several conditions into one reassuring word. The FCC's June 5 order, DA 26-553, granted Amazon Leo limited relief from its interim deployment milestone. It did not simply give the company an unconditional two-year extension.

The modified Gen1 constellation comprises 3,232 satellites. The interim requirement was to deploy and operate half—1,616—by July 30, 2026. The waiver prevents an automatic reduction of the authorised constellation to the number operating at that interim date. The final July 30, 2029 deadline remains.

There is a price in priority. Satellites not deployed and operational by the interim date temporarily lose their earlier place in the relevant spectrum-processing rounds. That period runs until March 30, 2028, or until half the constellation is launched and operational, whichever comes first. The order also provides a shorter, 15-month period if Amazon certifies both that it has constructed half the Gen1 satellites and that it has secured enough launches to deploy them. That is a conditional route, not evidence that the certification has occurred.

Priority matters when systems must share spectrum; losing it is not a blanket ban on service. The FCC also declined to waive the bond requirement. The order sets out forfeiture if the interim requirement is missed, but is not itself a record of a later bond collection. And Amazon's approximate October orbital count is not a certified account of what was deployed and operational on July 30.

The laptop, then, shows a connection that worked. The launch programme shows how Amazon plans to add spacecraft. The order explains the conditions under which the build-out can continue. A customer needs those strands to converge into a service that can be ordered, installed and relied on. The next persuasive evidence will be less spectacular than a peak speed: repeated performance over a stated period, in a stated location, under terms that say who answers when it stops.

Updated October 25, 2026: Clarifies the FCC's conditional 15-month priority provision and the distinction between manufacturing, orbital deployment and service readiness. The original publication date and URL are retained.