Cloudflare: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
Timeline of updates
- identifiedEdited
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.
- identifiedEdited
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.
- identifiedEdited
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.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Major incident: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
- Incident updated: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
- Incident silently edited: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
- Incident silently edited: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
- Incident updated: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
- Incident updated: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
- Incident updated: ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
0d843f08a9eb7356…Version 2 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
e595983135701d41…Version 3 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
a44276b29f09d63f…Version 4 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
29550001075d384c…Version 5 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
34f8d1a1f02fe14b…Version 6 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
3a82cfcae9458afd…Version 7 captured
In the 2026-10-27 checkpoint, timestamped by DigiCert and FreeTSA on . Record hash
5efc0944cc4f27bb…
Impact, status and times are the vendor’s own, as last archived. View on www.cloudflarestatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by Cloudflare, started 2026-10-27 12:28 UTC, resolved after 2.7 h, 5 update(s); edited after publishing.
- Title
- ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers
- Vendor
- Cloudflare
- Date
- URL
- https://rewindex.com/company/cloudflare/incidents/dk2obcyw2aew
Cloudflare profileRecent Cloudflare incidentsAll outages on October 27, 2026Cloudflare in October 2026MarkdownJSON