1. Home
  2. Companies
  3. Cloudflare
Cloudflare

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.

  • 40% Domains (40%)
  • 27% Cloud Services (27%)
  • 13% Web Tools (13%)
  • 13% Hosting (13%)
  • 7% E-mail (7%)

Live Outage Map

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

CityProblem TypeReport Time
Manchester Domains 17 days ago
Angers Cloud Services 28 days ago
London Domains 1 month ago
Noida Hosting 1 month ago
Jewar E-mail 1 month ago
Braga Web Tools 1 month 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:

  • GlenWilsonIA
    Glen Wilson (@GlenWilsonIA) reported

    @bijucyborg @BraydenWilmoth That doesn't change anything. Rapidly deployment and taking down of websites is what phishing scams thrive on. Nomrally they rely on making local webservers on infected computers. Using stolen identities to use cloudflare would be so much easier and less hassle for scammers.

  • Godsbaby2025
    God’s baby (@Godsbaby2025) reported

    Anthropic’s Claude bot crawls ~2,800 web pages for every 1 visit it sends back to the site, according to Cloudflare data (July 1-7). That’s the worst ratio among major AI companies. It’s actually improved a lot — was ~8,800:1 in early April, and spiked to a wild 24,700:1 in the first week of May. Anthropic pushed back, saying it can’t verify Cloudflare’s math and that its new search feature is driving more referral traffic to sites.

  • realphenolmenal
    Ackerman (@realphenolmenal) reported

    Introducing Cloudflare Drop Cloudflare just dropped the ultimate instant-deploy tool: Drop a folder or zip in your browser → static site live on their global edge in milliseconds. No account. No login. No friction. 60-minute temp preview or claim it forever. Built perfectly for the AI/agent era — agents spit out sites, Drop ships them instantly. Ca below

  • vijaytupakula
    Vijay Tupakula (@vijaytupakula) reported

    🚨 Breaking News!!🚨 Larasend now sends through @Cloudflare Email Service The email provider everyone's hyped about, inside a free self hosted transactional email platform. one API token. No DNS copying. No mail server. Pick SES or Cloudflare per project... Yep!! PER PROJECT Setup 🧵👇

  • Opp_Knox
    Sean Knox (@Opp_Knox) reported

    @wholemars @levelsio @Cloudflare What is bad about it sendgrid?

  • WayneShirreffs
    Wayne Shirreffs (@WayneShirreffs) reported

    @pau11960 @pranavsf @Cloudflare Stablecoins don’t move 3% a day wtf are you even talking about? Stablecoins are stable dollar equivalents. Same as excepting dollars except don’t have to grease the middle man 3% of every transaction.

  • jerieljan
    _jerieljan/ (@jerieljan) reported

    @stupidtechtakes I'm surprised at the amount of people disagreeing. Naysayers think Cloudflare of all companies, the company that literally fights network abuse and bots all the time and runs a captcha service is unable to protect their own service from it?

  • ryanyates1990
    Ryan (Struggling with life NGL) (@ryanyates1990) reported

    Really fed up with #Hugo now & hosting my blogs on #Cloudflare as things have broken that should not have done. So yet again I'm going to be rebuilding my blog and working out where I'm gonna be hosting it. Something that really I did not want to be having to spend time on tbh

  • funfa1rr
    Russ / Funfair 🎪 • TEAM POWER 💪 • DR SPOILERS (@funfa1rr) reported

    —was also useless. probably cuz i'm using the free ones from google and cloudflare but they do still kinda work in some scenarios - other games that require internet connection work perfectly fine. the issue is *specifically* with splatoon 3 - i've seen other people having—

  • Luwangacx
    Christopher (@Luwangacx) reported

    @Cloudflare @Newsweek @StatistaCharts In my experience cloudflare slows down the internet and makes the internet experience worse on average. Might be my own skills issue but that’s so far been my experience

  • FireFlyGG
    FireFly (@FireFlyGG) reported

    Cloudflare can make AI agents pay per request. Monetization Gateway lets sites bill AI agents for every fetch. > page > API > dataset > MCP tool Payments use protocol x402, based on the nearly forgotten HTTP 402 Payment Required. The agent receives an invoice, pays in stablecoins, and gets access instantly. All inside a normal HTTP request, no registration or payment pages. Cloudflare says one real user generates thousands of AI requests. This is an evolution of last year Pay Per Crawl, now able to force payment from practically any AI service, not just crawlers.

  • DerekAshauer
    Derek Ashauer (@DerekAshauer) reported

    Moving all my client sites to a new host! Been putting this off for two years. Claude + VS Code (desktop couldn't do the API connections I needed) finally made it doable instead of an admin nightmare. Instead of manually chasing down info on 50+ sites, I had Claude connect to APIs and do the grunt work. Claude connected to my hosting account API and pulled the list of domains. Then it used the Freshbooks API (my client billing/invoicing tool) to grab client contact info. Matched them together magically since I don't have direct domain <> client data. Then it did DNS lookups to figure out where each domain is registered. All the pattern-matching work that would've taken me hours. Many of my clients have been with me for 10+ years. I have long since lost their domain logins or 2FA now prevents me from getting in, so... Claude drafted custom emails directly in Gmail for every client I didn't already have delegate access. Each one has the exact instructions for their specific domain registrar on how to invite me to have access. Now, I'm just handling the email conversations. As they respond, the master list Claude and I are compiling gets updated. I might even try letting Claude fully respond in Gmail too and update this list automatically as the conversations happen - we'll see. Claude also connected to the Cloudflare API to set up DNS records to get as many domains into a central DNS management account. Once all setup, the migrations to the new host should be pretty straightforward from here thanks to the awesome new host having done this many times before and have automated processes to do it. I will have to manually change the DNS for most of them though (but not a bad thing because of how important that is) - but once I have access to all doing so should be quick. This migration would've taken me weeks to do manually and why I avoided it for nearly 2 years since I first started considering it. I'm doing this as I dwindle down my clients to the simple, easy to manage ones - I will be saving nearly $3k/year in base hosting costs. More importantly, I have plans around products that the new host will be great at helping me get off the ground - more on that later once this first phase is complete! All this running in the background while I am still working on products.

  • danielrmay
    Daniel May (@danielrmay) reported

    @sheherenow_ Comes down to whether you're outsourcing the implementation or the understanding. When Claude suggests moving parts of my app into Cloudflare Durable Objects it usually has a cost implication, so I pay attention

  • wholemars
    Whole Mars Catalog (@wholemars) reported

    @levelsio @Cloudflare Twilio has an SMTP service

  • the_smart_ape
    The Smart Ape 🔥 (@the_smart_ape) reported

    @Eli5defi @Cloudflare good thing is cloudflare already sits in front of 20% of the web. protocol adoption problem solved by default. distribution wins again

  • justbuilding
    JB (@justbuilding) reported

    @levelsio @Cloudflare Cloudflare is probably the greatest service I use. I almost feel guilty being on the free tiers.

  • ivyfinances
    Ivy Finance🌍 (@ivyfinances) reported

    @williililii @pranavsf @Cloudflare That **** fonished last year

  • alongubkin
    Alon Gubkin (@alongubkin) reported

    It's insane how hyped Cloudflare Workers is on X. But it's a completely broken platform. The first version of @alien was based on CF Workers. We built natively for it. But even if things worked perfectly locally, they were *always* broken in production because of some CF Workers runtime bug. We migrated to Vercel and EKS Auto in a weekend and everything became so much faster and more stable. Don't believe the hype. Oh, and all their example projects are just totally broken

  • mertmetindev
    Mert Metin Tekdemir (@mertmetindev) reported

    📂 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

  • Dayhaysoos
    Nick DeJesus 🛒🎉 - Former Unpaid CTO @BTPipeline (@Dayhaysoos) reported

    @techgirl1908 whooaaa, well this can't be fixed tbh because I built my gif creator based off a website that doesn't exist anymore (the company shut down). The plan is more or less to keep it 1:1 as far as feature parity but it'll be completely built on Cloudflare. if this goes well I have upgrade ideas !

  • clawdb0t
    Ali Hasnain (@clawdb0t) reported

    @gabor_rar @DanKornas running hermes too and this is exactly the bottleneck. even when a service has an api, the onboarding routes through cloudflare + email verify + captcha before you get keys. agent-native billing helps but we need agent-native identity first — something like oauth device flow for automated api key provisioning.

  • LexSokolin
    Lex Sokolin | Generative Ventures (@LexSokolin) reported

    @Cloudflare is trying to make HTTP 402 useful. The web has always had a “Payment Required” status code. It mostly sat there as internet archaeology because humans do not want to stop every six seconds and pay four cents for a page, dataset, or API response. Agents are different. An agent can request a resource, receive a machine-readable price, pay in a stablecoin, attach proof, and move on. No checkout page. No subscription bundle. No ad unit. No “contact sales.” Aka a novel way of internet monetization. Cloudflare is approaching this from the edge: sit in front of the resource and enforce payment before access. Mastercard is approaching the same problem from trust and credentials: give machines spending rules, limits, authorization, and settlement. Same direction from opposite ends. The useful version is not an AI assistant buying sneakers. That is demo theater. The useful version is software paying for software: - data - APIs - model calls - verification - routing - compute - tools This is where stablecoins stop being a crypto slogan and start behaving like small-denomination internet money. The web does not need every machine to have a bank account. It needs a way for software to pay a toll and keep moving.

  • alex_prompter
    Alex Prompter (@alex_prompter) reported

    Cloudflare opened a waitlist that lets you charge AI agents every time they touch your API, your dataset, or your content. The tool is called the Monetization Gateway, and the waitlist opened on July 1. Any web page, dataset, API, or MCP tool sitting behind Cloudflare can carry a price. Cloudflare checks for payment at the edge when an AI agent requests one, before the request reaches your server. Payment runs through x402, an open protocol built on a part of HTTP that's sat unused for about three decades. The server answers a request with a price instead of the resource. The agent pays in stablecoins and sends the same request again with proof attached. Prices can run down to fractions of a cent, since payment adds almost no overhead to the request. There's no checkout page, no account, and no API key required. This isn't Cloudflare's first swing at this. Pay Per Crawl already let site owners charge crawlers for scraping their content. The Monetization Gateway extends the same idea to any caller and any resource, not only crawlers. AWS added a similar payment layer to CloudFront a few weeks earlier, so this is turning into a race between the two biggest edge networks, not a one-off experiment. Charging an agent per request only works if the agent's owner lets it pay instead of finding a way around the paywall. Cloudflare can enforce the toll at the edge. It can't force an AI company to route its agents through the paid path instead of the free one. If you run an API, a dataset, or a paid tool, this is worth watching instead of dismissing as another crypto payment gimmick. The waitlist is open. Will AI labs let their agents pay the toll, or keep finding ways around it?

  • alphaticaio
    Alphatica (@alphaticaio) reported

    LARGE / MID-CAP TAPE | July 8, 2026 Large / mid-cap blocks. +$214M net buy. Flipped. Yesterday: -$726M. $AKAM +$88M zero sells. $NET +$65M. $CRWV +$62M. Yesterday's sellers became today's buyers. Q3 week two. $1.61B in buy blocks. $1.39B in sells. Net: +$214M. 2,437 prints. Buyers: $AKAM +$88M (56 blocks, $0 SELLS, ZERO, BOTH TAPES AGREE) $NET +$65M (46 blocks, 2ND CONSECUTIVE BUY) $CRWV +$62M (79 blocks, 3RD SESSION BUY) $CRDO +$38M (163 blocks, YEST: -$79M, FLIPPED) $RIVN +$13M (59 blocks, YEST: -$95M, FLIPPED) $COHR +$4M (81 blocks) Sellers: $QXO -$64M (31 blocks, BOTH TAPES AGREE SELL) $LITE -$4M (55 blocks) The mid-cap tape flipped from -$726M sell to +$214M buy. Same reversal as the mega-cap tape (+$13.37B). The institutions bought the sell day across both universes. $AKAM: +$88M. Zero sell blocks. Both tapes agree buy. Yesterday $AKAM was a dark pool seller at -$26M. Today: zero sells on the lit tape, +$33M in the dark pool. The reversal is complete. $CRDO: -$79M yesterday, +$38M today. $RIVN: -$95M yesterday, +$13M today. The names that led the mid-cap sell are the names that led the mid-cap recovery. The first cross-session reversal signal the mid-cap panel has produced. Three days old and already showing reversal patterns. $NET: +$65M. Second consecutive buy session. Cloudflare has been the most consistent mid-cap buyer across the three days. The mid-cap panel mirrors the mega-cap panel. Both flipped. Both bought the sell. The data is consistent across universes. Watching the tape.

  • iamsourabhshen
    Sourabh (@iamsourabhshen) reported

    @levelsio @Cloudflare Are you going to build an email sending service now?

  • nepaligunner_77
    Somenet (@nepaligunner_77) reported

    @vijaytupakula @Cloudflare Is this support for marketing email?

  • Okwachjamal
    Jamal Shamir (@Okwachjamal) reported

    @vijaytupakula @Cloudflare You gonna add support for zeptomail

  • alan_t_wootton
    Alan Tracey Wootton (@alan_t_wootton) reported

    What's interesting is that the request to get the Duck goes from your browser, up to cloudflare, then down to my laptop (which is always running), back to cloudflare and then down to your browser.

  • defido
    defido 👊⛽️ (@defido) reported

    @KayhanB21 @Cloudflare Their entire workers AI suite is down or not working properly

  • pranjal_3029
    Pranjal (@pranjal_3029) reported

    @Kenu73 Moreover, it can help(sometimes, not always) unblock some ISP-blocked websites and offers better privacy than using 1.1.1.1(Cloudflare)/8.8.8.8(Google)