Platform-specific

    Cloudflare Error 522 on WordPress

    Why it happens on WordPress

    Shared WordPress hosts throttle or firewall Cloudflare's IP ranges after a traffic spike, so the TCP handshake to the origin never completes and the edge gives up.

    The fix on WordPress

    Ask the host to allowlist Cloudflare's published IP ranges, then raise PHP workers or enable a page cache so the origin answers within the 15-second edge timeout.

    Is Cloudflare Error 522 happening on your domain?

    Probing the origin address directly shows whether it is reachable from outside Cloudflare, which immediately tells you whether the fault is the firewall or the host.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    If that didn't fix it

    WordPress has its own failure mode, but Cloudflare Error 522 has a wider set of causes that apply everywhere. The most common one overall is: the origin firewall silently drops cloudflare's ip ranges.

    All causes and fixes for Cloudflare Error 522

    Cloudflare Error 522 on other platforms and devices

    Monitor this continuously with LemWatch

    A one-off cloudflare error 522 monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.