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	4 days ago
Township of Evan	Hosting	4 days ago
Ahmedabad	Cloud Services	10 days ago
Le Puy-en-Velay	Cloud Services	11 days ago
Ann Arbor	Cloud Services	13 days ago
Palermo	Hosting	13 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:

• 
  pkuseri (🍉) (@Pkuseri_) reported 28 seconds ago

  @stupidtechtakes Do you know any better alternatives aside cloudflare? Not being rude or anything if the tone sounds rude mb

• 
  Krishna Singh (@krishnasinghdev) reported 12 minutes ago

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

• 
  junebnunny (@junebnunny_) reported 13 minutes ago

  @SportingNest @Cloudflare This is a click fix attack. Do not run the code. Do not do ctrl V. Do not do Windows plus R. You will lose all of your data. You will get scammed. Your bitcoins will be taken.

• 
  JK (@_junaidkhalid1) reported 15 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.

• 
  Sameer Bhagtani (@sameerbhagtani) reported 16 minutes ago

  @NiceCodeWriter You should make use of cloudflare tunnels. That should solve your problem.

• 
  Anthony Lambert (@AnthonyTBM) reported 17 minutes ago

  @jb_ma @sb_chadi Yes, but I've never had CloudFlare request a terminal command sequence. I think most people will be immediately on guard if that occurred after clicking their human status?

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

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

• 
  Przemysław Zalewski (@Ciunkos) reported 22 minutes ago

  @efalcao @proofpoint @Cloudflare Most likely by the fact Cloudflare is kinda bad at handling abuse reports - try filling their form and see for yourself. Any service that could be used for spam delivery, will eventually be used for that. And Cloudflare now tastes what other providers experience day to day.

• 
  Kristian Freeman (@kristianfreeman) reported 22 minutes ago

  Day one support for Cloudflare!

• 
  Saeid Shahriari (@saeidshahriari) reported 23 minutes ago

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

• 
  junebnunny (@junebnunny_) reported 27 minutes ago

  @Gion_the_critic @SportingNest @Cloudflare It's just the type of thing you've just got to come across and you don't really find them that often, because when a campaign is up, it's up for a few hours and then taken down very quickly, because it's quite obviously malware.

• 
  Sahil Mondal (@SahilMondal_) reported 29 minutes ago

  The fastest way to crash PostgreSQL is opening direct connections inside Serverless Lambdas. 1,000 concurrent requests = 1,000 DB connections = OOM crash in 2 seconds. Fix: Put PgBouncer or Cloudflare Hyperdrive in front. Keep 20 persistent connections open and reuse them.

• 
  avrin (@itsavrinwave) reported 31 minutes ago

  Is cloudflare down again??

• 
  Dave Bettin (@dbettin) reported 33 minutes ago

  @dillon_mulroy @EffectTS_ Where is the cloudflare support?

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

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

• 
  Simon Champion (@spudley99) reported 38 minutes ago

  @SportingNest @Cloudflare WOAH! I've not seen that one before, but damn, that's a really nasty phishing attack, trying to get you to run nefarious code on your computer. It's not cloudflare doing that. Whatever site you were on when that came up has likely been compromised; you might want to tell them.

• 
  lasan (@las_nish) reported 41 minutes 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.

• 
  J. (@munchivelo) reported 41 minutes ago

  @dillon_mulroy @EffectTS_ hm. what do you mean great cloudflare support? if i'm building apps for cloudflare ecosystem, what benefit does using EffectTS have over regular typescript/tailwind? can you be specific.

• 
  Noel Ceta (@noelcetaSEO) reported 43 minutes ago

  8/ Layer 5: CDN implementation (distribute content): CDN = Content Delivery Network How it works: - Content stored on multiple servers worldwide - User gets content from nearest server - Fast delivery regardless of geography Setup: - Cloudflare (easiest, free tier available) - Akamai (enterprise) - CloudFront (AWS) Impact: 20-40% speed improvement for global sites.

• 
  Alexey Vasilev (@Alvasilevv) reported 43 minutes ago

  @Jilles Code Mode trades an enumerated surface for a searchable one. Works when the agent already knows it wants Cloudflare. The tool list was a terrible context budget, but it was the only enumeration the model got. Once you import what you need, discovery is a step nobody owns.

• 
  Miget (@miget_com) reported 43 minutes ago

  Then you reach it from outside. Four terminators, and you can run more than one on the same network. WireGuard per person or per machine. Tailscale into a tailnet you already run. Cloudflare WARP into a Cloudflare org. IPsec site-to-site.

• 
  Ben Hocking (@bmwhocking) reported 43 minutes ago

  @rustie5555 There are a lot of round robin API calls for content. Works fine if you are close to their US data-centre. Sucks for us. They are using Cloudflare, I don’t believe they are processing at Cloudflare’s edge, just caching content. They need better & faster timeline building.

• 
  2$p00ky (@dos2p00ky) reported 47 minutes ago

  Cloudflare tracker already? Damn girl, you didn’t **** around today

• 
  DUNGEON-00X 💿📀 (@Dungeon00X) reported 49 minutes ago

  I think Cloudflare is about to go down, everything is loading slow again.

• 
  Kyle Avery (@kyleavery) reported 50 minutes ago

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

• 
  David Oks (@davideoks) reported 53 minutes ago

  @inoutremer @CharlieTyson1 this type of thing is solved by hosting on e.g. Cloudflare. pieces going modestly viral like Wilson's or Oyler's did shouldn't crash a modern web site! presumably they just have terrible IT. (but a quite wonderfully designed website IMO)

• 
  Jean Suze (@JeanSuze8) reported 54 minutes ago

  @Navlio @Lovable Cloudflare wasn’t the original cause. The initial issue happened before Cloudflare was added: mysite was unreachable from several Belgian networks, while it worked perfectly through a VPN and from abroad. DNS, TCP 443 and TLS were all fine, and another site of mine on the exact same hosting IP worked normally from the same connection. We only added Cloudflare later as a workaround. The redirect loop that appeared afterwards was a separate issue: my app still had an old hardcoded mysite → www.mysite redirect, while Lovable was redirecting www.mysite → mysite because the apex domain was set as primary. That created the infinite loop. That part is now understood and fixable. What we still don’t understand is the original Belgium-only outage. Nothing in the DNS/TLS tests explains why the hostname stopped returning HTTP responses from Belgian IPs but worked immediately over VPN. That’s the part we’re still waiting for Lovable to explain.

• 
  yakuzer5 (@conckrete) reported 55 minutes ago

  @OmegaNekoSimp Why are people mad about this? It's a nice break to see this instead of blank page or cloudflare ****

• 
  LUIS- LUIS- (@LUISLUIS532957) reported 56 minutes ago

  @itz_pippo still not working, akira is blocked by cloudflare, please include always other hosts, thanks.

• 
  manny shaw (@MannyShaw) reported 57 minutes ago

  @0xAdesola 1.1.1.1 does not block malware or phishing. For that, use 1.1.1.2. DNS generally cannot unblock geographically restricted streaming services. That normally requires an authorised VPN or Smart DNS service. It cannot increase your broadband speed. It may make the beginning of website loading slightly quicker if your ISP’s DNS is slow. AdGuard DNS blocks many domain-based advertisements, but not every advertisement. It usually cannot reliably block YouTube, Instagram or advertisements served from the same domain as the content. Parental DNS is useful but not foolproof. VPNs, encrypted DNS, mobile data and some apps can bypass router-level filtering. How to change DNS on your router While connected to your home Wi-Fi, open a browser. Enter one of these common router addresses: 192.168.1.1 192.168.0.1 192.168.29.1 192.168.100.1 The correct address is often printed underneath the router as Router IP, Gateway or Web GUI. Sign in using the router’s administrator username and password. This is not necessarily your Wi-Fi password. Check the router label or your ISP’s documentation. Before changing anything, take a photograph or screenshot of the existing settings. Look for a menu called: Internet or WAN Network DHCP Server LAN Settings DNS Settings Disable Automatic DNS, Obtain DNS automatically, or DNS from ISP. Enter your chosen pair. For general family protection, I suggest: Primary DNS: 1.1.1.3 Secondary DNS: 1.0.0.3 For advertisement blocking instead: Primary DNS: 94.140.14.14 Secondary DNS: 94.140.15.15 Do not mix servers from different providers; otherwise filtering may become inconsistent. Tap Save/Apply and restart the router. Disconnect and reconnect your devices to Wi-Fi, or restart them. Cloudflare confirms that router-level configuration normally applies the DNS setting across connected devices.