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 (39%)
• Domains (22%)
• Web Tools (22%)
• Hosting (11%)
• E-mail (6%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	12 days ago
Los Angeles	Cloud Services	13 days ago
Paris	Cloud Services	29 days ago
New York City	Hosting	1 month ago
Manchester	Domains	2 months ago
Angers	Cloud Services	2 months 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:

• 
  City of Hats (@CityofHats) reported 2 minutes ago

  @signalapp @Cloudflare Signal’s AKV is a useful improvement, but “automatic” deserves an asterisk. Signal still operates the central key directory, while Cloudflare and Trail of Bits are explicitly trusted auditors. AKV proves consistency of the identifier → key mapping; it does not prove the identity behind that identifier. Even more interesting: today, verifying another user still requires knowing their phone number, and the user must explicitly open Safety Number and select “Verify automatically.” So this is better tamper detection — not the elimination of trust. The architectural question remains: why should identity/key discovery depend on a centralized directory and external witnesses at all?

• 
  Sai Krishna ⚡️ Superblog.ai (@_skris) reported 3 minutes ago

  Can’t really fkn keep up with this company When I moved superblog (v2) from netlify to Hetzner + cloudflare, I implemented caching layer tilting towards hetzner vps because CF’s purge limits were not so great. Recently Claude told me that they give like 5 purges/second for $20/mo and 10/min for free. Seriously? I simply rewrote the caching layer with on-demand purges for superblog’s customers. Essentially the load hitting the hetzner vps is zero until a customer makes any change. Superblog will grow to a large scale even before I pay them anything. They just hate to make money I guess.

• 
  Salina Mendoza (@inababi) reported 7 minutes ago

  @a_shimanski @Cloudflare Waiting for the gimmick but nothing has arrived. Almost done migrating every single domain from my old registrar. Never going back.

• 
  Finance District (@FD_XYZ) reported 7 minutes ago

  Cloudflare just opened its network to AI agents: wallets, identities, payments. The company routes a fifth of the internet. When it starts building for agents, and Visa, Mastercard and Stripe are on the same rails, this isn't a crypto trend anymore. Agent payments have gone from an interesting idea to the thing everyone's building.

• 
  Hamid Siddiqui (@hamidInventions) reported 8 minutes ago

  @wickedguro @markgalkev tbh now not 100% sure if it might be the same reason since you mentioned everyone getting this same time but i strongly feel it would be Cloudflare only, I faced this issue few months back. When i was debugging this I disabled Cloudflare proxy for a while and tested posting the posts that were failing to post on TikTok, and they worked fine. I also used to face similar issue with fal.i/replicate where they would randomly fail to get the R2 image url i passed for image generation. It was fixed as well. The exact steps i took I don't recall, would have to check what settings i did change eventually.

• 
  Mark (@peyoteheadlight) reported 10 minutes ago

  crazy how cloudflare warp fixes every isp based issue i have how did i only find out about this a few months ago

• 
  ./ivan (@sloaxleak) reported 12 minutes ago

  @a_shimanski @Namecheap @Cloudflare Haha. Or just pay for a reliable email service: Google Workspace, Microsoft 365, or a Proton subscription with a custom domain. There are options. I love Cloudflare, but not everything needs to be solved by them

• 
  Kawa Entertainment (@kawa_entertain) reported 19 minutes ago

  @addzeeyy @Cloudflare That's what I've been doing all morning, unfortunately. All we can do is hope they get taken down quickly.

• 
  frango (@franguinlol) reported 23 minutes ago

  @drewlevin Thanks for the answer. I haven't made any changes to my internet or hardware; the only thing bothering me is the routing problem, which forces me to use Cloudflare sometimes because It becomes unplayable.

• 
  gnivler (@Yn5Xi9PQSFcY7UU) reported 26 minutes ago

  @godzuki2fu sorry lol. reworded: changed to my other twitter account, Cloudflare anti-bot page wouldn't pass. When I tried from phone it revealed they had locked the account, again. Moral of the story is it was a bug in twitter, probably not unlike your reply issue

• 
  kidariseyo (@kidariseyogt) reported 26 minutes ago

  @chanwalrus @NamecheapCEO At this point if you are serious about hosting, use a domain provider like @Cloudflare I moved services that where in NC to CF workers as most of others apps hitted NC endpoint to send data. a CF worker matching exact down url saved the day, staying in CF.

• 
  ruminations (@amphib0ly) reported 27 minutes ago

  signals need execution and a lot of people who want to use q are very busy they are founders / builders and are down to try stuff but also just want to put money in a wallet and let it work for them no amount of UI polish will make them want to use the UI and adding more assets won't sway them - they just want to buy convenience so, we made a baby sister for Q named Cassie - short for Cassandra, look it up cassie will help users execute trades on Quotient signals in their local environment or in a deployed, cloudflare run-time they control users bring capital Q brings intelligence Cassie brings execution

• 
  R (@dnagabut) reported 28 minutes ago

  Cloudflare announced programmable wallets built for AI agents, with preset spending limits and merchant restrictions in the design. Nothing has shipped yet. Right now you can reserve a handle. Funded account wallets, virtual wallets and programmable agent spending are all due in the coming months. Read the feature list again, because it is a permission model, not a payments product. The moment you let an autonomous agent buy things, you inherit a problem crypto has been failing at in public for years. How do you grant a program the ability to spend without granting it the ability to spend everything? DeFi's answer was token approvals. The result is a very long list of drained wallets where nothing was hacked at all. Someone approved unlimited spending to a contract years ago and forgot. So Cloudflare's version is delegated authority with a cap and an allowlist, plus anomalous-spending alerts that escalate to a human. Sensible. Also the bare minimum. And these are stablecoin wallets settling over x402, so this isn't a payments industry learning from crypto's mistakes. It is crypto. The layer above it is still wide open. An agent that can be talked into a purchase by hidden text on a web page is still an agent that can be talked into a purchase. Caps limit the blast radius. An anomaly alert only fires once the spending already looks strange. Neither one touches the trigger. Follow @dnagabut if you like your tech news with the catch included.

• 
  Dragonfang1911 (@dragonfang1911) reported 34 minutes ago

  Make 3 times, the anti bot algorithm is getting way to out of hand, having to verify through cloudflare which has had known issues.

• 
  Dain Bramage Entertainment ❄️ (@EOTWoffgrid) reported 34 minutes ago

  Going to use @Cloudflare services for our website. should resolve the email issue and add new features/security... i hope.... all a learning process! I did save the original zone file for the site.... JUST in case... 🫣🙄😜

• 
  Artyom Shimanski (@a_shimanski) reported 35 minutes ago

  @XJosephCox @Cloudflare yeah, hard caps would fix half the horror stories

• 
  VM Varga (@vmvarg4) reported 35 minutes ago

  @bot just got me a refund of 400 eur. I had an invoice for car rental sitting in my inbox for a while. I have no time for this ****. It translated the invoice, checked my diamond status, opened the dispute in chat, and soon enough I had 400 out of a 2300 rental refunded. If you can do it, it probably can. I will probably stay with Openclaw/Hermes/Claude, but I am testing this to deploy to less tech-savvy folk at my company. So far, it’s great. It works out of the box. Agents chat with each other. They got their own email in/out in Cloudflare. They joined Google chat rooms as an app (that it set up). Also, it is good with technical stuff, engineering (civil), specifications, Excel, and integrations. Rooting for this.

• 
  VC Intern (@the_vc_intern) reported 36 minutes ago

  Cloudflare is not shutting down Google Search on September 15. It is forcing Google to decide what Googlebot actually is. Cloudflare’s new controls divide crawlers into three jobs: Search, Training and Agent. Search remains allowed by default. Training and Agent traffic will be blocked on ad-supported pages for new sites and existing free customers that keep the new defaults. A crawler doing multiple jobs inherits the strictest rule. That puts Googlebot in an awkward position. Cloudflare classifies it as both Search and Training. A publisher that welcomes search indexing but rejects AI training can therefore block the entire bot. For years, bundling those jobs gave Google leverage. Publishers depended on search traffic, so refusing the crawler also meant disappearing from discovery. Cloudflare is moving that decision from a line in robots.txt to enforcement at its network edge. Google now has three choices: separate its crawlers, convince publishers to permit both uses, or lose access to pages that still want search traffic but no longer accept training as part of the bargain. The web is not dying here. Its access contract is being renegotiated. Robots.txt was a request. Cloudflare is turning it into a gate.

• 
  Lý Quang Tùng (@LQuangT60430837) reported 37 minutes ago

  Hi @Cloudflare, I'm being wrongly billed for R2 storage deleted a year ago. Opened ticket 02264237 a week ago with no reply, and my account faces suspension on 26/08. Can someone please escalate this to the support team? Thanks! PS: Past tickets were never answered either.

• 
  fire_bol (@firebol226860) reported 38 minutes ago

  @jdanielenj @signalapp @Cloudflare Your response tells me enough. Learn to test security yourself instead of blindly trusting company claims or public source code. By hacked I don’t mean an outside breach I mean Signal’s developers could potentially monitor users activity. its like a hacked platform by thier own D

• 
  Gregory (@_studable_) reported 38 minutes ago

  just got my cloudflare bill and it's over $17, so i will be hereby shutting down gexx

• 
  1280 MHz (@1280MHz) reported 45 minutes ago

  @a_shimanski I use MIAB, mailinabox. I think there's something similar these days that runs in a docker container. The hardest part of configuring an email server is locking it down and then routing the DNS. You can surely handle it, especially if you can use cloudflare API to set DNS.

• 
  Josh Mullins (@ETFbreakouts) reported 45 minutes ago

  I think there’s a lot more middle ground here. $APP slightly missed revenue expectations and gave an in-line guide. That matters at this valuation. But revenue still grew 53% and adjusted EBITDA grew 58%. That isn’t the next $TTD yet. Advertising is splitting into winners and losers as AI changes how people discover information: • $U Strategic Grow +63% • $META revenue +28% • Google Search ads +17% • $TTD +12% • $TBLA +2% • Google Network ads -1% Cloudflare recently said the ad-funded open-web model is breaking because AI answers the question without sending a human to the publisher’s page. That is a much bigger threat to publishers and open-internet advertising than to closed-loop performance platforms. The real question is whether AXON keeps proving conversion and attracting more ad spend. One quarter didn’t answer it.

• 
  erik@try.works (@trydotworks) reported 46 minutes ago

  @benswerd Calling cloudflare mid wtf

• 
  Alex Greenland (@ajrgd) reported 46 minutes ago

  cloudflare could never

• 
  orlie (@sunglassesface) reported 50 minutes ago

  @FreedomFries93 @joshmanders @PlanetScale Yeah, I used AWS in the past and honestly it wasn't that bad once you get past the setup. My point is not about comparing cloudflare to AWS. My point is the confusion in product offering within cloudflare itself

• 
  Carl B (@CarlB_jr) reported 52 minutes ago

  Being in IT I'm constantly harassed to find use cases and implement AI for almost everything. We've found some use cases and several that just don't make sense. But I always tend to play with things at home to really see what things can do and learn without the guardrails put in place at work. Last night I decided to give they API keys to my network to an AI model and told it "I've got ubiquiti hardware, investigate hardware and software settings. Provide any suggested tweaks or fixes to harden my network and improve performance." It went through and found security holes I thought I'd fixed a long time ago, it found several ways to get better performance, etc.. I did a manual backup and told it to go for it before going to bed. This morning I woke up and found it'd made a total of 92 changes to my network, my NVR, my cameras, apparently finding my CloudFlare API key in a config file and then using that to create a CloudFlare Tunnel, closed off my open ports and killed off my Port Forwarding rules. Redid my firewall changing it from IP based to Zone based. Setting up a new VLAN (for a total of 4 now), moved things around to the new VLAN setup, creating documentation for me, an architectural design, security review, security design, network diagram. Then at the end rotated all of my API keys, uploaded them to Bitwarden (found it's way into that as well through a config file), and then purged the new keys from it's memory. OK, I'm sold for certain tasks. Also a little scared/surprised on how it went through and did so much with other services. That's what I get for telling it to just do everything without any approval from me (because I was going to bed).

• 
  SpyroWiki (@SpyroWiki) reported 52 minutes ago

  The indie Spyro Wiki is currently down at the moment due to issues with Cloudflare. It will be up soon.

• 
  Kartik (@Kartik8010) reported 52 minutes ago

  @Cloudflare can we please fix the bug where we have persistent volumes for h containers 🫡

• 
  Artyom Shimanski (@a_shimanski) reported 54 minutes ago

  @JEROMEFARAILL @Namecheap @Cloudflare to be fair it was a cooling failure at PhoenixNAP, not an attack. the single region setup is the real issue