Cloudflare 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:

• 
  MoroJS (@Moro_Js) reported 5 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. 🚀

• 
  Dane Knecht 🦭 (@dok2001) reported 6 minutes ago

  @Nateemerson @ritakozlov @Cloudflare None of those. Technologist that love customer and understand developers.

• 
  David Hamilton (@David_mduw) reported 9 minutes ago

  A support email landed at 7:05am. By the afternoon the fix was live in production and the customer had his answer. My total input: one prompt, a plan approval, a deploy approval. The workflow: - Claude reads the email thread (Gmail MCP) - Reads my product docs for context (Obsidian vault) - Queries the live database, read-only. His data was fine. So something was missing, not broken - Traces the codebase and finds the gap - Ships the fix - Deploys to Cloudflare, verifies against production - Drafts the customer reply in my voice. I read it and hit send At some point I'll automate the whole flow. Email lands, agent triages, a draft waits for my review. For now it's one sentence at 7am.

• 
  Modi (@Modikiller) reported 13 minutes ago

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

• 
  KhloePai (@Khloes_Khloes) reported 13 minutes ago

  @Kitasure Yea, I've been noticing this in the evenings mostly. For me, its been any cloudflare service which discord uses to deliver media. I've been able to get around it with a vpn. Messages and connecting to vcs has been okay for the most part.

• 
  Komal Sibraan (@KomalSibraan) reported 16 minutes ago

  1/ The woman was Michelle Zatlyn. The company was Cloudflare. This came out in a viral VC horror story thread on X this week and I genuinely had to put my phone down.

• 
  Adolfo 🦀🔺 | OpenCrabs Creator | truelens.tech®️ (@AdolfoUsier) reported 19 minutes ago

  @HyperTechInvest Cloudflare approach works at scale but self hosted agents sidestep the whole problem. @opencrabs runs on a single VPS with persistent state, free Xiaomi MiMo tokens til June 27 if you want to try it bro

• 
  Krish Dasgupta (@officialKrishD) reported 19 minutes ago

  @threepointone lol ! But, You ought to keep an eye on Cloudflare today. Folks will route local models and route private compute endpoints. Might create a service disruption. People are going crazy over access issue of the model. Some even said that they incorporated it in their ecosystem. I wonder do they not even do the Evals ? Just plug the newest model to fool their clients . And now the system broke !

• 
  Puneet Patwari (@system_monarch) reported 21 minutes ago

  Caching at the CDN? Easy. Knowing when to clear it? That's where it gets fun. Scenario: you deploy a bug fix. API now returns corrected data. But CDN edges worldwide are still happily serving the old, broken response. And they'll keep doing it until the cache expires. Three ways to deal with this: 1. TTL-based expiry (the simple one) Set a timer. Content expires automatically. Some rules of thumb: - Changes every few hours → 5 min TTL - Changes daily → 1 hour TTL - Versioned assets (app-v2.3.1.js) → 1 year (filename changes with each version, so it doesn't matter) The tradeoff: if TTL is 60 seconds, users might see stale data for up to 60 seconds after a change. That's it. For 80% of use cases, totally fine. 2. Purge API (the manual override) Force-clear content from all edges immediately. Every CDN has this. CloudFront invalidations, Fastly instant purge, Cloudflare cache purge. The catch: if you purge 10,000 URLs after a deploy, all edges suddenly have empty caches. They ALL go fetch from origin at the same time. Thundering herd. Your origin gets crushed. Good for: targeted fixes on a few URLs. Bad for: bulk clearing after every deploy. 3. Stale-while-revalidate (the one you should actually use) This is my go-to for almost everything: Cache-Control: max-age=60, stale-while-revalidate=30 What this means: - Content is fresh for 60 seconds - After that, serve the stale version instantly to the user - But in the background, go fetch the fresh version from origin - Next user gets the updated content User never waits. Ever. Freshness catches up within seconds. No thundering herd. If you take one thing from this entire thread: use stale-while-revalidate. It fixes 90% of CDN cache headaches.

• 
  William Roush (@StrangeWill) reported 26 minutes ago

  Anyone else having a swath of issues on Cloudflare? I got sites and workers across domains and infra going up and down ugh

• 
  Tushar Dwivedi (@tush_2708) reported 27 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"

• 
  Dhairya (@dkare1009) reported 28 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

• 
  Agasta (@idkAgasta) reported 30 minutes ago

  @anirudhprmar But you will lose global cdn/ edge network with this .... Also I don't like to host forntend or full stacks in a single vm..... I will consider using Cloudflare workers if the budget is tight or AWS cloudfront + ecs with fargate if we are richy-rich

• 
  Deep Web Konek (@deepwebkonek) reported 30 minutes ago

  @anjo_bagaoisan it seems an issue again with cloudflare, apparently down rin sila 👀

• 
  Alex LaPrade (@alexlaprade) reported 32 minutes ago

  @dalexeenko @real_khanzunlah @Cloudflare Shot you a DM of a similar issue.