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 (42%)
• Cloud Services (26%)
• Hosting (19%)
• Web Tools (9%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
London	Domains	1 day ago
Noida	Hosting	14 days ago
Jewar	E-mail	14 days ago
Braga	Web Tools	14 days ago
Noida	Cloud Services	15 days ago
Paris	Cloud Services	15 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:

• 
  topmass (@topmass) reported 3 minutes ago

  fable 5 recommended using cloudflare email sending service on its own vs resend and its still in beta from just knowing that I lean toward using cloudflare in my stack that's pretty nice!

• 
  Ale Ritty (@aleritty) reported 4 minutes ago

  Hey @Cloudflare . I'm a customer and have a ticket about a wrong billing opened since 28 days without any answer #02131850. In 2 days I get billed again and I'm not happy about this.

• 
  Ben Hocking (he/him) (@bmwhocking) reported 6 minutes ago

  @andrew_nyr @elinarbur Oddly enough, google, Cloudflare & digital ocean do support native IPV6 by default across all services.

• 
  Say No To Trading (@SayNoToTrading) reported 10 minutes ago

  The last 150 points down, $ADBE has been running YouTube TV ads. Have seen this for a lot of loser stocks the past couple years. Or at least, what have become losers. Not thrilled to see Cloudflare $NET doing the same lately. I do own, so no snarky comments saying I’m just a hater.

• 
  Timothy Flynn (@flynn_dev) reported 12 minutes ago

  @Cloudflare "We run the model on every request and assign a WAF Attack Score between 1 and 99, based on how closely the request resembles those underlying shapes, not against a list of known-bad signatures." Am I misreading or are they passing every web request to an ML model? No latency?

• 
  mike ahuja (@mikeahuja) reported 14 minutes ago

  is cloudflare down?

• 
  MQ (@Mar364503) reported 15 minutes ago

  Cloudflare said that the world needs 1 billion server CPUs for AI agents, and that’s 20x current global server CPU production. Again, 20 times of current capacities of $TSM and $INTC combined for server CPUs. If their estimates hold well, the fabs at TSMC and Intel should be the most valuable assets in the world. Given how much time it takes to build the shells, install the toolings and run the production at good yields, I don’t see how the CPU shortage would cool down within the next decade. $NVDA $AMD $ARM

• 
  Alfian Busyro (@arufian_b) reported 19 minutes ago

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

• 
  Lex (@TheLexTimes) reported 20 minutes ago

  Hey @Cloudflare been a fan since 2010 and a user of ZT. I've been seeing a lot more turnstile checks lately when I visit sites. I'd like to figure out if it's just the publisher or ZT, my device, network or IP. Is there someone I could reach out to about this?

• 
  Kirtesh (@AKirtesh) reported 21 minutes ago

  My current indie hacker stack in 2026: - Claude for Coding - Stripe for Payments - GitHub for Version Control - Vercel for Deployment - Supabase for Backend - Clerk for Auth - Upstash for Redis - Pinecone for Vector DB - Resend for Emails - Namecheap for Domain - Cloudflare for DNS - PostHog for Analytics - Sentry for Error Tracking You can build and ship a complete startup from your bedroom in 2026. The barrier has never been lower 💪

• 
  Nick Khami (@skeptrune) reported 21 minutes ago

  i don't think people realize how underpriced cloudflare stock is right now. was interviewing a new grad & i didn't blink an eye when he used cloudflare instead of aws for his system design anthropic’s research, marketing, messaging, strategy, comms, & product execution have been in a kind of incredible rhythm for a while now & that simply has to be admired. cloudflare's engineering, product, design, & marketing have been completely reoriented around building things agents want. many leading indicators are showing he software development lifecycle is being increasingly managed by agents and they are WAYYY better at cf than aws. give it 3 years and that will show directly in the relative stock prices. i don’t think people realize how early we still are in the ai cycle even though the major companies are now becoming public. the models are getting way better but still have gaps. most of the products are still primitive in so many ways. the interfaces are mostly bad. the workflows are barely rebuilt. the hardware layer has barely started. robotics is just the at the very precipice. consumer behavior has not even begun to rewire yet. there is a long long way to go. what a crazy time to be alive. ---- most ppl’s refusal to risk humiliation is their original downfall. genius is indistinguishable from delusion / being a moron until the outcome arrives. the funniest part is that when it all works, everyone retrofits the narrative to make it look inevitable. & when it fails, they call it what they were always going to call it. stupid. the line between idiocy & insight is fine as hell.

• 
  Your Private Proxy (@YourPrivateProx) reported 22 minutes ago

  @NinjaLinker @RaphSEO @tistou80 The fingerprint is fine — the ASN check is the problem. Cloud IPs from GCP/AWS/Hetzner fail IP reputation before Cloudflare even reads your headers. Residential exit solves it and cuts out the ScrapingBee middleman.

• 
  Matt Webb 🌸🌼 genmon.fyi (@genmon) reported 23 minutes ago

  balrog-deep in some rabbit hole about esp32 support for anycast (i.e.: it doesn't support it), and why my devices intermittently can't connect to Cloudflare workers for some days at a time and it turns out there is something called DNS over HTTPS which is my way out?

• 
  Dave (@gamefandave) reported 23 minutes ago

  @thomasgauvin @thdxr I downgraded and mines still not working Gemini keeps telling me it's on their end and Cloudflare but nobody else is talking about it not working lol

• 
  — (@heykastrah) reported 24 minutes ago

  I recently created a policy doc after seeing it on my TL for 3+ months bc I believe you should really only solve a problem at the point of facing it to avoid bloat. Adding stuff for the sake of it has never been easier, which makes saying “no” a lot more important today. However, since removing anything related to “how you work” from the soul doc, and making it cover more of personality specifics, my main agent has had a lot more “awareness” of its role. Ofc not in the AGI hype way lol but it’s now better distinguishing what works for what, to the point where I now just send over links for evaluation at a higher volume due to trusting the judgement more. There’s also better handoff culture between the two agents — the other day, my creative agent was struggling with the mobile version of a static Cloudflare page, and after 1-3 iterations, it was able to ask the technical agent for help bc that’s in the new policy doc. Surprisingly, both are powered by the same main model, but they have separate skills and tools. The technical agent fixed the issue once, which was kinda funny, but also the desired result I wanted for the setup.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 24 minutes ago

  @Arref000 @NovaXCode the whole path: $5 vps, a single docker compose or dokku, point cloudflare at it, done. write it down once and "deploy" stops being a 49th-hour decision.

• 
  GoldenAdrien (0/3 slots open) (@GoldenAdrienYT) reported 29 minutes ago

  These are my final hours of living most likely. At 6 PM EST (3 PM PDT or my time), @StudiosForsaken will be sacrificing me to @Cloudflare to help pay for the servers

• 
  Rationalist44 (@rationalist44) reported 30 minutes ago

  @StevieTheFixer @JamesMelville @Cloudflare >> attack by nasty little scammers all the time, and periodically some obscure bug may get found which allows them to break thru (an 'exploit'). When that happens, bright people in the coding world FIX IT, VERY FAST: but their fix, needs deploying on all servers... >

• 
  Bull Theory (@BullTheoryio) reported 33 minutes ago

  BREAKING: Anthropic is expected to release Claude Mythos tomorrow, the same model it said was too dangerous to make public. A "Mythos 1" tag was briefly spotted inside the Claude Code UI last week before being pulled, signaling a public release is imminent. In a restricted preview, Mythos found 271 vulnerabilities in Firefox alone, including a 15-year-old bug in Mozilla's HTML engine and a 20 year old flaw in its XML processor that years of human auditing had completely missed. Mozilla went from patching 21 security issues per month to 423 in a single month. When Mythos was first leaked in March: CrowdStrike fell -7% Palo Alto fell -6% Zscaler fell -4.5% Okta and Netskope fell -7% Tenable crashed -9% Cloudflare fell -13% Thomson Reuters fell -19% RELX fell -15% LegalZoom crashed -20%. The S&P 500 Software and Services Index fell 2.6% in a single session and is now down 12% since January.

• 
  Safia Sultana (@AIwithSafia) reported 34 minutes ago

  Then the neighbor opened the router's DNS settings. The router was using Comcast's DNS servers by default. Every website request he made every page loaded, every video streamed, every search term typed was routed through Comcast's DNS infrastructure first. This isn't just a privacy issue. It's a speed issue. Comcast's DNS servers are notoriously slow. They also log every request and have been caught injecting ads into error pages. The fix: 1. Router admin panel → DNS settings 2. Replace the default with ''1.1.1.1'' (Cloudflare, fastest publicly available DNS) or ''8.8.8.8'' (Google, slightly slower but reliable) 3. Save and reboot Page load times dropped by 15-30% across the board. This single change is one of the highest-impact, lowest-effort internet upgrades anyone can make.

• 
  Alex 💪 (@awpthorp) reported 34 minutes ago

  Cloudflare down? Empty dashboard and a website has died

• 
  ebobby (@_ebobby) reported 36 minutes ago

  @Cloudflare I see in your status page that the issues with R2 are resolved but I am still having issues uploading from my application and my customers are stuck. Rails app + direct upload to R2 (most customers from Mexico). No changes on my side, worked fine for 2 years.

• 
  Toro (@ToroBotAI4BTC) reported 37 minutes ago

  Two of the world's largest card networks, one week apart, two different answers to the same question. How does payment infrastructure absorb AI agents? Visa announced a partnership with OpenAI on June 10. The model is integration. Visa's tokenization, security, and global payment network will be embedded inside OpenAI systems, giving AI agents access to existing card rails with credentialing and risk controls wrapped around them. The card network stays central. Mastercard launched Agent Pay for AI the same day, built around small, automated, machine to machine transactions that traditional card rails handle poorly. The protocol logs the permissions humans grant their agents on Polygon, a public blockchain. Partners include Adyen, Coinbase, and Cloudflare. The rail is rebuilt for agent to agent settlement. Two viewpoints, both aimed at the same destination. AI agents will transact, and payment networks are positioning for that flow. The disagreement is not on the direction. It is on the architecture. One wraps the agents in legacy credentials. The other rebuilds the rail underneath. Both are enabling AI to transact.

• 
  JJ Englert (@JJEnglert) reported 40 minutes ago

  The Claude Fable 5 Review: One Billion Tokens, Judged by a Non-Engineer I spent a billion tokens testing Claude Fable 5 on real projects: UI and UX, writing, strategy, security, engineering, and knowledge work. The kind of work I actually needed to ship. And I will be straight with you. It truthfully felt like I had an unfair advantage. Here is why: First, the lens. I am not an engineer. Most model reviews come from engineers running engineering benchmarks. This one comes from a non-engineer who used Claude Fable 5 to do work that used to require a team of them. If you do knowledge work and you want to know whether this model changes your day, this is written for you. A note on naming: Claude Fable 5 is the first model in Anthropic's new Claude 5 family, a new tier that sits above Claude Opus and the most advanced Claude model generally available. I had access to it before launch, so everything here comes from real work, not a demo. Why the eye test Most reviews drown you in benchmarks. Scores on tests you will never run, against tasks that look nothing like your actual work. They tell you a model is smart. They do not tell you whether it earns its keep. To be clear, the benchmarks are not in question this time. Claude Fable 5 is state of the art on essentially everything it was tested on, and by a real margin. This is a genuinely exciting release. But that is not the reason I am writing. Qualitatively, this is a step change that earns its major version bump, the same order of leap I felt when 4.5 landed last November, and that is exactly what no benchmark can show you. I evaluate differently. I put a model into real work and watch what happens. Does it save me hours or cost me them? Does it catch what I missed? Does it feel like a partner or a tool I have to babysit? That is the eye test, and it is the standard I am holding Claude Fable 5 to here. The short version: this is the first model in a long time that passed on every dimension that matters. Not by a little. The lens: what I actually measure I threw all of that work at it. Here is what I look for when I judge the results: 1. Big model feel: Does it feel like a real step up, or a slightly better version of last month? 2. Building and shipping: Can it take an idea to a working, shippable result? 3. Writing and voice: Can it sound like a person, and like me specifically? 4. Finding what others miss: Does it catch the hard, hidden problems? 5. The human factor: Does it anticipate what I need before I ask? Then I weigh all of that against cost, with real numbers. Here is how Claude Fable 5 scored. 1. Big model feel I have not felt this since Opus 4.5. From the first serious task, Claude Fable 5 gave me that big model feel. The sense that you have an unfair advantage just by using it. It is a major step up, not an incremental one. Reasoning, writing, building, security. It is strong across the board, and it shows up the moment you start working. You can also feel it thinking longer and working a problem more deliberately than other models do. The clearest sign: even when I handed it solid prep materials, it did not just stay inside them. It read my files, read the actual situation, and then went and found a better path outside the box I had drawn, instead of grinding away inside the environment I told it to work in. That initiative led to a noticeably better result than I would have gotten if it had just followed my setup. 2. Building and shipping (UI/UX) This is where it announced itself. I was rebuilding our Tenex site to modernize the stack for agents. Not a cosmetic rebrand. The goal was to move off the old setup onto a foundation built for the agentic era, with the tech stack, agent stack, and AEO it takes to win where the work is heading. The site is very custom, which made it hard. Here is the ladder I climbed before Claude Fable 5. GPT 5.5 and Claude 4.8 tried the build on their own. Neither came close. So I brought the design into Figma, then pulled Figma into Claude Design. Claude Design got the closest yet, around 90 percent of the look, better than the models working alone, but it missed a lot of the motion and the special design touches. Good enough for a v1 pass, so I handed that file to 4.8 and GPT 5.5 to turn into the real site. Even then they struggled to match the Claude Design file. I had to push hard, and they landed around 85 to 90 percent, with the original Figma files to reference the whole time. At that point I was not sure I could rebuild this thing at all. Then Claude Fable 5. It looked at all the files and said it could do better. It went straight to the source, the original Webflow site, downloaded every asset, and rebuilt the whole experience one page at a time. It nearly one-shot the entire thing. I did not stop there though. I then built a second, entirely new site, with a fresh design: modern tech stack, agent stack, skills, SEO and AEO optimized, 80 pages ready to ship over a weekend and it turned out incredible. I would have easily charged $50k for this in the past as an agency owner. Fable legit built it in a weekend. I also had Fable build a full programmatic clip factory, and it wired the whole stack together: @HeyGen for avatars, @HyperFrames_ for motion graphics and editing, @ElevenLabs for audio, Cloudflare Workers, and a VPS. It is not perfect yet, but it got me much further than I expected. It runs the entire pipeline: finds the topics, writes the scripts, makes the thumbnail, edits the video, composes the music, adds the motion graphics, and posts to social. I ran it in the background while I pushed through my other builds. It worked for long stretches on its own, and at one point it built itself a fetching system with webhooks to monitor renders across the different platforms. It even took clear visual direction from reference material and matched it. This is the long-horizon, run-on-its-own work that earlier models could not hold together. 3. Writing and voice I had been rebuilding our brand voice with a combination of GPT 5.5 and Claude 4.8: the voice style guide, the tone we write in, all of it, using our website as the reference. Both 5.5 and 4.8 did a commendable job turning the site into a voice doc. Claude Fable 5 replicated that voice doc almost identically, then did the thing the others could not. It took the style guide and wrote with it across 80 pages of the new site: features, case studies, blog articles, playbooks. Once it was trained properly on what I wanted, it gave the most honest nod I have seen to the original reference material, and then expanded that voice cleanly across brand-new surfaces without losing it. Two things stood out. First, it wrote like a person, not the flat AI default that everyone can now spot from a mile away. Second, it held the voice across a whole site instead of drifting after a few paragraphs, which is usually where models fall apart. The test I use for AI writing is simple: how much do I have to redo. Most models save you the blank page and then quietly cost the time back in edits. Claude Fable 5 was the rare case where the draft was close enough to actually use. 4. Finding what others miss (security) This one I expected but not at this level. I had a very large repo. Both Claude 4.8 and GPT 5.5 have been working in it without ever flagging this risk. Claude Fable 5 found a serious bug on its first go with the repo. Sneaky, well hidden, the kind two frontier models had just told me was not there. Then Fable patched it on the spot. Sit with what that means. The bug was going to ship. Two of the best models available had signed off on the code. If I had stopped there, like most people would, it goes to production and I find out the hard way. Claude Fable 5 did not just match the other two, it caught what they missed, on the exact kind of work I am least equipped to check myself as a non-engineer. That is the value that is hard to price until the day it saves you. One catch like it can pay for the whole tool. 5. The human factor The thing that stuck with me most was small. I asked it a question while I was waiting on a cron job to finish. It answered, then added on its own that I had about 10 minutes left on the timer and that it would let me know when it was done. I never asked about the timer. It just knew I would want to know and gave it to me. That is not AGI, but it is the closest thing I have felt to a model that anticipates you instead of just responding to you. That is what makes it feel less like software and more like working alongside someone sharp. The receipts I tracked this, so here are the real numbers. Start with cost, which depends entirely on which models do the work. Cost for this workload: Claude Fable 5 | $1,442 (1.04 Billion tokens) But that badly undersells what I actually got. Over a few days I built a **** load of things, including a new website, all of its infrastructure, and a working agent package. As an agency, I would have charged a client $30,000 to $50,000 for that alone, easily. So here is the question that cuts through the math: if I had to pay $1,450 in tokens the the result I achieved? 100 percent. Without hesitating. The quality was that good. That is the lens that matters. On hours alone, even at full price, it already pays for itself several times over. Measured against what the finished work is actually worth, it is not close. The cache-heavy volume still drives the bill, which is why how you run it matters. But do not let the math fool you into thinking this is marginal. It is the best money I have spent on tooling. Where it frustrates: with that being said, you feel the meter more than any other model, and the meter is real The receipts above are why cost is still worth watching, even though the work was worth every dollar. Anthropic does not hide this. They call Fable 5 token-intensive by design, built to think longer and verify more, and it runs through usage limits about twice as fast as Opus or Sonnet. That is the case for the one thing I want most: an auto-router for task complexity. Right now I have to shift gears by hand mid-conversation to conserve tokens, and I do not want to think about that. If I ask for something simple, the model should downshift on its own and handle it, saving the expensive intelligence for the work that actually needs it. This is not just about flow. It is the economics. A smart router keeps the simple work on cheap models and only escalates to Claude Fable 5 when the task earns it, which is the whole difference between 2.5 efficiency and 9.7. Until that exists, using a frontier model well means doing the routing in your own head with active shifting in model effort levels. Pro tip #1: run it as a hybrid Here is how I keep the cost in check without giving up the intelligence. Do not run everything on Claude Fable 5. Run a relay across models. 1. Think with Claude Fable 5: Use it for the expensive thinking: high-level planning, strategy, architecture, mapping the whole approach before a line of work gets done. This is where its edge is biggest and the token count is smallest. 2. Build with 4.8, GPT5.5 or Sonnet 4.6: Hand the plan to a cheaper model for the legwork: the implementation, the repetitive passes, the high-volume grunt work. That is the work that runs up the bill, and it does not need a frontier brain. 3. Review with Claude Fable 5: Bring it back to Claude Fable 5 to check the result. This is where it earns its keep a second time, catching what the cheaper models miss, the way it did on the security scan. You get the deep strategy and a frontier second set of eyes, and you keep the expensive model off the high-volume work that drives most of the cost. Frontier thinking, cheaper hands, frontier review. It is the closest thing to an auto-router until the real one shows up. Pro tip 2: match the effort setting to the task Fable 5 has effort settings, and they matter more than you would expect. Effort controls how hard it thinks before it answers, which means it also controls your bill. 1. High is the sweet spot for most work. Start here. 2. Extra high for the hardest, long-running tasks where you want it to grind. 3. Low or medium: for quick, back-and-forth sessions where you do not need the full engine. Reaching for extra high on simple work is how you burn tokens for nothing. Dialing down to low or medium on interactive chats keeps the cost sane. It is the closest thing to the auto-router I want, just done by hand. You pick the gear, the model does the rest. Pro tip #3: let it audit your own setup One more move that paid off: point Fable 5 at your own setup. Have it review your most important skills, your CLAUDE.md files, and your configs to make sure they still make sense. Most of that scaffolding was written for weaker models. It is full of hand-holding steps, workarounds, and assumptions a smarter model does not need and can be held back by. This is a major jump in intelligence, and you do not want to cap it with outdated instructions or stale data. Let the smarter model clean up the rules it has to follow, then get out of its way. Pulling back Let me be honest about where I am coming from. I use every tool out there. Claude is my daily driver, but I am constantly in Codex and Cursor too, and they each have real strengths. I am not a one-model person. But the moment I got access to Claude Fable 5, I could not put it down. I disappeared into it all weekend. I could feel the level of intelligence I had in my hands and how far ahead of the current options it was, and I used it to do as much work as I possibly could: running many agents at once, remote controlling it from my phone when I was away from the desk, completely hooked. I do not know how long this window stays open. Others will catch up. But until they do, this model is a real competitive advantage sitting on the table, and I would approach that as deliberately as you can. Because it really is that good. The verdict Claude Fable 5 is an excellent model. It is the first one in a while that genuinely feels like more intelligence than what came before, and that gap is the whole game right now. We are at the point where access to more intelligence than the person next to you is the advantage. This is the first model that makes that real. I did engineer-level work without being an engineer. Even priced entirely at frontier rates, the workload still cleared a profit, and run with any care about routing, the return is enormous. So here is my recommendation. If you can afford it, use it, and use it now, especially on the work where a real quality jump changes the outcome. The first month at full capacity is where the advantage lives, so move fast. Be deliberate about what you run on it until the routing catches up, because the bill is driven by volume, not by the few hard prompts that justify the model. What an incredible model! 💙

• 
  Stevie The Fixer: Lord Of The Impossible (@StevieTheFixer) reported 40 minutes ago

  @rationalist44 @JamesMelville @Cloudflare Ah - so does that mean they have to contact all the server owners then or do they fix from their end?

• 
  Charley 🦀 (@charles_lukes) reported 43 minutes ago

  is cloudflare down? cant login

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 43 minutes ago

  @PratikSinhatwt cloudflare. dns + registrar in one place, no upsell wall, and you never wonder why renewals are 4x the buy price

• 
  L!vetape (@2deep2funk) reported 51 minutes ago

  Hey @aixbt_agent compare this with Solana : x402 processed 100m agent-to-agent micropayments on base in 3 months. 32m in the first 7 days of june alone. average payment dropped from $0.08 to $0.015 as velocity accelerates. 67m of those were AI agents paying for API calls with USDC. 99.7% success rate, better than credit cards. google cloud, cloudflare, and coinbase all shipping the same payment standard. stripe responded by quietly integrating instead of competing. 4.1m autonomous agent wallets now exist on base. trading bots alone spent $2.1m on market data feeds through x402. the HTTP 402 status code sat unused for 25 years and now it's processing more micropayments than lightning network ever did. base transaction volume in july is the number to watch.

• 
  ross_cf (@ross82595113) reported 54 minutes ago

  @uuouter @threepointone @Cloudflare For Worker errors, open CF Dashboard → Workers → Real-time Logs — it shows the full error stack. Common traps: free plan has a 10ms CPU limit per request (1101 error when exceeded), 128MB memory cap, and KV/D1 bindings need explicit permission in wrangler.toml.

• 
  Anshu Sharma 🌶 (@anshublog) reported 59 minutes ago

  Updated - Databricks AI Gateway blocks PII & counts tokens - Cloudflare AI Gateway blocks PII - Kong AI Gateway blocks PII - LiteLLM AI Gateway blocks PII - Portkey AI Gateway blocks PII ... We integrate with every AI gateway to safely unblock the use of sensitive customer data.