Elevated Errors for Compute
Elevated Errors for Compute
07 September 2026, 18:50 UTC
07 September 2026, 18:50 UTC
We are investigating an issue causing elevated 431 errors on requests for our customers.
We will provide another update as more information becomes available or within the next hour.
11 September 2026, 15:34 UTC
11 September 2026, 15:34 UTC
Our engineers have identified the contributing factor causing the issue impacting our CDN service.
Our engineers are now deploying a fix, and we will post a new update once it has been fully implemented and we see signs of recovery.
All other products and services remain unaffected by this incident.
11 September 2026, 15:35 UTC
11 September 2026, 15:35 UTC
A fix is being deployed for the issue impacting our CDN service.
We are observing a gradual restoration of services, though some customers may continue to experience intermittent issues as the system stabilizes.
Our team is actively monitoring the recovery and will post another update once services are fully restored.
11 September 2026, 16:19 UTC
11 September 2026, 16:19 UTC
A fix has been deployed for the issue impacting our Next-Gen WAF services running on Compute.
We are observing a gradual restoration of services, though some customers may continue to experience intermittent issues as the system stabilizes.
To clarify an earlier update: this issue affected Next-Gen WAF on Compute, not our CDN service, which was not impacted.
Our team is actively monitoring the recovery and will post another update once services are fully restored.
11 September 2026, 22:06 UTC
11 September 2026, 22:06 UTC
Engineering has confirmed that our Compute services and NGWAF services that run on Compute have been fully restored. Customers may have experienced elevated 431 errors from September 7, at 18:50 UTC to September 11, at 20:00 UTC.
This incident is resolved.
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.