ERR_TIMED_OUT and ERR_EMPTY_RESPONSE being observed by Cloudflare Customers

Cloudflare

1. 27 Oct 15:12 UTCResolvedThis incident has been resolved.
2. 27 Oct 14:52 UTCMonitoringA fix has been implemented and we are monitoring the results.
3. 27 Oct 14:38 UTCIdentifiedCloudflare 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.
4. 27 Oct 14:38 UTCIdentifiedCloudflare 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) Cloudflare's network and edge are functioning normally. These failures occur at the firewall inspection layer. We're investigating to confirm the root cause and possible fixes.
5. 27 Oct 13:20 UTCIdentifiedCloudflare 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.
6. 27 Oct 13:20 UTCIdentifiedCloudflare 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) Cloudflare's network and edge are functioning normally. These failures occur at the firewall inspection layer. We're investigating to confirm the root cause and possible fixes.
7. 27 Oct 13:20 UTCIdentifiedCloudflare has identified a third-party issue affecting customers whose traffic passes through external vendor firewalls after recent firmware upgrades. Customers may observe: ERR_TIMED_OUT on standard HTTPS websites ERR_EMPTY_RESPONSE on non-standard HTTPS ports (e.g., 8443) Cloudflare's network and edge are functioning normally — these failures occur at the firewall inspection layer and can only be resolved with actions on the 3rd party software configuration.
8. 27 Oct 13:20 UTCIdentifiedWe are continuing to work on a fix for the issue.
9. 27 Oct 12:28 UTCIdentifiedCloudflare 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.
10. 27 Oct 12:28 UTCIdentifiedCloudflare 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) Cloudflare's network and edge are functioning normally. These failures occur at the firewall inspection layer. We're investigating to confirm the root cause and possible fixes.
11. 27 Oct 12:28 UTCIdentifiedCloudflare has identified a third-party issue affecting customers whose traffic passes through external vendor firewalls after recent firmware upgrades. Customers may observe: ERR_TIMED_OUT on standard HTTPS websites ERR_EMPTY_RESPONSE on non-standard HTTPS ports (e.g., 8443) Cloudflare's network and edge are functioning normally — these failures occur at the firewall inspection layer and can only be resolved with actions on the 3rd party software configuration.

• Service status now: every provider ChangeIntel reads, with ongoing incidents first.
• Status RSS feed: new and ended incidents as they happen.
• Everything about Cloudflare: its changes, known issues and incidents on one timeline.