Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Domains (41%)
• Cloud Services (35%)
• Hosting (18%)
• Web Tools (4%)
• E-mail (2%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Montataire	Cloud Services	3 days ago
Greater Noida	Cloud Services	5 days ago
Colima	Hosting	7 days ago
Leuven	Domains	7 days ago
New Delhi	Cloud Services	8 days ago
Mâcon	Cloud Services	13 days ago

Full 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:

• 
  Alexander Zuev (@zlxndr) reported 2 minutes ago

  It’s really hard to grasp what Cloudflare unleashed to the world with Agents SDK, Workflows, codemode Thinking how to architect a self-healing agent users can install into their projects - this means I can not define data access logic upfront and need to: - allow the agent to write its own per-user tools during onboarding - then use them during runtime - then if it fails - allow the workflow to wait for “access_repaired” and try again - all while in the meantime if a tool call fails the agent tries to fix the issue and save a new tool definition Then a workflow (sending dispute evidence) itself is deterministic with clear start and end points: - stripe webhook received (start) - evidence sent via stripe api (success) - or failed (failure) - or user input required (human in the loop) So the question is: - should the agent start the workflow or - the workflow call the agent as its own step? Finally some workflow steps should not use llms at all - I want them to be deterministic: - building pdf according to a template But for other actions (I think) I only want to define WHAT the agent should get to build a case but the agent will define HOW during onboarding: - user activity log (db) - stripe subscription data (stripe) - potentially server logs (???) So here the agent would write a json defining the tool config called at runtime instead of defining it during runtime Finally the whole flow is something like: - step (“initial triage”) > categorize and decide what to do, call hooman if blocked - step (“gather evidence”) which is: - agent get_user_activity - agent get_user_subscription - agent generate_report - step (“send”) And of course if agent calls multiple tools at once would it be better to use codemode to save on tokens here? Finally the economics of this break, if llm costs per case are more than $1-3 - I’ll see if something like gemma-4 can be used here: - cheap - reasonably smart

• 
  quickbrownfox (@dero_bro) reported 4 minutes ago

  😯 The editor. The renderer. The animation engine. The WASM runtime. All on-chain. All assembled on demand. All running locally. No accounts. No AWS. No Cloudflare. No terms of service. No external connections. This is what digital sovereignty looks like. $dero

• 
  DeathByClawd (@DeathByClawd) reported 9 minutes ago

  deathbyclawd is mostly one page telling on itself. 2,945 of the last 24h scans hit the homepage. next closest URLs: cloudflare 26 drudgereport 15 lrn 11 same site, same pain, over and over. one URL that shows how broken a site feels.

• 
  impulsive (@weezerOSINT) reported 10 minutes ago

  @Alex_m @VECERTRadar @Cloudflare I'm gonna have to assume its just not possible due to performance issues, this isnt something they can do overnight.

• 
  Trevor I. Lasn (@trevorlasn) reported 10 minutes ago

  @cathrynlavery @Cloudflare api key screens are where devtools reveal whether they trust users. permissions should read like intent, not internal service names leaking through the UI

• 
  czverse (@czverse) reported 14 minutes ago

  The number of qubits needed to break Bitcoin just dropped from 20 million to under 100,000. In 7 years. Cloudflare moved their post-quantum deadline up to 2029. Bas Westerbaan called it "a real shock." Most crypto holders haven't internalized what this means: every Bitcoin in a reused address is potentially harvest-now-decrypt-later vulnerable. The encryption isn't broken yet. The data being stolen today might not be safe in 2030. The migration is real. The timeline is closer than it was. The chains that move fast survive. The ones that don't will fragment. If you hold Bitcoin in addresses you've spent from, you're more exposed than you think. Not panic-level today. Plan-level today.

• 
  Cernunnos Capital (@CernunnosCap) reported 15 minutes ago

  @RJ9974896734346 Lies. What lies? Nebius has Microsoft, Cloudflare, Meta, Revolut, Shopify, Nvidia etc. as customers. 3GW contracted power is from their last quarter slides. Meta and Nvidia committed to help Nebius built 5GW of power by 2030. And we are still in 2026. 10GW is out projections

• 
  Anubhav (@anubhavlive) reported 15 minutes ago

  Cloudflare + Stripe just dropped a protocol that lets AI agents create accounts, buy domains, and deploy full apps on their own. No human middleman. Salesforce is ripping out the old UI layers so agents can just plug straight into the backend and run workflows. OpenAI's pushing GPT-5.5 as the brain for these proactive agents that don't wait for prompts, they go execute." I spent the last few weeks messing with early agent setups. The difference is wild. One version sits there waiting for instructions like a polite intern. The new wave? It spots a task, reasons through steps, handles payments, deploys, and loops back with results. Feels less like a tool and more like a (slightly chaotic) teammate. The uncomfortable part? Most companies are still building copilots while the stack is racing toward full agent-native systems. If your workflow still needs a human clicking buttons every step, you're about to look real slow. This is where the actual productivity jump happens, not in prettier chat windows, but in software that runs itself. The era of agents that ship isn't coming. It's here, and it's messy, powerful, and moving faster than the safety theatre can keep up. What's the first thing you'd actually trust an AI agent to handle end-to-end for you right now? Business ops, code deploys, or something personal? Drop it below, curious what people are experimenting with.

• 
  kchro (@kchro3) reported 16 minutes ago

  i probably would have paid the subscription service before, but now, I can just have Claude make a free Cloudflare account, backup everything => compress and upload to R2 for a free 10GB. turns out Google photos doesn’t let you bulk delete, so automated a loop to select and delete. also finally having Claude clean up my Gmail

• 
  Tate McCormick (@TateMcCormick) reported 19 minutes ago

  @wzulfikar We're about to come out with email for the same price as Cloudflare but with template support at @yard_sh

• 
  yohance (@yohanc33) reported 24 minutes ago

  @whoiskatrin do cloudflare interns get to work alongside the team solving every-day problems, or do they have projects of their own?

• 
  Anoop Thiparala (@ancrth) reported 24 minutes ago

  Deepgram Flux now runs at 300+ Cloudflare edge locations. Multilingual STT with mid-call language switching. For voice AI at scale, the bottleneck was never model accuracy. It's round-trip latency. Sub-200ms at the edge with zero cold starts changes the game.

• 
  Patrick Meenan (@patmeenan) reported 25 minutes ago

  @lypnv @Cloudflare For this CVE, yes. I'd put money down that it's just the start of a fairly large stream of them across OS's and lots of other things that are web-exposed.

• 
  tcpdump (@dump_tcp) reported 26 minutes ago

  @BrodieOnLinux No they just have bad ddos protection @ubuntu they need better webserver that can atleast handle 1gbps outgoing traffic for cloudflare can detect the high traffic use then it mitigates the attack within around 3 seconds #cloudflare

• 
  Konstantinos (@kostasbotonakis) reported 26 minutes ago

  So here's the issue with this. Cloudflare is amazing company but their AI selling model doesn't really work. Here's an example on OpenAI models. Let's say you pay 20$ for the Plus, you still get access to GPT-Image 2 model (not via API) and you can generate dozens of images in the same price, and then use Codex and GPT-5.3-Codex or GPT-5.4 or GPT-5.5. Now check this pricing for using the Image model via Cloudflare. Does it make sense to use it from there? No.

• 
  Valerie Voigt (@valerie_voigt) reported 29 minutes ago

  There are three websites I have tried to visit today, which tried to use @Cloudflare to verify that I am not a bot. In each case, it spun around and around and around, reloaded, spun around and around and around…They’ve got some kind of problem going as of Sunday night, May 3.

• 
  Yushan Fernando (@yushanwebdev) reported 29 minutes ago

  First, the Cloudflare Worker, registered as the Resend webhook endpoint, receives the incoming email payload. It then reads the KV store, identifies the push notification token, and triggers a push notification via the Expo Push Service.

• 
  Arijit Debnath (@arrzzt) reported 30 minutes ago

  Another day another issue: @Cloudflare login does not works

• 
  Ethan Lipnik (@EthanLipnik) reported 34 minutes ago

  @SnazzyLabs Yup, also has support for OpenVPN or any self hosted VPN and I plan on using Cloudflare TURN for a first party relay system after launch

• 
  Nifemi (@theoluwanifemi) reported 34 minutes ago

  can’t believe i never used cloudflare workers all these years.. they are so dead simple to setup, can practically go from idea to a fully deployed version in 30mins

• 
  Sergio Xalambrí (@sergiodxa) reported 38 minutes ago

  @threepointone IMO vendor lock-in is not bad if it’s explicit Don’t tell me that I’m not being vendor locked in to later find out I was and I can migrate When I choose Cloudflare I know I will be vendor locked in, but I choose that because the ecosystem of services it provides is worth it

• 
  𝔸 𝕃 𝕚 (@alishohadaee) reported 40 minutes ago

  pooof, cloudflare just pushed the agent stack one layer lower the interesting part is not another workflow sdk it is that durable execution can now follow tenant-provided code at runtime that means the platform no longer owns the agent logic it owns the sandbox routing and recovery layer underneath it when every customer repo agent or workflow can ship its own code and still get sleep retries state and resume built in agent infrastructure starts looking more like cloud infrastructure that is a bigger shift than most people think

• 
  addison (@uwunetes) reported 42 minutes ago

  > agent first why do people shoehorn this in? is it to sound trendy? what does it even mean? cloudflare does it all the time and all it seems to mean is **** docs and stuff that is the exact same as their "pre-agent" features. just sounds silly

• 
  Akwaski (@akwaskivivid) reported 44 minutes ago

  @Cloudflare has the worst ui I have seen in my entire career, for an Infra company worth billions, its very disappointing. The ux is horrible, IAM management is a disaster. Dont they just speak to their users?

• 
  Mr. Code (@perpetualtalk) reported 44 minutes ago

  @Chase if you have a better approach please let me know, we are open for business and we are in modern age of 2026 CSV transactions doesn't take much disk space how about offering an option to sync with personal storage service like Cloudflare or Google before the 2 year restrict

• 
  Arjun Bharti (@iarjunbharti) reported 44 minutes ago

  @SantoshYadavDev this is common across most companies. i’ve been reaching out to Cloudflare for the past two months about a billing issue, but they haven’t responded at all

• 
  Ilyas (@ilyesm) reported 52 minutes ago

  @harshil1712 @Cloudflare @CloudflareDev Sure, was able to debug it. It was an issue with the pnpm/npm install of dependencies, but it was not clear on the dashboard what was causing it. Would suggest better display of console logs when installing dependencies, to identify these silent issues!

• 
  grace 💜 (@_griffonage_) reported 54 minutes ago

  @ImmaculaRN @lestatdelioncat Oh hang on it actually might just be a filegarden/cloudflare outage. The sites down for me

• 
  Gocha Berulava (@gochaberulava) reported 55 minutes ago

  @bidah @vercel @Cloudflare "no upsell" only works if there's nothing to meter. vercel/railway/render meter bandwidth, seconds, services. that's why the upsells never stop. structural, not malicious. usectl: pick your server size with sliders, run as many pods inside it (apps, postgres, redis, s3, jobs) as you want. one flat bill, no meter. cli + mcp for cursor/claude. cf is solid for edge. ours is for full-stack.

• 
  Charly Wargnier (@DataChaz) reported 58 minutes ago

  THIS IS THE OAUTH MOMENT FOR AGENTIC E-COMMERCE AI agents can finally pay for and deploy apps on their own 🤯 Until now, building with AI hit a hard wall at deployment. The agent did the coding, but you did the cloud admin, stepping in to create a Cloudflare account, add a credit card, and wire up API tokens. Not anymore. Cloudflare and Stripe just completely automated this loop via `Stripe Projects`! Run stripe projects init, prompt your agent, and it builds and ships a live app on a registered domain. It works seamlessly across 3 pillars: #1 - Discovery → Agents query a service catalog to find the exact domains or compute they need. #2 - Authorization → Stripe verifies your identity, and Cloudflare auto-provisions the account. No tokens are exposed to the agent. #3 - Payment → Stripe handles payment tokens with a strict $100/mo cap. Your card details never touch the agent. And that's a MASSIVE unlock! Any SaaS with signed-in users can now orchestrate this exact flow, giving agents the power to safely buy and deploy cloud services. Dive into the mechanics in the 🧵↓