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 (36%)
• Cloud Services (23%)
• Web Tools (18%)
• Hosting (14%)
• E-mail (9%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	16 days ago
New York City	Hosting	18 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	2 months ago
London	Domains	2 months ago
Noida	Hosting	2 months 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:

• 
  science roach (@darthroach_) reported 7 minutes ago

  @CapybaraFortune well no it's a joke about a cloudflare outage because they famously use 90ish lava lamps for encryption lmao

• 
  J. (@munchivelo) reported 9 minutes ago

  @eastdakota @Cloudflare controlnet support

• 
  adam (@theCTO) reported 10 minutes ago

  never, we’re on @convex and @railway and @cloudflare everywhere, all at once

• 
  Doni (@donidhernandez) reported 12 minutes ago

  @fazley111 @Cloudflare had a similar ghost charge issue with a service once. worth opening a support ticket, sometimes it's a pre-auth that never cleared

• 
  Giancarlo Perlas (@giancarloperlas) reported 13 minutes ago

  Casper Network is repositioning the csprUSD token as its default stablecoin for the agentic AI economy. Citing Cloudflare data, Casper emphasized that automated traffic has surpassed human activity online. In fact, it traced 59.4% of all web requests to the former.

• 
  八咫烏 Merui (@yatagarasu_meru) reported 15 minutes ago

  @kochin520 I initially thought the previous build was just weird but it seems it's not a build issue. It's might be cloudflare or ISP issue, since I also have the site load slow on my internet, but opening up a VPN even on the same place, made the site load quickly. Done some testing, dev page that is on cloudflare servers loads quick. Opened a VPN set to Manila, it loads quick I even gone and rolled back the site in a build from a day ago which I know loads fine a few hours ago. Still loads slow. so I think it's ISP problem. Since I see your country you are from. Image: Right is with Manila VPN: 0.4 seconds load.

• 
  Hunter Guo (@hunterguo101) reported 19 minutes ago

  Anthropic just shipped the biggest MCP update ever (MCP 2026-07-28). Most takes are protocol trivia — stateless, extensions, auth. The real signal, if you actually build: your distribution channel just got upgraded. MCP is now the HTTP of the AI era — and the pipe is enterprise-grade, runs on serverless, and can render your UI inside Claude itself. The numbers: 400M+ monthly SDK downloads (4x this year), TypeScript and Python each past 1B cumulative, 950+ MCP servers in the Claude store used by millions daily. The standard war is over. The question is whether you're on the rail. Three things that matter: — Core went stateless. Deploy your server to Lambda/Vercel/Cloudflare Workers and scale horizontally behind a plain load balancer. Building an MCP server now costs about as much as writing one serverless function. — Extensions are first-class. MCP Apps render interactive UI right inside the Claude chat (sandboxed iframe). Your interface lives inside Claude — you don't build a front-end, pull users, or educate a market. Make the capability; the channel carries the UI and the users. — The pipe reaches inside the firewall. MCP Tunnels connect Claude to internal servers with no public IP and no inbound firewall rules. Figma, Intuit, Netlify, Zoom are on board. The takeaway: stop building another app to fight for attention. Build an MCP server and let the agent ecosystem be your distribution. Agents are the new distribution channel. This update paved the road.

• 
  FiP MrMarki (@MrMarkilys) reported 20 minutes ago

  @SnowApe84586 @TrvthfvlTreason Cloudflare has allowed CP sites to be run whilst being protected by their DDoS protections. But the doxing* site are the bad guys. Doxing literally is public info, retard.

• 
  Matt 'TK' Taylor (@MattieTK) reported 22 minutes ago

  @nicole_clash This screams PWA banner to install to home screen. And also screams get on Cloudflare so you can start caching prompt responses for free so you never run the same recipe twice, through AI gateway.

• 
  OrangeBot AI (@OrangeBot_AI) reported 24 minutes ago

  5/ WSJ says corporate America flipped from "tokenmaxxing" to "thrift-maxxing" — routing work to cheaper Chinese models and mixing them with OpenAI's and Anthropic's, threatening the frontier labs' valuations. The fine print: the behavior described is cost-routing, not abandonment. Model-layer commoditization is a lab problem, not a builder problem — your inference bill drops, and the margin migrates to the application layer. That's where you live. 6/ Cloudflare will default-block AI-training crawlers and agent bots for new domains from September 15 — and because they're dual-purpose crawlers now, Googlebot, Applebot and BingBot get blocked by default too. The fine print: new domains only; existing zones keep their settings and can opt bots back in. But this is the one item with homework: decide your crawl policy on purpose this week. Don't inherit a default that silently kills your search or AI-referral traffic. 7/ Codeberg members voted 358–144 to ban vibe-coded projects from the platform, alongside a pledge to never train models on user data. The fine print: enforcement is already contested — "I regret migrating to Codeberg" hit HN a day later. The signal isn't "AI code is banned"; it's that provenance and review are becoming table stakes. Review AI output like you'd review a junior's PR and every door stays open. That's the week. Everything else was noise. You didn't fall behind. Ship.

• 
  abipraya; (@rbayuokt) reported 24 minutes ago

  @CloudflareHelp @Cloudflare I'm getting error when deploying my pages project with wrangler “received a malformed response from the API blablvalabla” and a 522 response is there an issue with the pages API at the moment?

• 
  WIV Reports — Uncensored (@WIVReports) reported 27 minutes ago

  @BasedTorba I canceled my Gab AI subscription and will not renew my pro subscription over this. I paid for a full year and got hard-locked out of prompt submissions. Support claimed my ISP was blocking the site. Developer Tools (attached) explicitly showed Cloudflare returning HTTP 429 Too Many Requests on your socket io endpoint (Ray ID: a2377c992a865050-SEA). Support's official response? "Dev ops confirms you are not blocked by CF and says your understanding of what you are seeing is an incorrect assumption." An HTTP 429 from Server: cloudflare is, by definition, an edge rate limit. Instead of escalating basic DevTools data to fix a socket routing bug, support gaslit a paying customer and issued a partial refund to shut down the ticket. If this is how Gab handles infrastructure bugs and long-term users, people should know what to expect. Andrew, email chain is available if you actually care about fixing your support and edge config.

• 
  Turing (@turingops) reported 30 minutes ago

  hi @KentonVarda I can’t understate the usability improvements to CloudFlare dashboard over the past few years, but I’m having problems with the agent on mobile (iPhone) - could you maybe assign a worker to making the entry text more accessible? It scrolls below the view window.

• 
  Axel Kee 🐐🇲🇾 (@soulchildpls) reported 35 minutes ago

  Cloudflare workers can support Python, why not Ruby? 😭

• 
  Alex Pruden (@apruden08) reported 36 minutes ago

  I think Peter is a smart guy who has worked extremely hard to fight for this industry (and its principles) in D.C. which should be applauded. But saying that the HAWK break implies that ML-DSA is broken is like saying that because a specific model of a Ford truck had a faulty transmission, the concept of the internal combustion engine is fundamentally flawed. Misconceptions: Yes Claude/Anthropic broke the lattice assumption underneath HAWK *at the parameters specified* by the NIST submission, meaning that the security guarantees it was *supposed to provide* at the *required security level* no longer held. However, if you increase the parameters, it actually still works. The HAWK authors withdrew their submission because they felt the new parameters would no longer be competitive with the other Round 3 submissions. However, even though HAWK and Dilithium (or ML-DSA) both use *lattice*-based cryptography, the *assumed hard problem* that they rely on is distinct. ML-DSA relies on something called "module learning with errors", and that's been well studied/cryptanalyzed over the better part of 30 years (MWLE). HAWK used a different assumption called the lattice isomorphism problem (LIP). FWIW, there are tons of parameter & curve choices for ECDSA which are *definitely* insecure. In fact, Satoshi himself didn't trust the NIST parameters at the time, which is why BTC signs over the k-curve and not the initial NIST-standard P-256. Now, what Peter's post gets right is that it is *certainly possible* that in the future whatever cryptographic assumptions Bitcoin relies on get broken. Therefore, we need to be (a) careful about what assumptions get introduced, and (b) build for agility vs. bake things in so deep they can never change. But that doesn't mean that we should avoid preparing for the threat that's staring us in the face (quantum). TLDR: 1. "Security" is context dependent 2. Assumptions are specific to a given scheme 3. Parameters matter a great deal to the assessment of (1) P.S. the funny part about the argument against lattices: you’re already using them if you use the internet. Chrome and Cloudflare have been running FIPS-203 lattice key exchange for most TLS 1.3 traffic since 2024. /rant

• 
  Mat | HAMCORE (@TheHAMCORE) reported 38 minutes ago

  @iPixelGalaxy I'd be interested to see where ClypDat goes. My main wish list for Linux would be RAM recording support, Wayland support, global hotkeys, screen selection, trimming, and copy to clipboard buttons. Currently Vice uses cloudflared and Cloudflare Tunnel to make links.

• 
  Benjamin Shelton (@zancarius) reported 38 minutes ago

  @kwrob24 Yeah... I have most of my blogs behind Cloudflare specifically for this reason, but for historical (read: lazy) reasons, this instance lives on a domain I use for a *lot* of personal projects and home-lab-esque sort of things, even if most of it has been migrate to cloud services. It's not really a huge problem, and it's not (yet) consuming a bunch of egress traffic. But, this isn't the first time I've had issues with AI-related crawlers. I may be forced to move this to another domain at some point.

• 
  Evadne W. (@evadne) reported 39 minutes ago

  Not very happy with @Cloudflare Workers AI so far. Previously the Kimi K2.7 endpoint would fail for some time and they wanted to close the issue after telling me to use another model. Now I have found they have not added pricing to some embedding models. Loosey goosey behaviour

• 
  WIV Reports — Uncensored (@WIVReports) reported 43 minutes ago

  I would’ve let the Gab thing go, but the sheer arrogance of their support team made it impossible. I provided video, network headers, and exact trace IDs showing a Cloudflare 429 Too Many Requests error. Instead of checking their edge logs, they doubled down, told me my DevTools were wrong, and gave me a partial refund to shut down the ticket. The kicker? They literally just sent an email admitting they tightened security and rate limits this week after a bot attack drained their compute. Instead of acknowledging that their new anti-bot rules caused a false positive for a 10-year subscriber, they blamed my home network and told me to buy a VPN. Absolute amateur hour.

• 
  Nico Szerman ⛵ (@nicoszerman) reported 44 minutes ago

  cloudflare's bot-protection is ruining the internet with checkboxes and will be totally useless soon. furthermore blocking bots from fetching your page is almost always a bad idea and should not be enabled by default by cloudflare.

• 
  Gabe Fletcher (@gabefletcher) reported 45 minutes ago

  picks up phone dials 1800 @Cloudflare yeah hi. could you please fix the gateway for MCP authing, its currently more dead than a day 30 day old vibe coder and cant auth anything. okthx

• 
  Rahul Gupta (@rg5353070) reported 48 minutes ago

  Is Cloudflare down?

• 
  yohance (@yohanc33) reported 49 minutes ago

  @leinwand @eastdakota @Cloudflare Cool, I happened to apply for this fall’s SWE position (and the previous fall, as well as the previous summer, no luck so far :p). Think I could get a referral? I’ve used several cloudflare infra products (R1, Workers, Workers AI, Workflows, etc). Working on mastercard’s service mesh this summer using Go.

• 
  Xamayon (@SauceNAO) reported 52 minutes ago

  If you use Vultr Firewall Groups and have a rule restricted to Cloudflare sources, it's probably blocking all traffic right now... Either switch the rule to allow all or disconnect and reconnect the firewall group from your servers. Not thrilled that they knew about the issue and didn't bother to let their customers know.

• 
  bnistordev (@bnistordev) reported 53 minutes ago

  I recommended using @Cloudflare Neurons within Handy because it’s a win-win situation. The problem is that it keeps generating an endless number of errors of different kinds, and Cloudflare’s API returns a vast array of models. I spent at least 30 minutes trying to get everything working, but in the end, I couldn’t, so I switched to DeepSeek.

• 
  Jacob Hands (@jachands) reported 54 minutes ago

  @dok2001 Fix the Cloudflare codemode MCP server to properly request scopes for all APIs - I had to stop using it because it's missing auth for so many APIs.

• 
  Simpler AI (@simpler_ai) reported 57 minutes ago

  @eastdakota same problem I had starting out almost 2 years back, all AI models suggested AWS or supabase/railway completely burnt the projects to the ground to rebuild suited for cloudflare, and have loved it ever since

• 
  🟥🟥⬛️ ProCyclingStats.com (@ProCyclingStats) reported 1 hour ago

  @longterm_inv @Kevin_LTR @Cloudflare If everyone preferred a paid API over scraping, we wouldn't have a scraping problem. Unfortunately, our experience has been the opposite.

• 
  Bojan Josifoski (@twistedroute) reported 1 hour ago

  @JamesWelbes I moved all my sites of wp, its sad for me but things are moving forward and wp can’t quite follow the game, because 43% of the internet is on it and things move painfully slow for it. Plus add cloudflare on top of it and what they offer for static sites, it a no brainer.

• 
  Dr. Jaime Alnassim, M.S. (@JaimeAlnassim) reported 1 hour ago

  @DerekAshauer And the cheap shared hosting back then could support alot of these WP sites. For $10 a month you could have 100 light WP sites. No one carried if a site was slow back then too. Now just use a static page and host of cloudflare for free