Skip to main content
T-Minus ZeroComm Link

Docs

FAQ

How often is the data refreshed?

The schedule uses a shared adaptive refresh cadence across public and Premium schedule/detail surfaces. Refresh timing tightens automatically around active launch windows.

Where does the data come from?

Primary launch schedule and metadata come from Launch Library 2 (The Space Devs). News metadata comes from Spaceflight News API. Weather uses NWS (api.weather.gov) and, when available, 45th Weather Squadron forecasts. Feature-specific views may also use FAA, CelesTrak, NASA, NAVCEN, and SpaceX sources. See /legal/data for the full inventory.

Which locations are covered?

The default feed focuses on US pads. Signed-in users can switch region filters to include all locations when available. The homepage feed itself remains US-scoped by default.

What does NET mean and why is the time sometimes TBD?

NET means "No Earlier Than" and marks the earliest possible liftoff. If a provider publishes date-only or low-precision timing, the UI shows Time TBD and countdowns stay hidden until hour/minute precision is available.

What timezone are launch times shown in?

Launch times render in your local timezone when the app can confirm your location. On launch detail pages, if location access is unavailable, timing falls back to local pad time and the timing summary opens a reference popup that explains that state.

What happens when a launch slips, holds, or scrubs?

Timing and status changes appear after the next ingest/refresh cycle. Cards reflect HOLD and SCRUB states, and change events are tracked for alert workflows.

How do notifications work right now?

Anyone can turn on basic all-U.S. T-10 push alerts on supported browsers and current native mobile surfaces for that device. Account-level notification settings live in Account. Premium adds registered-device push alerts, quiet hours, reminder timing, launch-specific rules, and launch-day email.

Can I mute alerts during quiet hours?

Yes. Notification preferences support quiet hours with local start/end times. Dispatch pipelines honor those settings when scheduling sends.