Amazon Leo LV-01: launch time, payload and what it proves

Amazon Leo's first Vulcan mission is targeting November 13, 2026, with 40 satellites aboard. For people following Amazon's satellite internet rollout, the useful distinction is between a planned flight, confirmed deployment and an actual service offer. A launch target is evidence about the first of those stages, not a substitute for the other two.

The announcement is timely because a new launch vehicle can add a deployment route. It also creates an easy misunderstanding: a date attached to a rocket mission can be read as a date when a household can order broadband. The documents checked for this report describe a mission, not an address-specific subscription opening.

The scheduled flight and where to check it

ULA's live Vulcan Leo 1 mission page lists November 13 at 12:54 p.m. EST, or 17:54 UTC, as the launch time. It identifies the vehicle as Vulcan VC6L with six solid rocket boosters and a low-Earth-orbit-optimized Centaur V upper stage, departing Space Launch Complex 41 at Cape Canaveral Space Force Station in Florida.

That page also provides a launch livestream and live updates. Use the mission identifier as well as the date when checking again: a search result or an old countdown can preserve an earlier schedule. This report was checked November 12; the stated time remains a target, not a report that liftoff or satellite deployment has happened.

What Amazon says this mission adds

Amazon's November 9 mission announcement identifies LV-01 as its first Vulcan flight and the first of 38 contracted Vulcan launches. The company calls the 40-satellite payload its largest Leo batch yet. Those statements describe the planned payload and contracted program; they do not establish the outcome of this flight.

A second launch vehicle matters as a deployment option, but readers should keep a contract count separate from completed missions. A commitment to future launches is a schedule input, not a measurement of satellites already operating. Likewise, carrying more spacecraft on one flight does not by itself quantify the change in a particular customer's coverage or connection quality.

Three records to keep separate

A useful way to follow LV-01 is to maintain three short evidence records rather than a single launch-date note.

• Mission record: the current target, mission name and operator source, followed by whatever outcome the operator actually confirms. Do not replace a planned event with past tense before that confirmation exists.
• Network record: the operator's subsequent account of the spacecraft's status. A launch report and a statement about readiness to provide service answer different questions.
• Customer record: an offer that applies to the reader's location and intended use, including the terms actually presented. A launch livestream cannot supply those details.

This is an editorial reading framework, not a claim that we observed the mission or tested a terminal. Its purpose is to make the remaining uncertainty visible. If one record is still missing, leave that field open rather than filling it with a date taken from another stage.

A deployment update is not a household buying recommendation

Amazon's running mission log labels the LV-01 target as pending range approval. The log is useful for checking the named flight against the broader sequence; its original publication date should not be mistaken for the date of every update within it.

For a household deciding whether to replace an existing connection, the practical evidence needed is more specific than a payload count. Check whether an actual offer covers the address, what equipment and recurring charges it lists, and which usage and cancellation conditions apply. These are questions to verify in an offer, not terms established by this mission announcement.

There is no measured speed, latency, price comparison or service-availability test in this report. It would be premature to turn LV-01 into a recommendation to cancel another provider. The defensible next step is narrower: follow the official mission outcome, then assess service information on its own evidence. Keeping those steps separate makes a genuine deployment milestone informative without asking it to prove a consumer launch that the cited documents do not establish.