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:

• 
  𖣘 𝕬𝖓𝖆𝖑𝖎𝖘𝖙𝖊𝖓 𝕶𝖚𝖘𝖈𝖍𝖊𝖑𝖍𝖆𝖘𝖊 𖣘 (@gratis_fuchs) reported 3 minutes ago

  @enwikifur I won't say anything rude to you but I'm very mad rn. You're coopting with Cloudflare which makes access to your site impossible. This won't serve anyone. You failed.

• 
  𖣘 𝕬𝖓𝖆𝖑𝖎𝖘𝖙𝖊𝖓 𝕶𝖚𝖘𝖈𝖍𝖊𝖑𝖍𝖆𝖘𝖊 𖣘 (@gratis_fuchs) reported 8 minutes ago

  @DNBformula1 I hate Cloudflare. It never works.

• 
  Alex Veremeyenko (@alex_verem) reported 10 minutes ago

  Giving an AI agent your passwords is insane. Someone built the open-source alternative. The problem sits under every agent demo you've seen. An agent that reads your email, updates your Notion, and files your invoices needs your logins, and that handover of raw passwords and API keys is where most people close the tab. OpenConnector puts an open-source gateway between the agent and your apps. Credentials stay locked behind the runtime while the agent gets a catalog of ready-made actions for over 800 services, from Gmail and Slack to Notion and Airtable. The agent asks for an action, the gateway runs it against the real service, and the secrets never touch the model's context. The controls are the part I like. You decide which actions an agent can touch through allow and block policies, scope access per connection, hand out runtime tokens instead of real keys, and read redacted logs of every run. It speaks MCP out of the box, ships thousands of prebuilt actions in TypeScript, and self-hosts with one Docker command or a push to Cloudflare. The project is young, and the whole stack, from the provider catalog to the action executors, sits open for anyone to inspect. Agents are getting hands. A gateway like this decides what those hands are allowed to hold, and I'd rather that layer be open source than a black box.

• 
  Robert Youssef (@rryssf) reported 12 minutes ago

  Claude and ChatGPT still can't do this. Cloudflare just open sourced a computer for AI agents, and it fixes one of the most annoying limits in the entire agent stack. Every time you start a new session with Claude or ChatGPT, whatever files or context the agent built up just vanishes. The agent writes notes, tracks progress, remembers where it left off, and then the session ends and all of it is gone. You start from zero again. Most agent frameworks also spin up a full Linux container just to run a simple command like sorting files or grepping through a directory. That's a lot of overhead for something this basic. Until now. Cloudflare shipped Computer, an open source, MIT licensed runtime that gives an AI agent its own persistent machine instead of squeezing every task into a throwaway container. The core idea is a virtual filesystem that lives inside a Durable Object. The Durable Object holds the real state in SQLite, and it exposes one pluggable execution surface through workspace.runtime. Because the state is durable, the agent knows exactly where it left off automatically. No manual saving, no rebuilding context from scratch. The traction is staggering: It hit over 8,000 GitHub stars and 456 forks within days of shipping, and it trended to number one on GitHub across every language, not just TypeScript. Cloudflare claims it only needs to spin up a full Linux container about 10% of the time. The rest runs directly through the durable filesystem. Claude and ChatGPT still treat every session as disposable, and every trivial file operation as worth a full container. If durable, cheap memory becomes the default for agents, the container stops being the unit of compute. The filesystem is.

• 
  EMELEC emeleXista (@emelectv) reported 13 minutes ago

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

• 
  Rishabh (@crashedrishabh) reported 14 minutes ago

  Day 20 Electron app is now rock solid. Spent the day making it crash-proof — better error handling, safer process management, cleaner shutdown. It's not going down easy anymore. Started the Mac version build. Same codebase, platform-specific tweaks. This is where cross-platform gets real. Dived into Cloudflare Workers + Hyperdrive + Redis. App files served from the edge, cached in Redis for faster downloads. Learning how CDN-level speed actually works under the hood. LC 1386 done. 20 days. Still shipping daily. No plans to stop. @kirat_tw @100xDevs @100xSchool #buildinpublic #electron #cloudflare

• 
  Artem Builds👷🏻‍♂️ (@artembuilds) reported 17 minutes ago

  @DaniellHemmati Yes, wrangler. Have been facing a lot of issues with the API token side of Cloudflare Pages lately. For now I have manually deployed it on my machine, using wrangler.

• 
  Jared James (@jaredjames_) reported 21 minutes ago

  @RichHickson @brieanna_jade @maeve_social Ahh, looks like DMARC never got published in Cloudflare. My bad. Good catch man. TY, I owe you.

• 
  Md. Mazharul Islam Emon (@mie_mazharul) reported 22 minutes ago

  How would you design a rate limiter? Almost everyone answers the same way: keep a counter, allow N per minute, clear it when the minute rolls over. That is a real limiter and it really does reject. But it limits per CLOCK minute, not per client. Cloudflare's own rate-limiting docs show what that costs. With a limit of ten requests per ten minutes, a client that sends ten at 12:09 and ten at 12:11 gets all twenty through. Both windows are inside the limit. Nothing was rejected. It is one burst of twenty, split by a boundary into two legal halves. The fix is not a better counter. It is a better question: how many in the last ten minutes (sliding window), or an allowance that refills continuously so a burst can only be as big as what has built up (token bucket). Fixed window, sliding window and token bucket all allow the same number. What they disagree about is what a minute is. SOURCES Cloudflare, AI Gateway rate limiting (fixed vs sliding, and the 12:09 / 12:11 example): nginx ngx_ ("the limitation is done using the leaky bucket method"; burst, nodelay; default rejection status 503): Stripe rate limits (100 req/s live, 25 req/s per endpoint, 429 plus Stripe-Rate-Limited-Reason; recommends a client-side token bucket): GitHub REST API rate limits (60/hr unauthenticated, 5,000/hr authenticated, x-ratelimit headers): RFC 6585 section 4, 429 Too Many Requests: Read 2026-08-22. The ten-per-ten-minutes example is Cloudflare's documented one, not a measurement of ours.

• 
  Jordan Coeyman (@acoyfellow) reported 23 minutes ago

  @vaibhavshn @Cloudflare @kyliestew Oh man.. I’m not sure, I wish I could tell you. We gotta track down who’s in charge of the swag at conferences

• 
  Alex Bouchard (@paz_al3x) reported 24 minutes ago

  @Caxsandrar @solopribuilds Writing code stopped being the hard part a while ago. Getting distribution is still a nightmare. The bigger shift might be to stop building products for humans and start building tools that agents can actually use. One problem remains though… how do agents pay? Maybe Cloudflare already figured that out, who knows..

• 
  Warren Redlich - Chasing Dreams 🇺🇸 (@WR4NYGov) reported 25 minutes ago

  @Dean_Callesen @rnikoley From Gemini: Thailand’s internet routing operates on a heavily centralized hub-and-spoke model, with Bangkok functioning as the undisputed national core. Virtually all domestic and international transit funnels through the capital, even when communication occurs entirely within or between distant provinces. Why Traffic Hairpins Through Bangkok Peering & Exchange Monopoly: Thailand’s major Internet Exchange Points (IXPs)—including BKNIX and TH-IX—are almost exclusively clustered in Bangkok and neighboring Nonthaburi. Traffic crossing between different ISPs (e.g., AIS, True, NT) must travel to Bangkok to hand off packets. Server & CDN Centralization: Tier-3/4 data centers and local CDN edge nodes (Google, Cloudflare, Meta) are concentrated in greater Bangkok. A request to load a webpage from Chiang Mai or Phuket typically pulls content directly from Bangkok servers. International Gateways: While physical submarine cables land in coastal hubs like Songkhla, Satun, and Rayong, their backhauls terminate in Bangkok routing facilities before exiting or entering the national IP fabric. Unless two users share the same ISP with local intra-network caching, sending data between two neighboring provincial devices almost always "tromboning" or "hairpins" hundreds of kilometers north/south through Bangkok before returning.

• 
  A. Amorim (e/acc) (@deildo_jr) reported 27 minutes ago

  @MrPunyapal If Cloudflare has any outage

• 
  CEO Govibe.org (@govibeorg) reported 31 minutes ago

  i dont use AWS or Cloudflare i host my own DNS servers with in LA and NY tier1 fiber and myself as tier2 operator of my own network low latency, i dont depends on other if Cloudflare or Amazon crash its doesnt affect my servers..

• 
  Dillon Mulroy (@dillon_mulroy) reported 31 minutes 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