Cloudflare is down: what we know so far
This page is live and updates as StatusBird re-checks Cloudflare, every 2 minutes. First non-operational reading 07:45 UTC on November 11, 2026.
StatusBird recorded Cloudflare as non-operational from 07:45 UTC on 11 November 2026. The worst state observed was major. We check every 2 minutes and logged 30 non-operational readings in a row, covering 1 hour. Cloudflare posted an incident at the same time, titled SSL Certificate Provisioning Issue. The problem had not cleared when this was written.
Incident at a glance
| Service | Cloudflare |
|---|---|
| Date | November 11, 2026 |
| StatusBird first saw it | 07:45 UTC |
| Vendor posted an incident | 07:45 UTC |
| Recovery observed | Not yet |
| Duration | 38 hours 58 minutes and counting |
| Worst status observed | major |
| Non-operational readings | 1169 |
All times UTC. StatusBird polls Cloudflare every 2 minutes from its own infrastructure, so the true start and end sit within 2 minutes of the times above.
Was Cloudflare down on November 11, 2026?
Yes. StatusBird recorded Cloudflare as major from 07:45 UTC, and it was still non-operational 38 hours 58 minutes later at the most recent reading. 1169 consecutive checks came back non-operational.
Infrastructure issues may affect site availability.
What caused the Cloudflare outage?
The cause is not known. Cloudflare has published no root cause statement that StatusBird can read. The only description from the vendor is the incident title, SSL Certificate Provisioning Issue, posted at 07:45 UTC. StatusBird will not guess at what sat behind that title. If Cloudflare publishes an explanation later, that will be the place to look.
Cloudflare published an incident titled "SSL Certificate Provisioning Issue" at 07:45 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How long was Cloudflare down?
38 hours 58 minutes so far, measured from the first non-operational reading at 07:45 UTC to the most recent reading, which was still non-operational. StatusBird counts a service down from the first reading it fails, not from the moment the vendor admits it, which is why this number can be larger than the one on the vendor's own incident report.
Timeline, in UTC
| Time (UTC) | Event |
|---|---|
| 07:45 UTC | The vendor posts an incident on its own status page |
| 07:45 UTC | StatusBird records its first non-operational reading |
| 07:48 UTC | A second consecutive non-operational reading confirms the outage, alerts go out and this page is published |
| 22:44 UTC | Still non-operational at the last reading |
Who and what was affected
This affects any store that sits behind Cloudflare for its domain, its certificates or its traffic routing. When infrastructure of this kind degrades, shoppers may fail to load your storefront, product pages or checkout, so orders in progress can be lost and paid traffic can land on a page that does not open. StatusBird cannot say from its readings which of your specific pages failed, only that Cloudflare was measured as non-operational for the period above.
How StatusBird detected it
StatusBird recorded its first non-operational reading for Cloudflare at 07:45 UTC, and Cloudflare's own status page confirms the incident, posted at 07:45 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Method: StatusBird reads Cloudflare's published status endpoint every 2 minutes and records every reading. Availability figures count major and critical only. The full method is at statusbird.io/methodology.
Lessons for merchants
- Record which parts of your store depend on Cloudflare, including domain, certificates and routing, so you know what is at risk next time.
- Set up a status page or holding message you can publish from somewhere that does not sit behind the same provider.
- Keep a way to reach customers who were mid-checkout, such as abandoned basket email, and plan how you will follow up after an outage.
- Check vendor status pages against your own monitoring, since a vendor may post an incident title long before it posts a cause.
The longer version, with the checks specific to this service, is in the Cloudflare outage playbook.
Frequently asked questions
Was Cloudflare down on November 11, 2026?
Yes. StatusBird recorded Cloudflare as major from 07:45 UTC on November 11, 2026. The incident was still running 38 hours 58 minutes later when this page last updated.
How long was Cloudflare down?
38 hours 58 minutes, measured from the first non-operational reading at 07:45 UTC to the most recent reading, which was still non-operational. Readings are taken every 2 minutes, so the true start and end sit within 2 minutes of those times.
What caused the Cloudflare outage?
Cloudflare published an incident titled "SSL Certificate Provisioning Issue" at 07:45 UTC. A root cause has not yet been published by the vendor, so nothing on this page attributes one.
How was this Cloudflare outage detected?
StatusBird recorded its first non-operational reading for Cloudflare at 07:45 UTC, and Cloudflare's own status page confirms the incident, posted at 07:45 UTC. StatusBird polls every 2 minutes from its own infrastructure, so these are two independent records of the same window.
Was my store affected?
If your store calls Cloudflare during checkout or fulfillment, the requests to check are the ones made between 07:45 UTC and now on November 11, 2026. Infrastructure issues may affect site availability.
Monitor Cloudflare with StatusBird
This page exists because StatusBird was already watching. It checks Cloudflare and the rest of the stack an online store runs on every 2 minutes and sends an SMS, email, Slack, Teams or Discord alert the moment a reading goes non-operational, which on this incident was 07:45 UTC.
Start monitoring free Live Cloudflare status All Cloudflare outages