| Previous | Next |
| HTTP_E_STATUS_BAD_GATEWAY | HTTP_E_STATUS_GATEWAY_TIMEOUT |
HTTP_E_STATUS_SERVICE_UNAVAIL
HTTP_E_STATUS_SERVICE_UNAVAIL maps to HTTP 503 Service Unavailable. The server is currently unable to handle the request because of temporary overload or scheduled maintenance.
What to check for HTTP_E_STATUS_SERVICE_UNAVAIL
- Honor the
Retry-Afterheader when present. - Use capped backoff with jitter for safe retries so clients do not amplify overload.
- Check health checks, capacity, deployment events, and upstream dependencies; a gateway may emit 503 even when the origin process is running.
RFC 9110: 503 Service Unavailable
Diagnostic interpretation
This result has the HRESULT value 0x801901F7. AllStat records the condition as “Service unavailable (503).”.
Evidence to capture
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions this result or the service / unavail operation.
- Preserve the first failure in the call chain; a later HRESULT can describe cleanup rather than the original service / unavail condition.
Retry and recovery
” has changed.
Looking for a different code? Search another status or error code.
