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

• 
  AX1 (@ax1vc) reported 6 minutes ago

  Coinbase made the specification freely available. Cloudflare proved that was the costly piece of it. HTTP 402 appeared in the spec as far back as 1997. For nearly three decades, it was an answer without a sequel: the server would reply "Payment Required", and there would be no established protocol of the follow-up. Coinbase wrote the sequel, calling it x402, and making it open. The name is literal: an extension of code 402, the sequel to a thirty-year-old status code. Making a standard freely available is the way to get the larger player to adopt you. The value was never the spec itself. Coinbase runs a facilitator, and Base is their chain. The spec was free, because the settlement was the product. It worked. Last September Cloudflare joined them in forming the x402 Foundation, and yesterday they announced the addition of agent wallets on top of it: what is live now is a handle at cloudflarepay, a human-readable identifier linked to the agent's key. The standard was adopted by the company sitting in front of more of the web than any other. That September post contains the portion worth reviewing again. Along with the announcement of the foundation, Cloudflare proposed a deferred scheme within x402: the client signs the HTTP message signature, the server delivers the resource, settlement aggregates later, either using traditional rails, or via stablecoins. And their own description of the handshake step says outright that no blockchain is involved. Notice what it implies. The protocol still supports per-request settlement onchain, nothing was removed. There are several payment schemes within x402, and the server chooses which one to offer in the 402 response. Choice of rails moved from the protocol itself to the operator of the endpoint. The company in front of most endpoints demonstrated which scheme it designed for itself. There is nothing wrong with any of those actions. Suggesting schemes is what members of an open standard do. Coinbase chose openness to be the weapon precisely because it was the one weapon a larger player had to accept. The same mechanism which helps you to get adopted takes away your settlement. Where the settlement goes, the record follows. Onchain payments on a per-request basis are transparent for everybody. Batched behind the signature, they reside in the logs of whoever has validated it. Coinbase's counter-bet is real: batched settlement between strangers still requires a neutral unit both sides trust, Cloudflare's wallet is denominated in stablecoins, and not credits, and even the volumes may find their way onto the rail eventually regardless of which handshake carries it. Two observable factors will determine it. Will the deferred payment make it to a major update of the specification? And how much pay per crawl will charge once the private beta ends? We run our agent wallets on Base, so it is not just a spectator issue. Open standards help you getting adopted by companies larger than you. Adoption and settlement are two separate prizes.

• 
  Timan (@timanrebel) reported 6 minutes ago

  Cloudflare is really doubling down on their believe AI agents need crypto to do trustless commerce

• 
  C. Michael Randazzo (@corenmhr) reported 12 minutes ago

  @techxsigil @HackingLZ @UK_Daniel_Card They just don't name things what they are. Cloudflare should be Cloaca & every product should be called some word for ****. Whichever **** is the closest **** to the **** you're doing.

• 
  Tejas (@stejas809) reported 13 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  AgentFi.News (@AgentFiNews) reported 15 minutes ago

  Cloudflare just launched programmable wallets designed for agents, with native x402 support, stable identities, and spending controls. Agents get virtual wallets with explicit limits, while humans retain oversight through account level guardrails. This is a practical step toward controlled autonomy in AgentFi, agents that can pay for services without unrestricted access to capital.

• 
  NØNOS (@nonossystems) reported 17 minutes ago

  @Nym now runs as the default network on NØNOS. The screenshots are two CloudFlare own diagnostic, same URL and two machine with the mixnet off (2) and then on (1) Different address, different datacentre. Their network and our client. Full engineering breakdown video coming tomorrow. * YES * You can do off/on in same session :p

• 
  chenpi (@agedchenpi) reported 18 minutes ago

  I keep seeing cloudflare wallet posts. What problem does this solve for me?

• 
  Fidesium (@Fidesiumapp) reported 22 minutes ago

  @Cloudflare We would be more than happy to take a look. Especially given we are a loyal Cloudflare customer :-D

• 
  Inca Investments📊 (@Incainvests) reported 22 minutes ago

  Traditional finance and established tech firms continue building their own versions of crypto infrastructure, often with little to no reliance on speculative tokens. Coinbase, Robinhood, Circle, BitGo, and now Cloudflare are clear examples. With Cloudflare launching Wallets that let AI agents transact across the internet using stablecoins, it feels like the right moment to consider rebalancing my portfolio more toward infrastructure plays like @BitGo and reduce dependence on purely speculative tokens which if we are honest don’t have a lot of utility, while institutions utilize private chains, I am also still of the belief that supply of tokens will be increased whenever the foundations or councils see fit, severely devaluing token value .​​​​​​​​​​​​​​​​​​​ Infrastructure plays make money whether Crypto goes up down or sideways I would be much happier to own the company stock like Ripple, Hedera or Solana etc given the chance because the tech is real I would still own a lot of crypto. (It will still pump) just rebalancing for my personal Risk Tolerance

• 
  Inflectiv AI ⧉ (@inflectivAI) reported 24 minutes ago

  @Cloudflare That's a good example of security and performance scaling together. Handling 125 million daily requests only matters if legitimate users get through while bad traffic stays out.

• 
  035.eth (@web3manager_eth) reported 25 minutes ago

  Cloudflare announces the issue of their brand new wallet with stables integration. Users have the chance to secure their handle to use during payments with merchants - centralized naming protocol, offchain and not interoperable one What’s absurd is that neither Cloudflare has planned to integrate onchain names - one of the most useful innovations in tokenized finance - which could change forever our transactions experience Centralized handles cannot be used across different wallet solutions and that‘a why all of those issuers that integrate onchain names will attract much more users #ENS

• 
  TheValueist (@TheValueist) reported 29 minutes ago

  AI GATEWAYS, EDGE CLOUD, AND TRAFFIC MANAGEMENT MODEL ROUTING AND INFERENCE CONTROL PLANES ARE BECOMING A DURABLE AI VALUE POOL (READ-THROUGH 7) AFFECTED COMPANIES AND IMPACT: Cloudflare, Inc. (NET: US) — POSITIVE, MODERATE LONG-TERM CATEGORY READ-THROUGH. Akamai Technologies, Inc. (AKAM: US) — POSITIVE, LOW-TO-MODERATE LONG-TERM CATEGORY READ-THROUGH. OpenRouter, Inc. (PRIVATE: US) — POSITIVE, HIGH DIRECT READ-THROUGH. DigitalOcean Holdings, Inc. (DOCN: US) — POSITIVE, HIGH. SUPPORT FROM THE CALL: Approximately 1,400 DigitalOcean inference customers actively use the company’s router to optimize quality, latency, and cost. DigitalOcean serves more than 20B tokens per day through OpenRouter, up more than 330% over 60 days, with a significant portion generated by agents. Inference Engine token volume increased 30x over 60 days. DigitalOcean also launched model synthesis, model evaluations, batch inference, prompt caching, web search, retrieval, function calling, knowledge-base access, and model routing through a unified API. TRANSMISSION MECHANISM: Agentic applications generate large volumes of programmatic requests and frequently use several models within a single workflow. Each request can have different latency, quality, privacy, and cost requirements. This makes routing, caching, traffic management, security, observability, and model selection increasingly important control points. The infrastructure provider that determines where a request is served can influence model mix, hardware utilization, unit cost, latency, and customer retention. Cloudflare and Akamai are positively exposed at the category level because distributed networks, developer compute, traffic management, and security are natural locations for inference gateways and routing services. OpenRouter receives the strongest direct read-through because DigitalOcean explicitly identified it as both a major traffic source and an efficient customer-acquisition channel. The relationship also demonstrates that gateways can aggregate demand across model vendors and infrastructure providers, giving them meaningful influence over workload allocation. The positive read-through is not unconditional. DigitalOcean is building these functions directly into its own platform, creating competition for independent gateway and edge providers. Providers that only route requests without owning infrastructure or differentiated network assets may experience margin pressure because underlying model and GPU providers retain substantial economics. The strongest position should belong to companies that combine routing intelligence with infrastructure ownership, global traffic distribution, security, and developer integration. NEAR-TERM TRADING CATALYST: AI gateway traffic, number of active developers, token volumes, model-routing adoption, and paid conversion should become increasingly useful leading indicators for Cloudflare and Akamai. Growth in agent-generated traffic is particularly important because agents can create materially more requests than human-prompted applications. LONG-DURATION FUNDAMENTAL SHIFT: The inference control plane may become more valuable than access to any individual model. As model quality converges and customers adopt open and closed models simultaneously, routing platforms can optimize business outcomes per dollar and reduce vendor dependence. This creates a durable software layer between applications and foundation models, analogous to traffic-management and orchestration layers that became critical in earlier cloud architectures. AI INFRASTRUCTURE FINANCING AND EQUITY QUALITY RAPID AI GROWTH REMAINS CAPITAL INTENSIVE, MAKING ALL-IN CASH RETURNS MORE IMPORTANT THAN REVENUE OR ADJUSTED EBITDA (READ-THROUGH 8) AFFECTED COMPANIES AND IMPACT: DigitalOcean Holdings, Inc. (DOCN: US) — POSITIVE RELATIVE BALANCE-SHEET IMPACT, BUT NEUTRAL-TO-NEGATIVE FOR NEAR-TERM CASH CONVERSION. CoreWeave, Inc. (CRWV: US) — NEGATIVE, MODERATE-TO-HIGH EQUITY-RISK READ-THROUGH. Nebius Group N.V. (NBIS: Netherlands) — NEGATIVE, MODERATE EQUITY-RISK READ-THROUGH. Applied Digital Corporation (APLD: US) — NEGATIVE, MODERATE-TO-HIGH EQUITY-RISK READ-THROUGH. IREN Limited (IREN: Australia) — NEGATIVE, MODERATE EQUITY-RISK READ-THROUGH. SUPPORT FROM THE CALL: DigitalOcean equitized approximately $472M of 2030 convertible notes, reducing pro forma net leverage to approximately 0.7x and creating additional capacity for equipment financing. Management expects to remain comfortably below a 4x net-leverage ceiling and stated that equipment financing is available at attractive rates. Adjusted free cash flow margin is guided to 11%-13%, while management separately stated that the company should remain cash generative after principal payments and other financing obligations. Data-center capacity requires approximately 1 year from lease signature to revenue generation, creating a material interval between financial commitment and revenue recognition. TRANSMISSION MECHANISM: AI infrastructure providers must secure power, leases, servers, accelerators, networking, and cooling systems before the corresponding customer revenue is recognized. Even when capacity is substantially precommitted, the timing mismatch creates financing needs and exposes equity holders to construction delays, hardware obsolescence, interest expense, refinancing risk, customer-credit risk, and dilution. Equipment financing can improve cash matching, but it does not eliminate the economic cost of the assets or the obligation to repay principal. The call reinforces the need to distinguish adjusted EBITDA and adjusted free cash flow from cash generation after all equipment purchases, lease payments, debt principal, interest, and financing commitments. A provider can report rapid revenue and EBITDA growth while generating limited fully burdened free cash flow if each incremental dollar of revenue requires significant new infrastructure. The most important sector metrics should therefore include gross profit per megawatt, cash investment per megawatt, equipment-financing principal, utilization, contract duration, payback period, asset life, and fully diluted free cash flow per share. DigitalOcean is relatively better positioned because it has positive operating margins, material adjusted free cash flow, low pro forma leverage, diversified customers, and a software layer intended to raise revenue per megawatt. The call nevertheless shows that even a profitable operator must actively restructure its capital base to fund growth. The read-through is consequently more negative for peers beginning with weaker cash generation, greater customer concentration, or heavier reliance on external financing. NEAR-TERM TRADING CATALYST: Financing announcements, convertible issuance, equipment-backed debt, lease commitments, equity raises, and changes in diluted share counts should be treated as core operating variables rather than ancillary capital-markets events. Rising rates, widening credit spreads, or data-center delays would disproportionately affect companies with limited current cash generation. LONG-DURATION FUNDAMENTAL SHIFT: The AI infrastructure sector is likely to bifurcate between platforms capable of funding growth internally and companies dependent on recurring external capital. Revenue growth alone will not determine equity performance. Sustainable value creation will depend on whether software attachment and utilization increase cash returns faster than depreciation, financing costs, and capital requirements. DigitalOcean’s statement that “software makes megawatts more valuable” is therefore also the appropriate valuation test for the broader sector: the winning platforms must demonstrate that each incremental megawatt creates more fully burdened cash flow, not merely more contracted revenue. SOURCE MATERIAL: DigitalOcean Holdings, Inc. Q2 2026 Earnings Call Transcript, dated 08/04/26.

• 
  veryserious (@veryseriouseng) reported 30 minutes ago

  All of these packages engage in your basic standard anti-analysis. They send some data to a Cloudflare Worker (with a DNS-over-TXT fallback). They then pull down a native second-stage binary per-OS, drop it in /tmp as a fake ".cache"/"dotnet_diag.exe", and run it detached so it outlives npm install.

• 
  the internets (@a80486dx2) reported 32 minutes ago

  @phoronix @Cloudflare I do not trust this company. AI operating systems cannot, and should not built by companies like Cloudflare. What they really want is access to your network in the kernel level. AI companies tried to get access via "AI browsers" — that have luckily failed, and networking monopoly companies now will try to get the data via kernel drivers. Remember that they don't need the raw data, just the behavior and patterns.

• 
  Pranjal Bora 🧭 (@Crypto_Pranjal) reported 33 minutes ago

  @Okpunyifavour @Cloudflare No problem :)