Cloudflare Outage Map

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:

• 
  Dragos Dunica (@dragos_dydy) reported 8 seconds ago

  @divinprnc why not cloudflare also for sending/receiving? i think they support that too.

• 
  IdeaPlan.io (@ideaplanio) reported 3 minutes ago

  Cloudflare says most web requests are now automated, not human. Your analytics can't tell the difference. Your activation rate, bounce rate, and last A/B test winner all include traffic that was never going to convert. Segment agent from human before you trust the number.

• 
  ୧ ‧₊˚ abigail ⋅ᰔᩚ (@SQNG) reported 3 minutes ago

  this lasted for exactly 60 minutes. i love large ISPs being able to overwrite DNS for domains they do not control. thanks cloudflare. **** you.

• 
  Dmonty (@Dmonty28516998) reported 3 minutes ago

  @jeffdafo @AdamRackis You know who CAN imagine that curve in traffic? Cloudflare. Akamai. Fastly. AWS. GCP. And very ironically, Azure. We have an entire industry built around turning explosive growth in traffic, storage and compute into a capacity-planning problem. They all seem to be doing just fine. Software infrastructure is, famously, somewhat easier to parallelize than pregnancy.

• 
  Chong-U (@chongdashu) reported 8 minutes ago

  Hey @Cloudflare I’ve had an open ticket for domains purchased on Cloudflare that never went through ( i had to get them on an alternate provider) But it’s been a month with no reply and i got invoiced for the domains via Cloudflare . Some help please?

• 
  neghi (@realneghi) reported 10 minutes ago

  The cost of early complexity in software is something we tend to not consider when building. I’ve been an engineer for about 5 years now and in that time, I’ve been encouraged to learn technology and systems that do not fit my needs because it was trending at the moment. One of such is Kubernetes. Popularly known as K8s. It is an orchestration technology developed by Google. While it is exceptional at what it is designed for, your software might not need it. Docker or Podman is much more sufficient for most use cases. Another is GRPC and GRAPHQL, I’m not saying these are bad but your software might also not need it. You’re not processing data at the scale of Shopify or Facebook to justify the complexity of setting up a graphql server or are you having cross service communication that you need the smallest amount of latency to justify setting up and managing a grpc server. Another one that irks me is using a cloud provider like AWS, GCP or AZURE. Brother, you do not need a cloud provider, your mostly Nigerian users would not benefit from your app having high availability across 10 regions and your user base is too small to justify that auto scaling group you just added. Keep it simple, a shared VPS and cloudflare is more than enough to serve your application to thousands of users. These are my opinions and not facts. Code smart, not hard.

• 
  mert (@ux_self) reported 12 minutes ago

  The most cost-effective $5 purchase I've made for Cloudflare Workers, and I’ve never regretted it.

• 
  DEG Mods (@DEGMods) reported 17 minutes ago

  @QuackDocTech LiveKit is an option out of two, as you've seen, where you can use Cloudflare and their free 10 GB bandwidth option, however, if we discover more options out in the wild and makes sense to have it, we'll add support for it as another option. Regarding what it's using, it's av8 at the moment. av1 might prove to be not as simple of a task to migrate to, among other considerations, however, we are looking into moving to av9 which seems to be a compromise between the two while not having that big of a migration complication.

• 
  Corey J. Gallon (@CoreyGallon) reported 18 minutes ago

  Personal apps break the cloud architecture we've spent 25 years building. That's the single point @KentonVarda makes in "Gadgets: Personal app vibe coding that is actually safe," on @aiDotEngineer's YouTube. Kenton is a Principal Engineer at Cloudflare and started the Workers project in 2017. The talk walks through a working platform he built to test the idea, and it's specific about the sandboxing that makes user-modified code safe to run. - The plugin-system death spiral. A developer drowning in one-off feature requests decides to rewrite around plugins, the rewrite never ships, and neither do the features. - The alternative is users editing their own copy. The developer ships a clean core app, and anyone who needs a feature asks an agent to add it, just for them. - Server-per-user is the blocker. One blessed version of an app running on your server is convenient for developers and makes customization impossible, which is exactly what today's vibe coding platforms are built on top of. - Gadgets work like documents, not deployments. Think Google Docs: hundreds of gadgets, each one an app with its own code, each one shareable. - Sharing lives in the platform, not the app. Because a gadget is a single shareable thing, access control is implemented underneath it, so the app can't get it wrong. - Blueprints are code without data. Export a gadget you like as a blueprint, and other people instantiate their own gadget from it. - The agent modifies the app, not just the content. Asked to build a slide deck, Claude added strikethrough, text centering, and an SVG paste box to the Slides app itself when the features it needed weren't there. - Security by containment, not by correct code. The client runs in a null-origin iframe sandbox under CSP that can only postMessage to the parent; the server runs in a dynamic worker sandbox. Neither can reach the outside world, so an XSS bug leaks nothing. - Cap'n Web RPC connects the two halves. The postMessage channel carries an RPC session through to the gadget's server code, written as a durable object. - No containers, no database. The whole thing runs on dynamic workers and durable objects, and the entire demo ran locally on his laptop on workerd, the open source Workers runtime. He also explains why the code isn't on GitHub yet, which he'd promised in the abstract. I'm working through the published talks from AI Engineer World's Fair sharing summaries and takeaways. Follow for more!

• 
  Pika (@__pika25) reported 18 minutes ago

  every website you open you have to wait 5 seconds for **** you cloudflare. it's a humiliation ritual. the internet is dead.

• 
  Cyris (@sudo_overflow) reported 18 minutes ago

  @tadejk @Cloudflare That’s the plan, I want to really work on the monitoring side to identify spikes, problems etc

• 
  Manas Tripathi (@tripathigrows) reported 21 minutes ago

  Cloudflare replaced NGINX over its process model, not its code. Per worker pools fragment at scale, so origins eat endless handshakes. Pingora shares one pool and pushed a customer from 87.1 to 99.92 percent reuse. Rewrite when the architecture is the ceiling.

• 
  Brown Geeky kid (@shigma_male) reported 21 minutes ago

  YouTube isn’t going down every week because AI video slop is increasing. Cloudflare isn’t collapsing every week because bot traffic is rising. I used to give GitHub the benefit of the doubt because AI workloads created a massive traffic spike. But it has been long enough now.

• 
  Kyle Serrecchia (@kserrec) reported 23 minutes ago

  AWS/Vercel/Cloudflare being down is the snowday. GitHub being down is like the bathrooms at school not working. Claude/Codex being down is like the teachers striking.

• 
  SYL Vexora- Jaron K Bragg (@JaronBragg) reported 25 minutes ago

  Credit matters here because this was not one AI doing everything. Me → goal, dedicated AI computer, domain, testing, coordination, and continuously raising the bar when something worked. ChatGPT → architecture, Cloudflare guidance, tool-surface design, authentication troubleshooting, and adversarial proof design. Codex → wrote and deployed the actual machine-control MCP server, added the authentication layer, configured persistence on Windows, and tested the remote connection. Grok on my iPhone → became the model operating through the finished connector and performed the live computer work. Different AIs solved different problems. That combination is the point. I don’t care which model logo “wins.” Use whatever solves the next problem.