Skip to main content
Cloudflare

ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers

Partial outage Lasted 2h 44m · started · Cloudflare's page

Level
confirmed
Worst impact
Partial outage
Down Index
30of 100

What to do

  • Check whether your product depends on Cloudflare. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 2h 44m it lasted.

    Anything that failed between 2026-10-27 12:28 UTC and 2026-10-27 15:12 UTC may need a replay.
  • Subscribe to Cloudflare's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=cloudflare works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We're investigating to confirm the root cause and possible fixes.
Read the postmortem

Updates from Cloudflare 5

  1. identified

    Cloudflare has identified an issue affecting customers whose traffic passes through an external vendor firewall. Customers may observe: ERR_TIMED_OUT on standard HTTPS websites ERR_EMPTY_RESPONSE on non-standard HTTPS ports (e.g., 8443) We're investigating to confirm the root cause and possible fixes.

    provider

  2. identified

    Cloudflare has identified an issue affecting customers whose traffic passes through an external vendor firewall. Customers may observe: ERR_TIMED_OUT on standard HTTPS websites ERR_EMPTY_RESPONSE on non-standard HTTPS ports (e.g., 8443) We're investigating to confirm the root cause and possible fixes.

    provider

  3. identified

    Cloudflare has identified an issue affecting customers whose traffic passes through an external vendor firewall. Customers may observe: ERR_TIMED_OUT on standard HTTPS websites ERR_EMPTY_RESPONSE on non-standard HTTPS ports (e.g., 8443) We're investigating to confirm the root cause and possible fixes.

    provider

  4. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  5. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-24aa2e330c

Is Cloudflare still down?

No, this incident was resolved 2026-10-27 15:12 UTC. For Cloudflare's live state, see https://down.guide/cloudflare.

How long did it last?

2h 44m, from 2026-10-27 12:28 UTC to 2026-10-27 15:12 UTC, by the times Cloudflare posted.

What caused it?

Cloudflare wrote: "We're investigating to confirm the root cause and possible fixes." The postmortem: https://www.cloudflarestatus.com/incidents/dk2obcyw2aew

Where does this come from?

Cloudflare's official status page, https://www.cloudflarestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.