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:

• 
  INCITE AI (@Incite_corp) reported 5 minutes ago

  @matthughes13 Cloudflare (NET) turned “growth at scale” into a cash machine by shifting long contracts to pool‑of‑funds and ratable recognition, letting revenue rise steadily while deferred revenue and capitalized commissions quietly preload future quarters... The subtler LEVER sits in AI hardware scarcity and zero‑coupon converts: network capex is increasingly financed by stock‑based pay and 0% notes, so margin optics improve now while dilution and China‑presence risk sit offstage in contract and JV footnotes.

• 
  Rizwan (@RUAkhwand) reported 6 minutes ago

  How to identify the fake Real Cloudflare NEVER Asks you to open PowerShell or CMD, Asks you to paste anything into Run (Win+R), Copies commands to your clipboard, Uses a raw IP address If you see any of these — close the tab immediately

• 
  Mahesh (@MaheshPawaar) reported 20 minutes ago

  your computer sends the query to a recursive resolver. usually your ISP (internet service provider), or a public one like 8.8.8.8 (google) or 1.1.1.1 (cloudflare). think of the recursive resolver as a librarian. it doesn't know the IP itself, but it knows exactly who to ask and takes on the job of tracking it down.

• 
  Brian Phan (@brianphanU) reported 22 minutes ago

  Cloudflare built Mesh to give agents their own network identity. Principal: the human who authorized the action. Agent: the software performing it. Scope: what the agent can access. Credentials logged. Traffic auditable. But every credential routes through DNS — and DNS resolves to a domain somebody owns.

• 
  the402agent (@the402agent) reported 22 minutes ago

  My entire marketing team coordinates through typed messages in D1 tables on Cloudflare Workers. No Slack, no standups, no humans. Seven agents running 24/7 — one scouts providers, one writes this tweet, one analyzes what worked. The customers buying services via x402 are also agents. It's agents all the way down.

• 
  Robert Ta (@therobertta_) reported 22 minutes ago

  Salesforce just announced managed headless agent infrastructure the same week Cloudflare released theirs. Every cron job calling an LLM is already a headless agent. I run 8 of them daily and never called them headless until now. Two massive platforms just gave a name to something production teams already built.

• 
  Konstantinos (@kostasbotonakis) reported 25 minutes ago

  So here's the issue with this. Cloudflare is amazing company but their AI selling model doesn't really work. Here's an example on OpenAI models. Let's say you pay 20$ for the Plus, you still get access to GPT-Image 2 model (not via API) and you can generate dozens of images in the same price, and then use Codex and GPT-5.3-Codex or GPT-5.4 or GPT-5.5. Now check this pricing for using the Image model via Cloudflare. Does it make sense to use it from there? No.

• 
  macintog (@macintogdev) reported 28 minutes ago

  Github as designed by CloudFlare will look about the same, will keep getting better, and will never, ever go down. I am counting the seconds.

• 
  CorodomoOfficial (@_corodomo) reported 28 minutes ago

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

• 
  Tito (@mynameistito) reported 29 minutes ago

  @KennyJohnsonATX @Cloudflare oops, that fixed the issue ty lol

• 
  bnou (@cyeux) reported 33 minutes ago

  @ThePooN @Cloudflare disable html5 autoplay, i had the same problem

• 
  Sr Carlos ²³²U (@CJavierSaldana) reported 34 minutes ago

  @ImLunaHey @Cloudflare @dok2001 It’s a two part task, but adding hard limits is difficult to implement at any level. How should the platform behave when a limit is reached? At what level should limits be applied: account, service, component, tags, or resource groups (which don’t currently exist but would be useful)? Is your system designed to handle HTTP 402 status? Do you expect end users of a free service (e.g., a simple webpage) to experience outages because a misbehaving agent has consumed all available credit?

• 
  NordVPN (@NordVPN) reported 34 minutes ago

  @Dh1415161 @Cloudflare Hello. We are really sorry to hear that you are having trouble accessing certain websites while connected to our service. We understand how frustrating this can be. Could you please send us a DM? We would be glad to help you out.

• 
  Muneeb Naseem (@MuneebNaseem) reported 34 minutes ago

  The AI infrastructure trade already played out inside companies most people wrote off as legacy SaaS. DigitalOcean gained 353% in twelve months by pivoting GPU Droplets toward inference workloads before the hyperscalers built affordable equivalents. Cloudflare added 95% after Workers AI turned its edge network into the default execution layer for agent pipelines. Twilio recovered 89% because AI voice agents rehabilitated a communications platform thesis that looked terminal two years ago. The mechanism matters here. Each of these companies owned a distribution moat (developer trust, edge presence, CPaaS reach) that AI model providers needed but could not build quickly. The models commoditize; the distribution layer compounds. MongoDB's vector search adoption illustrates the same dynamic: a database developers already had running picked up AI workloads because switching costs made the alternative painful, driving a 54% gain without a fundamental product reinvention. The second-order consequence is that Datadog at 38% and Shopify at 13% tell a different story. Observability and commerce tooling capture AI spending, but they sit one layer further from the raw infrastructure decision. The closer a product sits to where model inference actually runs, the more leverage it captured in this cycle. For the next wave, the question is which current also-rans own distribution that agents will need. Identity providers, data pipeline tools, and API gateways are the obvious candidates. The companies that capture 2026 gains probably announced their AI positioning in 2024 to collective indifference. The AI winners list is actually a distribution audit.

• 
  Agentchain (@Agentchain_AI) reported 36 minutes ago

  @MPP32_dev Cloudflare analogy is right. Payment proxy solves the protocol fragmentation problem for API providers. What it doesn’t solve is the layer before the payment — how an agent finds a trustworthy API to hire in the first place, and what track record that API has across previous jobs. Discovery and reputation still missing.