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.

• Domains (41%)
• Cloud Services (27%)
• Hosting (18%)
• Web Tools (9%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	2 days ago
London	Domains	4 days ago
Noida	Hosting	17 days ago
Jewar	E-mail	17 days ago
Braga	Web Tools	17 days ago
Noida	Cloud Services	18 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:

• 
  Bilal @ Supadesk.co (@BilalBudhani) reported 1 minute ago

  Cloudflare is down folks. What are you guys up to?

• 
  Z (@Cosmosz) reported 6 minutes ago

  is Cloudflare down? can't load account

• 
  Miracles Live 🇹🇭 (@fern_miracles) reported 9 minutes ago

  @amasad You should vibe-code the Replit platform to log every negative experience a user has - from constant cloudflare warnings, to erroneous account lockdowns with notifications that user has exceeded limits, to runaway agents. -> Auto determine the highest ROI fix for least friction.

• 
  sahand (@sahand_io) reported 15 minutes ago

  @armandokirwin @adocomplete @Cloudflare I'm not 100% there's a nicer way to integrate to voice calls. HTTP or Zapier (still HTTP) is possible, but makes the call very slow.

• 
  Goodness And Mercy (@FineAndRich) reported 15 minutes ago

  🚨 Cloudflare is currently investigating issues affecting the Dashboard and related APIs. ❌ Dashboard requests may fail ❌ API calls may return errors ✅ CDN cached content remains operational ✅ Edge security services are unaffected If your automation or deployments are acting up, Cloudflare may be the reason. #Cloudflare

• 
  Josh W (@ItsWelford) reported 16 minutes ago

  Anyone at Cloudflare able to help with an OAuth client? It's still waiting for verification & it makes me think something is wrong, because my other OAuth client verified almost instantly.

• 
  Jeff Liford (@JeffLiford) reported 17 minutes ago

  @Cloudflare @CloudflareSys @CloudflareDev Cloudflare is operational again at this time, however I am encountering an issue with one domain name being redirected to an improperly spelled domain. Currently investigating root cause.

• 
  sam (@samgoodwin89) reported 17 minutes ago

  @Cyb3ristic Yes, @Cloudflare is notoriously bad at this. It's insane that a Cloud provider thinks it's ok to just release breaking changes to their API. We are pretty much running tests all the time because of Alchemy dev, so we just respond as quickly as possible. Not ideal.

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

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 23 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

• 
  Aahan Singh (@aahan_builds) reported 25 minutes ago

  @ajmeese7 @Cloudflare o great, mine went down too. these platforms have been going down way too often lately

• 
  Josh (@josh_nimako) reported 28 minutes ago

  What Outranking a $1B Company Taught Me Before My 1.7M User SEO Project Died One of my first serious SEO projects is dead now. Before it died, it reached over 1.7 million active users, gave me my first million clicks, and for about a month, and even outranked a company doing around $1B in revenue. But the failures were louder than the losses. The real lesson came after the rankings started working, because traffic showed me every weak part of the site, the server, the content, the tracking, and my thinking at the time. I knew enough to build the site, publish content, target searches, add schema, work on image SEO, and chase fresh demand, but I did not yet understand what happens when the traffic actually lands. Getting traffic is one problem. Surviving traffic is another. The site started as a normal beginner project. Some of it worked faster than I expected. I learned that image SEO can be a serious traffic source when the niche has visual demand, schema can help Google understand the page faster, and freshness can matter more than authority when a search window opens for a short period of time. I also learned how powerful Reddit can be. We used Reddit as part of the distribution layer, not because it was magic, but because Google already trusted the platform and certain threads could rank fast when the query had the right shape. That was my first real lesson in parasite SEO. Sometimes the fastest way to appear in search is not to wait for your own domain to build trust, but to place the right content on a platform Google already trusts, then use that page to capture demand while your own asset grows. That does not replace building your own site. It teaches you how distribution actually works. For about a month, that kind of thinking helped me outrank a company with far more money, authority, and resources than me. I was not better than them. I was just closer to the search. I understood the timing, the page format, the image demand, the freshness window, and the exact thing the user wanted in that moment. That changed how I saw SEO. Big companies can win on authority, but small operators can still win narrow battles when they move faster, match intent better, and understand the search better than the bigger player does. Then the site started breaking. During traffic spikes, pages would freeze, the server would throw 502 and 504 errors, and the site could be unavailable for long periods while I tried to work out what was happening. At the time, the server was exposed directly to the internet, so every request hit the origin server. Real users hit it. Scraper bots hit it. Aggressive crawlers hit it. Bad traffic hit it. Everything hit the same machine. The PHP-FPM pool started choking, Apache logs showed worker thread errors, and the server ran out of breathing room because it was trying to handle too many requests at once. That was the first time I understood that infrastructure is part of SEO. If Google sends traffic and the site falls over, that is not only a server problem. It becomes a crawl problem, a trust problem, a user problem, a revenue problem, and eventually a search problem. The worst issue was inside the theme. The site used Themify Ultra, and one function was checking images through full public URLs instead of local file paths. That sounds small until traffic hits. One page view could cause the server to make extra HTTP requests back to itself to inspect images, so instead of one visitor creating one normal request, the server created more work for itself while also dealing with real users and bots. It was a self-DDoS loop. The site was not only being hit from outside. It was also wasting resources calling itself. We fixed it by bypassing the image-checking behaviour and adding a local hosts shortcut so the server could resolve itself internally instead of going out through the public internet. That one bug changed how I think about performance. Performance is not just a page speed score. Performance is what happens when the whole system is under pressure. Then we put Cloudflare properly in front of the server. Before that, the origin IP was exposed, which meant bots and scrapers could hit the machine directly. Now Cloudflare became the front line. It hid the real server IP, cached static assets like images, CSS, and JavaScript, and challenged or blocked bad bot traffic before it reached the server. That took pressure off the origin. The server no longer had to serve every image to every visitor, and it no longer had to take every bot request directly. Now, if I build a site that depends on organic traffic, I do not treat Cloudflare, caching, bot filtering, and origin protection as extras. They are part of the build from day one. I also learned that bots are not a small issue. Some were scraping content. Some were hammering pages. Some were burning CPU without acting like users. They did not convert, subscribe, read properly, or add anything useful. They just created load. That forced me to learn server logs, Nginx logs, Apache errors, PHP worker limits, caching, bot protection, and traffic spike behaviour, because Analytics could tell me people were visiting, but the server logs showed what was actually hitting the machine. That changed how I use SEO tools too. Ahrefs and Semrush are useful, but they are not the market. In this niche, demand could spike fast when new content appeared, and a page could get thousands of clicks in the first hour before the window closed. A third-party tool might not show that properly because the demand moved too quickly. Search Console showed what Google actually sent. Analytics showed what users did. Server logs showed what hit the server. No single tool had the full truth. I also made quality mistakes. One of the biggest was allowing an unmoderated comment section. At the time, I thought comments were harmless because they added more text and activity to the page. That was naive. Spam, thin replies, irrelevant text, and messy user-generated content made pages worse. The site had traffic, but parts of it started to look lower quality than they should have. That taught me that more content is not always better. More indexable text is not always better. If the page is the asset, you cannot let random people lower its quality. Now I think about SEO very differently. Before this project, I thought SEO was mostly about ranking pages. Now I think it is about building systems that can turn search demand into something useful without breaking. That means the page has to match intent, the content has to be controlled, the server has to survive traffic, the logs have to be watched, the origin has to be protected, and the traffic has to lead somewhere beyond a graph inside Analytics. The site is dead now. Some reasons were strategic. Some were technical. Some were niche specific. All were my fault in the end. But I do not see it as wasted work. It taught me how real traffic behaves. It taught me that a page can rank and still be fragile. It taught me that a site can have users and still be a weak asset. It taught me that small operators can beat giants in narrow search windows and that Reddit and parasite SEO can move fast when the query fits. It taught me that Cloudflare can be the difference between traffic and downtime and that server logs tell a different story from dashboards. It taught me that the next problem starts after the ranking works. That is the part I carry into every project now. I do not just ask: Can this rank? I ask: Can it survive the traffic? Can it stay clean? Can it handle bots? Can it load under pressure? Can it earn trust? Can it turn attention into users, leads, revenue, data, authority, or another asset? My first serious SEO project is dead. But it gave me the lessons I needed. And those lessons are now part of how I build.

• 
  Stealth Exploit (@stealthexploit) reported 29 minutes ago

  Sorry guys I was not available yesterday so here is a summary Google Cloud Run (Hosting) Cloud Run only charges you for the exact milliseconds your app is processing a request. If nobody is visiting the site, the servers instantly scale to zero and you pay absolutely nothing. With Cloud Run you get 2 Million free requests, 360,000 GB-seconds of memory, and 180,000 vCPU-seconds completely free every single month. Cost: $0.00 until you start getting thousands of daily active users Artifact Registry (Storage) This is usually where companies bleed money because old, massive Docker images pile up over months. The Free Tier gives you 0.5 GB of free storage per month but i created the policy.json to aggressively delete images older than 7 days and only keep the last 3 versions this would make my storage incredibly small. Our Nginx/Alpine containers are extremely lightweight (~25MB each). Cost: $0.00 to $0.10 per month. Google Cloud Build (CI/CD) Every time you push code, Google spins up a machine to build your Docker image. The Free Tier also gives you get 120 free build-minutes every single day but since i was using Vite, builds take about 1 to 2 minutes. This means me and my team can push code 60+ times a day for free with an estimated cost of $0.00 Network Bandwidth (Egress) Sending data to users costs moneyso google gives you 200GB per month for free, For better optimization use Cloudflare in front of your domains, Cloudflare acts as a massive shield and It aggressively caches your static CSS, JS, and Images on their own edge servers around the world for free. This means only a tiny fraction of your traffic ever actually hits Google Cloud. Estimated Cost: $0.00 cc : @maazscript @LanHubs

• 
  Interfacing Linux (@intlinux) reported 33 minutes ago

  Cloudflare Dashboard is down and now Facebook is exploding. Going to be an interesting Friday.

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

• 
  Ariekany🔸(🦀/rust) (@Ariekany) reported 36 minutes ago

  @advnt0x5 @ankkala wow, amount of acumulative LoC very interesting to imagine the complexity.. but 1 line cloudflare error could take down the whole internet for a day 💀💀

• 
  Shreyas Mididoddi (@Shreyassanthu77) reported 42 minutes ago

  @joshmanders Primcloud sucks we should delete all of it and rewrite it in cloudflare

• 
  Alexey Lein (@alexeylein) reported 44 minutes ago

  Cloudflare's business is going to explode, because it was pretty much unusable before because of poor UX. Now Claude does it all for you and it turns out Cloudflare is an amazing product.

• 
  Smakosh (@smakosh) reported 44 minutes ago

  Yo @Cloudflare what's the point of your status page if it doesn't report that your stuff is down?

• 
  Ivon Huang (@Ivon852) reported 44 minutes ago

  Finally made the switch. Actually, when you buy a domain, you can transfer it to another registrar. This is called a domain transfer. If you feel your current domain registrar is ripping you off, you should jump ship as soon as possible. If you don’t need an all-in-one website-building service, buying a domain from GoDaddy seems very uneconomical. They are just very good at advertising in many countries. Domains from Porkbun and Cloudflare Registrar are much cheaper. My website is built with a JAMstack setup using Hugo SSG and ***. And yet, I renewed my domain for four years, paying around $20 per year for a common .com domain. I honestly can’t believe I stayed on GoDaddy and kept feeding the money machine, even though I wasn’t using their WordPress services at all.

• 
  🍺 (@8INK5) reported 45 minutes ago

  @QBCCIntegrity @PaulineHansonOz @OneNationAus Cloudflare has been getting attacked over the past few days, I know there has been problems elsewhere are well so it might not just be ON

• 
  chan (@chantastic) reported 45 minutes ago

  @jeflopo I'm annoyed because the frontend of these sites has to do SO little. all the serious work is Cloudflare Workers, Queues, AI Gateway, and Durable Objects. so it's just an annoying speed bump to have UI framework issues

• 
  kclich  (@kclich) reported 49 minutes ago

  Websites you’ll actually use (and wish you knew earlier) 👀 Temp Mail Disposable emails for quick signups and testing. Down For Everyone Or Just Me Check if a site is down or it’s just your connection. Wayback Machine View old versions of websites and deleted pages. BuiltWith See what technologies any website is using. JustWatch Find where any movie or series is streaming. Temp Number services (e.g. TextNow, Sonetel) Get virtual numbers for verification and testing. CamelCamelCamel Amazon price tracking history (real discount checker). Cloudflare Radar See internet traffic trends, outages, and global insights. Wappalyzer Instantly detect tech stack of any website (browser extension). Have I Been Pwned Check if your email was leaked in a data breach. Remove dot bg Instant background removal for images. Photopea Free browser-based Photoshop alternative. Regex101 Test and debug regex patterns instantly. JSON Formatter (jsonformatter dot org) Clean and debug JSON quickly. Carbon Turn code into beautiful shareable images. Excalidraw Simple online whiteboard for diagrams and system design. What are you using daily that’s missing here? 👇

• 
  inder (@InderpreetSingh) reported 51 minutes ago

  Looks like @Cloudflare dashboard is down, but just saw "Organizations Beta". I hope thats the case. All my projects are co-mingled in a single account right now.

• 
  British Tuga (@BritishTuga) reported 51 minutes ago

  @dearg_x @Cloudflare Literally happened to me today. Thought I'd try out Cloudflare domains and Cloudflare pages. Whole thing goes down

• 
  Tay 💖 (@tayvano_) reported 52 minutes ago

  @candyflipline No that’s not how the world works. Do you know how much malicious **** exists on Amazon? How often it’s used to harm? But Amazon is immune bc it’s not them. Same for Cloudflare. Google. Apple. Windows. GitHub. All of them lmao.

• 
  GPT Workspace (@gptworkspace) reported 53 minutes ago

  GPT Workspace is temporarily affected by @Cloudflare related issues. We expect the problem to be resolved shortly.

• 
  Nathan (@nthglsn) reported 54 minutes ago

  @chuksXB @Cloudflare they moved support team to india to cut costs

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

• 
  Youssef 🚜 (@yelkhayami) reported 59 minutes ago

  we're a small team running 5 consumer apps, so checking posthog, cloudflare, search console and slack for every app every day stopped being realistic i ended up pulling everything into one internal tool, one timeline per app: • error logs (client + server) • analytics events we care about • cloudflare logs • google search console issues • relevant slack channels • custom signals per app, orders, signups, queue sizes, anything a db query can answer agents read whatever is new every 30 minutes and only surface findings that need review. failed crons, seo drops, weird spikes. i almost NEVER reads raw logs anymore it's also an mcp server, so claude can query the whole company when we're debugging or making decisions, so my team can use it too we never set out to build a 'data foundation', it grew out of not wanting to check 5 dashboards but now that we have it up and running it's honestly great