Skip to main content

Status and support

Check status.constellation.space first: if a service is down, it says so there. For anything else, write to contact@constellation.space with the details below.

Check the status page​

status.constellation.space shows each service, such as the API, the MCP server and the Platform, with its status now, 90 days of uptime and the incidents that affected it. It runs apart from the Platform, so it stays up when the Platform does not.

To check the API from your own network, call /health, which needs no key. See Health.

Who to contact​

ForWrite to
Problems, questions and security reportscontact@constellation.space
Your Enterprise deploymentYour Constellation contact, or contact@constellation.space
Invoices and paid plansContact billing on Settings, Billing, which writes to sales@constellation.space

The Platform does not name your forward-deployed engineer yet. If you onboarded with one, write to them directly, or to contact@constellation.space. See Onboarding with your FDE.

What to include​

  • Where. The shared service, or your Enterprise site and its API host.
  • When. The time in UTC.
  • What you did. The endpoint and method, or the Platform page. Share, at the top of each tab, copies the view's link and its API call. See Share a view or its API call.
  • What came back. The status code and the whole error body: its error code, and the incident_id when there is one.
  • Which ids. The workflow and run_id, the ground_station_id, ground_antenna_id or satellite_id, or an uploaded file's key.
  • Which key. Its prefix as the key list shows it, such as cos_live_ab12. Never the whole key.
  • For the fleet agent. The output of status, verify and sudo constellation-agent logs 300. See Fleet agent troubleshooting.

Leave out API keys, passwords and telemetry you would not share.

Solve it yourself first​

  • Troubleshooting: connections and access, missing telemetry, empty forecasts and missing saved work.
  • FAQ: what teams ask most about setup, forecasts and calibration.
  • Errors and limits: every error code, rate limit and retry rule.