Status: Resolved
Our services are now operating normally.
Between 11:20 and 17:06 UTC on 18 November, some users experienced errors due to an issue with Cloudflare network. No data was lost, and we are continuing to monitor performance. Thank you for your patience.
What happened
At approximately 11:20 UTC on 18 November, a change in Cloudflare’s systems caused critical failures in parts of their network. Many sites using Cloudflare, including ours, began returning Cloudflare error pages and HTTP 500 internal server errors.
Root cause
Cloudflare has attributed the incident to a bug in how a Bot Management “feature file” was generated following a database permissions change. The file, which is distributed globally to help detect and manage bot traffic, became significantly larger than expected and caused the software handling core network traffic to crash in multiple locations. This led to elevated error rates for sites behind Cloudflare until they reverted to a stable configuration. Cloudflare has confirmed this was not the result of a cyberattack or data breach.
Timeline
11:20 UTC – First significant failures in Cloudflare’s network delivering core traffic.
14:30 UTC – Correct Bot Management configuration file deployed globally; most services operating normally again.
17:06 UTC – Cloudflare reported all systems functioning as normal and the incident as resolved.
Cloudflare is aware and investigating an issue that potentially impacts multiple customers ,and more information will be provided when it becomes available.
We’ll find your subscription and send you a link to login to manage your preferences.
We’ve found your existing subscription and have emailed you a secure link to manage your preferences.
We’ll use your email to save your preferences so you can update them later.
Subscribe to other services using the bell icon on the subscribe button on the status page.
You’ll no long receive any status updates from Stripe21, are you sure?
{{ error }}
We’ll no longer send you any status updates about Stripe21.