A Cloudflare error page does not establish a Cloudflare-wide outage. Check current Cloudflare status and compare any official notice with the affected product, location and time. Keep the failing request as the starting point for your investigation.
Preserve one useful example
Record the timestamp and timezone, hostname, response code and any Ray ID displayed. Capture the error page, then compare a known working route with the failing route. Do not repeatedly submit a purchase, payment or deployment to test recovery: a failed response does not prove the underlying operation never completed.
If you are a visitor, send the example to the site's operator. You do not need to change your DNS settings or disclose account credentials to report an error.
Investigate the origin as well as Cloudflare
Cloudflare documents both origin-side and Cloudflare-side causes of 502/504 responses. Its 502 and 504 troubleshooting guide recommends checking origin load, crashes, connectivity and application timeouts. Error-page appearance can provide context, but collect logs before assigning responsibility.
| Observation | Useful next evidence |
|---|---|
| One application route fails | Application and upstream logs for that route |
| Errors begin after a deployment | Change time and the first failing requests |
| Several unrelated routes fail | Origin health and shared dependencies |
| Only some locations report failures | Request times and available location evidence |
| A matching provider incident is active | Its stated scope and latest update |
For a site you operate, correlate a failing request with the origin's access and error logs. A timeout in an application upstream and a request that never reaches the origin point to different places to investigate. A missing log entry alone is inconclusive if logging is sampled or disabled.
If you use Cloudflare Tunnel
A tunnel connection and its application are separate parts of the request path. Cloudflare's Tunnel troubleshooting documentation explains that a 502 can occur when cloudflared cannot reach the origin service configured for it. Check the configured service address, protocol and port from the connector's environment, together with the connector logs.
Keep diagnostic checks within systems you administer. Avoid making the origin publicly reachable or removing TLS verification as a general troubleshooting shortcut. If a configuration correction is needed, change one understood setting and record the result.
Confirm recovery at the affected function
A homepage loading again does not establish that login, checkout or an API request has recovered. Recheck the failing read-only function and review error rates over an appropriate observation period. For state-changing operations, inspect the existing transaction's outcome before trying again.
When escalating, share the request example and relevant logs through the operator's or provider's private support channel. Remove tokens, cookies and personal data from anything posted publicly. Describe what failed and what you checked; leave the root cause open until evidence supports it.
Follow Cloudflare provider alerts or inspect Cloudflare incident history. An operational provider indicator does not verify your origin server or every Cloudflare feature.