---
title: "HTTP 5xx status codes on Cloud Platform"
date: "2024-02-14T06:18:38+00:00"
summary: "Troubleshoot HTTP 5xx errors on Cloud Platform. Learn causes, access logs, and resolve issues for improved site performance."
image:
type: "page"
url: "/acquia-cloud-platform/http-5xx-status-codes-cloud-platform"
id: "88f0e3eb-53c7-49ea-a0af-4efa8cb83741"
---

If your server experiences slow queries, use the provided documentation to identify and resolve these issues. Tools and guides are available to help parse slow query logs and understand how to improve query performance. To request help for severely-impacted production sites, [create a Support ticket](/service-offerings/support "Support") with critical urgency for immediate assistance or to terminate problematic queries on your behalf.

Cloud Platform replaces all HTTP 500, 501, 502, 503 and 504 status code responses served to visitors of your production environments with a generic `503 Service Unavailable` response. Displaying the following common response prevents the production environment from leaking error message information:

    Temporarily Unavailable
    
    The website that you're trying to reach is having technical difficulties
    and is currently unavailable. We are aware of the issue and are working
    hard to fix it. Thank you for your patience.

Important

Normally, you cannot change the preceding message. However, if you use a WAF, you can replace the message with other content. For more information, refer to the documentation for the specific WAF. For example, [Cloudflare Error Pages](https://developers.cloudflare.com/rules/custom-errors/ "https://developers.cloudflare.com/rules/custom-errors/").

To assist with troubleshooting during development, _non-production environments_ pass all HTTP 5xx status codes through the load balancers back to the requesting client without any replacement. You can review these error messages in your [log files](/acquia-cloud-platform/monitor-apps/logs), which you can access using the following methods:

*   [Downloading active log files](/acquia-cloud-platform/monitor-apps/logs#cloud-download-logs-ui)
*   [Downloading historical logs](/acquia-cloud-platform/monitor-apps/logs#cloud-download-logs-cli)
*   [Streaming log entries in real time](/acquia-cloud-platform/monitor-apps/logstream)
*   [Log forwarding in Cloud Platform](/acquia-cloud-platform/monitor-apps/logs/forwarding)

For production environments, use logs and [log streaming](/acquia-cloud-platform/streaming-log-entries-real-time "Streaming log entries in real time") to determine the root cause. Access logs display the real HTTP status code at the back end. To find corresponding logs from other sources, such as PHP errors and Drupal Watchdog, use the `X-Request-Id` value, which matches all logged items for the same request.

Common causes of Temporarily Unavailable pages on production environments include but are not limited to:

*   Transitory resource limits such as insufficient CPU or DB resources, which occur due to high traffic, application complexity, or both. This high traffic can be expected or caused by unusual robot crawls or DDoS attacks.
*   Code changes, data changes, or bugs that trigger PHP exceptions or errors.

To resolve this, do one or more of the following:

*   Roll back changes to a site by restoring older configuration, code, or a database backup.
*   Adjust PHP memory limits.
*   Block traffic through a Web Application Firewall (WAF) with [Acquia Edge](/acquia-cloud-platform/add-ons/edge/overview "Overview") or other methods.

To learn more about how your infrastructure allocates resources, visit [Tuning your infrastructure configuration](/acquia-cloud-platform/manage-apps/infrastructure/tuning).