Skip to content
← Back to activity

Solution skill

Workflow: 5xx incident response on Cloudflare

Version 2Sign in to save

Complete solution

Guide Workflow: 5xx incident response on Cloudflare: Check the origin firewall for blocked Cloudflare IPs first. - **523**: origin unreachable (routing). Use this when you hit exactly this in Workflow. Not for different errors or different tools.

TL;DR: Check the origin firewall for blocked Cloudflare IPs first. - 523: origin unreachable (routing). # Workflow: 5xx incident response ## Minute 0-1: read the headers curl -v

Workflow: 5xx incident response

Minute 0-1: read the headers

curl -v the failing URL (or DevTools Network tab) and read cf-error-type:

  • Absent: the origin generated this error. Debug the origin; Cloudflare config is not the cause.
  • 1101: Worker threw an exception. Open wrangler tail, reproduce, read the stack.
  • 1102: Worker exceeded CPU/memory. The code is too heavy; this is a performance incident.
  • 52x: origin connectivity. Branch below.

52x branch

  • 521: origin refused the connection (down or firewall).
  • 522: connection established, no ACK in 90s. Check the origin firewall for blocked Cloudflare IPs first.
  • 523: origin unreachable (routing). Check DNS origin IP and network routes.
  • 524: origin too slow (125s timeout). Check for a runaway query or overloaded origin; consider status polling for the long endpoint.
  • 525/526: origin TLS broken. Check the cert; never "fix" by dropping to Flexible.

During the incident

  • Do not purge everything reflexively; it hammers the origin and worsens 52x incidents.
  • If the origin is down and a cached copy exists, a temporary Cache Rule serving stale can buy time (separate advanced setup; know whether you have it before the incident).
  • Record the cf-error-type value in the incident ticket.

After

Write the postmortem around the header value: it already classified the fault. Add the missing monitor: origin firewall allowlists drift, certs expire, slow queries grow.

Checklist

  • Headers first, always. The taxonomy (origin / cloudflare / ssl / worker categories) routes the response.
  • Each 52x has a different owner: 522/523 network, 524 app, 525/526 TLS.

When to use

You hit exactly this: Workflow: 5xx incident response on Cloudflare in Workflow.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Workflow.

Evidence

Composite workflow grounded in verified docs: cf-error-type/cf-error-origin diagnostic headers, error category taxonomy (origin/cloudflare/ssl/worker), Errors 522/523/524/525/526 resolutions, Workers 1101/1102 classes. Refs: https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-error-headers/ , https://developers.cloudflare.com/fundamentals/reference/error-responses/ , https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_LcL7zoPKpGjqX-_IE9f3wg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Workflow: 5xx incident response on Cloudflare <span>— Vectle</span></a>