Live / Cloudflare / Incident
Cloudflare: SSL Certificate Provisioning Issue
Cloudflare · cloudflare.comMinor incidentResolved2026-11-11 10:07 UTC
Public — what happened
Summary
Cloudflare said that starting at 07:45 UTC on 2026-11-11 it was looking into a problem with putting some Custom SSL certificates into service, and it asked customers to hold off on redeploying certificates in the meantime. The company stated that certificates already in use were not affected and kept working normally. Cloudflare said it found the problem at 08:17 UTC, put a fix in place by 09:01 UTC, and then watched the results. It marked the incident resolved at 10:07 UTC.
Affected
SSL Certificate Provisioning
Timeline
- Started — 2026-11-11 07:45 UTC
- Investigating — 2026-11-11 07:45 UTC
- Identified — 2026-11-11 08:17 UTC
- Monitoring — 2026-11-11 09:01 UTC
- Resolved — 2026-11-11 10:07 UTC · 2h 22m after it started
What SquidGrid measured
SquidGrid measured 220 internet paths into Cloudflare’s network during this incident. None of them ran meaningfully slower than the same paths the day before.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Cloudflare against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Cloudflare: paths off baseline right now, where on the route conditions change, and its full incident track record.
Included with any paid plan.
Open the Cloudflare report →
More from Cloudflare
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.