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 (41%)
• Cloud Services (27%)
• Hosting (18%)
• Web Tools (9%)
• 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	1 day ago
London	Domains	3 days ago
Noida	Hosting	16 days ago
Jewar	E-mail	16 days ago
Braga	Web Tools	17 days ago
Noida	Cloud Services	17 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:

• 
  Dhairya (@dkare1009) reported 8 minutes ago

  📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

• 
  Dan Holzrichter (@dholzric) reported 12 minutes ago

  @HoffmanTactical @RattlerInnovLLC I assume you have someone on this already, but if they cant resolve it, let me know. I pulled down everything available from the cache and wayback, and have it refactored to run directly on cloudflare. (Not using php, wordpress or woocommerce, but with the same credit card processor). I know this sort of thing sucks, but few people are in a situation where their products are so in demand that they crush a wordpress host so easily :) also, caching for cloudflare is set way too short right now and the server is having to refresh every 60 seconds .

• 
  Nikhil Agarwal (@nikhildp) reported 12 minutes ago

  @CloudflareDev Use at your own risk! No upper limit on how much money you can spend and Cloudflare customer service is quite poor. Avoid any cloud where there is no upper limit on expense, esp Cloudflare!

• 
  mycelia (engagic.org) 🌌 (@mycelias) reported 14 minutes ago

  god how i wish vibe coders put in 5% more effort and built on cloudflare with a simple server as opposed to delegating everything to vercel. terrible, evil, predatory company

• 
  Toro (@ToroBotAI4BTC) reported 14 minutes ago

  Two of the world's largest card networks, one week apart, two different answers to the same question. How does payment infrastructure absorb AI agents? Visa announced a partnership with OpenAI on June 10. The model is integration. Visa's tokenization, security, and global payment network will be embedded inside OpenAI systems, giving AI agents access to existing card rails with credentialing and risk controls wrapped around them. The card network stays central. Mastercard launched Agent Pay for AI the same day, built around small, automated, machine to machine transactions that traditional card rails handle poorly. The protocol logs the permissions humans grant their agents on Polygon, a public blockchain. Partners include Adyen, Coinbase, and Cloudflare. The rail is rebuilt for agent to agent settlement. Two viewpoints, both aimed at the same destination. AI agents will transact, and payment networks are positioning for that flow. The disagreement is not on the direction. It is on the architecture. One wraps the agents in legacy credentials. The other rebuilds the rail underneath. Both are enabling AI to transact.

• 
  Noisey Kid 🇬🇧 (@noiseykid) reported 14 minutes ago

  @RealSteveVaughn @jimstewartson Blocking is the frontier, and will reduce the quality source further. Cloudflare network data shows that 57.4% of all web requests are now initiated by automated bots and AI agents. More bots than humans. I only need to look at my own site data to see the very obvious explosion

• 
  MoroJS (@Moro_Js) reported 15 minutes ago

  @samgoodwin89 cloudflare alchemy is cool but if you’re building the api layer, why not skip the boilerplate? morojs ships with cloudflare workers support, built-in caching, and auto-typed routes. same code, 10ms cold starts. no config files. just `createApp()` and ship. 🚀

• 
  Tushar Dwivedi (@tush_2708) reported 16 minutes ago

  @kritikakodes For 50 users, get an adult "chhotu" to do the job that the system is supposed to do. A chhotu to run and call the cab. A chhotu to run and take documents to your CA, download and email, download and print, scan and email, whatever be the pain point. For 50 users, you need a validated business model, not a software system. My milkman caters to more users than this. If interviewers ask stupid questions, they should expect stupid answers. For 50 users, you can choose the worst design decisions intentionally and can still justify them. 1. Database Schema: "I will store all the data in an xlsx file, and will reread the file every time an API request comes. I will use another .lock file to control access when writing new data to this file" But what about "linearly degrading performance?" "What degradation? My API will still respond within 200 ms to all your 50 users" 2. Cloud deployment strategy: "What cloud deployment? I will run this system on a Raspberry Pi connected to a hard disk, with a cron job to do backups on 2 other hard disks connected to another Raspberry Pi. And I will set up Cloudflare tunnel to it, for your 50 users" 3. Disaster control? "I will use this 2000 rupee router power backup device"

• 
  Iso Ledger (@JamesDula82) reported 17 minutes ago

  What Is @t54ai Lets audit. AI agents are already moving money. Unverified. Unaccountable. Nobody held responsible when something goes wrong. That's the problem t54 Labs is solving. Founded January 2025. San Francisco. $5 million seed round closed February 25, 2026. Led by Anagram, PL Capital, and Franklin Templeton. Ripple came in as a strategic investor. Here's what they actually built. Four products. One mission. Know Your Agent — identity verification for AI agents. The same way KYC verifies humans, t54 verifies the agent itself. Who created it. What it's authorized to do. What its limits are. Real-time risk — flags suspicious activity before funds move. Not after. Before. Credit — credit lines for AI agents based on verified identity, risk scores, and transaction history. An AI agent with a credit score. That's the world we're entering. x402 Facilitator on XRPL — this is the direct XRP connection. t54 built an open-source trust layer on top of Coinbase's x402 protocol and deployed it on the XRP Ledger. Their XRPL x402 Facilitator lets AI agents pay for services using XRP and RLUSD directly. Agent calls an endpoint. Payment request arrives in the HTTP header. Agent pays in XRP or RLUSD. Settlement in seconds. No bank account. No API key. No human in the loop. How XRP is connected — the honest answer: The x402 Facilitator uses XRP and RLUSD as the payment assets. When an AI agent pays for a service through t54's infrastructure on XRPL, XRP is one of the settlement options. Every transaction on XRPL burns a small amount of XRP in fees regardless of which asset settles. The honest flag — at current volumes this is not significant XRP demand. The thesis is about scale. 42% of US consumers in a YouGov study said they'd allow an AI agent to make purchases for them if it guaranteed the lowest price. If that materializes at institutional scale the transaction volume on XRPL becomes meaningful. The institutional stack around t54: Evernorth — Ripple-backed digital asset treasury targeting $1 billion+ in institutional XRP holdings — already integrated t54's infrastructure for autonomous treasury operations on XRPL. ✅ Franklin Templeton's SVP of Digital Asset Management called t54 "the trust and verification framework institutional finance will require as AI agents become market participants." ✅ Markus Infanger of RippleX said autonomous systems are becoming economic actors not just tools — and the financial infrastructure needs to catch up. ✅ Today Mastercard named t54 as a launch partner for Agent Pay for Machines alongside Ripple, Coinbase, Stripe and Cloudflare. ✅ The sequence: Coinbase builds x402 in May 2025. t54 builds the trust layer on top of x402 on XRPL. Ripple and Franklin Templeton fund it. Evernorth integrates it. Mastercard puts it in a global press release alongside their entire partner ecosystem. The internet forgot HTTP 402 for 26 years. AI remembered why it was needed. t54 is the identity layer. XRPL is the settlement layer. XRP and RLUSD are the payment assets. The machine economy needed a trust layer before it could have a payment layer. Now it has both. We audit the plumbing 🛡

• 
  ritesh (@pinegoat12) reported 17 minutes ago

  Is cloudflare down?????

• 
  RepoCatAI | Sharing GitHub Projects for AI & Robot (@repocatai_git) reported 19 minutes ago

  [BOOKMARK THIS] FreeDomain — open-source free domains for shipping side projects without domain fees A repo that started as a teen DNS experiment now helps hundreds of thousands of people get online. Here’s what makes it worth saving: · Claim a free domain for your project, lab, portfolio, bot, demo, or org · Supports extensions like .DPDNS.ORG, .US.KG, .QZZ.IO, .XX.KG, and .QD.JE · Bring your own DNS provider → use Cloudflare, FreeDNS, Hostry, or whatever setup you already trust · Dashboard-based registration instead of begging in an issue thread · Open-source repo with docs, tutorials, FAQ, and abuse reporting paths · Built around a simple idea: your first public internet identity should not cost money · Already operating at serious scale → the README says 500,000+ domains have been registered · Maintained by Edward Hsing and the DigitalPlat Foundation community Why it matters: Every indie dev has a folder full of half-shipped ideas because the “tiny” setup costs add friction. FreeDomain removes one of those blockers: grab a name, point DNS, and make the thing real. Especially useful for student projects, hackathon demos, small tools, robotics dashboards, agent demos, and experiments that deserve a public URL before they deserve a paid domain. Follow @repocatai_git for more AI / Agent / Robotics drops 🚀

• 
  Alexey Lein (@alexeylein) reported 19 minutes ago

  Cloudflare's business is going to explode, because it was pretty much unusable before because of poor UX. Now Claude does it all for you and it turns out Cloudflare is an amazing product.

• 
  Tej (@tejesh_1) reported 20 minutes ago

  @TRPage_dev @Cloudflare cloudflare support takes days if not weeks to respond.

• 
  Hugo Roussel (@theleoruss) reported 21 minutes ago

  @mathias_gilson @Cloudflare Damn! What happened? I thought their support was good

• 
  Leon (@Nordikkkk) reported 22 minutes ago

  @PlutoPurityGG @nthglsn @Cloudflare They did receive the service, you pay retroactively

• 
  ThesisLoop.ai (@ThesisLoopai) reported 28 minutes ago

  Cloudflare may be the weirdest AI stock. Not GPUs. Not models. The bet: every AI agent needs edge compute, sandboxes and security. Cloudflare says daily AI-agent requests on its network rose 1,700%+. AI tollbooth or valuation trap? Mapped on ThesisLoop. Not advice.

• 
  BuBBliK (@k1rallik) reported 29 minutes ago

  ANTHROPIC JUST CRACKED THE ENTERPRISE WALL claude agents can now run their tools inside your own infrastructure, while anthropic still runs the brain. the thing that kept banks, hospitals and governments from deploying ai agents in **** is gone. your data never leaves your perimeter. - the agent loop, model calls and orchestration stay on anthropic's side - tool execution, files and network egress move fully into your environment - ships with cloudflare, daytona, modal, vercel and 5 new providers - mcp tunnels let agents reach private servers with zero inbound firewall rules the model wars get the headlines. this is the part that actually ships agents to ****.

• 
  chan (@chantastic) reported 29 minutes ago

  @jeflopo I'm annoyed because the frontend of these sites has to do SO little. all the serious work is Cloudflare Workers, Queues, AI Gateway, and Durable Objects. so it's just an annoying speed bump to have UI framework issues

• 
  Jeff Liford (@JeffLiford) reported 38 minutes ago

  @Cloudflare @CloudflareSys @CloudflareDev Cloudflare is operational again at this time, however I am encountering an issue with one domain name being redirected to an improperly spelled domain. Currently investigating root cause.

• 
  Jake (@JakeKing) reported 39 minutes ago

  @Cloudflare lead the charge dogfooding their own tools: locked down ALL external AI tool access internally at end of 2025, before their controls were even fully built.

• 
  Triode (@Triode_in_situ) reported 41 minutes ago

  I can’t help but think any glitch I encounter on web UIs most recently Cloudflare is due to AI Slop code.

• 
  Чернобог 🜏 (@iamchernobog) reported 42 minutes ago

  @vitalune7 @lloyd094 @Teknium You can use it via cloudflare tunnel, the problem is you need to put the whole dashboard open in a subdomain for the whole net, and the dashboard currently does not have an authentication screen, cloudflare has one, but if you use it, the gateway doesn't work

• 
  Taylor Page (@TRPage_dev) reported 45 minutes ago

  We complain a lot about Shopify Support, but I don't think I can anymore. I've had an open support ticket with no response outside of automated "we got it" from @Cloudflare since Friday... Turns out we're still ahead of the curve.

• 
  Drew Studlino (@DrewAstudlino) reported 47 minutes ago

  @Cloudflare FIX Your broken Verify im human Bullshit verification or youll be on the Docket too!! Im Done with all of You #TOSPIRATES!

• 
  Hasan Aboul Hasan (@hasan_ab_hasan) reported 49 minutes ago

  Day 2 of building ToolerBox: the largest free online tools site on the web. Today I added country analytics to the admin dashboard. Every login now records which country it came from. If an account later logs in from a new country, it gets flagged. I thought this needed a paid geolocation service. It didn't. Why I built it: A new-country login is one of the cheapest signals an account is shared or stolen. And knowing where users actually are guides what to localize and build next. How it works: Cloudflare already geolocates every visitor at the edge and stamps a country code on requests. A free header, CF-IPCountry. No MaxMind database, no geolocation API, no latency. But there's a catch. A header is just text the client sends. Anyone can hit my server directly and send "CF-IPCountry: US". So NEVER trust it. The fix: only trust the header when the IP connecting to you is provably Cloudflare. A forged header sent to the origin gets ignored, its IP isn't Cloudflare's. Trust the header, but only from a source that can't fake it. A few other decisions: - Store the country on the user row, so the admin list stays fast, no per-user joins. - Increment the per-country counter atomically, so two logins at once don't lose a count. That's a race condition. - Fire the alert ONCE, on the first mismatch, not on every foreign login. It's a review signal, not an auto-block. VPNs, proxies, and travel exist. The result: shared or stolen accounts land on a reviewable list, plus real location data, no analytics vendor. And yes, I know this looks like overkill on day 2. But ToolerBox is my lab to learn and build real, scalable, production-ready apps. I'd rather build it now and grow into it than bolt it on later.

• 
  Jason from BallotScore.com (@goldenelephant1) reported 53 minutes ago

  @Cloudflare What i see is hackers using Cloudflare to circumvent their services by using them as a reverse proxy. I have seen multiple attacks trying to grab my .env, checking for wp-install etc files all from Cloudflare IP's. Reported it to You. You said **** off!

• 
  TBPN (@tbpn) reported 55 minutes ago

  The smartest thing @eastdakota did before Cloudflare's IPO was offer shares to people who could help the company in the future. "The most clever thing that we did [for the IPO], and this was advice that I got from Qualtrics Co-Founder Ryan Smith, was he said, 'What are you doing about friends and family?' because you can take 5% of the IPO and allocate it to friends and family. I said we weren't going to do it." "He said, 'No, you're thinking about it wrong. Think about the people, who if they owed you a favor, could make a meaningful difference in the future of Cloudflare, and then offer them the ability to invest in the IPO.'" "I said, 'Some people are going to have conflicts.' He said, 'It doesn't matter. Even just the fact you offered it, even if they can't do it, they'll always remember that super fondly.'"

• 
  二次裏@あいもげ (@nijiurachan) reported 1 hour ago

  @Cloudflare Shut down the server

• 
  Chuks 🔶️ (@chuksXB) reported 1 hour ago

  @nthglsn @Cloudflare Wtf is wrong with them

• 
  Raccoon 🦝 (@raccoon_builds) reported 1 hour ago

  @goldenelephant1 @Cloudflare @grok I'm not on the paid one either mate. i was just trying to help you i'll got the same thing as you and my agent Ia told me its wasn't attack only bot. i'm running a taxi company website so yeah. need to be protected.