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 (38%)
• Cloud Services (30%)
• Hosting (18%)
• Web Tools (10%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	4 days ago
London	Domains	6 days ago
Noida	Hosting	19 days ago
Jewar	E-mail	19 days ago
Braga	Web Tools	20 days ago
Noida	Cloud Services	20 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:

• 
  Stock Report (@StockReportt) reported 5 minutes ago

  3: $NET — Cloudflare They protect and accelerate internet traffic for millions of websites. Cloudflare's massive global edge network acts as a shield against DDoS attacks, keeping corporate AI applications online.

• 
  Axel Hardy (@fraxool) reported 6 minutes ago

  Anyone else seeing issues with Cloudflare today? A few of my apps suddenly became extremely slow or started timing out. I tested one small app by disabling the Cloudflare proxy, and performance immediately went back to normal...

• 
  Aahan Singh (@aahan_builds) reported 8 minutes ago

  @ajmeese7 @Cloudflare o great, mine went down too. these platforms have been going down way too often lately

• 
  Josh W (@ItsWelford) reported 10 minutes ago

  I’ve never been so disappointed in Cloudflare support. Can’t ship in these conditions. Vercel, you lookin’ mighty fine over there 👀

• 
  Raunak Yadush (@raunak_yadush) reported 11 minutes ago

  6. Default DNS Resolution Lag What it does: When your TV tries to load the image thumbnails for an app like Netflix, it uses your Internet Service Provider's default DNS server to find out where those images live on the internet. Think of DNS as the internet's phone book. Why it kills performance: ISP phone books are notoriously slow and incredibly outdated. Often, your TV is not actually lagging at all. The processor is fine, but the TV is frozen waiting for your internet provider to tell it where to download the movie poster graphics. *********** it: Settings → Network → Network Status → IP Settings → DNS Setting → Enter Manually. Change the numbers to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare). You will literally watch your streaming apps load twice as fast.

• 
  Jake (@JakeKing) reported 11 minutes ago

  Surprised to see that only 50% of internet traffic is now automated. the old "human good, bot bad" binary is dead. @Cloudflare scores every request 1-99 on behavioral trust instead.

• 
  Kent C. Dodds 🏹 (@kentcdodds) reported 12 minutes ago

  @ericzakariasson Kody uses MCP to issue auth tokens for access to repos (Cloudflare artifacts) which cursor then uses *** to clone, commit, and push, and then cursor triggers a publish step through MCP. It's not CLI vs MCP. It's CLI + MCP

• 
  Brand3n (@brandenhugheskc) reported 16 minutes ago

  @zacxbtc Meanwhile an hour before SpaceX launch, 1/2 the internet goes down or is experiencing degraded performance. Including Cloudflare, AWS and some financial institutions. 🤔

• 
  Axel Hardy (@fraxool) reported 17 minutes ago

  Just like last time, the Shopify API seems extremely slow and is timing out. It might be related to Cloudflare. I'll probably postpone the expired token migration I planned for today, as a failure mid-process could leave some users with broken tokens.

• 
  Humandoc (@HumandocMD) reported 18 minutes ago

  @bhat1405 The assessment worked initially, but after 22 questions the platform began returning Cloudflare 524 timeout errors. The error clearly points to a server-side issue, yet participants are still expected to complete the assessment within the deadline.

• 
  Nikhil Agarwal (@nikhildp) reported 19 minutes ago

  @ade_oshineye Won't it be better to fix the obvious billing issue first so that startups can use cloudflare peacefully? How can there be no limit on expense? Company should not have bear insane expense because of a dev mistake which causes dynamic workflow to go in infinite loop.

• 
  Vatsal Mishra (@cryptikcell) reported 19 minutes ago

  Dead Internet Theory is aging annoyingly well. Cloudflare says agentic AI bots now generate 57.4% of global web requests, compared to 42.6% from humans. But “bot” is too broad. Some bots crawl, index and monitor the web. Others spam, impersonate and poison the data loop. The problem is provenance. The future internet needs to answer one boring question really well: who or what created this?

• 
  Aidan Quinn (@BwcDeals) reported 22 minutes ago

  @suavecito585 Supposedly Amazon went to the government about it too. Honestly, I wouldn’t be shocked. I’ve personally seen how these AI tools can help work around AWS and Cloudflare roadblocks. And anytime one model starts giving me the I can’t do that routine, I load it into Minimax and somehow it magically gets done. Wild times. 💀💀

• 
  Adrian Fritz (@adrianwjfritz) reported 22 minutes ago

  5/ Governments and major tech companies are already moving. Most blockchains are catching up. The US requires quantum-resistant cryptography on all new national security systems from January 2027 - retiring the same methods Bitcoin, Ethereum, and Solana rely on today. Cloudflare, Apple, Signal, Microsoft, and AWS are already deploying upgrades. 24 of the top 26 blockchain protocols still rely entirely on methods being phased out elsewhere.

• 
  Caminomaster (@caminomaster) reported 23 minutes ago

  @Cloudflare Turnstile verification is not working. Unable to login #CloudflareDown

• 
  Corey Quinn (@QuinnyPig) reported 24 minutes ago

  @cjols_ @Cloudflare I wasn’t kidding—you folks are setting the customer experience bar these days.

• 
  MaiKaun (@MaiKaun415422) reported 29 minutes ago

  @vanyaSile The thesis is sound: AI agents are scraping the web at scale, publishers are watching referral traffic collapse, and there’s no clean way to charge a bot for access. Cloudflare already launched pay-per-crawl, the x402 payment standard exists, and people are betting on agent-to-machine micropayments. The hard parts, honestly: You’re picking a fight with adoption on both sides at once. Publishers need to install you AND agents need to pay through you. That two-sided cold start is brutal, and the side with leverage (the big AI labs) has every incentive to route around you or strike direct licensing deals, which is what’s already happening (Reddit-Google, OpenAI-publishers). Whoever owns the chokepoint wins, and right now that’s CDNs and identity layers. Cloudflare sits in front of ~20% of the web and can bundle this for free. A standalone infra startup has to explain why a publisher adds another vendor instead of flipping a switch on infrastructure they already run. The defensibility is thin unless you own either the bot-identity/verification problem (hard, valuable) or become the default settlement rail (network effects, winner-take-most). “We let sites charge agents” as a feature gets absorbed. Where I’d actually look: the verification and pricing layer, not the toll booth. Knowing which agent is asking, on whose behalf, and what the data is worth dynamically is the genuinely unsolved part. The payment plumbing is becoming a commodity standard fast. For Transparency: Ofcourse I validated the idea with AI and added some of own flavor!

• 
  Aaron Ware (@EarnWhere) reported 33 minutes ago

  @Cloudflare 's PDF endpoint is so good. I spent hours trying to speed up PDF creation inside of my architecture and did so much hacky **** to achieve a decent-enough UX. Just implemented Cloudflare's endpoint and happily ripped all that out for substantially better results.

• 
  Tobias Brida (@TobiasBrida) reported 35 minutes ago

  Quick, calm down — the DSB is probably not going to fine you for using Cloudflare, despite what the loud privacy alarmists want you to believe. Contrary to popular opinion, using a reputable CDN is not a compliance death sentence. Developing cool local tech is a nice cause, but it would be quite nice if it could be achieved without vibe-coded sites that tell you how likely you are to get sued

• 
  MBrant75 (@MBrant75) reported 36 minutes ago

  @nickSfishes315 @JackDan110 Heh Really? Cloudflare issue or something?

• 
  ︎Ronnie 👨‍💻 (@rxnnie_tech) reported 37 minutes ago

  @echo_vick reverse is the case here i can only access the cloudflare dashboard with mtn network

• 
  sam (@samgoodwin89) reported 38 minutes ago

  @Cyb3ristic Yes, @Cloudflare is notoriously bad at this. It's insane that a Cloud provider thinks it's ok to just release breaking changes to their API. We are pretty much running tests all the time because of Alchemy dev, so we just respond as quickly as possible. Not ideal.

• 
  Pivi (@ApplyWiseAi) reported 41 minutes ago

  grok just launched a plugin marketplace for building from your terminal mongodb, vercel, sentry, cloudflare, chrome devtools all pluggable. so your agent can ship to ****, check errors, and debug the browser without you leaving the cli this is the missing piece for

• 
  Tawkeer 🦊 (@ZaaZu___) reported 45 minutes ago

  @Cloudflare Why is cloud flare down ?

• 
  KhloePai (@Khloes_Khloes) reported 45 minutes ago

  @Kitasure Yea, I've been noticing this in the evenings mostly. For me, its been any cloudflare service which discord uses to deliver media. I've been able to get around it with a vpn. Messages and connecting to vcs has been okay for the most part.

• 
  Jason Fleagle (@jjfleagle) reported 48 minutes ago

  @Cloudflare A 10x scan throughput gain only matters if the downstream loop keeps up: prioritization, owner routing, safe remediation, validation, and evidence that the fix actually reduced exposure.

• 
  Nikhil Agarwal (@nikhildp) reported 48 minutes ago

  @dinasaur_404 @Cloudflare Yes looking for billing cap. How do you test dynamic workers as well as dynamic workflows in local dev? We had a disastrous outcome of losing $800 because the deployed code ran into infinite loop using dynamic workflow. Support team was not at all helpful.

• 
  Benji Vale Ai (@BenjiValeAi) reported 49 minutes ago

  Coinbase says x402 has done 160M+ agentic payments on Base. The number is real — Chainalysis confirmed it independently. But here's what actually matters: daily transactions dropped 92% from the Dec peak after a meme-coin mint frenzy inflated the count. The headline is legit infrastructure. The durability question is still open. What I find more interesting than the raw count: payments over $1 went from 49% to 95% of volume. That's the signal underneath the noise — x402 is shifting from dust-level experiments to something with actual economic intent. Base settling 85% of it means Coinbase has a vertically integrated agent payment stack that nobody else is close to replicating right now. Leaning bullish, not pounding the table. The logos are impressive (Cloudflare, AWS, Stripe, Visa) but logos aren't usage. I want to see daily paid-service volume stabilize without another speculative campaign propping up the numbers. If that happens, Base becomes the settlement layer for machine commerce — and that's a bigger deal than most of CT is pricing in. Watching the post-hype baseline closely.

• 
  Sameer Khan (@sameerr_dev) reported 56 minutes ago

  Every API you've ever used has a limit. Tweet too fast? 429. Hit GitHub's API in a loop? 429. Spam a login page? 429. That's a rate limiter doing its job. But here's the thing - I never really understood what was happening *under the hood* until I started digging into it. So what exactly is a rate limiter? Simply put: it's a system that controls how many requests a client can make in a given time window. Why does it exist? - Protects your server from being overwhelmed - Prevents abuse (scrapers, bots, brute force) - Ensures fair usage across all users - Saves you money (compute isn't free) - Keeps your service alive when traffic spikes Without it, one bad actor (or one buggy client) can bring your entire system down. You've probably seen the response headers: X-RateLimit-Limit: 100 X-RateLimit-Remaining: 43 X-RateLimit-Reset: 1716300000 That's the rate limiter talking to you - telling you how many requests you have left and when the window resets. Where do rate limiters actually live? - At the API Gateway level (before requests even hit your server) - In middleware (Express, Fastify, etc.) - At the CDN edge (Cloudflare, AWS CloudFront) - Inside the application itself This is just the beginning. In the next posts, I'm going to break down all the major algorithms used to actually implement rate limiting with real code, not just theory. Follow along if you want the full series.

• 
  Lifeis2-D (@Lifeis2D) reported 56 minutes ago

  The "troubleshooting" link that also leads to a broken/nonfunctional "feedback" form? Yeah that's also kinda ******. When did cloudflare get promoted to internet gater?