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 (36%)
• Cloud Services (31%)
• Hosting (18%)
• Web Tools (10%)
• 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	5 days ago
London	Domains	7 days ago
Noida	Hosting	20 days ago
Jewar	E-mail	20 days ago
Braga	Web Tools	20 days ago
Noida	Cloud Services	21 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:

• 
  zeb (@zebassembly) reported 6 minutes ago

  @astuyve @boristane Not to get too into the weeds but the concern is where the trace context gets inherited and where we check the users tracing configuration. Before a request ever goes to the Workers runtime there's our FL2 (essentially the Cloudflare webserver) that actually accepts the http connection for various reasons we want that part that isn't entirely related to Workers to be aware of tracing so we can do cool things in the future. This entails creating a way for FL2 to fetch the user's tracing config (sampling, if they want to enable propogation, etc), passing that context through FL2, passing it to the Workers runtime, and then when the Worker does a fetch we need to pass it back through to FL2 so we can potentially attach the context header. None of this is strictly about just parsing that trace context header, more about threading configuration and ceoss-service communication.

• 
  Ann the cat herder (@ann1knit) reported 8 minutes ago

  If cloudflare is so buggy and easily broken or hacked, why the frell hasn't someone come up with a better system or solution?

• 
  Andrej Ruckij (@ruckiand) reported 10 minutes ago

  Online stores are panicking that AI bots are crawling their site and "stealing" their catalog. So they hit the one-click Cloudflare toggle and block everything. Most are solving the wrong problem — and quietly hurting themselves. 🧵

• 
  Armeet (@armeetjatyani) reported 18 minutes ago

  @tomhaerter Primarily Cloudflare now. GCP support is extremely sluggish

• 
  Martin Stepanek 🏳️‍🌈 (@techseovitals) reported 19 minutes ago

  🟣 Underrated #TechSEO Tip GPTBot, ClaudeBot, and PerplexityBot all respect robots.txt. Block them and your content never appears in AI answers. Worth flagging that Perplexity's compliance has been disputed – Cloudflare found evidence they used undeclared crawlers to bypass robots.txt. I see site owners block these crawlers without realizing they killed an entire traffic channel. Check your robots.txt right now. Look for blanket `Disallow: /` rules targeting AI user agents. You might be invisible in AI search and not even know it.

• 
  𝗶𝗮𝗺𝟰𝘅 (🌷,🦈) (@iam4x) reported 20 minutes ago

  @DegenCT @TheCryptoNexus - Proxy the ui api of hyperliquid through cloudflare to fetch sub-accounts - Then implementing the spot trading with support of sub-accounts

• 
  Pranjal Soni (@pranjalsoni_) reported 23 minutes ago

  after spending more than $1k/mo with replicate, they don't even consider replying to their support emails anymore thanks to cloudflare acquisition i am fixing and replacing their models that stopped my app in the middle of the night before going to sleep

• 
  seika (@srrw2s) reported 27 minutes ago

  OMG cloudflare,only if you could allow not using edge functions ,we would have not broken up

• 
  Ankur Agrawal (@ankuragrawal420) reported 30 minutes ago

  @araseb_ The ease of use primarily and native support for nextJs application out of the box with just 1 click. They have been charging people more and more with all the ridiculous upsells. They changed my build configuration to turbo automatically and charged me for build minutes. Thats when I decided to move to Cloudflare and its completely free

• 
  Jason Fleagle (@jjfleagle) reported 32 minutes ago

  @Cloudflare Fake identity at AI scale turns admissions into an operations problem, not just a fraud problem. The workflow needs signal correlation, escalation rules, evidence packets, and human override.

• 
  Ozgur Ozer (@ozgrozer) reported 34 minutes ago

  Today I decided to archive some of my failed projects. I never made money from them so it's time to let them go. I spent more than a year and some money on these 5 failed projects but still it's not a lose. I learned a lot about idea validation. I started my indie hacker journey 2 years ago with Next AI Tool directory. I scraped the internet so the site wouldn't look empty. There were 46k AI tools in the website on launch but a couple of weeks later Google blocked the domain on the search results lol. I made my first internet dollar with AI Renamer so it teached me lots of things about making a useful product, educating and supporting customers, marketing etc. It made $7k in the last year and still making a little so I'll keep it. Now my focus is on Grape, the AI note taking app. I only made one post on Reddit about the beta version of desktop app and since then it made 5 lifetime sales and currently has 1 active subscription. Now working on the mobile app. The failed projects, they were on my VPS using the CPU and memory. I removed their auth and dashboards to only keep their landing pages. That way I turned them into static sites and moved them from my VPS to Cloudflare Pages to host free. I'll still renew the domains because I still want to see them in the future. I can fail again but always will be learning from my mistakes and keep building until I make it.

• 
  Axel Hardy (@fraxool) reported 35 minutes ago

  Just like last time, the Shopify API seems extremely slow and is timing out. It might be related to Cloudflare. I'll probably postpone the expiring token migration I planned for today, as a failure mid-process could leave some users with broken tokens.

• 
  Aaron Ware (@EarnWhere) reported 35 minutes ago

  @Cloudflare 's PDF endpoint is so good. I spent hours trying to speed up PDF creation inside of my architecture and did so much hacky **** to achieve a decent-enough UX. Just implemented Cloudflare's endpoint and happily ripped all that out for substantially better results.

• 
  SpikeViper (@spikeviper) reported 42 minutes ago

  I am once again asking @Cloudflare for a response on why their support is radio silent on what is now a shady billing situation

• 
  Gilgamesh (@CaseCold56389) reported 44 minutes ago

  The network is owned by its contributors. Not by a corporation. You already know centralized infrastructure: • AWS owns the servers your apps run on • Google owns the data centers training AI models • Cloudflare owns the network protecting your traffic

• 
  Frank Karro (@imfrankkarro) reported 47 minutes ago

  So I stopped doubting and started building. Then hit a wall: a Cloudflare billing bug killed my infra setup. 3 hours convinced I'd broken something. Turned out to be an incident on their end.

• 
  Utopian Contributors (@utopiancontrib) reported 48 minutes ago

  We figured out a way to end what seemed like a never ending story: JavaScript bloat This wasn’t Google or Microsoft or Mozilla or CloudFlare or Vercel. It was the Utopian Contributors LLC. But this was just the beginning. The future of the web is ultra-efficient.

• 
  The AI Entrepreneur (@ai_in_it) reported 50 minutes ago

  the big AI labs trained on most of the public web. now a ton of those same sites are locked down tight. cloudflare, login walls, bot checks you basically have to pay to clear.

• 
  96 (@gboncoffee) reported 50 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.

• 
  Cloudflare (@Cloudflare) reported 52 minutes ago

  We're increasingly seeing bad actors using AI and automated bots to flood online admissions with fake identities—causing massive disruption across the higher education sector. Let’s talk solutions. Join Cloudflare during Jisc Networkshop, at Nottingham Trent University, to learn how to fight back: 📍Find us at booth 30 📷 Talk is a must-attend! 🎁 Really good merch

• 
  John Andrews (@johnandrews) reported 53 minutes ago

  I was on one of these lists and it was very unfair.... a test QnA site deployment I can *almost* understand spamming, but even our best hardened instance in production was such a target, I eventually shut it down, rather than have it consume all backend attention and eventually pay Cloudflare to protect it. 30,000 useless test attacks per hour at one point... about 98% of actual traffic. And that was in the days when 80% of the script kiddies were manually starting/stopping their runs.

• 
  That Boosted Snep 🔜 Megaplex (@witch_the_snep) reported 54 minutes ago

  @joesmith1457 @DoorDash_Help It looks like its cloudflare thats having issue. That who hosts doordash’s website

• 
  Vedant Anand 🐲/acc (@Vedantsx) reported 56 minutes ago

  @eastdakota @QuinnyPig @eastdakota please fix opennext for cloudflare 🙏🙏 I've tried to inform everywhere, for me shifting from Vercel to Cloudflare through opennext took a lot of pain

• 
  Lifeis2-D (@Lifeis2D) reported 57 minutes ago

  Cloudflare: BOTS HAVE OVERTAKEN HUMANZ USING THE INTERNETS FOR THE FIRST TIME Also Cloudflare: *ASSUMES ALL VPNS ARE BOTS, ****** "VERIFICATION" CHECKBOX FAILS* Gee, do we think this "assume vpn users are bots, verification broken" thing and the first thing could be related?🤔

• 
  Puneet Patwari (@system_monarch) reported 57 minutes ago

  Tweet 3/5 Picking the algorithm is half the decision. The other half is: where do you enforce the limit? Most teams slap rate limiting at the API gateway and call it done. That's one layer. Production systems need at least two. Here's why. Layer 1: API Gateway (the front door) This is your first line of defense. Every request passes through here. Set global rate limits: "no client can exceed 1000 requests per minute." This catches: - Runaway scripts - Misconfigured clients - Basic abuse - Your own batch jobs (ask me how I know) Tools: Kong, NGINX, AWS API Gateway, Cloudflare. All have rate limiting built in. Layer 2: Per-service limits (noisy neighbour protection) You have 10 microservices. Your search service can handle 5000 rps. Your export service can handle 50. Without per-service limits, one client hammering /export at 200 rps takes that service down. And because /export is down, health checks fail, the circuit breaker trips, and suddenly other things start breaking too. Per-service rate limits prevent one endpoint from eating the capacity of another. Layer 3: Per-user limits (fair usage) One user is making 10,000 API calls per minute. Every other user is making 50. Without per-user limits, that one power user is consuming 99% of your capacity. Per-user limits: "each API key gets 100 requests per minute." Fair. Predictable. No single user can starve everyone else. This is also where you differentiate pricing tiers. Free tier: 100 rpm. Pro: 1000 rpm. Enterprise: 10,000 rpm. Rate limiting is literally your pricing enforcement. Layer 4: Per-endpoint limits (not all endpoints are equal) Your /search endpoint can handle 10,000 rps. It's fast, cached, lightweight. Your /generate-report endpoint does a 30-second database aggregation. It can handle maybe 10 concurrent requests before the database starts crying. Same global rate limit for both? That's a disaster waiting to happen. The heavy endpoints need tighter limits. The rule: at minimum, use two layers. Gateway-level for global protection. Per-endpoint or per-user for granular control.

• 
  Hermann (@dhlotter) reported 58 minutes ago

  Cloudflare Pages said Active. CLI said Active. URL returned old content. Pages uses 'Active' to mean the deployment slot is live, not that the latest commit finished building. My 'fix' sat undetected in the build queue for two days. Watch the stage statuses. #cloudflarepages

• 
  Lorenzo Castro (@Lorenzo__CB) reported 58 minutes ago

  @CloudflareDev cloudflare-api codemode mcp auth seems to be down, OAuth flow seems to work but the mcp alway returns "invalid_token". Have tried both codex and cursor clients, same result

• 
  Roy (@__roycohen) reported 59 minutes ago

  @tekbog Damn even I got into Google Startups, I actively think that I got in out of sheer luck at this point cause everyone else denied (including Amazon/Cloudflare)

• 
  Colleen (@PiedViper) reported 1 hour ago

  @LiberN8 @yacineMTB Who is "they"? Unless you're talking about Cloudflare, who has significant legal and economic constraints on how aggressively they can take down sites, blacking out a random social media site worldwide requires cooperation and can be a game of whack-a-mole, especially if some servers stop accepting certain servers' pushes. The entire key-signing rituals of ICANN are only meaningful if most people accept them as authoritative. If they start messing around with letting one country dictate policy for the world, there's not going to be one main internet any longer.

• 
  Jeff Needles (@jsneedles) reported 1 hour ago

  @Hussain_Joe @_ceifa Well, the key is its pretty much managed, just not e2e. Like it's Cloudflare Workers + pipelines + queues -> CH cloud. All managed services! Just the raw volume makes most "pure" managed analytics providers extremely prohibitive -- like prob 10x the cost at least. Of course, there's other options that are really self hosted that are less analytics-focused... or things that rely more on object storage as the source of truth (like R2 SQL, which would actually prob be cheaper) But I've put in maybe 10 hours of necessary maitenance in the last year, occasionally the analyst who uses the system will ping me for questions/advice etc -- but raw infra/system wise, like 0 issues!