Skip to main content
err:frontline:capacity:deployment_offline
The hostname points at a Compute deployment that was stopped, or whose was canceled. It stays offline until someone starts it. You get 503 Service Unavailable.
Example response
Browsers get the same error as an HTML page.

If you’re calling an API hosted on Unkey

Retrying won’t help. The owner has taken this deployment offline. If you expected it to be up, contact the API owner with the hostname and the request ID.

If you own this API

A hostname still points at a deployment that isn’t running. It starts the moment you stop the deployment, even while instances are still shutting down. Common causes:
  • You stopped the deployment.
  • The project was canceled.

How to fix

  1. Start the deployment from the dashboard or with deployments.startDeployment.
  2. Or promote a different deployment so the hostname points at one that’s running.
You can’t start a deployment while the workspace is paused at its Compute spend limit. If callers also see spend_limit_reached, fix that first.
Last modified on October 22, 2026