API
The control plane behind the dashboard, CLI and integrations. This is what the live check calls.
Live check: yes
System status
This page calls the Deployxa API health endpoint from your browser and shows exactly what came back. Nothing on it is simulated.
01 / The check
One request to the public health endpoint of the API. A 200 response with status ok means the API HTTP process responded. It does not establish database, queue, worker or application health. The round trip is measured in your browser, so it includes your own connection.
curl -s https://api.deployxa.com/health
{"status":"ok"}02 / Components
Component-level status is not published on this page yet. Each part below shows where to look for the state of your own resources.
The control plane behind the dashboard, CLI and integrations. This is what the live check calls.
Live check: yes
The web console for projects, deployments, domains, team and billing.
Uses the API above
Webhook-triggered builds, health-checked rollouts and rollbacks.
Per-deploy logs in the dashboard
GitHub, GitLab and Bitbucket connections and push webhooks.
Delivery shown per project
Custom domains, DNS and automatic Let's Encrypt certificates.
Per-domain state in the dashboard
Provisioned databases attached to your projects.
Per-database state in the dashboard
03 / If something looks wrong
If the API responds, its HTTP process is reachable from where you are. Dependency and application health require separate checks.
Deploy logs, health checks and domain state show what happened to your app.
A previous release can be used for warm rollback during its configured standby window. Check the deployment state before starting recovery.
Send the project name, the time and what you saw to support@deployxa.com.
Ready when you are
Send the project name, the time and what you saw, and we will take it from there.