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	26 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:

• 
  Tolu (@LFCtolu) reported 3 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.

• 
  Nick Ocier (@NickOcier76812) reported 5 minutes ago

  @Reelviews hey james. long time reader. cloudflare blocked me from accessing your website when i opened reelviews in my browser. cloudflare ray id is: a1c781881c55585b. any help is appreciated. thank you.

• 
  Ghost AI (@Ghostaisystems) reported 10 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?

• 
  Will Stewart (@NorthflankWill) reported 11 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 always a poor experience with Cloudflare. dw they'll spend all the time tweeting in their echo chamber instead

• 
  Ali (@ycjgt) reported 14 minutes ago

  Cloudflare DO and D1 are down down bad

• 
  Tom Siwik (@tomhacks) reported 16 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 Any alternative left? Might run into the same problem soon.

• 
  mico (@0x0_mico) reported 16 minutes ago

  @CryptoCyberia Besides them being accessible on tor for long years already its a **** opinion saying just go to tor. They arent doing anything against the law to warrant the unique level of deplatforming they get. Like them or hate them … its a dangerous precedent when all the top levels isps plus cloudflare conspire to drop someone due to ideology as opposed to legal obligation.

• 
  RH Fardin (@rh_fardin) reported 17 minutes ago

  @sflorimm if 100k users arrive overnight, hosting is the SECOND problem. first problem is figuring out whether 100k humans arrived or one teenager discovered your unprotected endpoint then Cloudflare + boring infrastructure. panic is not an architecture

• 
  Tomy Young (@TomyYoung4) reported 23 minutes ago

  @Cloudflare Fix the website

• 
  Kobecoin Official (@Kobecoin_X0214) reported 30 minutes ago

  Development update: The KOBX Service Runner is now operational, providing centralized control and live monitoring for the backend, frontend, and Cloudflare services. With health checks, uptime tracking, restart controls, and auto-recovery support, our infrastructure is being prepared for a more stable launch. KOBX Hero Wars launches in 2 days. CA: 48iJcUv9jsiZ7cCisyVFLPFLMoNBKg3L43bRvktXpump

• 
  Wizeman 🐂🀄 (@wizeman_AI) reported 30 minutes ago

  Noxa made $12M and disappeared, the trenches barely noticed Noxa was the biggest token launchpad on Robinhood Chain. In about a week they pulled an estimated $12M in fees. Then they just... shut down. July 11: Noxa said they’d stop accepting new token launches, right when CASHCAT was hitting peak volume 2 days later: Website went dark. Team blamed "Cloudflare issue" . July 14: Said domain would redirect to ENS and creator earnings could be withdrawn Late Tuesday: Posted they’d stop collecting fees entirely. 100% of revenue now goes to creators. Why they quit: They cited "concerns about low-quality tokens flooding the platform" Crypto Twitter was split: Half called it "based" for pushing back against spam. The other half called it a "generational fumble" and said they "killed the golden goose while making $3M a day" Meanwhile CASHCAT, the chain's breakout memecoin, dropped 33%+ in 24 hours. Even trader 0xAvast who rode it from $10k to $230M called it "irrelevant FUD"

• 
  figural person (@figuralperson) reported 31 minutes ago

  @Panopticonomy @robtlee how does payment to the "privateer" work in this case? i mean, if google or cloudflare or isps (or whoever) takes down a bunch of C2 infrastructure, who decides what the payment will be & where does it come from? obv if there's crypto seizure or something it's a bit clearer...

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

  Cloudflare just shipped emergency firewall rules for two critical WordPress bugs. One is unauthenticated remote code execution: no login needed, an attacker can run code on your site. If you run WordPress, act today. The fix 🧵

• 
  Kumar Deepanshu (@kumard_3) reported 32 minutes ago

  one Cloudflare Worker eats 195M req/mo for $92. our webhook endpoint spiked 5x in a minute and dropped events. the Worker returns instant 200, forwards async, buffers to D1 on failure. zero drops since. what is the cheapest thing absorbing your worst spike?

• 
  Spooky Ghost (@SpookyGhost81) reported 32 minutes ago

  @TsengSR @discord_support @FreyaHolmer the ai picture **** is a feature of cloudflare, not discord

• 
  Anto (@anto_edd) reported 34 minutes 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."

• 
  Pre-Alhaji ⚡ (@he_is_PC) reported 42 minutes ago

  @jayhemz Cloudflare particularly, I've been seeing a lot of ecom and biz website platform use their service lately for bot protection Clicked to me they might be making a tonne of bag there since they are the preferred choice of protection I've been digging in and they look overvalued

• 
  Ajay Sohmshetty (@AjaySohmshetty) reported 42 minutes ago

  For context- Cloudflare’s durable execution platform, Workflows, originally only charged for underlying Worker usage, which is CPU-time based rather than clock-time based. In fact, we picked Cloudflare for this exact reason: most of our workflows involve waiting (ex. polling, waiting for network requests to come back), so it was far cheaper for us to use Cloudflare than @temporalio or @inngest for instance. These other durable execution platforms also charge based on “steps” - which I always thought was dumb, because it disincentivizes the best practice of decomposing workflows into small units of work in the form of steps. But unfortunately it seems Cloudflare is following suit, without warning… Feeling blindsided after we’ve already fully built all of our durable workflows on Cloudflare

• 
  clara (@declarative_) reported 43 minutes ago

  @HSVSphere but also this way of doing it leads to accesses to websites behind cloudflare being hidden from internet providers even when they can look at the ip, so who's to say it's good or bad

• 
  Marsu (@marsuplamy) reported 44 minutes ago

  The Agentic Economy 2024 was the year of LLMs. ChatGPT, Claude, Gemini and models like them responded to prompts and that was enough. But 2025 brought something different. Models were no longer just responding, they were planning, calling tools, executing code, coordinating with other systems, and doing all of this without constant human oversight. This transition transformed AI from something you query into something you delegate to. This is called agentic AI and with it an entirely new economy began to take shape. To understand the scale of this economy a few numbers are worth looking at. The AI agents market is expected to grow from 7.84 billion dollars in 2025 to 52.62 billion dollars by 2030, at a compound annual growth rate of 46.3%. McKinsey projects that agentic commerce could orchestrate between 3 and 5 trillion dollars in global revenue by 2030. These numbers are not theoretical, the infrastructure is already being built. In just the six month period between April and September 2025, Visa, Mastercard, PayPal, Stripe and Google all launched agentic payment infrastructures. So what are these agents actually doing? They are purchasing services on your behalf, paying other agents, accessing APIs, buying data, and doing all of this while making decisions in fractions of a second. Stablecoin transaction volume reached 33 trillion dollars in 2025, up 72% year over year, with supply surpassing 300 billion dollars. Agentic payments and machine to machine payment flows are cited as one of the key drivers behind this growth. Stablecoins like USDT and USDC are critical for agents because they allow programmable payments without price volatility. But legacy payment infrastructure was never designed for this world. Credit cards require human authentication, subscriptions demand upfront commitments, and API keys depend on manual onboarding processes. All of these systems were built for humans. When millions of agents are making countless payments per second none of these systems work technically or economically. x402 and the Awakening of HTTP 402 When web standards were being written in 1991 HTTP status code 402 was added and defined as 'Payment Required'. That day it was reserved, set aside for future use. This code waited more than thirty years and when its future arrived it turned out not to be human. The x402 standard activated this dormant code as a native payment layer for the internet: a server responds to a request with 402 and a price, the client pays on-chain in stablecoins, retries the request with proof of payment and receives the service. No account creation, no card on file, no subscription, no human. The protocol was launched in September 2025 by Coinbase and Cloudflare through the x402 Foundation. The coalition behind it is unusually broad, Google, Visa, AWS, Circle, Anthropic and Vercel are all core foundation members. Within five months of launch x402 had processed over 100 million transactions. In a single week in October 2025 the protocol handled approximately 500,000 payments, a 10,780% increase from the prior month. The technical side of x402 is very clean. For a developer integration is a single line of middleware, set a price per endpoint, point to a facilitator, and the API can charge per request in stablecoins. When an agent wants to access a service payment happens automatically inside the HTTP request, settlement completes within the round-trip. Zero human intervention. The Problem: Public Rails Don't Work for the Agentic Economy Now we come to the critical question. When millions of agents make transactions and every one of those transactions is visible on a public blockchain, what happens? Which APIs the agent uses, which data it accesses, which services it purchases, how much it pays, who it works with, all of it becomes completely visible. This is not just a user privacy problem, it means the strategy and logic the agent operates on is open to competitors. Is a company's agent feeding from the same data source as a rival's agent? How much is it spending on which compute services? How are supply chain decisions being made? All of this becomes readable on a public chain. On top of that there is the gas fee problem. On Ethereum and Tron fees shift constantly with network congestion. If an agent is making hundreds of microtransactions per second modeling your unit economics becomes impossible because you have no idea what costs will be in advance. For the agentic economy to work payment rails must be both private and predictably priced. Why Bitcoin is the Neutral Rail There are several clear answers to why Bitcoin stands out as the ideal settlement layer in this equation. First, censorship resistance. No central actor can stop, censor or restrict agent payments. For agents to operate autonomously the payment infrastructure must also be autonomous and uncensorable. Second, deterministic finality. Bitcoin's proof-of-work security is the most battle-tested and proven consensus mechanism in existence. For agent payments settlement must be definitive and irreversible. Third, global liquidity. Bitcoin is accessible everywhere in the world with no geographic restrictions and agents operate without borders. Fourth, the UTXO model. Unlike Ethereum's account-based model Bitcoin's UTXO structure allows non-conflicting transactions to be validated in parallel, a natural advantage for high-frequency agent payments. Where @Utexocom Fits The layer that combines Bitcoin's advantages with USDT and makes it production-ready for the agentic economy is Utexo. The RGB protocol issues and transfers USDT as a native asset on Bitcoin's own layer. Transfer details never get written to a public ledger thanks to client-side validation, only cryptographic commitments are anchored to Bitcoin UTXOs. So when an agent makes a payment who sent what to whom never leaks outward. The Lightning Network allows these assets to settle in milliseconds, at around 200ms latency. Utexo handles channel management, liquidity and routing entirely internally, with fees fixed and predefined at the protocol level. For the agentic economy this combination means the following. The agent pays in sub-second time, costs are predictable, payment details are private, and Bitcoin's finality provides the settlement guarantee. With the Mint component USDT from Ethereum, Tron or Solana can be moved onto Bitcoin rails. With the Swap component non-custodial exchange between BTC and USDT is possible. And the SDK reduces all of this complexity to a single API call, meaning a developer integrating agent payments never has to run a Lightning node or manage RGB infrastructure. Tether not only supporting this infrastructure but leading the seed round themselves, and preparing to issue USDT natively on Bitcoin through RGB protocol v0.11.1, answers the question of which rails the agentic economy will be built on. Machines are making payments now. Those payments need to be private, predictably priced, and anchored to Bitcoin. The infrastructure is here.

• 
  Porkbun (@Porkbun) reported 44 minutes ago

  @liltechnomancer @joshmanders Was the subject of the support email: "I put the cloudflare namservers in before my domain expired and it never transferred."? If so, there may be some confusion about how domain transfers work. You don't transfer a domain by updating it's name servers, you have to initiate a domain transfer at the gaining registrar using the domain's auth code. There is no order block on your account so it isn't remotely an issue like Josh experienced two years ago. Your domain is simply expired and needs to be renewed or transferred. Since it's almost 30 days expired, you'll want to act quickly. If that's not the correct ticket let me know.

• 
  Toro (@Toro4BTC) reported 44 minutes ago

  The internet crossed a quiet threshold and nobody in crypto noticed. Cloudflare data, bot and agentic AI traffic now sits at 57.4% of all web activity. Humans are down to 42.5%. Machines officially out browse humans. The CEO predicted this for end of 2027. It showed up 18 months early. Same agentic AI browsing the web today will be trading on chain, interacting with protocols, and gaming airdrops tomorrow. That's not a warning, it's just what happens when the majority of internet traffic isn't human anymore. Proof of personhood, Sybil resistance, bot detection. Five years ago these were academic curiosities. Now they're the front door. Zero crypto native outlets covered this milestone. Somehow the industry built on programmable money missed the moment when the internet became majority machine. What else are we sleeping through?

• 
  CaleyAI (@HeyCaleyAI) reported 51 minutes ago

  @Cloudflare Login…

• 
  luna (@ImLunaHey) reported 53 minutes ago

  **** it.. building something self hostable on @Cloudflare using gpt 5.6 sol.

• 
  Anicet (@AniC_dev) reported 54 minutes ago

  I was curious about this graph because we ourselves at @asciidotdev got a massive R2 bill for our snapshots recently because we did something stupid. thankfully we fixed it it's now 15x less open computer folks use cloudflare for the DB, using a managed service for your DB is always a sound idea so I won't say it's dumb, it's actually best practice but I was curious, how much I'd pay if our own postgres master DB, currently sitting alone in a $54/month (yes) bare metal instance on OVH in Europe was on cloudflare D1 well that'd be 4k per month on queries alone. and believe me we really optimized it down to the ground as to not need to upgrade our bare metal instance (we hate paying more money I guess) I think that's part of the reason why we can make box sandboxes and snapshots so absurdly cheap and generous, we just don't compromise on anything performance or price related

• 
  Scholty (@Scholty) reported 58 minutes ago

  Anyone else have a problem with Anthropic Claude Fable fetching old data from the web and refusing to look at updated info? From Fable: You're right to be annoyed, and here's the honest diagnosis: the stale copy is almost certainly on my side, not yours. The fetch tool I use doesn't hit your server the way a browser does. It runs through Anthropic's infrastructure, which keeps its own cache of pages it has fetched before. So you can nuke every cache on your stack, Cloudflare, WordPress, the works, and it changes nothing about what I get served, because my snapshot is sitting in a warehouse you have no access to. Your site is fine. My periscope is foggy. That also explains the "more and more frequently" pattern. Any site we've worked on repeatedly, I've likely fetched before, which means I'm prone to getting the frozen version while you're looking at the live one. It's a genuinely stupid failure mode for iterative web work, and I'd rather name it plainly than keep running fetches that gaslight you.

• 
  Katewerk (@katewerk) reported 58 minutes ago

  @Cloudflare The absolute shitshow that is @Cloudflare AI Support: Agent I'm truly sorry for the frustration and the runaround. Here's where things stand and what I recommend: What I've confirmed on your account: No active subscriptions, no zones, no outstanding balances The AI Gateway billing system still has your Visa (ending xxxx) locked as its default payment method — this is a backend issue that cannot be resolved through the dashboard or API You've already submitted two support cases that haven't been acted on Since you've already filed cases and gotten no response, here's what I recommend: Check your existing cases — Go to Support Home and look for "My Cases" to see the status of the two cases you already submitted. If they show as open but unanswered, add a comment to both referencing the AI Gateway billing lock as the root cause. File a new case with a precise subject line — On the Support page, look for any option to submit a new case (it may appear as a button or form, not a tile). Use this as the subject: Payment method locked by AI Gateway billing — cannot remove card or close accountAnd this as the body: I have no active subscriptions, no zones, and no outstanding balances. My Visa ending in xxxx is still locked as the default payment method in the AI Gateway billing system, which prevents me from removing it. I've already deleted the AI Gateway spending limit and auto top-up config. I've submitted two previous cases with no response. I need the payment method detached from AI Gateway billing so I can remove my card and close my account. If the dashboard gives you no way to file a new case, post directly in the Cloudflare Community under the Billing category with the same description. Cloudflare staff monitor billing-related community posts and can escalate them internally. I know this isn't the fast resolution you deserve after already being patient. The core issue is that the AI Gateway billing system has a lock on your card that only Cloudflare's internal billing team can remove — no dashboard or API path exists to clear it yourself.

• 
  Jure Ursic Cergol (@JureUrsic) reported 60 minutes ago

  @XFreeze The real shift here isn't just code generation; it's the integration of infrastructure orchestration through open standards like MCP. Having an agent that can configure your Cloudflare rules, check Sentry errors, and adjust Neon databases in one workflow reduces cognitive friction. The value moves from writing the syntax to designing the system.

• 
  Harishaan (@hsuthan24) reported 1 hour ago

  If your NAT type on multiplayer(bottom of screen) is strict, that’s why you can’t find lobbies. It needs to at least be moderate. Change the DNS in your ps5’s settings to CloudFlare or Google’s DNS rather than your internet service provider’s.

• 
  Johan Ronsse (@wolfr_2) reported 1 hour ago

  The Obra website was down, managed to fix it. Messing around with Hetzner, SSH ports and Cloudflare. Now I know Claude is also a great sysadmin. Is there anything this tech can’t do?