Watch the frontier
leave the ground.

Country filters use the active upcoming source’s launch-pad country / territory; annual country statistics use Launch Library 2 pad locations. Neither means launch-provider nationality or payload-owner country. Provider countries appear separately in mission details when supplied. International or unknown entries are not silently reassigned.

The annual view covers the selected year’s orbital launch-attempt records from Launch Library 2, not payload or satellite counts. Suborbital records are excluded by the source query. A full-year total is shown only when every page in the selected historical result set has been retrieved and validated. Source-record coverage and exclusions are shown with the totals.

Success, failure and partial failure are separate outcomes. An attempt with no final outcome is listed as unknown/pending; unconfirmed past schedule entries are not automatically counted as flown attempts. Launch-vehicle outcome is not the same as successful payload operation.

When fresh Launch Library 2 upcoming data is unavailable, the tracker can show the independent RocketLaunch.Live free next-five feed. It is not a complete upcoming catalog. The Site excludes any suborbital records in that small feed and does not infer provider nationality, payload ownership, payload count or orbit when those fields are absent.

The fallback does not supply verified Go/hold status. Listed dates may be estimates even when a planned time field exists, so no precise countdown is manufactured. Annual totals remain the separately retrieved Launch Library 2 dataset; the two sources are never merged into country or company counts.

Mission names, types and descriptions come from the source. A mission’s associated agencies are not necessarily its payload owners. If a dedicated payload count or owner is not supplied, the field is marked accordingly rather than inferred from the rocket, country or mission name. A rideshare can contain many payloads.

The featured vehicle follows the earliest future Go or To Be Confirmed entry with day-or-better timing in this cached list; otherwise it uses the earliest listed record. It is not a probability forecast. The schematic is illustrative, not an engineering drawing.

The page requests a shared server cache, not the launch API directly. The last successful retrieval time is shown. Source checks are periodic and request-driven—not live telemetry or a guaranteed real-time feed.

Second- or minute-precision NETs can count down only when the source status is Go and the cached schedule is no more than 30 minutes old. Coarser dates, holds, uncertain statuses and stale data do not produce a precise countdown.