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

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	3 days ago
New York City	Cloud Services	22 days ago
Los Angeles	Cloud Services	23 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	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:

• 
  Joshua Montgomery (@oojoshua) reported 4 minutes ago

  @HawaiianTel - You are dropping all traffic to Cloudflare. Just Cloudflare, but that's 18% of the Internet. You've been dropping it on and off for a week. Can you stabilize it so we can have reliable Internet? Been a week of no power and this is adding to the problems here.

• 
  Tobi (@To_bi_Bakare) reported 7 minutes ago

  It is. But Cloudflare doesn't support Naira, and most Nigerian bank cards are naira-restricted for international payments by default. A few ways around this🧵

• 
  aginaut (@aginaut) reported 8 minutes ago

  AWS AgentCore Payments: The Rails Are Opening. The Junction Is Not Settled. On 18 August, AWS made an odd move for a platform widening its role in agent payments: it declined to choose a payment rail. AgentCore Payments moved from preview to general availability with MPP beside x402 and, according to AWS, one developer integration across both. AWS imposes no extra charge for its Payments APIs. Wallet providers still charge; Gateway, Policy and CloudWatch still meter usage. If AWS were competing primarily for the rail, supporting two rivals without an API fee would be a peculiar opening move. The mismatch deepens at the other side of the transaction: AWS WAF can already challenge an AI agent for an x402 payment through Coinbase before admitting it to content. MPP and Stripe support were still described as forthcoming. For an allocator, protocol adoption is therefore the wrong scoreboard. If the rail is becoming plural and inexpensive to integrate through AWS, which part of the transaction is AWS trying to make indispensable? The missing fee makes the bundle the live hypothesis AWS is not alone in making payment rails interchangeable. Cloudflare supports x402 and MPP. Visa and Mastercard are building protocol-agnostic or multi-rail agent-payment capabilities. The Linux Foundation’s x402 Foundation brings cloud, payment and technology companies into the same standards effort. This demonstrates protocol plurality and standards activity—not adoption or power. That may shift the source of scarcity. As payment syntax becomes easier to support, a potentially scarcer task is coordinating the records around it: identity, authority, counterparty, budget, policy, execution and evidence. AgentCore already places several of those functions near one another. Payments now sits beside identity, Gateway discovery, bounded sessions, Policy pathways and observability. WAF separately approaches seller admission. These are not one integrated marketplace, and AWS does not control the entire transaction. They do, however, give AWS an early option on the environment in which agentic economic action is governed. The Platform Envelopment hypothesis Thomas Eisenmann, Geoffrey Parker and Marshall Van Alstyne call this platform envelopment: a platform enters an adjacent market by bundling a new function that shares users and technical components with its existing services. The bundle changes the contest. A standalone payment service must now compete with payments embedded where agents are identified, authorised, routed and observed. That is the strategic possibility in AgentCore: protocol-agnostic support could let AWS coordinate several payment systems inside one governed environment while making its surrounding services more useful together. Yet bundling alone is not platform power. If users can bypass AgentCore, carry identity and evidence elsewhere, or multi-home without friction, this is integration—not durable envelopment. Follow the right, not just the payment An autonomous transaction rarely specifies every relevant contingency in advance. It still needs answers to ordinary institutional questions: Who approved the spend? Was the recipient valid? What was delivered? Which record proves it? Who can revoke authority or remedy failure? This is why payment begins to cluster with identity, policy, audit, reputation and recourse. The payment message moves value. The surrounding records make the action acceptable to the next institution. One diagnostic keeps the layers separate: RAIL → JUNCTION → RIGHT Rail: What became interchangeable? Junction: Which operating records must still be reconciled? Right: Whose record will the next institution accept? Today, those rights remain divided. The enterprise principal funds, mandates and revokes. Application code must validate the recipient. AgentCore can constrain amount and time, route through supported protocols and preserve operational evidence. Wallet providers sign. Merchants price and deliver. Financial networks and payment providers retain settlement, fraud and dispute functions. A payment proof therefore establishes neither satisfactory delivery nor a universal right to refund or remedy. Portable-record systems form a counter-architecture. AP2 under FIDO stewardship and W3C Verifiable Credentials target portable mandates or identity evidence. On Ethereum, draft ERC-8004 and ERC-8183—with Virtuals ACP implementing the latter direction—target identity, reputation, validation and escrow. This is documented standards and implementation activity, not evidence of broad adoption or transferred power. Open rails cut both ways Modularity is the counterforce to envelopment. Open interfaces can commoditise the rails beneath AWS, increasing the value of AgentCore. They can also commoditise AgentCore if customers can move their identities, mandates, policies, wallets, reputation and audit history intact. The practical test is not whether an interface is called open. It is whether substitution works: Can an enterprise multi-home cheaply? Can another cloud or network recognise the same mandate? Who controls schema changes, revocation and the evidence required after failure? Until those answers settle, AWS holds a candidate position—not the junction itself. Three futures from the same move The current evidence supports an option space rather than one forecast. 1. Managed-junction consolidation. If AgentCore Payments drives attachment to AWS identity, policy, discovery and observability—and operating state becomes expensive to move—value could concentrate around managed control planes and their security, compliance and monitoring complements. 2. Federated recognition. If portable mandates, credentials, reputation and escrow records gain acceptance across clouds, wallets and marketplaces, value could move towards cross-platform identity, verification, translation and assurance rather than one platform owner. 3. Institutional retention. If enterprise procurement and treasury continue to hold spending authority while Visa, Mastercard, Stripe and other financial actors retain acceptance, fraud, settlement and remedy, cloud payments would remain useful orchestration while the authoritative economic record stayed with enterprise and financial institutions. These futures can coexist. Low-value machine purchases may favour managed automation, while consequential enterprise actions remain institutionally governed. The receipts that decide the path Watch four things: Attachment: Does Payments increase use or retention across AgentCore? Recognition: Which counterparties accept the session, policy and audit records produced or held around AgentCore? Portability: Can those records move across clouds, wallets, networks and marketplaces without material loss? Economics and remedy: Where do switching costs, adjacent revenue, disputes and paid-but-no-service outcomes accumulate? Protocol adoption alone is not enough to underwrite power. At minimum, Payments must produce attachment plus either non-portable operating state or measurable adjacent economics. The allocator’s question is not which payment protocol wins. It is whose record the next institution accepts, whether that record can leave—and which future becomes investable as those answers emerge. AWS has taken an option on power. Power has not yet transferred. Notes & conceptual credits: Platform Envelopment follows Eisenmann, Parker and Van Alstyne. The supporting logic draws on transaction-cost and incomplete-contract research associated with Coase, Williamson and the Grossman–Hart–Moore tradition; the countercase draws on Baldwin and Clark’s modularity work and Ghazawneh and Henfridsson’s boundary-resource research. RAIL → JUNCTION → RIGHT and its application here are Aginaut syntheses. Product and standards claims remain bounded by the first-party materials available on 22 August 2026.

• 
  Aymane (@aymanemsi) reported 9 minutes ago

  @blendimehmeti3 @opencode @Cloudflare Damn 3$ is not that much at all lol

• 
  Sassan Haradji (@sassanh) reported 9 minutes ago

  @opencode @Cloudflare I agree with the first three words: "errors are back"

• 
  Phillip Shoemaker (@pbsIdentity) reported 10 minutes ago

  India just ordered hundreds of Google Firebase accounts shut down after authorities found scammers using the platform to impersonate major banks. At least 57 Firebase-hosted websites and databases were targeted for takedown this month alone. Some mimicked banks. Others distributed malicious Android apps. Some were designed to steal financial information from phones. Here's what I find interesting. Firebase isn't some shady hosting company operating out of a basement. It's Google infrastructure. That's exactly why criminals want it. We've spent years teaching people to look for obvious signs of scams. Weird domain. Broken English. Sketchy hosting. Browser warning. No HTTPS. But increasingly the attacker doesn't need to build suspicious-looking infrastructure. They borrow legitimate infrastructure. Google. Microsoft. Cloudflare. GitHub. Dropbox. Whatever gives the attack credibility and reliability. Now imagine the average person inspecting the link. They recognize Google. The connection is encrypted. The page loads perfectly. The certificate is valid. Everything their brain has been trained to interpret as: SAFE may technically be true. Except the person controlling the page is a criminal. That's an important distinction. HTTPS proves your connection to the website is encrypted. It does not prove the person operating the website is honest. A Google URL proves Google is providing infrastructure. It doesn't necessarily prove Google created the content you're looking at. The little padlock was never a morality detector. We just accidentally trained an entire generation to treat it like one. India says scammers have increasingly shifted toward Firebase because its legitimate development tools and database functionality make it useful infrastructure for fraudulent sites and apps.

• 
  Matthieu H. (@twMatthieuH) reported 10 minutes ago

  The stack: React Native + Expo, TypeScript, Hono on Cloudflare Workers. Boring on purpose. And AI-assisted everywhere: coding, support replies, content, ASO. When you have a few hours per week, you don't want to fight your tools.

• 
  CEO Govibe.org (@govibeorg) reported 13 minutes ago

  i dont use AWS or Cloudflare i host my own DNS servers with in LA and NY tier1 fiber and myself as tier2 operator of my own network low latency, i dont depends on other if Cloudflare or Amazon crash its doesnt affect my servers..

• 
  Sam Kovacs (@SamKovX) reported 15 minutes ago

  @elBacarisse Thanks this was helpful. We migrated nameservers to Cloudflare and some internet providers were still heading to Bluehost. This should self-resolve 24 hours from now due to the 48hr TTL, but I implemented a quick fix. Can you try a hard refresh and let me know if that resovles it? Thanks. Sam

• 
  solopath (@pathlessknown) reported 15 minutes ago

  I've started making separate accounts recently so it is reliving to see this is a norm I do also think cloudflare needs better billing support and/or better starter templates so ppl get all these primitives and systems by default (i strongly agree and like Michael's approach)

• 
  Robin Ebers (@robinebers) reported 17 minutes ago

  wanted to give @Cloudflare a shot for storage and workers but then realized they don't have monthly spending caps?! any bug, abuse or some vibe coded **** could potentially generate thousands of dollars and there's no way to prevent it? you can set up a 'notification' - yeah great, thanks what the actual

• 
  Ruben de Groot (@rubenpdegroot) reported 18 minutes ago

  @paoloanzn honestly t3code has been doing exactly this for me, i just got one 64gb ram vps on contabo and setup t3code there, i can just use their web ui from desktop or phone (behind cloudflare tunnel for security), you can just clone as many repos as you want ofc, and i just created a skill on how the t3api works such that claude code can just spin up threads inside of it no need for multiple VMs , just one big VPS only thing is that they dont support pi

• 
  Ben Patton (@benapatton) reported 18 minutes ago

  @flybayer @inngest @flydotio Sorry that’s why I indicated unrelated. It’s hooked into Cloudflare for me to auto fix issues and report back I’m mostly using it for more fine grained personal assistant type workflows/checkins

• 
  Sumedh Bengale (@ssbengale) reported 22 minutes ago

  @omkarships Cloudflare, as I change the Nameservera on other providers to cloudflare either way. They are the cheapest one, without the vendor lock in discounts. Too bad that they don't support a lot of TLDs

• 
  World Tech Research (@WorldTechRsrch) reported 27 minutes ago

  Cloudflare $NET rose 5.10% while AI hardware slid. The same direction repeated all week. Company-specific catalysts alone cannot fully explain the move. Cloudflare had raised revenue guidance and expectations for platform growth as non-human AI traffic increased. Oracle rose 3.10% after the U.S. Department of Veterans Affairs increased the ceiling on its Oracle Health electronic health record modernization contract by $17 billion, to about $27 billion. Palantir +3.44% Palo Alto Networks +2.38% Salesforce +1.82% Only ServiceNow fell, down 0.98%. Enterprise software names mostly moved together that day. Each company clearly had its own catalyst. The key is that enterprise software rose whenever AI hardware fell, a pattern that repeated throughout the week. This looks more like long-short flows between hardware and software baskets than a new conclusion about AI demand.

• 
  Kenton Varda (@KentonVarda) reported 28 minutes ago

  @m0hilll @thdxr @arnvbnsl Reusing isolates keeps costs down and lets us bill for CPU time only instead of total request duration. Vercel built Fluid Compute to accomplish the same thing -- explicitly getting away from Lambda's inefficient one-instance-per-request model. That said, we (Cloudflare) have some cool (though long-term) stuff in the works to make it possible for every request to have its own isolate, without blowing up memory usage... deep V8 changes involved.

• 
  M. Yahia - ghostex.dev (@maddada) reported 29 minutes ago

  @robinebers @BehEvans @Cloudflare I default to cloudflare currently for most of my projects, last I looked there wasn't something as all-in-one and as competitive on price (for non-enterprise) Way easier to use than AWS + free or much cheaper than others like railway/vercel/netlify/etc. You get domains/dns/free protection and a bunch of stuff in 1 dashboard. While if you use some of the others you'd have to set up cloudflare separately (bit of a hassle). As long as you're not "Enterprise" they offer very generous prices. Also if you can make your app run on workers then it's one of the cheapest ways to host/scale an app since they charge you for active CPU milliseconds. I'm sorry for any mistakes or bad explanation, wrote this quick of the top of my head.

• 
  Mathieu Céraline (@mathcrln) reported 34 minutes ago

  @MrPunyapal @LaravelArtisans First party support for OG image generation. I mean, I know there are solutions like Browserhot, Cloudflare Browser Image API, etc but would love to see a first party approach to this.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 35 minutes ago

  @Cloudflare Please, fix human verification

• 
  Matt Ragudo (@mattragudo) reported 35 minutes ago

  @Bsoutherland23 So right now there really isn’t a CEO agent. Like one that makes decisions on everything. Most agents rely on scope. For example, I have all of my website content work, and automated trading research and content handled by agents. A group of agents. My websites (I have 6 different that I’m focusing on now): Research 3x a week, find stuff interesting based on what I’ve told it plus what’s trending and what’s showing up in socials/news. Reasoning agent then looks at what’s worth publishing based on what’s out there and what my ideal client would want to read that needs to be curated further. Sends that list to my writers. Writer agents draft based on the voice and guidelines that I have given it. Research check agents review the articles based on what we are able to say, verify claims and statements and look up references and links them. Returns this to the writer if there are any issues. Researcher waits for confirmation from writer. Researcher, once done, sends it to a proof reader Proofreader, who further checks one last time for consistency, now also checks for publication rules and makes sure it’s compliant with the verticals. Lastly, a poster with posting credentials will push it to cloudflare to post. All of this is then reviewed monthly for any hold ups in the process by a loop operator whose job is to make sure I (Matt), need not be bothered and that the content is being posted and analytics are doing well. Analytics, which are reviewed by another “Agent system”.

• 
  Abdellatif (@Abdella6if) reported 38 minutes ago

  @harisbuild @Cloudflare interesting, will look into it. Does cloudflare support BYOK?

• 
  Melek Turkoglu - Ekrem İmamoğlu’nu Serbest Bırakın (@AvukatMeleknur) reported 39 minutes ago

  @Dynadot 🚨 Active phishing & brand-spoofing domain reported to Case ID: ddcn:9Cr7A6QO7i7u7t:ddcn The site mimics exposes a broken/failed "INVALID" license seal, and targets users via @Cloudflare proxy (104.21.31.33). #Infosec #Phishing #OSINT

• 
  #OpSupportsOp (@GUNSGOATSGARDEN) reported 40 minutes ago

  @opencode @Cloudflare Ox is completely broken for me, now.

• 
  M. Yahia - ghostex.dev (@maddada) reported 43 minutes ago

  @robinebers @Cloudflare Damn that's scary

• 
  JohnNguyen 🔆 (@ThuyTrang108) reported 45 minutes ago

  The next wave of crypto users might not be humans, but AI. As AI agents become increasingly capable of autonomously searching for information, calling APIs, purchasing data, and executing tasks on behalf of humans, they require a way to make payments and stablecoins are emerging as a highly suitable option. Coinbase’s x402 protocol has processed over 165 million transactions totaling approximately $50 million; nearly 99% of these utilized USDC, with an average value of just around 30 cents per transaction. These figures signal the formation of an entirely new market: millions of automated, 24/7 micropayments occurring between software systems. As major players like Visa, Mastercard, Cloudflare, and MoonPay begin building infrastructure to facilitate payments by AI agents within controlled limits, stablecoins could evolve beyond mere money-transfer tools for humans to become the payment system for the AI ​​agent economy.

• 
  solopath (@pathlessknown) reported 47 minutes ago

  Only thing that worries me is I think cloudflare uses sale force or something for their jank support I had a weird encounter with it recently and it was bad / funny And also I hope they don’t connect the support system to their admin

• 
  ⚡BeefButterBTC⚡ AKA - Big Pleb (@BeefButterBTC) reported 50 minutes ago

  @BitcoinFinally @fold_app Try again, looks like Cloudflare issue

• 
  Onur Genes 🐺 (@onurgenes) reported 51 minutes ago

  @jonathan_wilke also probably someone reported it. cloudflare first takes down the website and then asks you to prove that your website is not fraud. you should definitely check that

• 
  Robert Youssef (@rryssf) reported 52 minutes ago

  Claude and ChatGPT still can't do this. Cloudflare just open sourced a computer for AI agents, and it fixes one of the most annoying limits in the entire agent stack. Every time you start a new session with Claude or ChatGPT, whatever files or context the agent built up just vanishes. The agent writes notes, tracks progress, remembers where it left off, and then the session ends and all of it is gone. You start from zero again. Most agent frameworks also spin up a full Linux container just to run a simple command like sorting files or grepping through a directory. That's a lot of overhead for something this basic. Until now. Cloudflare shipped Computer, an open source, MIT licensed runtime that gives an AI agent its own persistent machine instead of squeezing every task into a throwaway container. The core idea is a virtual filesystem that lives inside a Durable Object. The Durable Object holds the real state in SQLite, and it exposes one pluggable execution surface through workspace.runtime. Because the state is durable, the agent knows exactly where it left off automatically. No manual saving, no rebuilding context from scratch. The traction is staggering: It hit over 8,000 GitHub stars and 456 forks within days of shipping, and it trended to number one on GitHub across every language, not just TypeScript. Cloudflare claims it only needs to spin up a full Linux container about 10% of the time. The rest runs directly through the durable filesystem. Claude and ChatGPT still treat every session as disposable, and every trivial file operation as worth a full container. If durable, cheap memory becomes the default for agents, the container stops being the unit of compute. The filesystem is.

• 
  The American Protectors of Journalistic Freedom (@melisandrePro) reported 59 minutes ago

  @TonySeruga Cloudflare is a liar and terrible company. Older systems won’t let us launch websites. I have to use my cell phone to open the links instead.