Cloudflare Outage Map
The map below depicts the most recent cities worldwide where Cloudflare users have reported problems and outages. If you are having an issue with Cloudflare, make sure to submit a report below
The heatmap above shows where the most recent user-submitted and social media reports are geographically clustered. The density of these reports is depicted by the color scale as shown below.
Cloudflare users affected:
Check Current Status
E-mail
Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.
Check Current Status
Most Affected Locations
Outage reports and issues in the past 15 days originated from:
| Location | Reports |
|---|---|
| London, England | 16 |
| Madrid, Comunidad de Madrid | 14 |
| Melbourne, VIC | 13 |
| Berlin, Land Berlin | 12 |
| Paris, Île-de-France | 12 |
| Vienna, Wien | 10 |
| Frankfurt am Main, Hessen | 9 |
| Sydney, NSW | 9 |
| Hamburg, HH | 9 |
| Dresden, Saxony | 6 |
| Zürich, ZH | 6 |
| Munich, Bavaria | 5 |
| Lyon, Auvergne-Rhône-Alpes | 5 |
| Barcelona, Catalunya | 4 |
| Manchester, England | 4 |
| Marseille, Provence-Alpes-Côte d'Azur | 4 |
| Seattle, WA | 4 |
| Warsaw, Województwo Mazowieckie | 3 |
| Toronto, ON | 3 |
| Adelaide, SA | 3 |
| Bristol, England | 3 |
| Cardiff, Wales | 3 |
| Newham, England | 3 |
| Taipei, Taiwan | 3 |
| Kingston upon Hull, England | 3 |
| Hackney, England | 3 |
| City of London, England | 3 |
| Hyderabad, TG | 3 |
| Düsseldorf, NRW | 3 |
| Milton Keynes, England | 3 |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Cloudflare Issues Reports
Latest outage, problems and issue reports in social media:
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
Aaron Boodman
(@aboodman) reported
@dnlhmnt @thdxr Sorry this was a little snarky. I agree that degraded not necessarily equal to corrupt. But the context was the discussion that has been happening around the recent cloudflare outage that was caused by a production assert. SWE have generally come out in favor of the production assert – SWE like these because they avoid corrupt/incorrect results. SRE have generally come out against the production assert – why would you want code in product whose entire purpose is to crash it. You should instead work toward graceful degragadition. To a SWE, "graceful degradation" is the same as or very close to "incorrect/corrupt result". Because every additional path is additional complexity/risk. This is just inherent in software: more code, more bugs. So SWE want to reduce code. Graceful degradation == more code. More code == more chance of incorrect result.
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
Aaron Boodman
(@aboodman) reported
@dnlhmnt @thdxr Sorry this was a little snarky. I agree that degraded not necessarily equal to corrupt. But the context was the discussion that has been happening around the recent cloudflare outage that was caused by a production assert. SWE have generally come out in favor of the production assert – SWE like these because they avoid corrupt/incorrect results. SRE have generally come out against the production assert – why would you want code in product whose entire purpose is to crash it. You should instead work toward graceful degragadition. To a SWE, "graceful degradation" is the same as or very close to "incorrect/corrupt result". Because every additional path is additional complexity/risk. This is just inherent in software: more code, more bugs. So SWE want to reduce code. Graceful degradation == more code. More code == more chance of incorrect result.
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
-
pittakionomaniac emeritus
(@kehlarn) reported
@Megalithik_ @tobi cloudflare has a habit of not vetting customers who seek their network protection products to thwart lawful intercept. because the true origins are somewhat hidden LI has to target cloudflare by default
Check Current Status