config_load_failed

err:frontline:platform:config_load_failed

The gateway failed on our side while loading what it needs to route the request. It isn’t caused by the request or by the owner’s configuration. You get 500 Internal Server Error, usually with Failed to load route configuration or Failed to load instance configuration.

Example response

{
  "meta": {
    "requestId": "req_3k2j1h0g9f8e7d6c"
  },
  "error": {
    "code": "err:frontline:platform:config_load_failed",
    "message": "Failed to load route configuration"
  }
}

Browsers get the same error as an HTML page.

If you’re calling an API hosted on Unkey

Retry with backoff. It’s usually brief. If it keeps failing, contact the API owner or Unkey support with the request ID.

If you own this API

Nothing in your deployment causes this. A hostname with no route returns config_not_found instead.

How to fix

There’s nothing to change on your side. If it lasts more than a few minutes, check the Unkey status page and contact support with the request ID and the hostname.

err:frontline:routing:config_not_found: the hostname has no route.
err:frontline:config:invalid_configuration: the configuration loaded but couldn’t be parsed.
err:frontline:platform:internal_server_error: other failures inside the gateway.

Last modified on October 6, 2026

⌘I

Get started

Workspace

Audit logs

Billing

Root keys

API

CLI

AI coding

Security

Errors

If you’re calling an API hosted on Unkey

If you own this API

How to fix

​If you’re calling an API hosted on Unkey

​If you own this API

​How to fix

​Related errors

If you’re calling an API hosted on Unkey

If you own this API

How to fix

Related errors