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:

• 
  Mat | HAMCORE (@TheHAMCORE) reported 3 minutes ago

  @iPixelGalaxy I'd be interested to see where ClypDat goes. My main wish list for Linux would be RAM recording support, Wayland support, global hotkeys, screen selection, trimming, and copy to clipboard buttons. Currently Vice uses cloudflared and Cloudflare Tunnel to make links.

• 
  William (@dxgl_org) reported 5 minutes ago

  @davepl1968 Since you're using Cloudflare would it be a good idea to disclose that in your privacy policy, or would that make said company that blocked me here upset? Note there's an excellent chance your website is sharing an IP address with some pretty bad sites, especially if it's free.

• 
  Astrid (@just_some_dev) reported 6 minutes ago

  cloudflare worker deploys seem down rip

• 
  science roach (@darthroach_) reported 17 minutes ago

  @CapybaraFortune well no it's a joke about a cloudflare outage because they famously use 90ish lava lamps for encryption lmao

• 
  Citedy (@citedycom) reported 18 minutes ago

  Cloudflare Dashboard is temporarily unavailable. Claude down. What next. Aliens?

• 
  Sulfur (@sulfurscales) reported 19 minutes ago

  here's how to BUILD a phone farm for tiktok that costs under a cent per post instead of $0.5-3 per piece 10 old iphones running locally off a mac, iphone 7 through iphone 11. 2-3M views a month across 20 accounts, 30-40 posts a day, all targeting the us while running physically outside it. best single post hit 1.1M, median sits around 5000. 2000 views turning into 1 install, 5% of those installs converting to paid, best days pulling 80 installs and 5 new customers the problem being solved: every slideshow tool on the market charges per piece, reelfarm and the rest land around $0.5-3. at 40 posts a day that's $500+/month before you even know which angle works. a proper testing phase at that rate runs $2-3k before you get any signal, and none of those tools guarantee quality even with good prompts the fix: build the generator yourself. python scripts, settings files per phone, no database, no cloud, no saas. runs entirely off a laptop the pipeline breaks into a few agents. a parser that pulls content across the niche and ocr's it. a reference builder that turns that into reusable angles. a slide and video generator that mixes pre built pieces with new hooks and captions, no llm needed for the actual generation. a daily poster that pushes content to each phone through shortcuts so there's no manual airdrop, content lands straight in the clipboard ready to paste. a calendar and analytics scraper once excel stopped being enough past 20-30 accounts phones were $50 each, bought old. an iphone 7 on ios 15 matched an iphone 11 on ios 26 for performance, newer hardware didn't move the needle at all. the actual variable is content, not device each phone runs 30+ settings from an internal library before it touches tiktok, and the exact list differs slightly per model and ios version. dns leaks patched, webrtc leaks closed, ip tied to a specific location so the account can't be traced back to a base photos get run through a module that rewrites exif data to match a real iphone camera roll. camera dimensions, mb size, live photo data, geo tag matching that specific phone's ip, dozens of parameters layered in. this is the part that actually moves rankings, tiktok ranks native capture higher than obvious stock or ai output, and none of it triggers an ai generated label after posting video repurposing works too, same clip with a different hook counts as a new video to tiktok once it's run through the pipeline posting 20 slides across accounts takes 35 minutes total with shortcuts handling the transfer running cost: $40/month proxies, $40/month llm subscriptions, hosting free on cloudflare. one time setup was ~$300 for hardware plus ~$300 for courses, on top of $500 for the phones themselves. total spend so far sits around $1k, three months to build, now running at 2 hours a day android was tested and dropped. cloud androids passing google's full integrity check cost more per month than buying a used iphone outright, and still underperformed, the cheaper android tiers did worse. rented androids also couldn't run a second account on the same device, which killed the option outright account health has been mostly clean on ios, androids were the ones getting banned. one attempt at running tiktok on a jailbroken ios 16 device got logged out fast, no ban, but enough of a signal to not push jailbreak further until there's a way to test it without burning dozens of accounts first what's still unexplained: two accounts running nearly identical content and setup, one hits 1M on post 3, the other barely moves. same hook photos with minor crop or filter changes keep working, no clean read on whether that step is even necessary. one of the best performing accounts doesn't have us dns at all and still pulls more us traffic than accounts that do. no clean answer for any of it, just logged as unresolved and moved on next step is pushing toward phones running 24/7, automated swiping included, and expanding past tiktok into instagram reels

• 
  WIV Reports — Uncensored (@WIVReports) reported 21 minutes ago

  Any first-year network engineer knows the playbook: see a 429 with a CF-Ray ID, log into the Cloudflare dashboard, check the WAF/Rate Limiting logs for that ray ID, and adjust the rule. It’s literally a 2-minute fix. Instead, they insisted Cloudflare wasn't blocking anything, claimed DevTools were wrong, and issued a partial refund rather than taking 120 seconds to look at their edge logs. Pure laziness.

• 
  bnistordev (@bnistordev) reported 22 minutes ago

  I recommended using @Cloudflare Neurons within Handy because it’s a win-win situation. The problem is that it keeps generating an endless number of errors of different kinds, and Cloudflare’s API returns a vast array of models. I spent at least 30 minutes trying to get everything working, but in the end, I couldn’t, so I switched to DeepSeek.

• 
  🧞‍♂️Martin Donadieu - oss/acc (@martindonadieu) reported 28 minutes ago

  So France is joining spain to make all @Cloudflare down during games? 😭 Europe is omega doomed it's so sad

• 
  Huintellimance (@Huintellimance) reported 29 minutes ago

  Anthropic just deleted sessions from MCP — and it's the biggest protocol update since the spec launched. Here's what changed and why every AI developer should care: OLD MCP = a phone call. Your client and server ran an initialize handshake. The server returned a session ID. Every subsequent request carried that ID, and the server held your negotiated state in a live object inside one specific process. Think of a restaurant where only the waiter who took your order knows what you ordered. Works fine — until that waiter goes home. The problem: because state lived in one process, you couldn't spread requests across instances. Load balancers needed sticky sessions. Teams pushed state into shared storage. A single server restart dropped every open session. Autoscaling was essentially blocked. NEW MCP = an order slip. Anthropic killed the handshake and the Mcp-Session-Id header. Every request now carries its own protocol version, client identity, and capabilities in a _meta field. Any request can land on any instance behind a plain round-robin balancer. MCP servers are now ordinary HTTP services. They run on serverless. They run on edge. They survive restarts. But removing sessions broke three features, so each got rebuilt: Interactive tools → Servers used to push questions down a held-open stream. Now they return an "input_required" status and the client retries with the answer attached. Clean request/response. No persistent connection needed. Routing → Method and tool names moved into Mcp-Method and Mcp-Name headers. Gateways and rate limiters can route and meter without parsing JSON-RPC bodies. This is a massive win for API infrastructure teams. Caching → List responses now carry ttlMs and cacheScope. Clients cache tool catalogs instead of refetching on every reconnect. Less overhead, faster cold starts. Here's the part most people missed: State didn't disappear — it moved somewhere the model can actually see it. Instead of a session ID hidden in a header (invisible to the LLM), tools now return an explicit handle as an argument. The model can read it, thread it between tools, and recover from failed calls. A session ID in a header = the model has no idea it exists. A handle in the arguments = the model can reason about it. This is a fundamental shift in how agent state works. The protocol now treats the model as a first-class participant in state management, not a bystander. What this means in practice: Deploy MCP servers on Cloudflare Workers, Lambda, or any edge runtime — no session affinity required Horizontal scaling is finally trivial: round-robin, no shared store Server restarts don't kill active workflows Agent state becomes explicit and model-readable instead of hidden in infrastructure The MCP vs. CLI debate was already the wrong frame. This update makes it irrelevant. MCP servers are now as easy to deploy as any REST API, and agent state lives where it should — in the model's context, not in some ephemeral server process. If you're building agent infrastructure and haven't read the 2026-07-28 spec update, you're already behind. What's your current MCP deployment setup — and does stateless change your architecture plans? #MCP

• 
  Jacky Chou (buying online businesses up to $1m) (@indexsy) reported 30 minutes ago

  RIP local SEO agencies. claude just one-shot your entire job and it took one prompt. here's the full breakdown: the workflow is stupidly simple. jacky didn't even look at the client's site. he transcribed the previous episode, exported the local SEO ebook, gave both to claude and said fix this. out came a massive document: hero section changes, schema gaps, missing pages, internal linking fixes, and a full build order of what to ship first. next step is feeding this call's transcript back in, getting the final mockup, and handing it to the team to one-shot. claude suggested pages that didn't exist and they're genuinely smart. practitioner pages so the clinic ranks when someone googles their physio by name. neighborhood pages like "physiotherapy in killarney, 7 minutes from our victoria drive clinic" to capture every surrounding area search. pricing FAQs. the neighborhood play works because people search their specific scenario now, and AI search made long tail queries explode. the one warning: don't blast 60 boilerplate pages at once. tristan audited a member's site this week that got deindexed for exactly that. the guy one-shotted the whole site with templated content and google sandboxed it, and it's way harder to come back out of the sandbox now. rewrite every page, phase them in, be surgical. the interlinking structure is the actual sauce. service pages stay location neutral (no city terms in the H1 or you cannibalize), then link down to their east vancouver and mount pleasant versions. each location page links back to its respective service area pages. one to one targeting in every area. tristan's words: once your authority and reviews build up on top of that structure, it's game over. RIP wordpress too while we're at it. the only clients still on it are the ones whose teams can't leave. everything new runs out of github and cloudflare, changes ship in one sentence to claude ("put these six service pages in the menu nav and deploy"), and the sites look infinitely better. one advise member keeps a stack of HTML templates and just runs one up every time he finds a rank and rent. that's the stack now. the meta lesson: tristan's buddy in singapore watched the last episode, took the transcript, and had his codex agent running all day shipping every change to his new jersey site. citations in, indexed, tier 2s queued. he's probably gonna make it. the era of watching a youtube video and having AI implement it before the next episode drops is fully here. next up: a live rank and rent case study, national level, built in public. niche suggestions wanted. full claude local SEO takeover with @tristanzheng watch/listen ↓

• 
  Anıl Soylu (@anilsoylu) reported 31 minutes ago

  @SlumpBusterLock @Cloudflare Posting the URL doesn't help anyone here, and the CTO already has it. The site itself isn't the variable. On a free plan a report takes you down regardless of what's on the page. On the $25 tier and above the same report goes nowhere.

• 
  TolkienWindow (@AbionMorse) reported 33 minutes ago

  @dok2001 @anilsoylu @Cloudflare yeah that is a very bad process, yikes! 🙃

• 
  2024=2023+1 (e/acc) (@commondoubts) reported 35 minutes ago

  @paularambles Site is down now. @Cloudflare to the rescue?

• 
  Larius Woodson (@LariusWoodson) reported 37 minutes ago

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