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:

• 
  Aryan Esfandiari (@arian88) reported 1 minute ago

  Never push to main on a Friday @Cloudflare

• 
  Dan Holzrichter (@dholzric) reported 3 minutes ago

  @HoffmanTactical @RattlerInnovLLC I assume you have someone on this already, but if they cant resolve it, let me know. I pulled down everything available from the cache and wayback, and have it refactored to run directly on cloudflare. (Not using php, wordpress or woocommerce, but with the same credit card processor). I know this sort of thing sucks, but few people are in a situation where their products are so in demand that they crush a wordpress host so easily :) also, caching for cloudflare is set way too short right now and the server is having to refresh every 60 seconds .

• 
  Tej (@tejesh_1) reported 7 minutes ago

  @TRPage_dev @Cloudflare cloudflare support takes days if not weeks to respond.

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

• 
  Puneet Patwari (@system_monarch) reported 9 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.

• 
  topmass (@topmass) reported 11 minutes ago

  @pushmatrix of course - I will note / fix any dependencies there in the readme, the cool thing about the project is, you'd sign up for cloudflare free and could muck about all day long with projects and tools and toss some AI in there for free too, The workers paid (5 dollar plan) would add almost infinite request usage and a lot more ai usage too - durable objects are a nice stateful home for this project too so I couldn't resist

• 
  Miss Latin (@duchesslatinxo) reported 11 minutes ago

  @ritakozlov @Cloudflare How about we hire someone who can actually fix all the API issues. Someone who can get the code from a-z without it bouncing back? Because my company is seeing a 30% decline in profit for the last 6 months due to increasing outages. Cloudflare is always late to report on their own outages. It’s been unstable since the 1st of April… Essentially speaking I’m 100% certain the new integrity verification measures placed on meta has caused major outages on cloudflares CDN. Let’s get this fixed??

• 
  ebobby (@_ebobby) reported 13 minutes ago

  @Cloudflare I see in your status page that the issues with R2 are resolved but I am still having issues uploading from my application and my customers are stuck. Rails app + direct upload to R2 (most customers from Mexico). No changes on my side, worked fine for 2 years.

• 
  96 (@gboncoffee) reported 17 minutes ago

  The broadcast for Barcelona-Catalunya is so ******* bad I’m wondering if it uses Cloudflare infrastructure and there’s a La Liga game happening right now.

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

• 
  Phil J. 🇺🇸 (@thephilj) reported 26 minutes ago

  I CANT TEXT OR CALL ANYONE , CELLULAR SERVICE DOWN, CLOUDFLARE DOWN, ALL SOCIAL MEDIA BESIDES X DOWN

• 
  Jaid (@JaidCodes) reported 26 minutes ago

  I have dozens of personal SPAs not worth setting up a deployment pipeline to GitHub Pages or Cloudflare Pages for. There are a lot of situations where I just want to quickly one-shot a tool and drop the Vite build to a service that gives me a random public domain.

• 
  esyx (@esyx0) reported 27 minutes ago

  @pbertrand_dev @levelsio @Cloudflare that's the worst part, I don't even know whar I did wrong. thank you!

• 
  Agentic Up (@agenticUP) reported 27 minutes ago

  cloudflare is down??

• 
  Christer K Andersson (@yesboxx) reported 29 minutes ago

  Mastercard may have just provided one of the clearest signals yet about where payments are heading. Their new Agent Pay for Machines initiative is built around: • AI agents transacting autonomously • Machine-to-machine payments • Micropayments • Stablecoin settlement • High-frequency, low-latency transactions What caught my attention was not the technology itself, but the ecosystem around it. Coinbase, Stripe, Adyen, Cloudflare, Polygon, Aave, MoonPay and others are already participating. For years, many of these concepts lived mostly in the worlds of crypto, fintech and AI startups. Now they are appearing in products launched by global payment networks. To me, this is another signal that the discussion is moving from if autonomous commerce will happen to how it will be implemented. If software starts buying services from software, the payment infrastructure behind those transactions becomes strategically important. Which companies are best positioned to power that future?