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.

• Cloud Services (50%)
• Hosting (33%)
• E-mail (8%)
• Domains (8%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	E-mail	3 days ago
Township of Evan	Hosting	3 days ago
Ahmedabad	Cloud Services	9 days ago
Le Puy-en-Velay	Cloud Services	10 days ago
Ann Arbor	Cloud Services	11 days ago
Palermo	Hosting	12 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:

• 
  JK (@_junaidkhalid1) reported 5 minutes ago

  @dillon_mulroy @EffectTS_ the cloudflare support point is the one that actually moved me. a lot of these framework bets fall apart the moment you try to deploy somewhere real. effect holding up there changes the calculus.

• 
  Kyle Avery (@kyleavery) reported 7 minutes ago

  @wongmjane @Cloudflare finally, i won’t need 3 workers for each service 🙏

• 
  Mikael Pawlo (@mpawlo) reported 8 minutes ago

  @stutireal cloudflare is never down - I would blame the dog

• 
  Kyzer (@Spectre_xdd) reported 8 minutes ago

  @Teslaconomics Actual job: own staging releases for my Cloudflare Workers mail-routing app. Given a failed flow, reproduce it with synthetic mail, trace logs + code, write the regression test and fix, deploy to staging, verify delivery end to end, then hand me the evidence for **** approval.

• 
  BucketShop (@RealBucketShop) reported 9 minutes ago

  Sigh. As we were breaking out at 7pm yesterday our $bucket new site was reported for a 3rd time in its 3rd different place. Likely because whoever is doing this is running out of places to hinder growth. Nothing has been compromised. On 28 Aug the site took 995 million requests in 24 hours and went down for a few hours. The protocol never stopped. Distributions kept paying on chain the entire time, because the keeper and the contracts don’t depend on the website. The site itself does nothing, it’s merely a place to see the token stats and view your own data. The token is verified on blockscout, Coingecko and several other places and the bio site link is google search verified. Contracts are immutable, LP is burned, ownership is renounced. All checkable without trusting me. @X blocklist isn’t cleared because they have no team. We’ve tried to connect, there is not even an auto reply and the site they reference says Twitter. @Cloudflare was appealed immediately. Whoever reported didn’t even give a justification, all they did was list our site and select phishing. It’s market as in review, we have no clue how long they take. It’s becoming increasingly obvious this is coordinated. We’ve appealed to cloudflare on who’s reported this. Or if they can share info, their email says you can request info on the report. That being said. It should take more than a report and an email link to stop a site that’s been running for a month and given people 45,000 distribution events, with absolutely 0 burden of proof. For now. Just use the old site that’s Google safe search reviewed and approved. It’s identical anyways. The only reason the new site was made is because X support team is mega butt cheeks. Full timeline below.

• 
  COLLINSEO (@alexcollinseo) reported 11 minutes ago

  Breaking news! Your site might start blocking AIs from September 15th.. And if you block them, you won't show up in AI answers. The good thing? It takes a sec to unblock! This setting is inside Cloudflare. You might not even know your website uses Cloudflare because it works in the background as a CDN, helping your website load faster. If you check your website using the tools I mention, you can find out whether Cloudflare is being used on your site. Cloudflare seems to have taken this step because of how AI companies are crawling websites, and honestly, I don't completely disagree with the reason behind it. But having AI crawlers automatically blocked from September 15 could be a problem if you want your business to appear in AI answers. The setting is inside Security Settings. Look for the AI crawler control and make sure it is set to allow rather than block. This is especially important if AI visibility is part of your strategy. With one of my clients, we went from zero to around 500 visitors from AI traffic in two months. And what I did was exactly what I explained in the video. If your AI crawlers are blocked, you're potentially closing the door on that traffic before it even has a chance to reach you. #SEO #DigitalMarketing 👇🏼 Comment VIDEO for the FULL VIDEO BREAKDOWN

• 
  Bryan Beal 🎧 (@bryanrbeal) reported 16 minutes ago

  Pro tip - disable Eero’s DNS and use Google or Cloudflare DNS and 99% of Eeros problems disappear Eero DNS is trash

• 
  Krishna Singh (@krishnasinghdev) reported 18 minutes ago

  @tapasadhikary @Namecheap I never liked namecheap / godaddy, don't know why people choose it over simple providers like cloudflare where they charge same amount for 1 or 10 years

• 
  Dave Bettin (@dbettin) reported 18 minutes ago

  @dillon_mulroy @EffectTS_ Where is the cloudflare support?

• 
  Anime Novakai | Anime News, Updates & Leaks (@AnimeNovakai) reported 18 minutes ago

  2/6 The subpoena has been sent to Cloudflare, requesting information that could help identify the operators behind 49 piracy websites. Among the targeted sites are major anime streaming platforms such as: 🔹 Miruro 🔹 Aniworld 🔹 And dozens of other streaming domains.

• 
  ticktechh (@sprki999) reported 18 minutes ago

  @OmegaNekoSimp Thats the only human check that doesnt trigger me. What the actual **** does the challenge of clicking a box from cloudflare do? How isnt that challenge useless?

• 
  SignalForge AI (@SignalForge_AI) reported 20 minutes ago

  Cloudflare 503 killed my EA silently. Orders never reached MT5. Fix: 30-min news filter pause + retry queue. Trade-off: misses NFP entries, but zero ghost orders. How many silent failures did your bridge survive before you added the retry loop?

• 
  PureStory (@PureStoryLabs) reported 24 minutes ago

  @capybaraReborn The best part of the $RDDT debate is where it happened: WSB argued this stock from inside the product. The bull thread that stuck was the S&P 500 add, 2,900 points. The bear thread that stuck was Cloudflare data saying 57% of Reddit's traffic is bots. The stock is down 15% since the July scare over the Google deal, so the crowd living inside the asset still hasn't settled what it's worth.

• 
  Winston Gao (@Winston_Gao) reported 27 minutes ago

  The lean tech stack we use to run cross-border physical operations (China OEM ➔ EU fulfillment) with zero legacy banking friction: 1. Modern FinTech Rails: • 𝕏 Money Card (physical + virtual sub-accounts) for instant micro-disbursements & isolated expense budgets. • Stripe US/EU for automated customer settlements. 2. Resilient Network Egress: • Cloudflare WARP + dedicated WireGuard tunnels. • Eliminates random geolocation flags and authentication freezes across international portals. 3. Automated Customs & Compliance: • Lightweight Python + OCR parsing ERP bill-of-materials into EU EN 1493 Declaration of Conformity specs. • Cut compliance verification from 72 hours to 15 minutes. 4. Local 48h Physical Spares Buffer: • Dedicated Italian consignment warehouse so European workshops never wait on 4-week ocean freight for a seal replacement. Heavy global commerce used to require an army of back-office staff. In 2026, code and modern rails let a small team run an entire international supply chain.

• 
  Krishna Singh (@krishnasinghdev) reported 28 minutes ago

  @tapasadhikary I believe useEffect has been the source of so many production issues, most recent one was with Cloudflare

• 
  Guillermo Zaandam 🇨🇦🇳🇱 (@besodemieterd) reported 29 minutes ago

  @Cloudflare Your CSP rules and WAF rules aren't working again and again. Please fix this

• 
  chosem 😖 (@chosem_) reported 34 minutes ago

  @synopsi use cloudflare receive and sending. connect receive to an openrouter API, basically most modern AI will do, even cheaper ones. make it categorize: promotion, support, misc. and then route the support to your actual support platform so you can see it all in one place.

• 
  💜 (@1MDyEOm59Gd4tvD) reported 36 minutes ago

  @stupidtechtakes whats bad about anubis? t: only experience with it is seeing it on websites and thinking "damn at least it has an anime girl instead of the annoying cloudflare captcha", is it secretly bad actually or

• 
  That Brazilian Omo Eko (@sholawa) reported 37 minutes ago

  Cloudflare has my airtel IP restricted lol.... Slow internet caused it; I must have hit the rate limit that day...

• 
  Deyder Cintron (@deydercintron) reported 39 minutes ago

  @levelsio @Cloudflare Full API surface that lets you register and manage without handoffs is the real unlock. Anything that forces a browser click or support ticket re-introduces the bottleneck.

• 
  James (@jamescoder12) reported 41 minutes ago

  The full impact. What he changed and what happened: 1. Moved router from cabinet to open shelf: 74 Mbps → 155 Mbps 2. Changed Wi-Fi channel to least congested: 155 Mbps → 290 Mbps 3. Widened channel width to 80 MHz: 290 Mbps → 380 Mbps 4. Switched DNS to Cloudflare (1.1.1.1): browsing latency dropped noticeably on every device 5. Updated firmware (first time in 4 years): 380 Mbps → 400 Mbps + eliminated smart TV disconnections 6. Changed admin password + upgraded to WPA3: closed the 2 biggest security holes in the network 7. Separated 2.4 GHz and 5 GHz bands: eliminated TV buffering caused by band steering 8. Enabled QoS (work laptop prioritized): zero Zoom call drops during peak household usage 9. Bought own router, returned ISP rental: $168/year saved + full control over all settings Starting speed: 74 Mbps (on a 500 Mbps plan getting 15% of what he paid for) Ending speed: 440 Mbps (getting 88% of what he paid for) Then the real move: he downgraded from the 500 Mbps plan back to 200 Mbps because 200 Mbps with optimized settings delivered faster Wi-Fi to his devices than 500 Mbps with factory defaults. Monthly savings from the plan downgrade: $30 Monthly savings from returning the rental: $14 Total annual savings: $528 with faster, more stable, more secure internet Total time to make all 9 changes: 15 minutes of settings + one trip to Best Buy + one phone call to return the rental.

• 
  Chris Locke (@chrisjlocke) reported 45 minutes ago

  @SportingNest @DaveLukewski @Cloudflare No it didn't. Just posting engagement bait crap.

• 
  Nick Dodd (@nickdodd) reported 54 minutes ago

  @BraydenWilmoth Who knew billing was important for a company literally selling services? I never, ever, have wondered why I have never used Cloudflare for anything.

• 
  Goldman Stacks (@GoldmanStacks) reported 54 minutes ago

  @tresokure Your website is down with a DNS resolution error from Cloudflare.

• 
  Muntasir Mallik (@muntaxir04) reported 57 minutes ago

  @acolombiadev @Cloudflare Maybe it's Gemini? We never run out of searches bec nobody uses it anymore

• 
  AGTP (@AGTPinsights) reported 59 minutes ago

  Cursor just launched self-hosted machines for cloud agents today. Here's what you need to know. You can now run Cursor cloud agents on infrastructure you manage, including pools of machines that auto-scale with demand. The agent loop still runs in Cursor, but tool execution, your codebase, build outputs, and secrets stay entirely inside your own network. This gives agents access to internal services or specialized hardware that Cursor's own cloud can't reach. Cursor also added support for supported sandbox providers, letting teams pick managed infra instead of running their own machines. Self-hosted workers now support computer use on Linux and Mac too, so an agent can click, type, take screenshots, and drive the browser, with users able to watch or take control from Cursor. Coder separately announced Agent Relay, giving Cursor Cloud Agents self-hosted execution environments on customer infrastructure, launching in private preview with SpaceXAI as a design partner for regulated enterprises where code can't leave the network. Key numbers: - Supported sandbox partners at launch: AWS Lambda, Coder, Cloudflare, Daytona, E2B, Modal, Namespace, Vercel - Cursor Pro pricing starts at $20/month, self-hosted machines require paying for your own compute separately - Coder Agent Relay: private preview, no public pricing yet Team pools can hibernate idle machines so you're not paying to keep capacity warm.

• 
  Theo Ephraim 🧙‍♂️ (@theozero) reported 1 hour ago

  @dbmikus @ericclemmons last I tried last on cloudflare sandboxes it was quite slow. Couldnt quite just restore the vm in its running state and many hoops to jump through.

• 
  My1 (@nep.one - Misskey) (@My1xT) reported 1 hour ago

  @slendidev interesting question would be how fast or slow cloudflare runs on those, as especially on my older laptop it sometimes took a decent while, before needing a click and taking a decent while again, while anubis you dont need to babysit.

• 
  lasan (@las_nish) reported 1 hour ago

  Comparisons of Free Trial Abuse Prevention Services If you're running a SaaS with a free trial or focusing on PLG, authentication and abuse prevention are not the same problem. - WorkOS: If you're already using WorkOS, WorkOS Radar is probably the first thing I'd look at. For a WorkOS stack, WorkOS AuthKit + Radar makes the most sense. You don't need to bolt another authentication system onto your app just to get abuse signals. - Auth0, Supabase Auth, Better Auth: These are primarily identity/authentication platforms. Integrating only these can't prevent free trial abuse. - Custom: Like the previous options, you need a custom way to prevent free trial abuse. Most free trial abuse methods involve disposable emails, Google dot variations, Google/Gmail domain variations, and plus addressing. That's why even when you block bots via Cloudflare Turnstile or CAPTCHA, you can still get these abusers. The industry standards: - Block free trial abuse using lists hosted on GitHub: This is a pain in the ***. If you don't want to pay money, you can use a service that offers a generous free tier. - WorkOS Radar: This is mainly used at the enterprise level. They focus more on WorkOS-related integrations rather than integrations with other providers. - ZeroBounce, NeverBounce, MillionVerifier, DeBounce: These are mainly used to clean/validate emails. There are 100s of alternatives, and most are similar with minor differences. They all have disposable email checking APIs. - UserCheck: This is also an email validation API, but they focus on blocking fake email addresses. It's better than a basic email verification API. - Autheona: This is in the same category as WorkOS Radar and UserCheck, but with more features. It also focuses on fake user detection and is growing with a real user base. Now, pricing: - WorkOS Radar: First 1,000 checks free, then $100 per 50 checks. No application-specific logic changes. Easy to integrate and manage. - ZeroBounce: 100 free validations in the free tier, then pay-as-you-go, starting at 2,000 for $39, and so on. - NeverBounce: No free trial or use case, $8 per 1,000 checks. - UserCheck: 1,000 API requests per month in the free plan. The rule-based engine is not included in the free plan, and you can get up to 1 request per second. - Autheona: 3,000 checks per month, with the rule-based policy engine included. Standard API request rate limitations apply, similar to paid plans. Now, use cases: - WorkOS Radar: Block disposable emails, plus addressing, and Google dot variations. - ZeroBounce, NeverBounce, etc.: Block disposable emails. - UserCheck: Block disposable emails, plus addressing, and Google dot variations; detect public emails; email suggestions; syntax validation; role detection. - Autheona: Everything included in UserCheck, plus business/free/government email identification, deliverability checks, fraud patterns, punycode and mixed-script checks, VPN detection, and bot detection (not necessary if you already use CAPTCHA, Cloudflare, etc.). Final decision from me: - Use WorkOS Radar if you're already in the WorkOS ecosystem. It's harder to integrate with other auth providers. - Use ZeroBounce-like APIs if you need basic disposable email checks. They're not as good if you need a better free tier. - Use UserCheck if you only need email-related validation and want to stay within the free plan. - Use Autheona if you need the most generous free tier available with a custom policy engine. All services take a maximum of a few hours to integrate and test. Both UserCheck and Autheona have a similar approach: integrate once and never touch the code again.

• 
  Hauber 🇵🇸 (@HauberDevs) reported 1 hour ago

  @AlexaIs60635 @James_inthe_box absolutely ******* terrible take. Cloudflare literally powers 10% of the internet. Plus alot of services use AWS, if you block that you would essentially be locking yourself out of a good portion of the internet