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 (58%)
• Hosting (25%)
• Domains (17%)

Live Outage Map

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

City	Problem Type	Report Time
Ahmedabad	Cloud Services	5 days ago
Le Puy-en-Velay	Cloud Services	6 days ago
Ann Arbor	Cloud Services	8 days ago
Palermo	Hosting	8 days ago
New York City	Hosting	17 days ago
New York City	Cloud Services	1 month 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:

• 
  CerooDan (@danieldmai) reported 3 minutes ago

  Whats going on ? Gmail not working properly rn, websites not loading properly. Don't see errors on cloudflare or AWS.

• 
  Austin (@IamAroke) reported 4 minutes ago

  @nickstewart_ Cloudflare went down because of a regex. That's not a joke, that actually happened.

• 
  Patrick Meenan (@patmeenan) reported 13 minutes ago

  @Cloudflare So awesome, but so many questions! Always transcode or pass-trough zstd if the client supports it (since most browsers now support zstd)? Is this also the case when origins provide compressed assets or only when they don't?

• 
  Tang Vu (@tangvu_dev) reported 18 minutes ago

  I compared Cloudflare Workers and Vercel Edge Functions, two production platforms built on V8 isolates, using a latency-sensitive crypto analytics service. The workload fetched prices and computed OHLC + VWAP over 24 kline periods.

• 
  JK (@_junaidkhalid1) reported 18 minutes ago

  @dillon_mulroy @EffectTS_ the cloudflare support point is the one that actually moved me. a lot of these framework bets fall apart the moment you try to deploy somewhere real. effect holding up there changes the calculus.

• 
  Sergei Aksjonov (@sergeiaksjonov) reported 20 minutes ago

  @Printful Also this: 1 day of my time 1 domain on Cloudflare $20 on AI That’s the whole budget. 10 years ago I thought you needed a Social account of the service, a pretty brand, a PR campaign, the “right” image. This time I just launched it as is from my own account. No polish. No theater. Just shipped. And the first order still came in. Just start as it is. Let it flow.

• 
  Serriff (@serriff) reported 22 minutes ago

  @xbtactics damn i thought we were all buying cloudflare, no?

• 
  Sahil Mondal (@SahilMondal_) reported 23 minutes ago

  The fastest way to crash PostgreSQL is opening direct connections inside Serverless Lambdas. 1,000 concurrent requests = 1,000 DB connections = OOM crash in 2 seconds. Fix: Put PgBouncer or Cloudflare Hyperdrive in front. Keep 20 persistent connections open and reuse them.

• 
  Bryan Beal 🎧 (@bryanrbeal) reported 24 minutes ago

  Pro tip - disable Eero’s DNS and use Google or Cloudflare DNS and 99% of Eeros problems disappear Eero DNS is trash

• 
  Nuvorlane (@nuvorlane) reported 24 minutes ago

  Default `/crawl` is `contentUse: "full"`. A site that sets `use=reference` now 400s you at job start. Aug 31, Cloudflare Browser Rendering. The endpoint honors the Content Signals `use` level in robots.txt. Allowed `contentUse` values: `reference` or `full`. `immediate` is not accepted because `/crawl` stores pages. Mismatch = 400 `Crawl disallowed by Content-Signal directive (purpose or use level)`. Site `use=immediate` blocks every crawl. Site `use=reference` blocks the default. This is a second gate beside `crawlPurposes` (`search` / `ai-input` / `ai-train`). Defaults are all three, so `ai-train=no` 400s you too unless you narrow the array. If the job is RAG/index, declare `reference` and drop `ai-train`. Don't debug a 400 as an outage until you've read the site's `Content-Signal`.

• 
  My1 (@nep.one - Misskey) (@My1xT) reported 25 minutes ago

  @slendidev interesting question would be how fast or slow cloudflare runs on those, as especially on my older laptop it sometimes took a decent while, before needing a click and taking a decent while again, while anubis you dont need to babysit.

• 
  Hanif Carroll (@HanifCarroll) reported 25 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.

• 
  HandsomeHank (@HandsomeHank_) reported 28 minutes ago

  Last night through this afternoon I was pushing Reed (Bot) to maximize my usage after the free reset. I had another reset today at 2pm. I had him create and edit multiple trailers, merge two old websites into one with a new theme, host it on Cloudflare, and create and link a Square store. Then I had him use Printful to recreate old designs from the other site that were never really finished. We also updated a current site so it stays current until we switch over. Reed ended up bringing in another bot (Jules) to help so we could finish before 2pm. Both of them worked hard and stopped at 1:56 so I wouldn’t burn into the next allotment. I have other uses for this week. They left notes to pick it back up if I have extra usage left. Very pleased with their work. @bot @grok 🔥

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 29 minutes ago

  AI-generated Rivet Actors / Workflows are (finally) here 🥂 Some design notes on Dynamic Apps: Powered by agentOS → provides lightweight sandbox-as-a-library V8 isolate runtime → generated apps scale to 0, cold starts in ms, 22 MB per app, native JS performance (not slower WebAssembly like QuickJS) Novel Node.js-compatible runtime → ground truth agents already know & existing libraries work, native performance No nested virtualization → pure userspace, like Chromium & Cloudflare Workers Self-hostable → Dynamic Apps can run anywhere, including Kubernetes, Railway, EC2, etc (which don't support microVM / KVM) SQLite sharded by actor → scalable, fast, cheap, uses no compute when idle A Rivet namespace per app → isolates its actors, separates billing, and nothing to provision Builds run inside agentOS → npm install & build steps in the WASM sandbox, like a Dockerfile without the Linux VM Dynamic Apps also supports plain REST backends & static frontends deploy the same way

• 
  Durp  (@durpsick) reported 31 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!

• 
  Saeid Shahriari (@saeidshahriari) reported 34 minutes ago

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

• 
  James (@jamescoder12) reported 37 minutes ago

  The uncomfortable truth. Your ISP has no incentive to optimize your router settings. They have every incentive to leave them on factory default and every incentive to upsell you when the defaults cause problems. When your Wi-Fi is slow, you call and complain. They test Speed 1 the connection to your modem. It's fine. So they tell you "everything looks good on our end" which is technically true. Then they offer you a faster plan. You pay $30/month more. Speed 1 goes up. Speed 2 the Wi-Fi to your devices doesn't change. Because the bottleneck was never the pipe coming into your home. It was the 6 feet between your router and your laptop. When your firmware is 4 years out of date, they don't push an update. When your channel is congested, they don't suggest switching. When your DNS is slow, they don't mention Cloudflare. When your channel width is halved, they don't widen it. When your security is on WPA2 with the factory admin password, they don't flag the risk. Every free fix that would make your Wi-Fi faster is a fix that prevents them from upselling you a more expensive plan. Every month you rent their router is $14 in revenue for a $60 device they deployed years ago. The rental has no end date. The equipment depreciates. The revenue doesn't. He called his ISP 4 times. They suggested upgrading twice. He upgraded twice. He paid $360 extra over a year for a faster plan that didn't make his Wi-Fi faster because the problem was never the plan. It was 9 settings his ISP could have fixed in a 5-minute phone call. They chose to sell him a faster highway instead of widening the off-ramp. "Your ISP isn't slow. Your settings are. And the company delivering your internet profits every month you don't know the difference." 9 settings. 15 minutes. $528/year back. Faster internet on a cheaper plan. The router was never broken. The defaults were designed by a company that makes money when you think it is.

• 
  Adie (@wbvend) reported 41 minutes ago

  @levelsio @Cloudflare My agent can buy on Namecheap API without issues Then goes on to build + deploy on the VPS everything is very easy now I also have expired domain hunter which pulls down then checks on DataforSEO 🎉🥳

• 
  Andy Knowles (@andykn101) reported 42 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.

• 
  DUNGEON-00X 💿📀 (@Dungeon00X) reported 42 minutes ago

  I think Cloudflare is about to go down, everything is loading slow again.

• 
  Tim (@Trendy_Tim) reported 45 minutes ago

  @The_Baron_X150 @SportingNest @Cloudflare That was crowdstrike, cloudflare take down half the internet with some dodgy js or dns config.

• 
  Ben Hocking (@bmwhocking) reported 47 minutes ago

  @rustie5555 There are a lot of round robin API calls for content. Works fine if you are close to their US data-centre. Sucks for us. They are using Cloudflare, I don’t believe they are processing at Cloudflare’s edge, just caching content. They need better & faster timeline building.

• 
  COLLINSEO (@alexcollinseo) reported 48 minutes ago

  Breaking news! Your site might start blocking AIs from September 15th.. And if you block them, you won't show up in AI answers. The good thing? It takes a sec to unblock! This setting is inside Cloudflare. You might not even know your website uses Cloudflare because it works in the background as a CDN, helping your website load faster. If you check your website using the tools I mention, you can find out whether Cloudflare is being used on your site. Cloudflare seems to have taken this step because of how AI companies are crawling websites, and honestly, I don't completely disagree with the reason behind it. But having AI crawlers automatically blocked from September 15 could be a problem if you want your business to appear in AI answers. The setting is inside Security Settings. Look for the AI crawler control and make sure it is set to allow rather than block. This is especially important if AI visibility is part of your strategy. With one of my clients, we went from zero to around 500 visitors from AI traffic in two months. And what I did was exactly what I explained in the video. If your AI crawlers are blocked, you're potentially closing the door on that traffic before it even has a chance to reach you. #SEO #DigitalMarketing 👇🏼 Comment VIDEO for the FULL VIDEO BREAKDOWN

• 
  Muntasir Mallik (@muntaxir04) reported 48 minutes ago

  @acolombiadev @Cloudflare Maybe it's Gemini? We never run out of searches bec nobody uses it anymore

• 
  Eli Yumn (@EliYumnik) reported 52 minutes ago

  @acolombiadev @Cloudflare GitHub for CI/CD and hosting the damn internet’s repos Supabase Resend Replit Gemini Eleven labs

• 
  Jonathan.G (@Jonathan2134) reported 55 minutes ago

  In reality CloudFlare makes searching the internet worst place because number of websites you can't use despite not VPN.

• 
  Jeff Weinstein (@jeff_weinstein) reported 55 minutes ago

  Cloudflare, known for internet-scale internet infrastructure, is now building internet-scale billing infrastructure, in partnership with @stripe. (Detailed data about usage and cost is now a fundamental element of any service.)

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

  @DanielZahoor But Cloudflare DNS routing is so bad.

• 
  Kevin Minnelli (@minnelli) reported 1 hour 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?

• 
  Henry C | DevSecOps (@_theCyberDoctor) reported 1 hour ago

  4/ The part I'm proudest of isn't the happy path. It's what happens when the web fights back. CrunchBase threw a Cloudflare captcha → agent refused to bypass it, wrote down why, moved on. LinkedIn threw a sign-in popup → agent closed it and read what was visible. Chrome crashed → agent reloaded.