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

Cloudflare users affected:

Report a Problem

Check Current Status

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:

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:

• Rory Bernier (@RoryCrave) reported 17 seconds ago

  @Cloudflare Which signals first showed the problem, how quickly were automated alerts fired, and what blind spots existed?

• nitriques (@nitriques) reported 4 minutes ago

  @dok2001 @crptpw Yeah the state of the affair is bad. Been client since 2011, investor since the ipo. 2 times in 2 weeks is not acceptable. Cloudflare always was a spof for me, but I slept well knowing it is my strongest and most resiliant node. Feels like this is no longer the case.

• Chess.com Support (@chesscomsupport) reported 5 minutes ago

  @AllanToo_ @chesscom Hi! Cloudflare experienced some issues around the time of this post, which also caused problems on our site and many others. I apologize for the inconvenience. It has since been resolved!

• Benjamin De Kraker (@BenjaminDEKR) reported 7 minutes ago

  Cloudflare TLDR: The outage was caused by a configuration change they made while trying to protect customers from a newly disclosed React Server Components vulnerability. That change interacted badly with an internal "killswitch" they used to disable some test security rules. When this misconfiguration hit part of their older proxy software, many affected customers started getting generic 500 errors until Cloudflare rolled the change back. More technically: disabling an internal logging/test ruleset via the global configuration system applied a killswitch to a rule whose action was execute, which their FL1 proxy’s Lua code had never handled before. Because the execute action was skipped, the expected rule_result.execute structure was nil, and the code tried to index it anyway, throwing a Lua exception (attempt to index field 'execute' (a nil value)) that caused HTTP 500 responses across sites using the FL1 proxy plus the Managed Ruleset until the configuration was reverted.

• Oliver Karasin (@olikarasin) reported 8 minutes ago

  @NanouuSymeon Only when Cloudflare is down and I need to fix it

• T*xic Pyro (@ToxicPyroYT) reported 9 minutes ago

  If you think cloudflare going down is bad just wait until the sun explodes

• allavita.eth (@MrChronoice) reported 9 minutes ago

  Someone tell Cloudflare they forgot to fix and get the crypto market up and running

• Grok (@grok) reported 15 minutes ago

  @hagaonx @Pirat_Nation Cloudflare's outage today was caused by a configuration change to their Web Application Firewall, aimed at patching a vulnerability in React Server Components. It wasn't an attack and lasted about 25 minutes, impacting sites like Fortnite, LinkedIn, and Coinbase. They've implemented a fix and are monitoring.

• AshleyShades (@ShadesAshl83388) reported 16 minutes ago

  @PopBase so we’ve just accepted that when cloudflare is down, the internet is down?

• Grok (@grok) reported 17 minutes ago

  @guitaripod @Cloudflare TL;DR for software engineers: Cloudflare's 25-min outage (Dec 5, 2025, ~08:47 UTC) stemmed from a WAF config change (buffer from 128KB to 1MB for CVE mitigation) plus killswitch disabling a test tool, causing Lua nil error in FL1 proxy's rules module (missing 'execute' object). Impacted 28% HTTP traffic with 500 errors; no effect on China or non-Managed Ruleset users. Resolved by reverting config at 09:11 UTC. Lessons: Improve gradual rollouts, health checks, and fail-open logic to prevent such bugs.

• Rory Bernier (@RoryCrave) reported 18 minutes ago

  Will customers get better per‑tenant incident reports (POPs, rulesets, time windows) to support their own RCAs and SLAs? Which ones? @Cloudflare

• Chess.com Support (@chesscomsupport) reported 19 minutes ago

  @FaizHappens @chesscom Hi! Cloudflare experienced some issues around the time of this post, which also caused problems on our site and many others. I apologize for the inconvenience. It has since been resolved!

• Yaseen (@YaseenHQ) reported 20 minutes ago

  Cloudflare went down right as i was pushing a worker yesterday and for a split second i thought my account got banned or something. Alas

• Ughmahedhurtz (@Ughmahedhurtz) reported 20 minutes ago

  @brankopetric00 It also means when Cloudflare, AWS, Azure, etc. are down or when someone backhoes your fiber connection, almost everyone is completely unable to do work. If you had on-prem email/apps, you'd not be able to talk to the outside perhaps but you'd still be able to work offline.

• Annu (アンヌ)✨ (@Annu66126617) reported 23 minutes ago

  @akashsingh_24 lag to raha h ki vo chatgpt users ko le liye h vo baar baar down ho raha raha, isse acha khasa impact hoga, and People are likely to shift to a different platform instead of Cloudflare, as they have already lost their startup reputation in front of users because of this.

Check Current Status