Chinese commercial provider (Interstellar Glory); flies the solid Hyperbola-1 and is developing the reusable methalox Hyperbola-3.
Orbital launches per quarter, with failed attempts highlighted. A shrinking interval between launches signals a provider scaling; a widening one flags bottlenecks. Method →
Fewer than two launches in the last 12 months, so there's no meaningful average interval to report yet — the quarterly record below still shows the cadence so far.
Fill consistency — how close each family flies to its own demonstrated peak payload. A consistency read, not absolute efficiency. Full method →
No cargo-utilization data yet for this provider's rockets (fewer than the minimum scored LEO flights in the measurement window).
A directory of the companies and agencies flying rockets to orbit (one row each, click to expand to the rockets in their fleet), joining a hand-curated catalog of providers and rockets to live launch counts, success rates, mass to orbit and cargo economics. Launch providers fly the rockets — distinct from satellite operators, who run the fleets in orbit.
Each row is one launch provider; expanding it shows the rockets in its fleet. I curate the provider’s identity (name, parent company, country, ownership) and each rocket’s specs (lift class, reusability, status, orbit reach, payload to LEO, published list price), then join at request time to live launch activity.
Launch Library 2 (TheSpaceDevs), /launch/previous/ for the current year — the same fetch the homepage and /launches use, so the totals reconcile. Launches YTD is a provider’s share of that count; share of global launches is the provider’s count ÷ all orbital launches this year.
My historical launch record (Launch Library 2, backfilled into Supabase) — the same data behind /failures. Success rate is 1 − the failure rate over the trailing 24 months. Providers with fewer than 5 launches in the window are flagged as a small sample (asterisk), because a single failure would otherwise swing the rate wildly.
Jonathan McDowell’s GCAT (launch.tsv), the same dataset behind /mass-to-orbit. Mass YTD is the payload mass a provider has delivered to orbit this year; share of global mass is that ÷ the year’s total.
Provider identity, ownership, one-line context, notable customers and every rocket’s specs are hand-curated in src/lib/launcher-catalog.ts. Western vehicles cite manufacturer spec pages; non-Western and commercial figures are often public estimates with no official spec sheet — those are flagged with an asterisk pending a source-by-source verification pass.
Sticker price at full capacity — a rocket’s published list price ÷ its advertised maximum LEO payload. This is NOT what any single customer pays: real missions rarely fill the rocket to its LEO maximum, and rideshare or marginal pricing differs. A row shows its cheapest rocket’s figure. Coverage is partial by design — most state providers don’t publish a price, so their $/kg reads ‘not published’ rather than a guess.
Each rocket is tagged with the orbit regimes it can deliver to — LEO, MEO, GEO, or Beyond (lunar / interplanetary / escape) — from demonstrated capability, or design intent for in-development vehicles. Curated.
Read the denominators carefully. Launches, share of launches, success rate and mass to orbit count ALL orbits — a GEO comsat or an interplanetary probe counts the same as a LEO Starlink batch. $/kg, payload-to-LEO and cargo utilization are LEO-specific, because LEO is the standard reference orbit for comparing capability and cost. So a row’s all-orbit ‘Mass’ and its LEO-only ‘$/kg’ are not the same denominator; the orbit-reach tags on each rocket show where it actually flies.
Launch data arrives keyed by provider, but the three sources name the same provider differently, so I normalize each to one catalog key. The biggest correction is CASC: GCAT splits China’s Long March family across its academies and subsidiaries (CALT, SAST, CGWIC, Changzheng, China Rocket Co.), which I fold back into CASC so its launch and mass totals aren’t undercounted — the launch-provider analog of the Guowang attribution on /constellations. Roscosmos similarly absorbs its VKS, Khrunichev and RKK Energiya designations; JAXA folds in Mitsubishi Heavy (the H3 operator); ISRO folds in its commercial arm NSIL.
The catalog covers every provider with an orbital launch since 2023 — about 24 providers, roughly 97% of this year’s launches. Launches by an uncatalogued provider show in the page’s ‘Not yet catalogued’ row so the coverage figure stays honest.
A curated, marquee list per provider, cross-linked to /constellations where the customer is a satellite operator I track. It’s editorial, not a complete manifest — a live ‘top customers this year’ derivation is planned but not yet wired.
Filters apply in the browser over the loaded rows (no refetch) and are encoded in the URL so a filtered view is shareable. Lift class, reusability and rocket status match a provider when ANY of its rockets qualifies; ownership and region are provider-level. Region is derived from the provider’s country — US, China, EU/ESA (the 22 ESA member states) or Other (everything else, including Russia). Within a category, selections are OR; across categories, AND.
Many payload and price figures are public estimates, not official specs (flagged with an asterisk). List price ÷ max-LEO is a capability-normalized sticker price, not a transaction price. Lift class is curated from demonstrated payload and can sit on a boundary. Success rate uses a rolling 24-month window, so it diverges from program-lifetime figures elsewhere. The scheduled-ahead count is best-effort from LL2’s near-term manifest, not a full backlog. Values are computed live at fetch time; the directory doesn’t yet show captured history.
Launch Library 2 (TheSpaceDevs) — attribution required. GCAT — Creative Commons CC-BY (J. McDowell, planet4589.org/space/gcat). Rocket specs, list prices and customer lists are curated and attributed per claim to their original source.