A timeout occurred 524
Reference guide
Does the request eventually succeed if you wait longer when hitting the origin directly, or does it never complete?
Eventually succeeds directly, just slow
Request path
- You (reached)
- DNS (reached)
- Cloudflare edge (reached)
- Origin (not reached)
times out
Your origin is responding, but too slowly — Cloudflare's connection timeout (100 seconds) is being exceeded before your origin finishes.
What to do
- Check. Measure how long the slow request actually takes when hitting the origin directly, and compare against Cloudflare's ~100 second timeout.
- Fix. Speed up the slow operation (add caching, optimize the slow query/process, or increase origin resources) so it consistently responds well under the timeout.
- Verify. Retry the request through Cloudflare and confirm it completes within the timeout.
Never completes, even directly
The request never completes even without Cloudflare in the path, which points at the origin application itself hanging or deadlocking rather than raw slowness.
What to do
- Check. Check your origin application's logs/process state for the hung request — look for a stuck thread, an external API call with no timeout, or a deadlock.
- Fix. Add a timeout to whatever external call or lock the application is waiting on, and restart the hung process.
- Verify. Retry the request directly first to confirm it now completes, then retry through Cloudflare.
Want to narrow it down interactively instead? Use the error lookup tool.