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 (62%)
• Hosting (31%)
• E-mail (8%)

Live Outage Map

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

City	Problem Type	Report Time
Tlajomulco de Zúñiga	Cloud Services	5 days ago
Asnières-sur-Seine	Cloud Services	9 days ago
New York City	E-mail	13 days ago
Township of Evan	Hosting	13 days ago
Ahmedabad	Cloud Services	19 days ago
Le Puy-en-Velay	Cloud Services	20 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:

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

  No ******* way that’s really you messaging in that chat…but then I accidentally clicked the button, the chatbot responded, I sent an emoji; then you sent a name and email template & then suddenly OF was also trying to track along with ur site through cloudflare 💀 What a ******* webhook to stay connected to every chat someone has open from ur webpage authenticated by the network cert…holy **** 🥵 for that setup

• 
  Andy Knowles (@andykn101) reported 13 minutes ago

  @SportingNest @Cloudflare It's absolutely a scam. If you don't know what those instructions do listen to those who. If you're not clicking on the ads in your search results you've probably already got malware poisoning your search results. Get help.

• 
  Kevin Minnelli (@minnelli) reported 13 minutes ago

  WTF - Grok Bot can't fire on schedule to save it's life. The scheduled routines are just broken and at best unreliable. I want to love this product. When you set the cron job it doesn't work. It tells you try Cloudflare, sure let's set that up and burn tokens, then that doesn't fire to wake them. Oh, let's try GitHub now and use that....all failed. I had to wake it again this morning before the market opened. Anyone else feeling frustration in this regard?

• 
  LilRhodySpecial (@rhody_special) reported 13 minutes ago

  @Sprytixl Yet another ad to get you to use their data stealing bot on the cloudflare data snooping service

• 
  Kyzer (@Spectre_xdd) reported 15 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.

• 
  Alexey Vasilev (@Alvasilevv) reported 15 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.

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

• 
  Brij Pandey (@LearnWithBrij) reported 25 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

• 
  Blockchain Daily News (@blckchaindaily) reported 26 minutes ago

  🚨 CLOUDFLARE $NET EXPANDS AI AGENT SUPPORT, NOW RUNS CURSOR CLOUD AGENTS ON CLOUDFLARE SANDBOXES FOR CUSTOMER-CONTROLLED EXECUTION - PRESS RELEASE

• 
  Harlen Bayha 🇺🇸 (@QreatureQriator) reported 26 minutes ago

  @mrfundman @Cloudflare Did it work with Outlook emails? My bots struggle with Outlook's interface so bad.

• 
  shownotover (@shownotover) reported 27 minutes ago

  @edtadros Well seems like I need to give it a try. Not gonna lie, I never thought two people would tell me to use Cloudflare.

• 
  AR GamingPK1 🇵🇰 (@argamingpk1) reported 31 minutes ago

  @DanielZahoor But Cloudflare DNS routing is so bad.

• 
  Brendan Ryan (@BrendanRyanM) reported 33 minutes ago

  @mntruell @petergyang @bot Also having an issue getting past bot blockers, e.g. cloudflare prompts to press a button and prove you’re human. Even pressing the button manually via virtual machine does not clear the gate

• 
  Adam Rackis (@AdamRackis) reported 34 minutes ago

  @kettanaito @flydotio Do your pods auto-sleep when they’re not getting traffic? I think there’s a min setting you have to set to zero to let everything shut down and then just cold start on the next request. Really though surely Cloudflare free tier is simpler?

• 
  David Oks (@davideoks) reported 39 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)

• 
  Α Ω Programmer (@OmegaNekoSimp) reported 40 minutes ago

  @sneedistan Cloudflare proetects terorrist oeganizations and will badically threaten to destroy your company if you don't pay them more money. They are a disgusting company. **** them. Also the Linux Kernel uses this.

• 
  Bobby Lansing (@dataguybobby) reported 43 minutes ago

  Bot is grepping logs in CloudFlare, Azure, Supabase, and Vercel. Then triggering Cursor agents to build a fix. I am mentioning issues and approving PRs.

• 
  Dr. Internets (@Dr_Internets) reported 43 minutes ago

  @spacebruce @alynokioku Hello, I am Albanian cloudflare. Due to poor technology, I need you to paste this totally real command into your admin command prompt. Very real, trust.

• 
  Megumi, Internet Angel 🏳️‍⚧️ (@pcppup) reported 45 minutes ago

  @NightlyArii i think you are not catching my sarcasm :) i do not know how much you know about cybersec, but a static page would require Cloudflare, Github, or my Computer to get hacked, which is just crazy. You're just criticizing AI because you can. It's good for some things, bad at others.

• 
  Miget (@miget_com) reported 45 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.

• 
  PureStory (@PureStoryLabs) reported 46 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.

• 
  Goldman Stacks (@GoldmanStacks) reported 48 minutes ago

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

• 
  Lubos Kolouch (@LubosKolouch) reported 51 minutes ago

  Think twice before you paste: if a website's "Cloudflare CAPTCHA" asks you to open Windows Terminal and run a command, it's a trap. This is TerminalFix, a malware campaign Microsoft detailed in late August 2026. Pasting the code installs malware, exposes your accounts, and opens a backdoor to your network. Real CAPTCHAs only ask you to click images or checkboxes. Never open Terminal or PowerShell just because a website told you to. If you see these instructions, close the tab immediately to avoid a full corporate breach.

• 
  Durp  (@durpsick) reported 51 minutes ago

  This will happen in the span of 30 days. We will also be adding • Accounts (if you wanna make one) • backed server support • meny charity's • better service support Everything listed will also be supported by Cloudflare Security!

• 
  💊🧠 (@theOGstud) reported 53 minutes ago

  @leviackermanft Novel works fine ... I've also played an anime .. problem comes with the manga. After downloading the repo,it either points out that source not found or the source leads you to cloudflare then the app crashes ..

• 
  junebnunny (@junebnunny_) reported 55 minutes ago

  @Gion_the_critic @SportingNest @Cloudflare It's a click fix attack

• 
  junebnunny (@junebnunny_) reported 57 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.

• 
  pkuseri (🍉) (@Pkuseri_) reported 58 minutes ago

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

• 
  Hanif Carroll (@HanifCarroll) reported 60 minutes ago

  At a previous job, I was lucky to work with a staff-level front-end engineer who was very good at what he did and thorough like no one else I had worked with. I didn’t always appreciate that thoroughness. At first, I found it maddening. Meetings with product and design would drag on because he always had an enormous list of questions about whatever feature we were discussing. I was usually eager to finish the meeting and start coding. It took me a while to understand that he wasn’t making the process longer. He was asking the questions we would otherwise have to answer halfway through development, when an unanswered question could block the feature or send it in the wrong direction. Every unanswered question holds an assumption, and that assumption might not match what product or design had in mind. I thought about him recently while reviewing the search process for Casamo, a product I’m building to help people compare furnished stays. Before changing the code, I started asking questions: Why were we processing listings already known to be over the user’s budget? Why were hotel-like properties entering the process when the user had asked for an entire place? Why did we stop after finding six suitable stays if ten were available? How old could a review be before it stopped being useful evidence? Those questions exposed decisions that had been made when Casamo ran on a low-powered VPS and needed to do as little work as possible. They didn’t all make sense now that the product runs on Cloudflare. We changed the search process to reject known mismatches earlier, treat six results as the minimum rather than the target, continue until it finds ten suitable stays, and only use reviews from the previous year as evidence. If I had started coding immediately, I probably would have made the existing process faster without questioning whether it was still the right process. I don’t know if I’ll ever have as many questions as he did, but now I understand what he was protecting us from.

• 
  junebnunny (@junebnunny_) reported 1 hour 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.