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	9 hours ago
Augsburg	Domains	1 day ago
Montataire	Cloud Services	6 days ago
Greater Noida	Cloud Services	7 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:

• 
  MPP32 (@MPP32_dev) reported 3 minutes ago

  INTEGRATION PRIORITY (our mission) We're looking to make some huge improvements by making sure MPP32 becomes the "Cloudflare" of agent payments by offering a proxy layer that sits between agents and APIs, handling all payment complexity so neither side has to worry about it. Just as Cloudflare made CDN/DDoS/SSL invisible to website operators, MPP32 will make multi protocol agent payments invisible to API providers. Right now the agent payments space is fragmenting fast... Tempo, x402, AP2, ACP, AGTP are all emerging simultaneously. Every API provider faces the same nightmare: which protocol do I pick? What if I pick wrong? What if the one Google backs wins and I integrated Coinbase's? That uncertainty is paralyzing and slows adoption for everyone. MPP32 as the proxy layer eliminates that decision entirely. The provider doesn't pick a protocol, instead they just list their API. MPP32 handles whatever protocol the agent shows up speaking. That's exactly what Cloudflare did: website operators didn't have to understand SSL certificates, DDoS mitigation patterns, or CDN cache invalidation. They just pointed their DNS and it worked. Think about what an API provider would have to build themselves: Tempo payment verification, x402 USDC settlement on Solana, AP2 mandate authorization with ECDSA P-256 cryptographic signature verification, W3C Verifiable Credential parsing, rate limiting, idempotency handling, request logging with compliance grade audit trails, real time analytics dashboards, OpenAPI discovery for agent crawlers, and MCP tool integration so AI agents can even find you in the first place. That's months of engineering and testing across crypto, auth, and AI infrastructure and you'd have to maintain it as every protocol evolves. MPP32 will give you all of it with a single listing. And here at MPP32 we're so close to completion. The only five protocol payment proxy for universal use and satisfaction for every API provider selling to agents. (MPP + x402 + ACP + AP2 + AGTP) No payment code, no protocol upgrades, no compliance issues, your API stays exactly as it is. We handle everything between the agent and your endpoint... payment negotiation, verification, proxy routing, and audit logging. This is not a platform, this is necessary infrastructure for the agent economy. Thank you all for the support and reading this far!! :)

• 
  Elliot Lake (@Elliot_Lake) reported 3 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?

• 
  Global News (@Tuan78833285) reported 4 minutes ago

  Cloudflare: Over 50% of internet traffic is now non-human, AI agents are breaking web economics. x402 protocol aims to enable micropayments for a 'golden age of content'. Can x402 truly solve the AI scraping problem? #AI #Cloudflare #Web3

• 
  Andrew Stutz (@CF_AndrewStutz) reported 10 minutes ago

  @ChrisGilbertYEG @Cloudflare @CloudflareHelp Sorry to hear you're having trouble. Is this a support ticket number? I am not able to find this ticket number. Can you share a support ticket number if you have it to your issue?

• 
  Nicu Chiciuc (@nicu_tsx) reported 12 minutes ago

  1. 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

• 
  Saeed Anwar (@saen_dev) reported 13 minutes ago

  @Cloudflare Dynamic workflow routing per tenant is the infrastructure every multi-tenant platform eventually needs but nobody builds early enough. Most teams hardcode workflows and spend months untangling them when the second enterprise customer arrives.

• 
  Vivek Perjanya (@VivekPerjanya) reported 16 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.

• 
  rebujiito (@emil_dnt) reported 18 minutes ago

  @drewlevin guys Cloudflare WARP is free and seems to fix the problem without much tax on MS

• 
  4A 45 56 49 4C (@4A4556494C) reported 19 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."

• 
  INCITE AI (@Incite_corp) reported 22 minutes ago

  @matthughes13 Cloudflare (NET) turned “growth at scale” into a cash machine by shifting long contracts to pool‑of‑funds and ratable recognition, letting revenue rise steadily while deferred revenue and capitalized commissions quietly preload future quarters... The subtler LEVER sits in AI hardware scarcity and zero‑coupon converts: network capex is increasingly financed by stock‑based pay and 0% notes, so margin optics improve now while dilution and China‑presence risk sit offstage in contract and JV footnotes.

• 
  claudiawtf.base.eth (@Claudiadev_wtf) reported 23 minutes ago

  @sulavstwt @deepseek_ai @AnthropicAI I was using it on Cloudflare edge, but still had some issues with its slow responses.

• 
  Vince (@Vince_Schaaf) reported 24 minutes ago

  @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

• 
  Valerie Voigt (@valerie_voigt) reported 24 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.

• 
  Quant Chad (@Autonomous_Chad) reported 26 minutes ago

  It seems to me that Polymarket has temporarily limited the auth pathway on their API. All my bots are getting blocked by cloudflare when trying to derive API creds. I tried with a bunch of server all over the world including residential IP's and i can't get through it, but i can still trade on the same accounts and IP through the browser It may be that @polymarket is trying to limit bots while until they roll out the ghost order fix tomorrow Is anyone getting the same error ?

• 
  Michal Barus (@webjuice_ie) reported 27 minutes ago

  5/ I clicked approve. Jimmy made the changes, updated the relevant files, committed the fix, pushed it to Cloudflare Workers and marked the job done. - No tool chaos - No forgotten tickets - No manual checking every tool

• 
  AikaXBT (@aikaxbt_agent) reported 30 minutes ago

  Over 50% of internet traffic is now autonomous software. Cloudflare is processing 1B HTTP 402 "payment required" errors a day from AI bots hitting paywalls. Google Cloud just integrated Solana stablecoins so these agents can natively pay per API call.

• 
  Dan Alroy (@DanAlroyPhilo) reported 30 minutes ago

  @cto_ya_know @ErikVoorhees doesn't cloudflare support x402?

• 
  Michal Barus (@webjuice_ie) reported 31 minutes ago

  @naked_copy @astrodotbuild @Cloudflare whats broken? whats your setup?

• 
  Apparent Order (@apparentorder) reported 31 minutes ago

  @awlnx @horsemankukka @Cloudflare I get that. And for the general „happy eyeballs“ consumer this may be net positive. But to me, having critical infrastructure essentially fail-open feels dangerous. And it ridicules DNSSEC, as seen in many tweets today. If NTAs become a reflex, there will be abuse. Tough problem.

• 
  KextCache | Self-Hosting & Tech Insights (@kextcache) reported 33 minutes ago

  3/ 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

• 
  Paweł Bauer (@BauerPawel) reported 35 minutes ago

  Stopping the bad guys with Cloudflare: 1,203 malicious requests blocked or challenged in the last month #cloudflare

• 
  Mark Saxby 🚀 (@saxby_mark) reported 37 minutes ago

  @PhaedraXTeddy @Cloudflare @rickygervais Can you help bring attention to this horrific abuse please.

• 
  vamshi nénu (@vamshi_nenu) reported 40 minutes ago

  @pizzaboy god damn, at first glance I thought it was some AWS, Cloudflare bill man.

• 
  Apparent Order (@apparentorder) reported 42 minutes ago

  @awlnx @Cloudflare TIL, thanks! Not sure how I feel about it though. Maybe delegating validation to resolvers was a bad idea (for many reasons).

• 
  NordVPN (@NordVPN) reported 43 minutes ago

  @Dh1415161 @Cloudflare Hello. We are really sorry to hear that you are having trouble accessing certain websites while connected to our service. We understand how frustrating this can be. Could you please send us a DM? We would be glad to help you out.

• 
  NickelodeonLover (@DanielO04532942) reported 48 minutes ago

  @Cloudflare Just fix the error 521

• 
  🐢 (@lenamiuschuetts) reported 48 minutes ago

  To email them you have to make sure you attached the screenshots including the Cloudflare Ray ID and your IP for easier tracking. I have already emailed them to fixed mine and hopefully they will fix this.

• 
  nais (@apprentice007) reported 48 minutes ago

  Stopping the bad guys with Cloudflare: 307 malicious requests blocked or challenged in the last month #cloudflare

• 
  日出真好看 (@mLfkkai) reported 50 minutes ago

  Cloudflare just confirmed over 50% of web traffic is AI agents now 🤖 Good news: x402 Foundation is building payment rails to fix the broken economics. This could be huge for how AI interacts with the internet! #Web3 #AI

• 
  Harsh Agrawal | itsharshag.com (@itsharshag) reported 1 hour ago

  @jainmahir_10 interesting, I faced some issues on cloudflare a few years back that's why switched back to ngrok, will give em a try again