An HTTP 503 response indicates that the server is temporarily unable to handle the request, commonly because of temporary overload or maintenance. A 503 does not by itself prove that the entire server is down.
- Check whether the error affects every request or only an application endpoint.
- Review account resource statistics and faults when CloudLinux Resource Usage is available.
- Review application and web error logs for processes that are repeatedly failing or exhausting limits.
- Check for maintenance-mode features, long-running imports, backup operations, or jobs that began immediately before the error.
- Retry after the underlying workload has ended instead of rapidly refreshing the page.
If the response includes a Retry-After header, it can indicate when the server suggests retrying the request.
