SpaceNexus Launch Cadence and Slip Report

Attempts by provider

Every provider with a recorded launch attempt in the month, with outcomes and share of the month.

Provider names are as Launch Library records them; no names are merged, so a group launching under two recorded names appears twice.

Attempts by vehicle

Launch vehicles flown in the month, by attempts.

Launches behind these tables

Every recorded launch attempt in the month, in date order. This is the row set the tables above are computed from.

Manifest changes observed in the month

Every launch date move our ledger recorded inside the month. Positive days moved later; negative days moved earlier.

Schedule movement by provider

Held back until the month's ledger holds at least 25 observations. This month holds 5, and a rate computed from that many would not mean anything.

Nothing to report in this table for this edition. An empty table here means we recorded nothing, not that nothing happened.

Vehicles not currently flying

From the hand-maintained vehicle status sheet. Each row carries the date the entry was last checked, so a stale sheet is visible rather than silently trusted.

Methodology

• •Launch counts come from the SpaceEvent table, restricted to rows carrying a Launch Library 2 identifier and a terminal outcome (completed or failed). Curated seed events, which are not launches, are excluded by identifier shape.
• •A launch is attributed to the month its launch date falls in, in UTC.
• •"Attempts" counts every launch that left the pad and reached a recorded outcome. Success rate is successes divided by attempts for that month; a month with no attempts reports no rate rather than zero.
• •Provider is the agency recorded on the launch row as Launch Library spells it; no provider names are merged or renamed.
• •Slip figures come from the LaunchDateChange ledger, which records every manifest date move we observe. The ledger starts on 2026-08-29 and cannot be backfilled by anyone, us included — Launch Library exposes no revision history. Months before that date report launches without slips, and the page says so.
• •Per-provider slip statistics appear only once the ledger holds enough observations to be worth reporting; below that threshold the section states the count instead of publishing a rate.

What this edition can and cannot see

Coverage limits travel with the numbers, here and in every export of them.

• •This edition counts 26 launch attempts recorded for August 2026 — rows carrying a Launch Library identifier and a terminal outcome. Scrubbed and still-upcoming launches are not attempts and are not counted.
• •Launch counts describe our tracker. A month our launch history does not reach reports zero attempts, which is why every edition prints the count rather than only a rate.
• •Schedule movement comes from a ledger that began recording on 2026-08-29 and cannot be backfilled — Launch Library keeps no revision history, so no one can reconstruct moves observed before that date. Recording started part-way through this month, so the slip figures cover only part of it.
• •Per-provider slip statistics are withheld this month: 5 observations is below the 25 needed for a rate to mean anything.
• •Of 5 observed changes, 4 moved a launch later and 1 moved one earlier. The median move was 1 days.
• •No figure on this page is a forecast. This release publishes the record; it does not project cadence.

Cite this edition

SpaceNexus Launch Cadence and Slip Report, August 2026. SpaceNexus, data as of 2026-08-31. https://spacenexus.us/releases/launch-cadence/2026-08. https://spacenexus.us/releases/launch-cadence/2026-08 (retrieved 2026-09-15).