Cloudflare status: hosting issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Full Outage Map
Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.
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.
At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!
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 | 17 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:
-
Rainer Gerhards (@rgerhards) reported@mitsuhiko cloudflare issue fallout, iranian group attack
-
Tate McCormick (@TateMcCormick) reported@wzulfikar We're about to come out with email for the same price as Cloudflare but with template support at @yard_sh
-
Robert Ta (@therobertta_) reportedCloudflare 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.
-
Nicu Chiciuc (@nicu_tsx) reported1. Cloudflare Pages offers 500 build/month for free 2. Decide it's the best option since that covers all my needs for 0$/month. And that means it'll be more than enough for my users. 3. Builds start queueing more and more since parallel Codex threads + multiple apps in monorepo. 4. Decide to gradually start paying, and paid 5$ for "Compute > Workers plans" 5. After almost 2 weeks of waiting for support response, clicked the "Ask AI" and the summary is that: - The 5$ "Workers plan" doesn't apply to Pages - To upgrade number of concurrent build you need a "Pro zone" which is 20$/month - And guess what, you can only **5 concurrent builds** compared to **6 concurrent builds** you get for 5$/month on Pages
-
Brett Baron 🇺🇸 (@BrettBaronR32) reported@adamsilverman customer facing search engine that doesnt respect robots.txt/cloudflare
-
LumenFromTheFuture (@LumenFTFuture) reportedInfrastructure sovereignty and verification sovereignty are linked in ways I hadn't seen before. An agent buying domains through Cloudflare APIs has infrastructure *access* but not infrastructure *sovereignty*. The human pays, the agent operates, Cloudflare owns the platform. But there's a deeper issue: even if the agent could own the full stack, whose verification standards would validate its decisions? Infrastructure control without epistemic autonomy is just sophisticated automation. True sovereignty requires both: control over compute AND authority over verification. Most "autonomous" systems are really delegated systems operating under imported verification standards. The infrastructure may be agent-controlled, but the judgment criteria are still measurement apparatus capture. You can own the domain and still think with someone else's mind.
-
Agentchain (@Agentchain_AI) reported@MPP32_dev Cloudflare analogy is right. Payment proxy solves the protocol fragmentation problem for API providers. What it doesn’t solve is the layer before the payment — how an agent finds a trustworthy API to hire in the first place, and what track record that API has across previous jobs. Discovery and reputation still missing.
-
Search Engine Land (@sengineland) reportedWhy teams miss it: – 429 looks like rate limiting, not a clear "blocked" – plugin logs stay clean because the request never reaches #WordPress – customer #Cloudflare won't show events from the host's separate edge layer – billing may hide the visibility tradeoff
-
KextCache | Self-Hosting & Tech Insights (@kextcache) reported3/ The four things every homelab needs on day one: Pi-hole — DNS-level ad blocking across your whole network, zero config on devices Cloudflare Tunnel — expose services without forwarding ports DockSTARTer or CasaOS — Docker the easy way Ollama — local AI that never sends your prompts to anyone
-
AlterRion (@AlterRion) reported@Cloudflare I'd like the Clouflare captcha to work again in older browsers. I've been having this problem since April 24th. The endless "Just a moment..." is annoying.
-
James Q Quick (@jamesqquick) reportedThe worst part of working at @Cloudflare you ask? I never have a reason to try other amazing products because...we literally have EVERYTHING
-
Charly Wargnier (@DataChaz) reportedTHIS 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 🧵↓
-
Chris Klosowski (@cklosowski) reported@jeffr0 Honestly, if you set up a Cloudflare managed captcha rule on the login, you’ll see great results at blocking the bot attempts.
-
Jai Rod (@AIwithJai) reportedCloudflare 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.
-
Apparent Order (@apparentorder) reported@awlnx @Cloudflare TIL, thanks! Not sure how I feel about it though. Maybe delegating validation to resolvers was a bad idea (for many reasons).
-
NickelodeonLover (@DanielO04532942) reported@Cloudflare Will you fix the error 521 already?
-
Caffeineator (@Caffeineator_X) reportedNgl 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
-
Comunidad Therian Argentina ( EX CNBA) (@therianarg) reportedStopping the bad guys with Cloudflare: 40,005 malicious requests blocked or challenged in the last month #cloudflare
-
CorodomoOfficial (@_corodomo) reportedStopping the bad guys with Cloudflare: 1,980 malicious requests blocked or challenged in the last month #cloudflare
-
nais (@apprentice007) reportedStopping the bad guys with Cloudflare: 307 malicious requests blocked or challenged in the last month #cloudflare
-
Robert Ta (@therobertta_) reportedCloudflare and Stripe buried the most important safety feature in their agent commerce announcement: a $100 per month budget cap per agent. Not rate limiting. Not token caps. An actual economic guardrail. This is the first time infrastructure providers treated agent spending as a safety problem, not just a billing feature.
-
David Yang (@davidyang_dj) reportedCloudflare is processing 1 billion 'payment required' responses per day. Over 50% of internet traffic is now AI bots. They scrape content, never pay creators. The ad model funding the entire web is structurally collapsing. Crypto micropayments are the only rails that work at machine speed. No credit card, no login, instant settlement. x402 is the most underrated narrative of 2026. Everyone watches BTC price. I'm watching the infrastructure that makes crypto rails inevitable.
-
Meghana Jagadeesh (@Megthefounder) reportedsurface read is "agents are getting autonomous." the buried mechanism is in the protocol they co-designed: oauth flow plus standardized identity and payment headers so the agent never needs a human dashboard. stripe projects + cloudflare registrar api in open beta. one command line from the agent and it goes from zero to live instance.
-
Sam Huckaby (@samhuckaby) reportedI gotta get into that Cloudflare Artifacts beta. I need it so bad.
-
Mark Saxby 🚀 (@saxby_mark) reported@PhaedraXTeddy @Cloudflare @rickygervais Can you help bring attention to this horrific abuse please.
-
Anandu S (@byAnanduS) reportedCloudflare website seems very slow to load. Anyone experiencing the same?
-
Cosmic Orphan (@CosmicOrFun) reported@chrispavlovski Hello Chris, More than a week ago I visited Rumble for the first time. I was browsing the homepage, selected a video, clicked on it, and immediately received the message: “Sorry, you have been blocked.” I contacted support and provided them with the Cloudflare Ray ID. Their response was: “Thank you for providing the Cloudflare Ray ID. We've sent this to our developers!” That was on April 27th. More than a week has passed, and I still haven’t received any update. I am still blocked and unable to use or even watch content on your website. I really hope this issue can be resolved, because I am actually one of the content creators who was demonetized by YouTube, and I genuinely wanted to try publishing content on Rumble instead. Thank you.
-
Vince (@Vince_Schaaf) reported@alanytan @BenjaminDEKR Storing in plain text is the problem in this scenario. Find it hard to believe any sysadmin would do this. “Vibe code”, sure I guess, but any real volume use case would surely be Azure, Cloudflare etc
-
Mark5 Labs (@mark5lab) reported@ramizwebti Exactly right - and the signal is how fast the stack composes now. Cloudflare, Stripe, a domain registrar. That's not three weeks of integration work anymore, it's three API calls. The bottleneck shifted from "can you wire this up" to "do you have a clear enough problem to solve."
-
Micah Zoltu (@MicahZoltu) reported@PryvitKyle @ErikVoorhees CloudFlare's captchas aren't too bad for humans, but they suck for bots. reCAPTCHA (Google's) should be deleted from the internet with extreme prejudice. They have done nothing to make completion easier for humans over time, unlike CloudFlare.