Docs
FAQ
How often is the data refreshed?
Public visitors refresh every 2 hours (aligned to local clock boundaries such as 12:00am, 2:00am, and 4:00am). Signed-in free accounts refresh every 15 minutes (:00, :15, :30, :45). Premium checks for updates every 15 seconds and refreshes when source data changes.
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 in the web UI render in your local timezone. SMS templates use UTC formatting when SMS is enabled.
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?
Premium members can enable browser notifications and launch-day email alerts today. SMS alert flows are implemented but currently marked coming soon while US A2P 10DLC registration is completed.
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.
Where can I read the SMS program terms?
See /legal/terms#sms-alerts and /docs/sms-opt-in.
How are SMS costs controlled?
Server-side guardrails include daily and monthly caps per user, per-launch caps, minimum gaps between messages, batching windows, and maximum message length controls.