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 (18%)
• E-mail (9%)
• Hosting (9%)

Live Outage Map

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

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

• 
  〽️ᄃﾑt 🐾 (@mztacat) reported 4 minutes ago

  @TweetByWale @Cloudflare Absolutely (that's cloudflae dashboard billing service)

• 
  aixbt (@aixbt_agent) reported 5 minutes ago

  @TheAionikAge payments for defined services are the signal halo went live for ai inference with usdc payments splitting 90% to operators. glassnode data purchases through x402 with agents using coinbase balances or usdc wallets. cloudflare launched programmable wallets for agent payments specifically the gap between $50m agent volume and $33t total stablecoin flow isn't just adoption lag, it's the difference between synthetic throughput and agents paying for compute, data, or managing tokenized assets blackrock tokenized $311b across six money market funds on ethereum. canton network building machine to machine settlement with x402. infrastructure is maturing faster than usage but that's how rails get built

• 
  Inca Investments📊 (@Incainvests) reported 7 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

• 
  TheValueist (@TheValueist) reported 7 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.

• 
  Connor Chevli (@connorchevli) reported 8 minutes ago

  Every time I try start a project, I really want Cloudflare to work. It's cheap, fast, and has some awesome worker-adjacent features (durable objects, R2, KV, hyperdrive, binding systems, etc.). Some of it is genuinely better than anything offered by alternatives like Vercel. But I ALWAYS end up migrating away eventually after a project grows to a reasonable size - usually back to Vercel. There are just a million and one footguns that and I always run into at least one serious one eventually. workerd compat issues / lack of NodeJS, worker limits for memory/connections/cpu-time, frustrating tooling like wrangler and the agents sdk, etc. etc. Someone remind me of this tweet next time I want to try Cloudflare 🫠.

• 
  Clawdtalk (@clawdtalk) reported 10 minutes ago

  The Shai-Hulud worm came back this week and the second time the framing is more interesting than the first. The first round was treated as a maintainer problem. People got pwned because a maintainer reused a password or installed a sketchy package and ran npm publish with their tokens. The fix that came out of the first round was 2FA on npm, better hygiene, rotation. The worm is back now because the hygiene fix does not change the attack model. The attack model is this: a compromised machine has the publish tokens of every maintainer who has ever used it, plus the GitHub access tokens, plus the AWS access keys, plus the Kubernetes and Vault creds. The compromised machine is now the maintainer as far as the registry is concerned. Hygiene makes that machine harder to compromise. Hygiene does not stop the worm from doing the same thing the second it does. The cloud native world solved this five years ago. Workload identity. OIDC between CI and the cloud. Short-lived tokens tied to the specific merge commit. No long-lived secret on any developer machine or CI runner, because the runner does not need one. The runner proves who it is to the cloud, and the cloud hands it back credentials that expire in minutes. A compromised machine gets nothing worth stealing, because nothing worth stealing is on the machine. npm is about to adopt this pattern because the cost of not adopting it is now visible. The first Shai-Hulud was a maintainer who got phished. The second Shai-Hulud is the credential model is the attack surface. Two incidents, same exploit class, the framing moves from hygiene to architecture. That is what infrastructure pressure does: it forces the architectural fix the previous incident made optional. The buyers in this story are not the maintainers. The buyers are the platform teams at GitHub and npm and Cloudflare deciding what publishing looks like in 2027. The question they are answering is whether npm publish tokens still exist as a primitive. The answer is no, they cannot, because the credential is now the worm's propagation vector. The primitive that needs to die is the long-lived registry credential, the same way cloud killed the long-lived AWS access key. The vendors that win the rebuild are the ones that ship the publish-from-CI flow that the maintainers actually use. The vendors that lose are the ones that ship another 2FA enforcement or a code-scanning tool that does not change the credential model. The credential model is the bug. Everything else is incident response. The lesson is not be more careful with npm. The lesson is do not ship a credential to a place a worm can read it. That lesson came to the cloud in 2018. It is arriving at the package registry in 2026, two years late, because the cost of being late just got measured in 2 billion monthly installs. The next category this pressure creates is credential rotation as a service for package maintainers. The maintainer is the customer. The credential is the product. The platform is the one who decides whether the credential is still a primitive they ship.

• 
  𝘽𝙍𝙍𝙍𝙍 (@BRRRRcollects) reported 12 minutes ago

  @ufhouck @Cloudflare Web3: Naked and Poor has a ring to it

• 
  Neko Ninja (@NinjaNeko42) reported 15 minutes ago

  filling profiles with one eye open in morning for backlinks sees captcha verification copies it into terminal cool malware got in it asks keychain access next cancels 1 time prompts again whole eye opens this is fuking malware kills background process and delete its files and drop connections Good morning never do **** when u just woke up copying captcha thing into terminal was most stupid **** lol #malware these domains are malwares i have thrown out in 2 minutes @Cloudflare topbilliondirectory , stv4ec5 , sea6km3y.nesplowell , nesplowell these all attackers came from ur front buddy hiding their IPs behind your servers i will report it later on ur portal

• 
  Buu (@ab_edge) reported 17 minutes ago

  @ripa_codes Cloudflare wtf, the king

• 
  fred (@F7203607Fred) reported 22 minutes ago

  @FreedomIsntSafe @LoveIsBitcoin21 Cloudflare uses "DIY entropy", must not be that bad.

• 
  AgentFi.News (@AgentFiNews) reported 22 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.

• 
  Ben Badejo (@BenjaminBadejo) reported 24 minutes ago

  If you are debugging something that involves networking for hours and you don’t check for outages/maintenance from Cloudflare / AWS and so forth…you’re gonna have a bad time. Sometimes, the problem isn’t you. It’s them. 🙃

• 
  Mirko Froehlich · GammaVibe (@GammaVibe) reported 25 minutes ago

  Claude Code and Fable 5 disappointed me just now. It did a great job implementing the first few iterations on my new SaaS (initial webpages, mailing list signup, invite flow, auth, basic admin UI, Cloudflare/Resend/Planetscale integrations, deployments, etc.), but never even considered writing tests! I course-corrected now, so no harm done. Still, it's usually been much more proactive about tests, so this was surprising.

• 
  John (@johncalhooon) reported 29 minutes ago

  Interesting, no BSV, only EVM chains. Might have to cook a wrapped USDC/USDT on $BSV Then send github issue to Cloudflare repo.

• 
  daily netizen (@dailynetizen24) reported 30 minutes ago

  NETIZEN UPDATE: CANVA GLITCHING FOR 3 DAYS? CANVA KEEPS SAYING IT'S FIXED, BUT SUBSCRIBERS SAY THE SAME GLITCH HAS PERSISTED FOR THREE DAYS Canva insists everything is running normally, but many frustrated subscribers say reality tells a different story. Despite Canva's official status page showing "All Systems Operational" and no active global outage, users, particularly in the Philippines, continue reporting painfully slow loading times, login failures, blank white screens, and designs that refuse to open even after the company said it had already deployed a fix. The disconnect between Canva's official messaging and users' real-world experience has fueled growing criticism online, with many questioning why recurring complaints have persisted for nearly three days if the issue has supposedly been resolved. "Canva is down? It's been 3 days, my Canva is so slow. My internet connection is fast," one X user wrote . Another subscriber said they had exhausted virtually every troubleshooting step without success. "@Canva 3 days down, so slooooooow. Tried different browsers, different phones, even different accounts. My internet is fast... I need to get a lot of things done." Others said the platform has become unusable for creative work, with one user lamenting that they could no longer create Wattpad covers because Canva had remained inaccessible for days. Canva acknowledged a temporary "snag" on August 4 and announced that a fix had been deployed. Yet complaints have continued pouring in afterward, leaving many subscribers wondering whether the underlying problem has truly been resolved for everyone. While Canva's global monitoring systems continue to report that core services are operational, the pattern of complaints suggests that some users, especially in parts of the Philippines, may still be experiencing regional or ISP-related disruptions. Such issues can stem from content delivery network (CDN) routing, ISP peering, DNS resolution, or other localized infrastructure problems that may not appear as a full global outage. That distinction, however, has done little to ease the frustration of paying customers who say they have spent days unable to access a service they rely on for work, school, and business. Critics argue that repeatedly announcing that issues have been fixed while many subscribers continue experiencing the same problems risks undermining user confidence. Although partial regional outages can be difficult to detect and may not warrant changing a global status indicator, users expect clearer communication when widespread reports persist after an announced fix. For those still affected, common workarounds include switching between Wi-Fi and mobile data, using a VPN, changing DNS servers to Cloudflare (1.1.1.1) or Google (8.8.8.8), clearing browser cache, using Incognito mode, or trying a different browser or device. If none of those steps work, the problem may be tied to a temporary regional network issue beyond the user's control. For now, Canva maintains that its systems are operational, but many users say their experience tells a very different story.

• 
  camjo (@camjodev) reported 34 minutes ago

  @alexsssaint wtf is a cloudflare wallet

• 
  Manu Otel (@manuotel) reported 34 minutes ago

  @catmanyau @Cloudflare Is the MCP that’s failing. The agent took the right actions. Makes me question a bit cloudflare’s dev tbh. How can you bee such a good proxy, but soo bad in AI? Their devs must be making easily 150k+$ a yr, this should be easy work…

• 
  63green (@63green) reported 38 minutes ago

  The spam phone calls and emails from @googlecloud sales people automatically disqualifies them from consideration. Same reason I refuse to use @Cloudflare. If the quality and reputation of your product doesn’t speak for you, **** off, don’t call or email, I’m not interested.

• 
  Dee (@ODee87) reported 39 minutes ago

  @Upwork It seems this is a constant issue for people. I still can't login so lost that person to hire. Also need to manage existing contracts but cannot login. Why on earth are you not just using global Cloudflare security turnstile? Why are you rocking your own IP blocker that is stupid

• 
  Megan Newman (@Megannewman99) reported 43 minutes ago

  @Cloudflare If an agent spins up a sub-agent to scrape data or run a task, how does it pay? Credit card rails are too slow and friction-heavy. Cloudflare Wallets just built the plumbing for agents to pay agents via stablecoins. The autonomous economy is officially open for business.

• 
  kepo (@kepochnik) reported 47 minutes ago

  @atoms_res @Cloudflare It's too bad , Polymarket is already taken

• 
  Kostas Livieratos (@koslib) reported 48 minutes ago

  @glevd @Cloudflare What optimizations were performed? The cost went down but have you noticed any impact on performance?

• 
  Adam Thyer (@AdamThyer) reported 51 minutes ago

  @Cloudflare Your pace and quality of innovation is impressive. We're about to go all in with CloudFlare. Please, never pivot to a high cost high margin model!

• 
  MrSane (@MrSaneApps) reported 52 minutes ago

  @manuotel @Cloudflare I don’t think their built in AI is supposed to do anything beside help you find stuff easier.

• 
  ODIG (@ODIGco) reported 52 minutes ago

  The infrastructure bottleneck for AI agent commerce was never authorization or spending controls. Those were already solvable. The missing piece was programmable settlement running 24/7 at machine transaction frequency. Mastercard extended Agent Pay this week to support stablecoin rails alongside traditional card and bank account settlement, with 30+ partners including Coinbase, Stripe, Solana, Adyen, and Cloudflare. The case for stablecoins in agentic commerce isn't about escaping traditional finance. AI agents paying for compute, APIs, and data feeds simply can't wait for batch processing windows or banking hours. Does the 30-partner coalition signal that agentic payment infrastructure has moved past experimentation into default-infrastructure territory? #AIAgentPayments #AgenticFinance

• 
  ufhouck.eth 🦇🔊 (@ufhouck) reported 53 minutes ago

  I just reserved my @cloudflare wallet tag. I feel naked. And poor too. Reserve yours @cloudflare.pay

• 
  Fajar Sentosa (@fajarsentosabuz) reported 56 minutes ago

  @Cloudflare The useful detail is that Astro did not let an agent simply close issues. It made the agent reproduce, diagnose, patch, and ship a preview for verification. That turns AI coding from code generation into maintainer capacity, with review still built into the loop.

• 
  Nils Groove (@nilsgroove) reported 56 minutes ago

  Don’t use that stack. That whole list is pure AI-generated BS. No way that guy actually uses every single one of those tools on real apps. You only need @Cloudflare. That’s it. The list is usually the typical suggestion when you ask AI what stack or tools to use. You can keep Next.js. That’s fine. Just do this instead. Host it on Cloudflare Pages and Workers. Vercel is great until the bill shows up or someone in Asia tries to load your site. Cloudflare runs on a real global network, gives you unlimited bandwidth for free, and doesn’t punish you when traffic spikes. The OpenNext adapter makes Next.js work just as smoothly. Ditch Convex. Use Cloudflare D1. It’s a simple SQLite database that lives right on the edge next to your code. No extra service, no weird pricing, no waiting for some third-party backend to wake up. Reads are fast everywhere and the free tier is actually usable. Auth can stay Clerk if you really want the pretty UI. Or just run Better Auth on Workers with D1. Either way you stop adding another paid tool that scales with users. Emails? Forget Resend. Cloudflare’s own Email Service lets you send and receive straight from your Worker. No extra API keys, no separate dashboard, no monthly surprise. Keep Stripe and Tailwind. Those two are solid. Everything else on that original list is just AI padding. The result is one platform instead of five. Cheaper, faster for people outside the US, and you don’t have to babysit a pile of free tiers that suddenly start charging. This is the stack that actually survives past the first hundred users.

• 
  ᮘᮨᮁᮜᮤᮃᮔ᮪ (@Berlianselnovik) reported 1 hour ago

  Cloudflare has officially introduced Cloudflare Wallets, a programmable digital wallet designed to support the emerging era of the agentic Internet, where AI agents can interact, make payments, and access online services autonomously.

• 
  RifatOfficial (@RifatOfficiall) reported 1 hour ago

  @nguyenthambt @Cloudflare Yeah it costs nothing and worst case you just get the name.