@@ -16,6 +16,7 @@ The header is set on every branded proxy-layer error response, including WebSock
 | `upstream_dns_failure` | The upstream proxy host could not be resolved. | Yes |
 | `origin_tls_timeout` | The proxy reached the destination, but the destination did not complete its TLS handshake in time. | Yes |
 | `restricted_route_unavailable` | The destination requires a specialized egress route and Kernel could not build one. Kernel will not fall back to a provider known to reject the destination. | Yes, except on `.gov` destinations. There, create a new residential proxy with no targeting, country-only targeting, or a U.S. state, confirm it with [`POST /proxies/{id}/check`](https://kernel.sh/docs/api-reference/proxies/check-proxy-health), then use it for the session. |
+| `destination_route_unavailable` | The destination matches a per-host proxy route, but that route's proxy is unavailable, for example because it was deleted. Kernel does not fall back to the session proxy or a direct connection. | No. Assign an available proxy to the route, or remove the route. |
 | `proxy_unavailable` | A failure inside Kernel's own proxy layer, not your automation or the destination. | Yes |
 | `origin_response_incomplete` | The destination closed the connection before sending a complete response. | Only if safe. The destination may have received the request, so retry only when repeating the action cannot cause duplicate changes. |
 | `provider_rejected` | The upstream proxy provider rejected the request before the destination connection was established. | No. Try a different proxy or proxy type, and check the credentials on a [custom proxy](/proxies/custom). |