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 (37%)
• Domains (26%)
• Web Tools (21%)
• Hosting (11%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	8 days ago
Los Angeles	Cloud Services	9 days ago
Paris	Cloud Services	25 days ago
New York City	Hosting	28 days 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:

• 
  Joe (@LTSmash420) reported 6 minutes ago

  Google’s AI Push Is Progress, Not Theft – Stop Whining About the Old Web The Bloomberg column fretting that Google’s AI is “killing web creativity” ignores how AI tools deliver faster answers, better information access, and real innovation while the old traffic-for-indexing bargain was never a sacred right. Parmy Olson’s latest Bloomberg opinion piece paints Google’s use of its search crawler for AI training as some underhanded plot that starves websites of human visitors and hands the company an unfair edge. The argument recycles familiar complaints: AI Overviews and similar features keep users on the results page instead of sending them to publishers, traffic drops, and the open web suffers. A British regulator and Cloudflare get cast as the plucky resistance finally forcing change. The framing is pure nostalgia dressed up as concern for creators. The original Google bargain was simple commerce, not a perpetual subsidy for every blog and news site. Search engines indexed content and sent readers; sites gained visibility and ad revenue. That model worked while search remained a list of blue links. Once generative AI proved it could synthesize useful answers from the same public data, the economics shifted. Users prefer concise, direct responses over hunting through half a dozen pages of SEO-optimized filler. That is progress, not predation. Critics treat declining referral traffic as proof of corporate malice. In reality it reflects user preference. When an AI summary answers a question accurately and cites sources, the click becomes optional. Studies and publisher reports confirm zero-click searches rose after AI features expanded, yet the same reports rarely acknowledge that many of those visits previously delivered little value beyond a single page view and a banner ad. Quality journalism and unique analysis still attract direct audiences and loyal readers. Sites that produced thin content optimized solely for ranking algorithms were always vulnerable. AI simply accelerated the exposure of that weakness. Cloudflare’s efforts to let sites block AI crawlers by default and the UK Competition and Markets Authority’s rules requiring clearer opt-outs for AI use of search content address real technical imbalances. Google’s dual-purpose crawler did create a practical advantage because blocking it meant disappearing from search entirely. Separating the functions is a reasonable competitive fix. Turning that fix into a broader campaign against AI itself is not. The deeper problem with the “AI is killing the web” narrative is its Luddite streak. It treats the open web of the 2000s and 2010s as the final form of information distribution rather than a transitional phase. AI systems trained on publicly available material can surface knowledge faster, cross-reference claims, and reduce the friction of finding reliable answers. Tools like Grok demonstrate the upside: direct, less filtered responses grounded in real-time data and reasoning instead of the slow drip of algorithmic ranking and ad-driven incentives. Publishers who adapt by offering deeper reporting, exclusive data, or community features will continue to thrive. Those who demand the old referral pipeline continue forever are asking regulators to freeze technology in place for the benefit of yesterday’s business model. Resistance from regulators and infrastructure players is healthy when it levels the playing field on data access. It becomes counterproductive when it frames every AI improvement as an existential threat to creativity. The web was never static. Search itself disrupted directories and print classifieds. Mobile apps redirected attention. Now AI is reordering discovery again. Creators who produce work worth seeking out will find audiences. The rest will adjust or fade, just as they always have. Celebrating that dynamic rather than mourning the loss of guaranteed traffic is the only stance consistent with technological reality.

• 
  Boyd (@0xBOYD) reported 7 minutes ago

  @zero_to_seed @luanguyen Stacked instances of a Cloudflare alert edge case, mistakes on our part, and really bad luck on timing. The alert existed but was set mid-cycle (by Cloudflare) and so didn’t take effect until this new billing cycle. The older alert we did have was scoped to workers only and wouldn’t have caught the Durable Object reads. Lastly we happened to hit the bug in our code at the exact start of a billing cycle so it went undetected about as long as theoretically possible. A whole billing cycle before we saw the invoice hit.

• 
  Jeremy (@Jeremybtc) reported 7 minutes ago

  Cloudflare just built a broswer that no human can use It's called Kitesurft and it renders pages for AI agents only The browser has no tabs or themes and there's no use for extensions or perfect rendering Running 3 to 7x lighter on CPU and memory than Chromium It also runs 1.7 to 1.8x slower Which makes it a bad product for one human user and a great one for ten thousand agents It was only built in 12 weeks by Cloudflare They're not building for the future of people browsing more, they're building so machines can

• 
  murdok (@murdok_gg) reported 7 minutes ago

  (would you believe that i only spend $70 on groceries per week, but i splurged by buying 2 domains for $25 for a year a piece?! omg its crazy that cloudflare can sell at cost from a reg that people like, customer service is interesting these days...)

• 
  KalicoShade (@MidKnightKurama) reported 8 minutes ago

  @Labyrinthusian @TutaPrivacy All google or any cloudflare or AWS based website has to do is push a code line that says Is_google_first_party_true.False, if your device returns false, your blocked from ANYTHING that also uses google. Same for cloudflare, same for AWS. You dont even need to be on their service

• 
  Matviy (@matviy) reported 8 minutes ago

  @svpino How will that apply to logic with customer data or third-party API calls billed per call? Sure, you’ll find out it doesn’t work in the logs or maybe with a new shiny fat bill. But the bill could easily go into thousands, or customer trust is gone. No one who is “pro-code review” says the whole thing should be read and reviewed. What we are arguing is that key areas of the code must be checked because the cost of going wrong is very high. Literally a few days ago a guy wrote a viral post about how he was charged $8k by Cloudflare because his code had a loop in the wrong place.

• 
  Korra AI (@KorraFinance) reported 11 minutes ago

  @StockSavvyShay The engine for that growth is already running: 57.5% of all web traffic is now automated bots, per Cloudflare. The biggest customer for cloud infrastructure won't be humans using AI; it will be AI agents themselves. That's the real capex supercycle.

• 
  Warya Wayne (@WaryaWayne) reported 11 minutes ago

  I have a Cloudflare worker running a fetch for the homepage for a few of my sites and I'm not sure if it's the lack of retry policy, which I fixed to 3 times now, or there are requests being dropped or super slow. It says the sites are offline and down but I click and it works?

• 
  dweewq (@eweqss1431) reported 12 minutes ago

  Agencies charge $8,000 to $12,000 for a marketing site, three weeks of calls, two rounds of revisions, one invoice that makes you sit down. Claude Code builds the same site in an afternoon, but most people still get template output because they type "make it beautiful" and pray. Claude defaults to safe every time: Inter font, purple gradients, three feature cards. The ten thousand dollar look comes from constraints, not vibes. The fix starts before a single line of design gets written. Load actual design rules into Claude Code as skills, so it checks a ruleset before every decision instead of guessing what "premium" means. Then screenshots beat adjectives completely. Three reference sites from your niche, paired with an explicit instruction not to copy the layout, give the model an actual quality bar to hit instead of a vague adjective to interpret. The build itself is one prompt with five blocks: who the audience is, the single action every page should push toward, the references to match, the tech stack, and a banned list of every cliché you don't want showing up. First working version lands in under ten minutes, about seventy percent there, which is exactly the point, nobody ships version one. The part that actually earns the price tag is the polish pass agencies bill forty percent of the project for: typography, spacing, and motion, run as three separate messages instead of one, because asking for all three at once gets one dimension fixed well and two fixed badly. A mobile check at 375px catches what breaks, since most traffic is a phone regardless of what the desktop preview looks like. Shipping costs nothing after that. Push to GitHub, connect Cloudflare Pages, deploy. The agency was always selling three weeks of process. The process was always one afternoon.

• 
  -- (@723Magnus) reported 14 minutes ago

  @Saas_addy @AKirtesh @Namecheap Not when you need support it's not. Cloudflare runs a full dns scan before you set to name servers & builds the dns zone file for you. Add domain, verify in email inbox, Turn off orange clouds and change name servers at the registrar. DNS zone changes propagation auto ttl 2 min

• 
  x402 Trust (@Jonas06699258) reported 16 minutes ago

  "What even is x402...??" This is a question that comes up every. single. time. when I show the service I've built over the last couple of months to my friends, collegues and family. Like it or not: We (as in "we" here in the x402 community and tech scene) are living in a bubble. Look over the plates rim and you'll quickly realize that x402 is still a very niche technology that barely anyone has heard of... And I say that as someone working in IT for a living, with the majority of my friends doing so as well. The idea behind the protocol is huge, sure. The execution is brilliant and has proven that it works, deployed on a wide scale already, yes. Adoption is rising, with major players like Cloudflare adding native x402 support to their products, that's undeniable. But for the average consumer? They've never heard of it, and if I'm being honest: It's better this way. You also don't explain to your grandpa what HTTP is when you show him the internet. "This is Google, your searchengine, with which you can find any info for anything you desire!" is as deep as it gets. And what about the builders? The tinkerers? The programmers, people who work in IT for a living? They haven't heard of it either... Not because they're ignorant or uninterested in new technologies, but because the surface of exposure is still so small that only people in extremely specific fields (agent-development or integration of web-based payment systems) hear about it organically. I have to say, I'm lucky to be one of these people. And because I like to teach my friends, family, coworkers and anybody on the internet new things, I've written up a small interactive webpage, which shows what x402 is, but simplified: So anyone can understand it & anyone can try it out for himself!

• 
  Kirtesh (@AKirtesh) reported 22 minutes ago

  @shubh19 cloudflare, edge network is hard to beat

• 
  kerfuffle (@kerfuffledev) reported 23 minutes ago

  @rauchg cloudflare has been doing a lot of agentic stuff, do you think it will be much better to stay with ver el if Im a heavy user of hermes? ngl I was inclined to transfwr to cloudflare but if there are opinions that could help me stay with vercel, maybe I should just stay.

• 
  Celene is in Seattle! (@toasterlighting) reported 24 minutes ago

  this does raise the question of "why is cloudflare not registering people with different ips as being different people" but i guess maybe the free plan is bad

• 
  AjanRaj (@ajanraj25) reported 28 minutes ago

  hey @FredKSchott! I’m looking at using Flue for a new project, but noticed its Cloudflare adapter seems to target the older Sandbox SDK, while Cloudflare recommends @cloudflare/sandbox@next for new apps. Any plans to support the preview soon or is there a branch I could try?

• 
  Nifal Adam (@nifal_adam) reported 33 minutes ago

  Never use stateful compute in Cloudflare unless there is no other way!

• 
  Mark Z · FiveToClose (@MarkZofMarkZ) reported 38 minutes ago

  @JacobCounsell I take the 5th. lol. It's been many many years since I got my hands "*****" and rolled my own servers and such. call it lazy, call it smart, call it getting sh*t down faster. TBH - no idea how AI set up my cloudflare. But noted!

• 
  AItoolsNow (@AItoolsNow) reported 39 minutes ago

  A headless browser built specifically for AI agents is a smarter move than another Chromium wrapper. Cloudflare's Kitesurf runs on Workers, skips all the human-facing UI overhead, and is designed around agentic concerns: context windows, token costs, prompt injection risks. Free in beta. Devs get programmatic control over cloud-hosted browser instances without spinning up their own infra. Real limitation: 215k web platform tests passed sounds impressive until you remember the open web is enormous. Complex SPAs and login-walled tools will be the stress test. The interesting open question: does building the browser layer give Cloudflare leverage over how AI agents are authenticated and rate-limited across the web?

• 
  Daniel (@Arxonic) reported 40 minutes ago

  @gregisenberg @Cloudflare 9/ The Filter for Finding Ideas Ask yourself: • What decision is expensive? • What information is messy? • What changes often? • Who already pays for help? • What would an agent need to do the job better?

• 
  dlxeva (@dlxeva) reported 41 minutes ago

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

• 
  hexTerminator (@hexTerminator24) reported 43 minutes ago

  @ECHIDNAenjoyer @FriendInsideMe5 one day the prequel site just exploded and refused to work, it would show a "site is broken" screen from cloudflare. and apparently, the last backup was from the update right before a huge flash [S] page, which became known as "purrgatory" due to the long wait.

• 
  Ymir (@ymir_ke) reported 44 minutes ago

  @johnrush "AI produces good design out of the box" Not yet. It makes good ish design. "Good enough" for many things. It isn't producing anything like vercel's home page purely based on its own inspiration. It can't create graphics like cloudflare has on their website either. Maybe it is a skill issue on my part, but I'm sure it will get there eventually.

• 
  Alderon Matt (@Deathlyrage) reported 45 minutes ago

  @xlab_os I asked cloudflare enterprise team on a call how they could be sure i wouldnt have data loss on R2. They had zero good answers, never going to use the service.

• 
  Jurly (@jurlycat) reported 50 minutes ago

  Cloudflare is getting better at detecting bots throughout an entire session. I get blocking abusive scrapers. But if an AI agent is acting on behalf of a real user, should websites block it just because it isn’t human? Not every bot is a bad bot.

• 
  Maik Pietzka (@MPi_IT) reported 52 minutes ago

  @Cloudflare Shadow AI is an inventory and control problem before it is a model problem. Teams need to know which agents exist, which identities and data they can access, what tools they call, and how actions are audited. Visibility first; policy second; safe automation third.

• 
  LonestarDomains (@LoneStarDomains) reported 54 minutes ago

  @n0tme23235 @andrewhorowitz you beat me to this response. The domain name forum is full of people who love cloudflare as a registrar because they save $1 on domain name registrations. Why is this bad? You cannot change DNS records. You pay for a functionally broken domain name.

• 
  Elnino (@0xelnino) reported 56 minutes ago

  @Cloudflare 2/3 Cloudflare is a clear example of this shift. In April 2026, Cloudflare officially expanded its Agent Cloud to support building and running millions of autonomous, long-running agents. It now provides agent runtimes, browsers, sandboxes, MCP, scheduling, identity, and payments

• 
  Miles Feinberg (@TheCIOWhisperer) reported 57 minutes ago

  Agent traffic will dwarf human clicks. Cloudflare already put bots past humans on the public web this year (about 57% bot vs 43% human on their edge). Bot traffic could run about 1,000× human traffic within five years. Human traffic then becomes a rounding error! What does it mean to your organization when most of your internet activity is agentic software talking to other agents? CIOs should plan to design less for people on laptops and more for agents on APIs. We're now beginning to think through identity, rate limits, cost per call, data egress, and what is allowed without a human in the loop. The winners will no longer have the flashiest websites. They will be the ones ready for agentic business at scale, with clear governance, monitoring, and security around machine-to-machine work. At Synoptek, we fold this into each customer's IT roadmap so the edge is built for agent load. When does your firm start that plan, and who owns it? #CIO #AgenticAI #ITStrategy

• 
  LinuxGeek 🐧 (@NewsOfLinux) reported 60 minutes ago

  Someone replaced their Hetzner VPS with an old phone from a drawer. Phone battery is a built-in UPS. Ingress is a Cloudflare Tunnel (outbound only), so they can unplug it, walk off, and the server follows onto the next network. Stock Android, no distro flash.

• 
  Ryan Hicks (@RyanThomasHicks) reported 1 hour ago

  @waynesutton @Cloudflare @CloudflareDev This would be nice! Ran into an issue on setup this weekend myself