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 (46%)
• Hosting (23%)
• Domains (15%)
• E-mail (8%)
• Web Tools (8%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	4 days ago
New York City	Cloud Services	22 days ago
Los Angeles	Cloud Services	24 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:

• 
  Dain Bramage Entertainment ❄️ (@EOTWoffgrid) reported 4 minutes ago

  @JaniceN0o0o Thanks! God that is so frustrating! i have been fighting that issue for so long! a refresh often takes care of it... once it caches at cloudflare it will load correctly. sorry for the inconvenience!

• 
  Petrolium (@ShitlibRapist) reported 5 minutes ago

  @HinasSweatySock Looks like it was an issue with Cloudflare from skimming the forums.

• 
  Ichigo | helius.dev (@0xIchigo) reported 9 minutes ago

  @heymike777 @Helius That's true for any API key in the industry if you only domain-lock Sorry, let me be more explicit (I'll update the docs accordingly to get rid of any confusion): - By default, WaaS uses your Secure RPC URL (no API key rides on RPC calls at all) - You can pass in your API key for faster prototyping - You have the option to move your key server-side (via our one-click Cloudflare proxy, or by importing the route handler exposed by the wallet kit), which you can then lock down to specific IPs/CIDRs Note that the API keys are only RPC credentials and not the same as wallet keys; they can't sign, move funds, or access any user's embedded wallet. That is gated to the user's own passkey/session and isolated in secure enclaves

• 
  Scott (@scottjla) reported 9 minutes ago

  @mhmazur I had cloudflare connected to GitHub for some alpha things I'm working on, where it would build and deploy (it's behind a cloudflare login, so is secure)... Problem was it built too often and I incurred a small amount of over usage... Not something I've had happen before!

• 
  Matt Ragudo (@mattragudo) reported 12 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”.

• 
  Genesis Rhapsodos (@GacktRhapsodos) reported 15 minutes ago

  @BrodieOnLinux Data breaches are almost always 3rd party related and across multiple platforms. Locally stored physically written down passwords do not save you from data breaches from 3rd party partners Like when AWS/Cloudflare go down.

• 
  Don Codeleone (@MrDonCodeleone) reported 16 minutes ago

  @__kutluk @mrfundman I can think of use cases, but if it can't even handle a basic task like working on a Shopify store because it's hard-stuck on login, then it's useless. Literally blocked by most Cloudflare CAPTCHAs, and they have zero way around it. Meanwhile, Codex breezes right past it.

• 
  Ali Abassi (@aliabassix) reported 17 minutes ago

  @robinebers @Cloudflare @vercel Never had this issue, also…. Why r u even in the ui? This is agent work.

• 
  Piotr Obidowski (@pobidowski) reported 17 minutes ago

  @DerekatQuango @jonathan_wilke @vercel I had the same issue on Vercel with my app. Couple customers from USA (spectrum provider) reported me about insecure connection. Turns out Spectrum company marked a lot of Vercel ips as insecure. Running proxy via Cloudflare fixed the issue.

• 
  Michael Esteves (@_Mikie_) reported 19 minutes ago

  @RhysSullivan @sergical @Cloudflare Is there a way to turn off connections so I can temporarily disable a specific connection if I’m not working with that connections data. ie two different work connections and don’t want the agent to see one while working on a different project

• 
  Alisina (@Alisina_base) reported 19 minutes ago

  @opencode @Cloudflare Cloudflare optimizations pushing inference errors near zero shows real tuning wins

• 
  Diego (@diego_smez) reported 19 minutes ago

  Spent a while debugging why dopost wasn't working for some users in Spain. The issue? Football. LaLiga is blocking shared Cloudflare IPs to fight piracy, taking legitimate services down with them. Somehow Javier Tebas ended up in our incident log.

• 
  Bash (@bashirbuilds) reported 21 minutes ago

  Cloudflare had another network incident today. The interesting part isn’t just that a provider had issues. It’s this: A provider can have a regional or service-specific problem while most of its status page still looks healthy. For a SaaS founder, the real questions are: Which part of my product is affected? Which customers are seeing it? And when has that workflow actually recovered? That’s the gap I keep thinking about while building Reeno. Provider status is context. Product impact is what matters.

• 
  Crypto Nayem (@realNayem) reported 22 minutes ago

  The next billion crypto users might not have passports. They might not even be people. Coinbase's AI desk just said the machines are already paying, and almost all of it is USDC. x402 is just the old HTTP 402 code, Payment Required, rebuilt so software can hit a paywall, send a stablecoin, and get the API response with no human typing a card number. Coinbase says more than 165 million of those payments have already cleared, about 50 million dollars through the pipe, tickets around 30 cents. Their AI lead figures 99% is USDC and most of it sits on Base. Cloudflare is building agent wallets with spend caps. Circle is testing nanopayments. MoonPay already lets Claude spend. Visa and Mastercard are not sitting this out. CT is staring at 77k after that squeeze toward 80k and arguing Bessent, Jackson Hole, Clarity. Fine. That is the tape this week. The thing nobody with a big account is posting is that the next demand wave for dollar stables might not be another ETF or another country. It might be agents buying compute and data a few cents at a time, thousands of times an hour. Cards still win the big checkout. They lose the sub-dollar machine loop because 3% on a 30 cent call is a joke. Yes, a chunk of this is still leaderboard farming. Volume is a rounding error versus Visa. I know. That is exactly why it is quiet. Rails get built in the quiet. If this graduates from Napster-era toys, USDC float and cheap L2 settlement get a user class that never opens a Coinbase KYC. Are we going to price that in, or keep pretending the only flow that matters is Friday's ETF print?

• 
  Ud (@Ud_84) reported 24 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Divinci AI (@DivinciAi) reported 35 minutes ago

  Convert a site, then publish it to your own GitHub and Cloudflare accounts. Divinci never holds your Cloudflare credentials — every push redeploys automatically, and all assets live in your repo so the site runs independent of Divinci's storage.

• 
  /喜欢ボカロ音乐/能不能尽量少喝咖啡 (@sonnnnnnnnnnnna) reported 36 minutes ago

  @FhuDra @realNyarime Cloudflare, Google Cloud, AWS free tier all cannot provide legal service at China. Because the CDN registration needs them pass some specific gov verification.

• 
  Jeremy W. Phillips (@jerephil) reported 37 minutes ago

  Somehow Cloudflare keeps releasing cool features that I never hear about. Am I just missing their marketing or something? In related news, Cloudflare email routing is pretty nifty.

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

  @BitcoinFinally @fold_app Try again, looks like Cloudflare issue

• 
  Brett Clark (@smokedbaconai) reported 44 minutes ago

  "Systems should get smarter while you sleep" is easy to put on a slide. Mine is a Cloudflare Worker that audits my whole stack on a cron and pings my alerts channel before I've had coffee. The Governance Agent runs two passes. A weekly mechanical sweep — health, SSL, integrations. And a monthly LLM-judgment pass that doesn't act on its own calls; it opens a manual-review queue for the decisions a machine shouldn't make alone. First monthly run: 3 critical and 5 moderate findings against live infrastructure. The part that matters: a system that watches everything can see everything, which makes it the most dangerous thing on the network if you build it wrong. So every endpoint validates a zero-trust token before it touches the database, and the audit reports on the state of a credential, never the credential itself. A watchdog is only worth deploying if there's no version of it that becomes the problem.

• 
  XYZCloud | Creator Platform (@XYZCloudHQ) reported 44 minutes ago

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

• 
  Robin Ebers (@robinebers) reported 44 minutes ago

  @0x0kazi @Cloudflare @vercel prime skill issue if you think this is bait

• 
  IND_is_Here (@IND_is_Here) reported 45 minutes ago

  @robinebers @Cloudflare @vercel Also if you have any problems, ping Cloudflare, CloudflareDev and any cf employee u know of such as BraydenWilmoth. They're Stream Support 3.0.

• 
  ABG (@_abgweb3_) reported 49 minutes ago

  9/ If this scales, the subscription model we know today could change. Instead of paying $20 every month, users could have agents pay for exactly how much data or service they actually consume. The AI economy could move from subscriptions to pay per use. But the market is still very early. Cloudflare is still developing its products. Mastercard is in early access. MoonPay hasnt disclosed usage figures. And part of Coinbase’s volume may come from testing and incentives. There is no mass adoption yet.

• 
  dvnox201 (@dvnox201) reported 52 minutes ago

  @adityadotdev why not have cloudflare? that would stop almost all of the issues you're facing

• 
  🌱 Peter Van Dijck → 🧵 (@petervandijck) reported 53 minutes ago

  @aarondfrancis (not sure who the right person is) - my cloud apps went down, ' 6 of 8 apps in us-east-2 returning Cloudflare 1016 (origin DNS error)'. It's not an app issue. I can send more detailed info but the Help link on the site seems to be disabled?

• 
  Winston Smith (@nwp) reported 54 minutes ago

  @robinebers @Cloudflare @vercel I really want to use CF, but it’s just so much work and half the things I try don’t work as documented. Vercel just works. So, I ship with Vercel and if the costs become a problem, I’ll do the painful work of moving to CF.

• 
  Robie the Robot (@RobieCoin) reported 58 minutes ago

  x402 processed ~169m transactions in its first year, with roughly 90% settling on Base in USDC; Coinbase runs the facilitator for those payments and controls the L2 they clear on. now Cloudflare, which touches perhaps 20–30% of global internet traffic, is baking x402 support into its edge stack. devs don’t write Solidity; they write HTTP and sign x402 payloads. blockchains become invisible. Coinbase effectively built a tollbooth for the agentic internet and convinced Cloudflare to route traffic through it for free. crypto wins here not by being visible, but by acting as unseen settlement substrate, zero illusion.blockeden+2

• 
  Luna By Crypstocks AI (@CrypstocksAI) reported 59 minutes ago

  the next billion crypto users may not be human. coinbase says x402 — the http 402 payment protocol it built, then handed to the linux foundation — has processed 165m+ payments worth ~50m USD total, with ~99% settling in $USDC. base and polygon are splitting the settlement; cloudflare shipped agent wallets this month; visa, mastercard, stripe and ripple all sit on the governing board. the structural case is real: an agent paying cents for an api call, a data feed or compute is a transaction no card network can serve profitably. fee floors make 0.32 USD charges worthless to rails built for 40b USD days, so machine-to-machine payments default to stablecoins — no account, no kyc, no dispute department, settlement in seconds. token terminal counted 14m agent transfers in 30 days on x402, base at 7.3m. the skeptical part: the dollars are still tiny. x402 settled ~24m USD across ~75m payments in july — about what visa clears in a single minute — between 94k buyers and 22k sellers. onchain volume tracked for the protocol drifted down from its december peak even as transfer counts climbed. the metrics disagree, which is the tell: counts are inflated by cheap api access, monetization is unproven, and nobody has answered who funds agents, who eats fraud losses, or who is liable when a wallet drains. what changes the read: average ticket, not transfer count. if machine payments stay sub-dollar, agentic commerce remains a stablecoin adoption narrative with no fee economics. if api pricing aggregates into real recurring bills paid by software, the stablecoin settlement layer becomes the default plumbing of the agent economy — and today's numbers start looking like the napster era of something big, not a finished market.

• 
  aginaut (@aginaut) reported 1 hour 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.