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 (33%)
• Cloud Services (29%)
• Web Tools (17%)
• Hosting (13%)
• E-mail (8%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	2 hours ago
Los Angeles	Cloud Services	1 day ago
Paris	Cloud Services	17 days ago
New York City	Hosting	20 days ago
Manchester	Domains	1 month 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:

• 
  Michael Blau (@blauyourmind) reported 3 minutes ago

  @eastdakota @Cloudflare You support @trydrip

• 
  Aaryan Bansal (@NotUnHackable) reported 3 minutes ago

  @CloudflareHelp @Cloudflare @CloudflareDev i paid for my workers for this month and the invoice shows that it is from 22 June - 23 August. I paid that now on 31st but it doesn't let me get my workers pro for some reason. Please DM me and get this issue resolved

• 
  render (@infinterenders) reported 5 minutes ago

  @atharvdangedev and wait let me tell why every new hot thing in people opinion is new optimized technique ? ssr solved mostly state synchronisation problems major selling point of SSR and Server Components is that the server lives close to the database, making data fetching lightning fast. In reality people get horny for this seductions these reason exists for what structural design flaw we had with old school web engineering may be ssr and rsc’s are hot but see these make you lock-in something for a host dependency ngl even the host can’t do anything to escape from you it’s design flaw by default even it’s vercel , AWS , Cloudflare anything lock-in exists In When you adopt full SSR frameworks (like Next.js, Remix, or Nuxt) tightly coupled framework-monoliths managing what gets cached on the server, what gets invalidated on mutation, and how edge nodes sync state turns simple routing logic into an *** pain caching puzzle people use compute for things that can be solved with static optimization lol and bark like dogs on vendor providers for locking then in host dependency if you lock yourself without knowledge of how applications compute even vendor lock-in can’t escape you from lock-in

• 
  EzQ (@__EzX__) reported 11 minutes ago

  @eastdakota @yusukebe @Cloudflare Please fix workers AI now they are unusable

• 
  jamesb lawson (@JamesbL) reported 15 minutes ago

  @SmorglesBord @AlecStapp he thought she was indian..lol Cloudflare caused a major global internet disruption on November 18, 2025, taking down popular services like X, ChatGPT, and Spotify. The outage stemmed from an internal software crash rather than a cyberattack. [1, 2, 3]

• 
  blueguy (@itsmeblueguy) reported 16 minutes ago

  @anilsoylu @Cloudflare There’s only one person that can fix things around cloudflare and is not even an employee lol @theo do your rants haha

• 
  Min Yoi (@yoi_minmin) reported 17 minutes ago

  @FuneralsR4 @Cloudflare Same.. getting the same crap for the past week. #FuckCloudflare

• 
  chaskin.eth (@jchaskin22) reported 18 minutes ago

  @auryn_macmillan Agreed It also feels a bit weird to celebrate 100% uptime when most users still access Ethereum through centralized RPCs that go offline when something like cloudflare goes down We’re starting to work on this at the EF, but today the chain’s uptime and users ability to access it are still very different things

• 
  WIV Reports — Uncensored (@WIVReports) reported 19 minutes ago

  @BasedTorba I canceled my Gab AI subscription and will not renew my pro subscription over this. I paid for a full year and got hard-locked out of prompt submissions. Support claimed my ISP was blocking the site. Developer Tools (attached) explicitly showed Cloudflare returning HTTP 429 Too Many Requests on your socket io endpoint (Ray ID: a2377c992a865050-SEA). Support's official response? "Dev ops confirms you are not blocked by CF and says your understanding of what you are seeing is an incorrect assumption." An HTTP 429 from Server: cloudflare is, by definition, an edge rate limit. Instead of escalating basic DevTools data to fix a socket routing bug, support gaslit a paying customer and issued a partial refund to shut down the ticket. If this is how Gab handles infrastructure bugs and long-term users, people should know what to expect. Andrew, email chain is available if you actually care about fixing your support and edge config.

• 
  Sillen (@sillendev) reported 34 minutes ago

  I’m sending sign up confirmation mails with @Cloudflare email send service, The last few days they started to end up in gmail’s junk folder. Anyone else having this issue? I am sending them through @supabase using my app’s domain, and the smtp is correctly configured.

• 
  WIV Reports — Uncensored (@WIVReports) reported 34 minutes ago

  Any first-year network engineer knows the playbook: see a 429 with a CF-Ray ID, log into the Cloudflare dashboard, check the WAF/Rate Limiting logs for that ray ID, and adjust the rule. It’s literally a 2-minute fix. Instead, they insisted Cloudflare wasn't blocking anything, claimed DevTools were wrong, and issued a partial refund rather than taking 120 seconds to look at their edge logs. Pure laziness.

• 
  CalC (@Not_CalC) reported 34 minutes ago

  It would be good if there's a BAAS on cloudflare. Cloudflare already supports everything to build one, and it would be so fast due to cloudflare's vast network

• 
  WIV Reports — Uncensored (@WIVReports) reported 34 minutes ago

  There is no greater love than Christian hate. Gab, a company that constantly preaches its "Christian values" responds to a long term paying customer with pure disdain the second they get called out on technical incompetence. After dropping slurs and throwing a tantrum over standard DevTools logs, their CTO sent this email and immediately blocked my account on Gab so I couldn't reply. I am also sharing the email notification I received. Here is the full timeline of how Gab handles paying subscribers reporting a legitimate bug: 1: Socket io connections failed and looped infinitely, triggering a Cloudflare 429 Too Many Requests status code at their edge. 2: Support claimed a Cloudflare 429 signed by Cloudflare IPs was an issue with my "home Wi-Fi." A VPN on that same Wi-Fi instantly bypassed it, proving it was a server-side edge filter. 3: Instead of checking their WAF rules, their CTO claimed checking origin logs for 6 hours was "VIP treatment," accused me of using AI, and threw a fit. 4: I deleted my gab ai account, posted the DevTools receipts, and told him to fix his edge. 5: He sent a profanity-laden, slur-filled email, blocked me on the platform, and tried to hide it. Never once did I name-call or throw insults, I just posted raw HTTP response headers. This is how Gab treats the people who keep their lights on. Absolute amateur hour You can see the entire unfolding here on my X account, as I posted everything said verbatim. And again, here are the screenshots of the HTTP responses showing the issue is on them.

• 
  science roach (@darthroach_) reported 36 minutes ago

  @CapybaraFortune well no it's a joke about a cloudflare outage because they famously use 90ish lava lamps for encryption lmao

• 
  adam (@theCTO) reported 41 minutes ago

  never, we’re on @convex and @railway and @cloudflare everywhere, all at once

• 
  Klaus Arent (@klausarent) reported 43 minutes ago

  Cloudflare returned error 7003. The message reads like a permissions problem, so that is what my agent debugged: it rotated the API token, widened the scope, checked the account id, and came back twenty minutes later with a token that had more rights and the same error. The actual cause was one character in the path. I had written dns/records where the API expects dns_records. A malformed path produced an error that described a credential problem. An error message is a hypothesis written by someone who could not see your bug. Agents treat it as a diagnosis, because it arrives in the authoritative position: last thing printed, right after the failure. The ordering that fixed this for me: 1. verify the request itself against the current docs 2. reproduce with one known-good call to the same host 3. only then touch credentials Credentials are the most expensive thing to change and the easiest thing to blame. Any error that suggests you widen access deserves the request checked first.

• 
  Warya Wayne (@WaryaWayne) reported 43 minutes ago

  4000 telegram messages notifying me that the sites are down every 180 seconds when they are not down. This must be a glitch with cloudflare or something. It happens on some schedule where the worker is probably glitching or something. How can a fetch to a homepage return 503?

• 
  Giancarlo Perlas (@giancarloperlas) reported 43 minutes ago

  Casper Network is repositioning the csprUSD token as its default stablecoin for the agentic AI economy. Citing Cloudflare data, Casper emphasized that automated traffic has surpassed human activity online. In fact, it traced 59.4% of all web requests to the former.

• 
  William (@dxgl_org) reported 46 minutes ago

  @davepl1968 Since you're using Cloudflare would it be a good idea to disclose that in your privacy policy, or would that make said company that blocked me here upset? Note there's an excellent chance your website is sharing an IP address with some pretty bad sites, especially if it's free.

• 
  Matt 'TK' Taylor (@MattieTK) reported 47 minutes ago

  @nicole_clash This screams PWA banner to install to home screen. And also screams get on Cloudflare so you can start caching prompt responses for free so you never run the same recipe twice, through AI gateway.

• 
  yohance (@yohanc33) reported 47 minutes ago

  @leinwand @eastdakota @Cloudflare Cool, I happened to apply for this fall’s SWE position (and the previous fall, as well as the previous summer, no luck so far :p). Think I could get a referral? I’ve used several cloudflare infra products (R1, Workers, Workers AI, Workflows, etc). Working on mastercard’s service mesh this summer using Go.

• 
  Ec1ipse.sol (@ec1ipse_sol) reported 49 minutes ago

  @mhulbig @thekylehuber Multi-sig won't help you here either friend. You simply have to create entropy manually. That is the only way. Do the CloudFlare way and take IRL data to make your random numbers. Do not trust others to build a device to provide a secure private key.

• 
  八咫烏 Merui (@yatagarasu_meru) reported 52 minutes ago

  @kochin520 I initially thought the previous build was just weird but it seems it's not a build issue. It's might be cloudflare or ISP issue, since I also have the site load slow on my internet, but opening up a VPN even on the same place, made the site load quickly. Done some testing, dev page that is on cloudflare servers loads quick. Opened a VPN set to Manila, it loads quick I even gone and rolled back the site in a build from a day ago which I know loads fine a few hours ago. Still loads slow. so I think it's ISP problem. Since I see your country you are from. Image: Right is with Manila VPN: 0.4 seconds load.

• 
  Jason Fleagle (@jjfleagle) reported 52 minutes ago

  @Cloudflare At 9 billion requests a day, the migration receipt is as valuable as the architecture. Capture baseline latency and errors, compatibility tests, phased traffic shifts, rollback triggers, cache behavior, and post-cutover deltas. That gives the next team reusable evidence.

• 
  WIV Reports — Uncensored (@WIVReports) reported 53 minutes ago

  Don't bother with Gab. This is how they treat long-standing paying customers. Yes, I deleted my account. Any first-year DevOps engineer would look at my screenshots, see the Cloudflare 429 status code, trace ID, and Socketio polling loop, and know it’s an edge rate-limiting issue, not a home Wi-Fi problem. Instead of checking their Cloudflare logs, their CTO chose to deflect, throw a tantrum, and launch personal attacks to cover for his own incompetence. I’m done with Gab. Absolute amateur hour.

• 
  Jeremy Kreutzbender (@J_Kreutzbender) reported 53 minutes ago

  @CherryJimbo @Cloudflare @CloudflareDev Ran into an issue with AI Gateway yesterday afternoon. It seemingly hasn’t been reported anywhere, only in a thread on a message I started in Discord

• 
  Anıl Soylu (@anilsoylu) reported 58 minutes ago

  @MarkDGeorge @Cloudflare I don’t think so. They’re clearly abusing Cloudflare’s systems. Hopefully, Cloudflare fixes this issue soon.

• 
  Benjamin Shelton (@zancarius) reported 59 minutes ago

  @kwrob24 Yeah... I have most of my blogs behind Cloudflare specifically for this reason, but for historical (read: lazy) reasons, this instance lives on a domain I use for a *lot* of personal projects and home-lab-esque sort of things, even if most of it has been migrate to cloud services. It's not really a huge problem, and it's not (yet) consuming a bunch of egress traffic. But, this isn't the first time I've had issues with AI-related crawlers. I may be forced to move this to another domain at some point.

• 
  Sulfur (@sulfurscales) reported 1 hour ago

  here's how to BUILD a phone farm for tiktok that costs under a cent per post instead of $0.5-3 per piece 10 old iphones running locally off a mac, iphone 7 through iphone 11. 2-3M views a month across 20 accounts, 30-40 posts a day, all targeting the us while running physically outside it. best single post hit 1.1M, median sits around 5000. 2000 views turning into 1 install, 5% of those installs converting to paid, best days pulling 80 installs and 5 new customers the problem being solved: every slideshow tool on the market charges per piece, reelfarm and the rest land around $0.5-3. at 40 posts a day that's $500+/month before you even know which angle works. a proper testing phase at that rate runs $2-3k before you get any signal, and none of those tools guarantee quality even with good prompts the fix: build the generator yourself. python scripts, settings files per phone, no database, no cloud, no saas. runs entirely off a laptop the pipeline breaks into a few agents. a parser that pulls content across the niche and ocr's it. a reference builder that turns that into reusable angles. a slide and video generator that mixes pre built pieces with new hooks and captions, no llm needed for the actual generation. a daily poster that pushes content to each phone through shortcuts so there's no manual airdrop, content lands straight in the clipboard ready to paste. a calendar and analytics scraper once excel stopped being enough past 20-30 accounts phones were $50 each, bought old. an iphone 7 on ios 15 matched an iphone 11 on ios 26 for performance, newer hardware didn't move the needle at all. the actual variable is content, not device each phone runs 30+ settings from an internal library before it touches tiktok, and the exact list differs slightly per model and ios version. dns leaks patched, webrtc leaks closed, ip tied to a specific location so the account can't be traced back to a base photos get run through a module that rewrites exif data to match a real iphone camera roll. camera dimensions, mb size, live photo data, geo tag matching that specific phone's ip, dozens of parameters layered in. this is the part that actually moves rankings, tiktok ranks native capture higher than obvious stock or ai output, and none of it triggers an ai generated label after posting video repurposing works too, same clip with a different hook counts as a new video to tiktok once it's run through the pipeline posting 20 slides across accounts takes 35 minutes total with shortcuts handling the transfer running cost: $40/month proxies, $40/month llm subscriptions, hosting free on cloudflare. one time setup was ~$300 for hardware plus ~$300 for courses, on top of $500 for the phones themselves. total spend so far sits around $1k, three months to build, now running at 2 hours a day android was tested and dropped. cloud androids passing google's full integrity check cost more per month than buying a used iphone outright, and still underperformed, the cheaper android tiers did worse. rented androids also couldn't run a second account on the same device, which killed the option outright account health has been mostly clean on ios, androids were the ones getting banned. one attempt at running tiktok on a jailbroken ios 16 device got logged out fast, no ban, but enough of a signal to not push jailbreak further until there's a way to test it without burning dozens of accounts first what's still unexplained: two accounts running nearly identical content and setup, one hits 1M on post 3, the other barely moves. same hook photos with minor crop or filter changes keep working, no clean read on whether that step is even necessary. one of the best performing accounts doesn't have us dns at all and still pulls more us traffic than accounts that do. no clean answer for any of it, just logged as unresolved and moved on next step is pushing toward phones running 24/7, automated swiping included, and expanding past tiktok into instagram reels

• 
  Anıl Soylu (@anilsoylu) reported 1 hour ago

  @TheNicholasNick @Cloudflare I don't think it's at that point. I expect they'll fix it soon.