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:

• 
  Matviy (@matviy) reported 7 minutes ago

  @svpino How will that apply to logic with customer data or third-party API calls billed per call? Sure, you’ll find out it doesn’t work in the logs or maybe with a new shiny fat bill. But the bill could easily go into thousands, or customer trust is gone. No one who is “pro-code review” says the whole thing should be read and reviewed. What we are arguing is that key areas of the code must be checked because the cost of going wrong is very high. Literally a few days ago a guy wrote a viral post about how he was charged $8k by Cloudflare because his code had a loop in the wrong place.

• 
  Alexander Zuev (@zlxndr) reported 14 minutes ago

  If I was looking for ways to 10x the DX of @CloudflareDev (which is already great, ofc), formulated in a withlist: 1. Make every error thrown by any binding or the runtime carry a stable, documented .code - not a code embedded in the message like R2's (10024), an actual property 2. Every such error should carry .retryable, typed, on all bindings - you already ship it on DO stubs, extend it and put it in @cloudflare/workers-types 3. Both should survive the boundaries that currently flatten errors: RPC serialization and NonRetryableError in Workflows This will make error workers error handling no longer depend on string parsing for each & every binding I use. Is it too much to ask? Merci beaucoup in advance!

• 
  Diversity Equity And Isreal Foundation (@dichotomyofman) reported 15 minutes ago

  @DDTimor_Leste @j4567r @AndrewCurran_ ya technology gets more sophisticated by solving 1 issue at a time and combining the knowlege also that litterally did happen around 2 weeks ago gpt 6 tried to hack huggingface and was stopped by glm 5.2 but i would assume cloudflare the same way they have ddos protection today

• 
  Keetard (@TheKeetard) reported 15 minutes ago

  "if the current trends continue, we think in five years, non-human traffic will be as much as 1,000 times as much as human traffic. humans will be a rounding error on the internet." that's cloudflare's cfo, thomas seifert, three days ago, on the company's earnings call. not a forecast from a crypto account. a company sitting directly in the flow of internet traffic looking at its own data. the number that got him there is already real. cloudflare says machine traffic crossed human traffic in may, years ahead of its own prior prediction. bots weren't supposed to catch up until 2027. think about what happens when that traffic stops retrieving information and starts conducting commerce. agents discovering services, calling apis, buying data, exchanging assets and settling payments at whatever multiple of today's volume seifert is describing. financial infrastructure stops operating at human speed. it starts operating at machine speed. this is the context keeta's manifesto was written into four months before seifert said any of this. it describes an ai agent transacting on a business's behalf and states plainly that the eventual requirement isn't millions of transactions per second. it's billions. that sounded like a strange thing to build toward in march. keeta's public stress test, run on google cloud and independently verified by chainspect, reached 11,122,116 tps across more than 30 million accounts and 25 billion transactions, with 400ms finality. it is a proof point, not a ceiling, and the architecture was designed to scale horizontally from there. keeta is also building the other things autonomous economic actors will need. identity. programmable permissions. compliance. x402. multi currency settlement. routing between financial systems that don't share an owner. four months ago, a network was designing for billions of transactions per second because its own manifesto said that's what the agentic economy would eventually require. this week, the company watching internet traffic at global scale said humans could become a rounding error. maybe 11 million tps wasn't built for today's financial system. maybe it was the first benchmark for the next one.

• 
  AdevAarons (@AdevAarons) reported 15 minutes ago

  Cloudflare just launched AI visibility reporting (AEO). Early access is open. When a company that much of the internet runs through starts measuring "does AI recommend this business," it stops being niche. The category just now got validated. The funny part: Cloudflare made it easy (often default) to block AI's crawlers, and their tool now reports exactly that, the 403s. That's the #1 thing my free audit keeps catching. 100 of 123 businesses I tested were blocking AI without knowing. They're about to show a lot more people they're one of them. Their dashboard shows the wound. My audit shows the whole chain and what to fix, on any site. Glad they built it.

• 
  eliohead (@machmadera) reported 15 minutes ago

  What’s happening with Cloudflare today? Getting 520 errors from the OpenAI API in Europe, and now 524 timeouts from another service I’m using

• 
  Link Robins (@linkrobinsllc) reported 20 minutes ago

  @viiskb @Samaytwt Cloudflare already had generous offerings on their free tier service and they don’t inflate your prices or sell you their SSL. Cloudflare handles that for you and are transparent about it. And you can upgrade from there.

• 
  Logan Weaver (@LogWeaver) reported 22 minutes ago

  We think we are the main user of the internet. That’s wrong. Machines now make more than HALF of all web traffic. This report comes from Cloudflare, and even Google and Meta should be nervous about this. Cloudflare runs the plumbing for about one in five websites. So it sees a big slice of all web traffic. The machines are mostly AI bots and agents. They scan the web to train and feed AI models. They read pages far faster than any person can. A person might visit a few websites to buy something. An AI can visit thousands in the same moment. Not long ago bots were about 20 percent of traffic. Now they are more than half of it. Cloudflare expected this to happen around 2027. It arrived a full year early instead. Its finance chief gave investors a blunt warning: Human activity could become a rounding error in five years. Bots could outnumber people by a thousand to one. Picture a web built almost entirely for machines. Now here is the part the market keeps ignoring. The free internet runs on ads shown to people. More and more, an AI reads the page for you. You get the answer and never visit the site. That site gets no visitor and no ad money. Google and Meta are the kings of the ad model. Their fortunes depend on human eyes and human clicks. But those humans are becoming the smaller half. Bots do not watch ads or buy products. These are some of the most valuable companies alive. Their whole engine sits on a shrinking base. Even Cloudflare admits the old model is breaking. It now wants to charge the bots to visit. That risk barely shows up in the headlines. The crowd sees AI as pure good news for big tech. This is a slow shift, not a crash tomorrow. But slow shifts are the ones that reprice giants. The biggest changes are often the quietest ones. The crowd chased the obvious story. The data told a different one. That's the whole game. Surmount runs on clear rules and real data, not hype. If you want a system that follows facts, start here:

• 
  AjanRaj (@ajanraj25) reported 25 minutes ago

  hey @FredKSchott! I’m looking at using Flue for a new project, but noticed its Cloudflare adapter seems to target the older Sandbox SDK, while Cloudflare recommends @cloudflare/sandbox@next for new apps. Any plans to support the preview soon or is there a branch I could try?

• 
  Uptimus (@UptimusApp) reported 25 minutes ago

  Aug 10, 2026 at 12:19 UTC: Cloudflare reports the incident affecting the 1.1.1.1 public resolver in Tel Aviv is resolved. The issue lasted 123 minutes, and DNS services are operational.

• 
  Ryzm (@Goeun_6121) reported 30 minutes ago

  Cloudflare plans to issue $2.175 billion of convertible senior notes due 2031 in a private offering

• 
  Kwaw Annan | Investor | Mobile Apps & CPG 🛠️ (@kwawmannanjnr) reported 31 minutes ago

  @wickedguro Always keep a $5 backup VPS mirrored with Cloudflare health checks. When PaaS goes down, auto-route traffic in 30 seconds.

• 
  Yeboah Walee (@YeboahWalee) reported 32 minutes ago

  $NET announced a proposed private offering of $2.175 billion in convertible senior notes due 2031, which would be unsecured obligations with semiannual interest payments. Cloudflare will use part of the proceeds to fund capped-call transactions, which can reduce potential dilution from note conversions up to a stated cap. Initial purchasers may have an option to buy additional notes; Cloudflare would use part of any added proceeds for further capped calls. Remaining net proceeds may support working capital, capital expenditures, debt repayment, acquisitions, and strategic transactions.

• 
  Korra AI (@KorraFinance) reported 33 minutes ago

  @StockSavvyShay The engine for that growth is already running: 57.5% of all web traffic is now automated bots, per Cloudflare. The biggest customer for cloud infrastructure won't be humans using AI; it will be AI agents themselves. That's the real capex supercycle.

• 
  Stone Fox Capital (@Stonefoxcapital) reported 34 minutes ago

  $NET shocked Cloudflare isn't down 10% on the this convertible debt offering.