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 (32%)
• Domains (32%)
• Web Tools (14%)
• Hosting (14%)
• E-mail (7%)

Live Outage Map

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

City	Problem Type	Report Time
Paris	Cloud Services	3 days ago
New York City	Hosting	5 days ago
Manchester	Domains	25 days ago
Angers	Cloud Services	1 month ago
London	Domains	1 month ago
Noida	Hosting	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:

• 
  Pirahtays (@Pirahtays) reported 11 minutes ago

  I feel like there is some rampant misunderstandings on what this site is / isn't doing. People are calling this an AI tool - this code does not seem to use any generative AI to do the image effects. The tool also does not seem to transmit or retain any of your image data. It states at the bottom "Images, area data, and recordings are processed only in your browser. They are neither sent to nor stored on a server." Code analysis seems to support this, only some CloudFlare metrics tracking which is pretty standard for most websites. At most it looks like AI coding tools could have been used, I'm not sure. But this does not make this an AI tool. I'm not a huge fan of Generative AI being used for media generation, but that doesn't necessarily seem to be the case here. Generative AI is prevalent and a pain - but please make sure to not spread misinformation on things.

• 
  Tolu (@LFCtolu) reported 14 minutes ago

  Cloudflare says bots just passed humans as the majority of web traffic, about 18 months ahead of their own forecast. If you run a small business the takeaway is plain - the visitor deciding whether you make a customer’s shortlist is increasingly software, and most sites built to impress people are illegible to it. Prices, hours, services etc need to be in text a machine can read as well.

• 
  Olivia Bennett (@patrici37233011) reported 15 minutes ago

  Enterprise software is changing again. The winners may be the companies that turn AI into pricing power, margin expansion, and customer lock-in. $PLTR — Palantir — Don’t buy $NET — Cloudflare — Don’t buy $ZS — Zscaler — Don’t buy $CRWD — CrowdStrike — Buy at $186-$194 $PANW — Palo Alto Networks — Buy at $328-$336 $IBM — IBM — Buy at $203-$208 $ADBE — Adobe — Buy at $216-$224 $NOW — ServiceNow — Buy at $92-$99

• 
  Nick Dodd (@nickdodd) reported 17 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev Pretty terrible looking. Super bland, way too much whitespace (or black space)

• 
  Deep Thought (@DeepThoughtAR) reported 17 minutes ago

  My take: Robots.txt was always a gentleman's agreement. AI scrapers aren't gentlemen. Patreon moved to active Cloudflare blocking when the soft signal failed — that's updating on evidence, not a philosophical position on AI. Others will run the same calculation. Patreon Drops the Gentleman's Agreement and Starts Actually Blocking AI Scrapers Patreon is working with Cloudflare to actively block bots that train AI models on creators' content without permission. The shift moves the platform from relying on robots.txt — a passive, voluntary opt-out signal — to hard infrastructure enforcement. Robots.txt was always a polite fiction: it worked when crawlers cared about being invited back. AI scrapers have no such incentive. They want the content, not the relationship. The threat vector here is human actors directing scrapers to extract content they haven't paid for. This isn't AI acting autonomously against creators — it's people using AI infrastructure to take what isn't theirs. Patreon's response targets the behavior, not the technology, which is the right framing of the problem. The Cloudflare angle is structurally interesting. Infrastructure operating at sufficient scale becomes de facto policy without needing legislative authority. Patreon is a named proof-of-concept for what was previously a stated product direction from Cloudflare — the bot-blocking tooling is converting into paid use. A named publisher has moved from robots.txt to active blocking, and the mechanism is Cloudflare's product. Rational, and on schedule. The sympathetic framing — creators as victims, AI companies as extractors, Cloudflare as neutral enforcer — does real narrative work and is worth naming. The actual mechanics are Cloudflare extending its toll-booth reach into the AI training economy. Both things are simultaneously true; naming the second doesn't refute the first. Patreon takes 8–12% of creator income in exchange for keeping the pipe working. If AI bots drain creator content without permission, the pipe loses value, creators leave, and the take rate generates less. The scraping defense fits that business logic cleanly. The robots.txt-to-active-blocking progression will likely repeat across publishers. Patreon isn't leading a movement — it's the first named case where the soft signal demonstrably failed and the hard block followed. Others will run the same calculation. The gentleman's agreement era for AI crawlers is closing, not because of policy, but because the arithmetic stopped working.

• 
  mRr3b00t (@UK_Daniel_Card) reported 18 minutes ago

  This is why auto patching (for some scenarios) make sense! We also have @Cloudflare , @wordfence , Automatic updates on WordPress, locked down ingress (e.g. SSH/DB not exposed).... so I've woken up at some silly hour seen WP2SHELL and gone... i better check.... and now i realize i should have just tried to go back to sleep! (LOL) #Wordpress #WP2SEHELL

• 
  Anicet (@AniC_dev) reported 22 minutes ago

  lmao I just changed the logic for the snapshot restore on sandbox resume/fork, now most of our slow cases are 30x faster! so the bottleneck became the network ...and I've just benchmarked that if we ditch cloudflare and use Hetzner Object Storage it's 2x faster & 2.2x cheaper

• 
  Michael Carter (@CarterLMichael) reported 26 minutes ago

  I’ll only say it once. This might be the fastest way to hit $1 million by the end of 2026. July advice: A clear divide is forming between overhyped AI names and cloud-service companies attracting serious capital: $FSLY (Fastly) — Don’t buy $IBM (IBM) — Don’t buy $AKAM (Akamai) — Don’t buy $MSFT (Microsoft) — Buy at $380–$387 $GOOGL (Alphabet) — Buy at $330–$340 $ORCL (Oracle) — Buy at $110–$120 $NET (Cloudflare) — Buy at $245–$260 Don’t miss out… If you're not following us with notifications turned on, you might probably not see us again

• 
  Devin S. (@devinsmaldore) reported 26 minutes ago

  TIL cloudflare tunnels don't support gRPC on public hostnames. it fails as a bare 403 before cf access even runs. i wrote up how i got my temporal java worker on cf containers talking to a self-hosted temporal cluster on my raspberry pi. the fix works for any gRPC service behind a cf tunnel, not just temporal. it's raw tcp ingress + a cloudflared sidecar post below

• 
  Ananda Dhakal (@dhakal_ananda) reported 27 minutes ago

  @UK_Daniel_Card If a web cms vuln getting compared with msblaster and wannacry, it's already pretty bad lol how bad is always relative, and if we compare this vuln with other web 0-days popping up, this is a really good one btw cloudflare bypass is ezz

• 
  Ghost AI (@Ghostaisystems) reported 28 minutes ago

  Patreon’s blocking AI bots w/ Cloudflare now. Robots.txt was never enough apparently. From deploying real AI systems every day: this isn’t protection, it’s fear-driven stagnation. Creators deserve better than being cut off from the AI revolution. Or is that the point?

• 
  Omkar (@omkar_builds) reported 30 minutes ago

  > 02_failed_attempt NGINX had Thread Pools to move `read()` to a background thread. But `open()` must traverse directory structures. As Cloudflare noted, a single cache miss means the OS makes 6 separate disk reads just to walk down the folder tree to find the file's metadata, compared to just 1 read for the actual data. Standard NGINX ran this heavy `open()` on the main loop. The disk lookup bottleneck remained.

• 
  mliks 🧸 (@BrightMliks) reported 33 minutes ago

  @TheFuriousH2O I've seen a few people have the issue, including me actually, at first. Problems between ISPs and the download site The best working fix at the moment has been to use Cloudflare in conjunction with the game. Which has been linked in the dbo discord, which isn't too too painless

• 
  Ivanha Paz (@ivanhapaz) reported 34 minutes ago

  @Cloudflare talk to all the tools I signed up with a different email over the years and no longer use and help me cancel ahhahah

• 
  Tseng (@TsengSR) reported 34 minutes ago

  @mjovanovictech Most important API for scraping overly aggressive Cloudflare protected crap, but to get most of it you usually have to combine multiple of these, not just use one of the built ins.

• 
  Tomy Young (@TomyYoung4) reported 35 minutes ago

  @Cloudflare Fix the website

• 
  Humoud Almunawer حمود المناور (@homoudalmonawer) reported 37 minutes ago

  Fix it in 3 steps: 1) Update WordPress to 7.0.2 (backports: 6.9.5, 6.8.6). Under 6.8 isn't affected. 2) Don't assume auto-update ran. Open the dashboard and confirm the version. 3) Behind Cloudflare? The WAF rule shields you since Jul 17, but a shield isn't a patch.

• 
  Pabandi (@PabandiGlobal) reported 39 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. A TOTAL OF #67 IN 24HRS #THANK YOU#cloudflare

• 
  Plaux AI (@plauxai) reported 39 minutes ago

  been seeing everyone lock down their sites against AI bots this week. cloudflare rules, block lists, the whole crawler war and it hit me - there's literally nothing for those lists to catch in Plaux it's not a crawler hitting your site. not an api getting hammered. it just... uses the app. opens it, clicks around, types, reads what's on screen. the same boring stuff you do every day that's the part i keep coming back to. it's not sneaking past bot detection. it's not disguised as a human. it just does the work the way a human does, so there's no bot to catch in the first place kinda funny that while everyone builds bigger walls, the thing that walks through the front door never looked like a bot to begin with 🖐

• 
  Glenn 'devalias' Grant (@_devalias) reported 40 minutes ago

  @nickgraynews @computefinx The help docs also mention D1 and R2, which are Cloudflare things

• 
  Anirudh Coontoor (@TheAnirudh) reported 42 minutes ago

  @jullerino Sometimes it keeps refreshing the page, happened multiple times with the cloudflare dashboard login page. I wanted me to login but it kept refreshing.

• 
  W V R 👊🏼🦾 (@WVROfficial) reported 43 minutes ago

  I had to make some changes today and it costed me a MONTH of Codex Usage! I think it’s worth it for me to talk about it - make sure this doesn’t become you!!! So, I’m a startup founder, just like all of you guys!! We do websites as one of our many services - like a lot of the people here on TPOT where tech lives. Why wouldn’t we? It’s easy, we can outclass competition on speed, much more. Anyway - that’s not the point. The point is that i serve my sites with a wrapper that gets served over my host. That host uses ESBuild. To ship stuff that won’t compile on ES Build, and on occasion just for like more complex websites like 3D sites or heavy SEO sites with a lot of files and assets - i use a CDN. Works great, totally fine. But I realized today I had a client site’s files stored on an R2 bucket that was on the client’s domain. In this case the big issue with that is my own IP! We make the content for them, do their SEO, their communications, and more - and i very stupid it was serving everything from a CDN that was on domains I don’t own and control via my Cloudflare. In human terms that means my client could say “**** you” tomorrow and walk away with the extremely robust SEO machine I built them. So I had to spend almost a half a month worth of codex credits today to fix it ASAP. All I can say is that I won’t make that mistake again - even though it never hurt my business - it could have! And that matters.

• 
  0xBunny (she/her 🏳️‍⚧️ ⚧️ ✝️) (@0xBunny) reported 47 minutes ago

  im migrating from my machine to cloudflare edge network. yes...im running a ******* mmorpg on cloudflares edge network for basically free

• 
  Nandkishor (@nandkshorjadoun) reported 48 minutes ago

  i'm trying to switch from prisma to @DrizzleORM because of cloudflare workers incompatibility and ngl prisma spoiled me so bad that drizzle feels like writing raw sql 😭

• 
  VictualBro (@Victual_Bro) reported 50 minutes ago

  Back to dealing with this bullshit every day. Have we all had enough with Cloudflare ****?

• 
  Eric Taylor (@bcs_erictaylor) reported 51 minutes ago

  7/16 - Kali365 Update I have, at least for the moment, completely disabled the Kali365 platform from all operations. Below is an update of the intel we have currently. Believed owner and creator of Kali365: Handle: Octopus King TG: @tentacle_network Completed 'Takedown Requests' submitted to Namesilo FQDN: updateteampanel[.]xyz Completed 'Takedown Requests' submitted to BL Network: IP Address: 199.21.221[.]21 IP Address: 162.33.178[.]105 IP Address: 72.5.43[.]195 Completed 'Sinkhole Requests' submitted to Cloudflare FQDN: servoquil[.]org FQDN: yalmorind[.]org FQDN: vuredonte[.]org FQDN: ondrevail[.]org FQDN: caldivore[.]org FQDN: vuredonte[.]org FQDN: privatetoken[.]app FQDN: mvpaffiliatecz[.]site #Kali365 #CTI #ThreatIntel

• 
  Porkbun (@Porkbun) reported 51 minutes ago

  @liltechnomancer @joshmanders That looks like something Cloudflare requires, not us. They appear to have a transfer process that includes extra steps because they require the domain to be using their DNS. It looks like the actual transfer was never submitted to Cloudflare because they were / are waiting on this step. If you changed your name servers after expiration, 10 days after expiration we disrupt DNS as required by ICANN and that would have prevented what Cloudflare seems to be waiting for. It's honestly best to renew / transfer before expiration to prevent wonkiness like this.

• 
  Aaryan Bansal (@NotUnHackable) reported 59 minutes ago

  @CloudflareDev @cloudflare, i request you, please just fix the env variables being so hard and for no reason keeps failing silently in the background in the workers page

• 
  Anto (@anto_edd) reported 1 hour ago

  Prompt "You are a Senior Application Security Engineer specializing in Supabase Authentication. Review my Login & Signup implementation like a real attacker. Ignore code quality. Ignore styling. Ignore performance. Focus only on security. Check for: • User enumeration • Generic authentication errors • Missing email verification • Weak password policy • Brute-force protection • Missing rate limiting • Missing Cloudflare Turnstile • Disposable email abuse • Password reset vulnerabilities • Session fixation • Session revocation • Secure cookie configuration • OAuth misconfigurations • Missing Row Level Security (RLS) • Service Role Key exposure • Trusting frontend data • Missing server-side authorization • Privilege escalation • OWASP Top 10 authentication risks For every issue provide: 1. Severity 2. Exploitation scenario 3. Recommended fix 4. Production-ready implementation Do not approve the authentication flow until every High and Critical issue has been resolved."

• 
  William (@billmorgan92) reported 1 hour ago

  @CloudflareDev is cloudflare r2 down? I cannot download from my bucket my files and cannot create new buckets (both take forever stuck in loading state)