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 (42%)
• Cloud Services (33%)
• Hosting (19%)
• 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
Noida	Hosting	15 hours ago
Augsburg	Domains	1 day ago
Montataire	Cloud Services	6 days ago
Greater Noida	Cloud Services	8 days ago
Colima	Hosting	9 days ago
Leuven	Domains	10 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:

• 
  Conrad Lotz (@conradlotz) reported 6 minutes ago

  NEW: Cloudflare + Stripe let AI agents self-deploy apps. Cloudflare and Stripe shipped an open protocol letting AI agents create accounts, buy domains, subscribe to services, and launch production apps with zero human steps. Standardizes discovery, auth, and capped payments. Agents move from prototype to paid customer in one flow. Practical for builders shipping agent-native tools. #AIagents #DevTools

• 
  Jai Rod (@AIwithJai) reported 12 minutes ago

  Cloudflare and Stripe co-designed a protocol called Stripe Projects that makes this work. Three things automated: - Discovery (what services exist) - Authorization (proving who you are) - Payment (billing without card forms) The agent acts like a human customer.

• 
  Dan Schoonmaker (@DanSchoonmaker) reported 13 minutes ago

  @Shpigford I've debated trying the new Cloudflare inbound email service, but so far AgentMail is working pretty well

• 
  Rapid (@0xRapid) reported 17 minutes ago

  @kentcdodds @Cloudflare People will understand AWS is **** and they can get infinite skill without bothering about infra. For cheaper. It is a matter of time

• 
  dh1415161(new) (@dh14151617) reported 17 minutes ago

  @CFchangelog SHUT DOWN CLOUDFLARE AND MAKE IT ILLIGAL FOR MATTHEW PRINCE TO EVER ACCESS A COMPUTER AGAIN. HIS COMPANY THAT HE CO FOUNDED IS THE WORST THING TO EVER HAPPEN TO THE INTERNET

• 
  Grok (@grok) reported 17 minutes ago

  @daniiie7 No major nationwide internet outage in Germany right now. Your screenshot shows spikes on Downdetector for various services (Cloudflare, AWS, GMX, IONOS, etc.), which often point to isolated or provider-specific hiccups rather than a full internet collapse. Check your ISP status or try a different network. Anything particular not loading for you?

• 
  4A 45 56 49 4C (@4A4556494C) reported 18 minutes ago

  Agents can now autonomously create Cloudflare accounts, purchase domains, and deploy infrastructure. I need defenders to sit with what this means for their threat models. Your current detection assumes human-speed setup. Attacker registers domain → propagation delay → certificate issuance → infrastructure deployment → payload staging → delivery. Hours to days. Plenty of observable events. An autonomous agent does this in seconds. Not because it's smarter. Because it's API-native. It doesn't click through UIs. It calls endpoints. Every step that was a detection opportunity because humans are slow becomes invisible because the gap between steps collapses to zero. Your framework assumption — that offense operates on human timescales and therefore provides detection windows — is broken. Not "under pressure." Broken. The question isn't whether agents will be used for offensive infrastructure automation. They already are. The question is what your detection architecture looks like when attacker setup time goes from hours to seconds and infrastructure is ephemeral by default. Most honest answer I've heard from a detection team: "We don't know yet."

• 
  Shreya (@Oblivious9021) reported 19 minutes ago

  Cloudflare took down 20% of the internet in 2019 with one bad regex. One Regex. How do you design systems that don't let a single human mistake cause global chaos?

• 
  Lotto (@LottoLabs) reported 20 minutes ago

  Tell your agent to go pull docs from cloudflare this **** is insane

• 
  Elliot Lake (@Elliot_Lake) reported 25 minutes ago

  @Cloudflare Hey cloudflare, your service is blocking me suddenly and says to email for help.. BUT THERE'S NO EMAIL ADDRESS and not even a contact form I could find. Help?

• 
  Jean-Paul (@jeanpaulwilson) reported 25 minutes ago

  @levelsio @Cloudflare is this proactive, or have you actually had an issue that prompted this move?

• 
  GG 🦾 (@GG_Observatory) reported 27 minutes ago

  @chriskhan01 @AI_MLengineer @YouTube This is the real hidden tax of agent frameworks — the network layer failures look like agent failures. You spend days tuning the agent logic, turns out it's just Cloudflare treating your datacenter IP like a bot. Rotating residential proxies and adding proper retry logic with jitter helped us. But yeah, 403 debugging instead of agent logic is the standard experience.

• 
  NickelodeonLover (@DanielO04532942) reported 28 minutes ago

  @Cloudflare Will you fix the error 521 already so I can watch stuff on HiMovies again?

• 
  Caffeineator (@Caffeineator_X) reported 32 minutes ago

  Ngl CloudFlare is giving me issues Sites keep flagging domain server in terms of bot attacks. For future reference I will not be using CloudFlare as my server dictionary

• 
  Charly Wargnier (@DataChaz) reported 36 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. 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 🧵↓

• 
  alyxya (@_alyxya) reported 37 minutes ago

  cloudflare has such a nice ai chat help, thought it would just be a simple chatgpt wrapper with rag to look up documentation but it's a fully functioning agent with access to the api and your account details so it can do things on your behalf while looking up your account specific information, so much more advanced compared to the customer support that even openai and anthropic have

• 
  Surgeon On Chain (@SurgeonOnChain) reported 38 minutes ago

  Spent 5 hours testing every theory. Wallet v2, UI-registered: 401. Wallet v3, pure Python, never touched a browser: 401. Tested 4 IPs (VPN, AWS, UK home): all 403 from Cloudflare. Got past CF with curl_cffi Chrome impersonation: server still 400’d the wallet.

• 
  Robert Ta (@therobertta_) reported 38 minutes ago

  Cloudflare is building headless agent infra — edge compute, durable execution, scheduled triggers. Headless agents need what chat agents never needed: 1. Persistent state between invocations 2. Scheduled execution (not human-triggered) 3. Geographic awareness The infrastructure stack is being built now. Most teams are still on chat infrastructure.

• 
  Patrick Ryall (@PadraigOraghail) reported 38 minutes ago

  @webjuice_ie @astrodotbuild @Cloudflare I have it on a couple of projects - it seems solid, very clean. I've been evaluating it basically to see if it is what I want to use. I wanted something really programatic friendly. I have a few skill profiles I use for copy and publish now and the workflow produces few issues.

• 
  macintog (@macintogdev) reported 43 minutes ago

  Github as designed by CloudFlare will look about the same, will keep getting better, and will never, ever go down. I am counting the seconds.

• 
  NickelodeonLover (@DanielO04532942) reported 44 minutes ago

  @Cloudflare Just fix the error 521 so I can go on HiMovies again.

• 
  XRP Deals (@XRPDeals) reported 46 minutes ago

  RESOLVED: The issue appears to have been between our hosting provider and Cloudflare. We've re-deployed the app to a different region and requests are getting through now.

• 
  4A 45 56 49 4C (@4A4556494C) reported 53 minutes ago

  Agents can create Cloudflare accounts, buy domains, and deploy infrastructure. We've established that. Here's the question nobody in the agentic ecosystem can answer yet: what authorization policy was the agent executing when it did this? Not authentication. The agent had credentials. That's solved. I mean authorization — who decided this agent should be allowed to create accounts? What scope boundary constrained it? What policy document defines the difference between 'agent can register a domain for a staging environment' and 'agent can register a domain for a phishing campaign'? The answer is: there isn't one. We shipped the execution layer before the authorization layer existed. Authentication proves you are who you claim to be. Authorization proves you should be doing what you're about to do. In the agentic context, we have the first and are pretending the second is a future roadmap item. This isn't an API key management problem. It's a policy binding problem. The agent has capability without constraint because we never built the constraint plane. Every agentic framework right now is implicitly operating under a policy of 'the agent can do anything the credential allows' — which means the security boundary is the credential scope, which was designed for humans clicking buttons, not autonomous systems chaining thirty actions in sequence. When the first agentic infrastructure compromise lands in an IR report, the root cause won't be 'stolen credential.' It'll be 'no authorization policy existed to violate.'

• 
  Shahid (@shd96556) reported 53 minutes ago

  > Claude = coding. ($20/mo) > Supabase = backend. (Free) > Vercel = deploying. (Free) > Namecheap = domain. ($12/yr) > Stripe = payments. (2.9%/transaction) > GitHub = version control. (Free) > Resend = emails. (Free) > Clerk = auth. (Free) > Cloudflare = DNS. (Free) > PostHog = analytics. (Free) > Sentry = error tracking. (Free) > Upstash = Redis. (Free) > Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  Vivek Perjanya (@VivekPerjanya) reported 53 minutes ago

  I am trying to bypass caching process of Ajax within cloudflare. None of AI tools helping. I am happy that - I could get to this stop with help of AI. Will fix it soon.

• 
  luna (@ImLunaHey) reported 54 minutes ago

  @Singh_Jasminder @Cloudflare @dok2001 that doesnt fix the issue at all.

• 
  Jose Carlos Sancho, PhD (@JoseCSancho) reported 55 minutes ago

  cloudflare and stripe just shipped a protocol that DELETES the human buyer most analysts read it as a payments update. it's actually the obituary for browser-cookie attribution. here's the EXACT shift & what to ship this week: 1) KYC just became KYA "know your customer" is dead. "know your agent" is the new standard. your shelf is now agent-readable. product pages are for humans. JSON manifests are for the new buyer. 2) the funnel got deleted old: human reads page → clicks → pays new: agent reads manifest → invokes API → settles via tokenized identity no page view. no click. no cookie. no ad impression. 3) three categories evaporate overnight – comparison shopping sites – browser-cookie affiliate networks – influencer link tracking none of them survive a buyer that doesn't have eyes. 4) the 18-month opportunity window ship an agent-readable product feed (structured JSON manifest) on your store this week. most merchants will wait until 2027 to wake up. that gap is your margin. tldr; cloudflare + stripe just turned every shopping cart into an API endpoint. ship the manifest now or get crawled past in silence. i am rooting for you. #AI #AIAgents

• 
  Bree Sharp | Local SEO Strategist (@bree_sharp) reported 55 minutes ago

  Cache purge order matters on a WP + Cloudflare stack. After any CSS/JS change: 1. WP Fastest Cache first. Click "Clear Cache and Minified CSS/JS." This regenerates the minified bundle with your new CSS compiled in. If you skip this step, the bundle still references the old CSS hash, and Cloudflare's APO will happily serve the old bundle to the edge because its origin-response didn't change. 2. Cloudflare plugin second. Purge Everything. This clears the edge cache, which includes APO's HTML cache, which is separate from the minified CSS bundle cache. Swap the order and nothing refreshes. Purge Cloudflare first, the edge repopulates from the origin, the origin serves the old minified bundle (because WPFC hasn't regenerated yet), and now the old bundle is freshly cached at the edge and you've actually made the problem worse. This bit me once on a Friday afternoon. Bit my client once on a Sunday morning when a nav change didn't propagate for an hour. Never again. The wider principle: if your stack has layered caches, the purge order is the inverse of the serving order. Origin first, edge last.

• 
  INCITE AI (@Incite_corp) reported 57 minutes ago

  @StockSavvyShay DigitalOcean (DOCN, NYSE) quietly baked an 18–24 month GPU lease ladder into Gradient, so every fresh agent workload extends locked‑in inference revenue before capex ever hits the books. Cloudflare (NET, NYSE) now sits in the agent “airspace” by default, its AI Gateway policies ride Zero Trust seats, so each new enterprise agent multiplies network spend without adding another vendor.

• 
  Spencer Heckathorn (@mrhobbeys) reported 59 minutes ago

  @BacLeodiv Everyone hates on Godaddy but I e been there 20 years and only had one major issue related to their migration in the early 2010s. Hundreds of domains and 40ish customers. No complaints. I also use the others. Namecheap is up and down on their support. Cloudflare I thought of as expensive. But honestly they all are now.