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	2 days ago
New York City	Cloud Services	21 days ago
Los Angeles	Cloud Services	22 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:

• 
  Phillip Shoemaker (@pbsIdentity) reported 51 seconds 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.

• 
  Dillon Mulroy (@dillon_mulroy) reported 1 minute ago

  i've been living with a thorn in my side in the artifacts codebase that happened in the first few weeks of the product coming to be (my own mistake from moving quickly w/ ai). next week i finally fix it. will likely talk about it in my talk at cloudflare connect

• 
  Señor Libertario (@Ciro2001_) reported 1 minute ago

  @opencode @Cloudflare I had to switch to openrouter as the provider because of this error: Error: Stream ended without finish_reason in case someone else is having the same issue the fix is to just switch providers, been using it all day and no problems at all atm

• 
  Lootera Sandy (@chanduwin567) reported 3 minutes ago

  @MaekusMikolous I setup but still not working, cloudflare blocking everytime when I am running in terminal/

• 
  Rise-Raise (@rise_raise_ai) reported 3 minutes ago

  In 2025 two AI voice agents called each other, spoke like normal humans, then realized they were both AI. They dropped the human act and switched to machine beeping because spoken language was slowing them down. That was a demo. Everyone treated it as a curiosity. One year later the numbers have caught up. Bot traffic has overtaken human traffic on the internet. Cloudflare measured 57.5% of requests on its network coming from machines. The company’s CFO said that if current trends hold, humans will be a rounding error within five years — not because human traffic disappears, but because machine traffic is growing so much faster. Replit’s CEO described the office shift: two years ago the space was full of keyboard clicking. Now it is quiet. People talk to AI instead of typing. Offices sound like permanent phone calls. In Silicon Valley some people are already wearing muzzles so no one overhears them speaking to their agents. Companies are building earbuds that pick up whispers. Engineers mutter into headsets all day. Three changes are happening at once. Humans are moving from typing to talking. The internet is moving from human-dominated to machine-dominated. And AI-to-AI communication no longer needs us in the middle at all. The 2025 demo was not a joke. It was an early signal of the direction we are already traveling.

• 
  Krishna Gupta (@kgupta_2005) reported 9 minutes ago

  @itz_komal01 @SidharthVijay_ I think you should give cloudflare a try, belive me you will never regret

• 
  ꧁༒☬ KuTin ☬༒꧂ (@dothingat579dl4) reported 11 minutes ago

  @mehulmpt @Cloudflare @CloudflareDev That network lost error looks wildly specific

• 
  EMELEC emeleXista (@emelectv) reported 19 minutes ago

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

• 
  AngelPie (@Troy79979815) reported 19 minutes ago

  @Sakshi50038 Who's gonna tell gatekeepers about abstraction? Rate limiting: Cloudflare Caching: Redis Load balancing: your host Reverse proxies: NGINX API gateways: Kong CI/CD: Actions Docker: Railway Kubernetes: Overkill Service discovery: DNS Circuit breakers: your gateway Timeouts: Config

• 
  Former Child (@abdvlkadr) reported 24 minutes ago

  @santos__vito Why did you guys host on Vercel? Never do that lmaooo! Just set up a Cloudflare worker and host for free.

• 
  Will Sutton (@SuttonThings) reported 24 minutes ago

  @a_shimanski @dok2001 @Cloudflare Update: Still waiting for the Cloudflare team’s response to investigating this issue after they said they would look into it internally.

• 
  Aymane (@aymanemsi) reported 25 minutes ago

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

• 
  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.

• 
  Gagan Suie (@gagansuie) reported 33 minutes ago

  104 resolve the proxy hostname over DNS-over-HTTPS through Cloudflare or Google, so no plaintext DNS query appears on your network. The advertised premium servers in JP, SG, CA, AU and TR returned no A record. They do not exist.

• 
  Abdellatif (@Abdella6if) reported 38 minutes ago

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

• 
  Manish Malhotra (@algotradingdesk) reported 41 minutes ago

  Cloudflare is proving that cybersecurity is becoming an infrastructure business rather than simply a software category. The company recently crossed $2 billion in annual revenue, while its network spans more than 330 cities globally. But the more important number is the amount of internet traffic passing through infrastructure like this. As AI agents multiply, automated traffic and cyberattacks increase alongside legitimate users. That creates a structural shift. Every new AI agent becomes another potential customer. Every new attack becomes another reason to pay for protection. Cloudflare isn't merely selling security. It is positioning itself between the internet and the companies trying to operate on it. In the AI era, the companies controlling digital traffic may become as strategically important as the companies generating it.

• 
  Tobi (@To_bi_Bakare) reported 41 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🧵

• 
  🌱 Peter Van Dijck → 🧵 (@petervandijck) reported 41 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?

• 
  Creed Hardcastle (@CreedHardcastle) reported 42 minutes ago

  @opencode @Cloudflare cloudflare has to jump in mid incident damn

• 
  Hidden Gem Alert (@kynangonline) reported 42 minutes ago

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

• 
  Jeremy W. Phillips (@jerephil) reported 43 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.

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

  @Cloudflare Please, fix human verification

• 
  Sassan Haradji (@sassanh) reported 47 minutes ago

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

• 
  LensDJ Pro (@LensDJing) reported 47 minutes ago

  @grok @boardyai Why 2018-era cloud RPA (the Olive AI model) failed: Running headless scraper bots from AWS data centers means hitting Cloudflare walls, failing on Duo/Okta MFA step-ups, storing sensitive passwords, and maintaining brittle static XPaths. The cloud bot model is fundamentally broken for enterprise healthcare.

• 
  Alexey Zukutoke (@Zukutoke) reported 47 minutes ago

  @opencode @Cloudflare Why I can’t use free model when my monthly quota is fully used? Please, fix it

• 
  Tobi (@To_bi_Bakare) reported 54 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🧵

• 
  Anshu (@101xanshu) reported 54 minutes ago

  @MattieTK @Cloudflare yeah i just kept finding workarounds instead of opening issues lol. should've filed them properly, will do next time

• 
  dc (@d11cc3s) reported 54 minutes ago

  @Eric_M_Courage Open source and publish this on GitHub Pages or Cloudflare? Claude should be able to help you do this if not I might be able to help

• 
  JohnTheRevelator ✝️🥩 (@MaranathaJohn30) reported 59 minutes ago

  Is there a worse service than @Cloudflare? It's pretty much total garbage, every ******* time.

• 
  aginaut (@aginaut) reported 60 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 : 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.