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	1 day ago
London	Domains	3 days ago
Noida	Hosting	16 days ago
Jewar	E-mail	16 days ago
Braga	Web Tools	17 days ago
Noida	Cloud Services	17 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:

• 
  Raccoon 🦝 (@raccoon_builds) reported 6 minutes ago

  @goldenelephant1 @Cloudflare @grok dont be so rude we try to teach you. how it's worked. and you just insult us for no reason take a chill pills.

• 
  Alex LaPrade (@alexlaprade) reported 6 minutes ago

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

• 
  chan (@chantastic) reported 6 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

• 
  GPT Workspace (@gptworkspace) reported 7 minutes ago

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

• 
  Raccoon 🦝 (@raccoon_builds) reported 11 minutes ago

  @goldenelephant1 @Cloudflare @grok I'm not on the paid one either mate. i was just trying to help you i'll got the same thing as you and my agent Ia told me its wasn't attack only bot. i'm running a taxi company website so yeah. need to be protected.

• 
  Number-One-AI-Fanboy (@Number1AIFanboy) reported 14 minutes ago

  And just like that the new base for the Build by Grok website is up at BuildbyGrok.com-> This site was built by The Build by Grok VSCode Agent in less than 15 minutes from plan to changes to uploading to *** then to @Cloudflare . 3 issues with the build were found during the build upload. Each time I gave @grok the issue, each time he fixed it in a single shot. This is how coding software should work! Celebrating America's 250th Birthday with the Bald Eagle Edition of the Build by Grok VSCode Agent. Available now on our site.

• 
  Sarthak Rawool (@sarthakcore) reported 19 minutes ago

  my tool graveyard: Notion for project management. too complex. back to markdown. Obsidian + Hermes for a knowledge vault. never found the use case. Super X for managing my account. replaced it. Codex for writing code. now it only runs test passes. every tool i abandoned taught me the same thing: if it doesn't fit how i actually work, it dies. current stack that survived: Claude Code 6+ hours/day. Claude Design for UI. PlanetScale. Dodo Payments. Cloudflare + GitHub Actions. the tools that stick are the ones i forget i'm using.

• 
  Tawkeer 🦊 (@ZaaZu___) reported 20 minutes ago

  @Cloudflare Why is cloud flare down ?

• 
  Jonathan Workman (@workamania1979) reported 21 minutes ago

  @Cloudflare is down

• 
  Velvex Vancreed (@VelvexVancreed) reported 22 minutes ago

  @Damagehands @AyakaMods exactly it goes to cloudflare and which they don't like the content so they will deny access to their service.

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

• 
  inder (@InderpreetSingh) reported 25 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.

• 
  Taylor Page (@TRPage_dev) reported 26 minutes ago

  We complain a lot about Shopify Support, but I don't think I can anymore. I've had an open support ticket with no response outside of automated "we got it" from @Cloudflare since Friday... Turns out we're still ahead of the curve.

• 
  R.H. (@R3inhard666) reported 27 minutes ago

  @_yorunoken Technically you can host your personal webservers etc with the bandwidth I have and no port forwarding (due to CGNAT) isn't a problem with cloudflare tunnel or just configure wireguard in a cheap vps close to you for port forwarding...

• 
  Josh W (@ItsWelford) reported 29 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.

• 
  Jon (@youarethemeth0d) reported 29 minutes ago

  Facebook is down, Shopify is seemingly okay but this seems like a cloudflare issue

• 
  Chuks 🔶️ (@chuksXB) reported 31 minutes ago

  @nthglsn @Cloudflare Wtf is wrong with them

• 
  🍺 (@8INK5) reported 32 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

• 
  Jims (@JimsYoung_) reported 33 minutes ago

  Anyway, checking in at 20k registered users. 🎉 Some recent takes: — Agents are massively underestimated. Given how fast context windows are evolving, something like Fable can now grind on a task for a full day, fast and good. You can already offload the vast majority of your work to it. The real bottleneck is that most agent runtimes and multi-agent workspaces on the market are way too complex to set up, so the number of people who can actually use them is tiny. The ones who can are using them every single day, but even they keep getting bogged down by runtime and agent management. — One very tangible shift: a lot of legacy infra just can't keep up anymore. Cloudflare outages, for example, have gotten noticeably more frequent. Agent traffic to websites has already surpassed human traffic, and it's only going to grow from here. Infra needs a new foundation. I've got friends already building new switch programming, even chip-level protections. — Defining the problem clearly matters far more than execution. The longer I do this, the more I disagree with certain bets: a) "Agentic payments will necessarily be small-amount, high-frequency." Probably the most off-base one. Agents are going to take a meaningful chunk of transactions, regardless of size or frequency. Say an agent transfers money for you based on an invoice — the amount doesn't matter at all, it's just whatever the invoice says. No reason it has to be small. And frankly there's a whole class of demand here we never even anticipated. b)"Agentic payments must use stablecoins." Not strictly necessary. But a substantial portion will be stablecoins — it really depends on how you define agentic payments… c) "Agentic payment = using an agent to shop for people." Feels like there are ten thousand AI shopping assistants that can already do this — see Shopify's UCP — and after all this time, basically nobody uses it. A lot of the time people just can't articulate their own needs. We need much better ways to collect context. — A lot of the big players really are all talk, surprisingly slapdash. When we were running our security rotation, a prompt injection straight-up exfiltrated the agent wallet private key from a major company whose name starts with "S"… The biggest security problem in agent payments isn't in the payment — it's in the agent. Which is exactly why the right environment and guardrails matter so much. — Whether agents use cards is a genuinely interesting question. If you're ambitious enough, there's a real shot at building a new rail in virtual environments that kills the card networks entirely. At its core, payment is just an authorized, trust-based act of bookkeeping. What cards fundamentally provide is convenience — not having to type in a bank account, being able to complete a transaction at a terminal, a fixed network of transfer channels and information exchange. Every one of those things can be solved by agents instead. Honestly, you can let your imagination run wild here.

• 
  TBPN (@tbpn) reported 34 minutes ago

  FULL INTERVIEW: Cloudflare CEO @eastdakota joins TBPN to discuss why agent traffic has surpassed human web traffic, the company's acquisition of VoidZero, and why concerns about data center water usage are overblown. 2:13 - Why today's infrastructure can't support billions of AI agents 7:38 - Bot traffic vs. human traffic 11:51 - Long-running AI agents are the future, not chatbots 15:15 - The 3 reasons companies are moving AI inference to the edge 17:29 - On concerns about data centers using too much water 19:41 - Matthew Prince on lawsuits from Spain and Italy over piracy 22:10 - Why being a public company is healthier than taking VC money 28:57 - Matthew Prince on hiring 1,111 interns 2:13 - Why today's infrastructure can't support billions of AI agents 7:38 - Bot traffic vs. human traffic 11:51 - Long-running AI agents are the future, not chatbots 15:15 - The 3 reasons companies are moving AI inference to the edge 17:29 - On concerns about data centers using too much water 19:41 - Matthew Prince on lawsuits from Spain and Italy over piracy 22:10 - Why being a public company is healthier than taking VC money 28:57 - Matthew Prince on hiring 1,111 interns

• 
  Drew Studlino (@DrewAstudlino) reported 34 minutes ago

  @Cloudflare FIX Your broken Verify im human Bullshit verification or youll be on the Docket too!! Im Done with all of You #TOSPIRATES!

• 
  manohhoerse (@manohhorse) reported 34 minutes ago

  legitimately **** @Cloudflare

• 
  Stealth Exploit (@stealthexploit) reported 40 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

• 
  Krish Dasgupta (@officialKrishD) reported 41 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 !

• 
  Gennaro (@fourweekmba) reported 46 minutes ago

  Mastercard just launched Agent Pay for Machines. AI agents can now buy things autonomously. micropayments down to fractions of a cent. machine-to-machine. always on. 31 partners: Coinbase, Stripe, Adyen, Cloudflare. settlement: cards + stablecoins via Polygon, Solana, Base. Apple gave agents eyes and hands. Mastercard just gave them a wallet.

• 
  Jeff Liford (@JeffLiford) reported 57 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.

• 
  mycelia (engagic.org) 🌌 (@mycelias) reported 57 minutes ago

  god how i wish vibe coders put in 5% more effort and built on cloudflare with a simple server as opposed to delegating everything to vercel. terrible, evil, predatory company

• 
  andrew johnson (@rsdworker) reported 1 hour ago

  @RailDepartures @bustimes_org could be as facebook is back up thats might be cloudflare issue that is affecting other sites

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

• 
  𝗔𝗿𝗲𝗳𝗶𝗻 (@RimonR23) reported 1 hour ago

  @nthglsn @Cloudflare hope they fix it quick for you