no_running_instances

{
  "meta": {
    "requestId": "req_3k2j1h0g9f8e7d6c"
  },
  "error": {
    "code": "err:frontline:capacity:no_running_instances",
    "message": "No running instances are available to handle this request."
  }
}

​

If you’re calling an API hosted on Unkey

​

If you own this API

• The deployment is still starting and has no ready instances yet.
• Every instance failed, usually because the process exits at startup or never passes its health check.
• The environment has no current deployment, or its regions and replica counts aren’t what you expect.

​

How to fix

1. Open the deployment in the dashboard. During a rollout, wait for instances to become ready.
2. If instances are failed, read the runtime logs for a crash at startup or a failing health check.
3. Check that the environment has a current deployment, and that its regions and replica counts are set as you expect.

​

Related errors

• err:frontline:capacity:deployment_offline: the deployment was stopped intentionally.
• err:frontline:upstream:service_unavailable: an instance existed but refused the connection.
• err:frontline:capacity:spend_limit_reached: compute is paused by a spend budget.