Live data JPL Horizons

Distance from the Sun, speed, and one-way light time all come from NASA JPL's Horizons System — the same ephemeris service that powers most professional solar-system navigation software. No authentication required. Each probe needs two separate requests, since Horizons only accepts one observing center per call: Sun-centered for distance and speed, Earth-centered for distance and light time.

ssd.jpl.nasa.gov/api/horizons.api
Live data DSN Now

Signal/contact status comes from NASA's official Deep Space Network feed — the same XML data that drives the eyes.nasa.gov DSN visualization. A probe frequently shows "not in contact"; that's real dish-scheduling behavior, not an error state.

eyes.nasa.gov/dsn/data/dsn.xml
Periodically updated Instrument status

There's no public API that decodes actual Voyager telemetry to instrument-level status, so each probe's Instrument Health table is transcribed by hand from NASA's own status page rather than fetched live. Updated here whenever NASA's page changes.

science.nasa.gov — Where are Voyager 1 and 2 now?
Periodically updated Mission milestones

The Milestones timeline is hand-compiled, not fetched live. Launch dates, planetary flybys, and heliopause crossings are well-established public mission history; the more recent entries (2023 onward — comms anomalies, thruster events, and the power-conserving instrument shutdowns) are each verified against a specific NASA or JPL announcement:

Static asset About page background

The Voyager illustration behind the About page text is a NASA render, with its starfield background removed by hand — not fetched live.

science.nasa.gov — Voyager illustration
Static data

Launch date, heliopause crossing date, and constellation heading are real facts, but baked into the app rather than fetched live — they don't change often enough to need a live source.

Live figures are cached locally and refresh at most once every 15 minutes. If a refresh fails, the last known good values are shown rather than breaking the page.