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:

• 
  احمد (@born2code) reported 2 minutes ago

  @threepointone I did that with fargate (so I can use OpenAI subscriptions), sqs and dynamo. The problem with workers is that cloudflare blocks the OpenAI subscription calls (I suspect this this OpenAI buy blocked at CF edge), which is a non starter at the rate I use tokens

• 
  dnvhariprasad (@dnvhariprasad) reported 7 minutes ago

  From the new MCP spec, now coming to Claude: Stateless core: MCP moves from persistent two-way connections to plain request/response. Practical effect: MCP servers can now run on serverless/edge infrastructure (Lambda, Cloudflare Workers style) instead of needing an always-on process, which makes them far cheaper to host and scale. MCP Apps: servers can render interactive UI inside the Claude conversation itself: forms, pickers, visual output, instead of only returning text. No more bouncing between Claude and the tool's own website. MCP Tasks: proper support for long-running work. An agent can kick off a job that takes minutes or hours, disconnect, and check status later, rather than holding a connection open. Enterprise-grade auth: authorization now aligns with standard OAuth 2.0/OIDC, so MCP connectors plug into identity systems companies already run (Microsoft Entra, Okta) instead of needing custom auth. #mcp #anthropic #claude

• 
  nc (@encyapps) reported 10 minutes ago

  @onlinedopamine I had this issue too but i ended up setting up a deep link since i had my own domain. codex one shotted it with the cloudflare mcp, it opens straight to the App Store instead of in ig

• 
  DrGlitchy ⚒️⚙️ (@DrGlitchyTV) reported 10 minutes ago

  @CarlosHenr36599 @realrusro You would have to train 1.5 million moderators before you could put them in the job, the would have to speak a litany of different languages and you would need even more people to watch **** groups and relay the new slang and abbreviations. You also need a network team to prevent those people from getting back on the platform (or you could hire Cloudflare for a custom integration).

• 
  alex ▲ (@aldexdev) reported 12 minutes ago

  "Deploy it to the edge" was 2023's cargo cult. Here's the 2026 rule: run functions close to the data they read, not close to the user. Edge (Cloudflare Workers · Vercel Edge · Deno Deploy) — auth checks, geolocation, redirects, A/B splits, header rewrites. Latency-sensitive, stateless, reads from cache or edge KV. Never a DB call. Region (Vercel Fluid · Fly Machines · Lambda in DB region) — RSC data fetch, Server Actions, CRUD, anything touching your primary DB. Anything more than 2 sequential queries belongs here, not at edge. Origin (Railway · Fly · your own boxes) — long-running, WebSockets, uploads, scheduled jobs, queues. Anything that breaks the request-response shape. Serverless will bite you here. The 2024 mistake: putting DB reads at the edge because "edge = fast." You add latency, not save it — every round-trip from Sydney to us-east-1 for a Prisma query costs you 200ms and a rate-limit ticket.

• 
  Huintellimance (@Huintellimance) reported 16 minutes ago

  MCP just shipped its biggest update since launch. The protocol is now fully stateless — and that changes everything for how AI agents connect to tools. Here's what happened: The Model Context Protocol dropped spec 2026-07-28 yesterday. Since late 2024, MCP has gone from "spec nobody heard of" to nearly half a billion SDK downloads per month. Both the TypeScript and Python SDKs crossed 1 billion total downloads. It's the de facto standard for how AI models talk to external tools, databases, and APIs. But until now, MCP had a problem: it was stateful. Every MCP connection required a handshake (the initialize/initialized exchange), a persistent session ID, and an open bidirectional stream. That meant your MCP server had to live on a long-running process — no Lambda, no Cloudflare Workers, no edge functions. You needed a VPS or a container that could hold state across requests. That's over. The new spec removes the session handshake entirely. Every request is now self-describing — it carries its protocol version, client identity, and capabilities inline. No session ID. No persistent connection. Any HTTP request can land on any server instance behind a plain round-robin load balancer. What this unlocks: Serverless MCP servers. Deploy to Lambda, Workers, or any function-as-a-service platform. Pay per request, not per idle server. Edge deployment. Put your MCP server at the edge, close to the user. Cold starts are irrelevant when there's no session to establish. True horizontal scaling. No shared state means no sticky sessions, no Redis, no session stores. Just spin up more instances. Built-in observability. Method and tool names now travel in HTTP headers (Mcp-Method, Mcp-Name), so gateways can route and authorize without parsing the body. But the protocol didn't just strip things away — it added smart replacements. The old server-to-client requests (like asking the user for confirmation mid-tool-call) used held-open streams. Now they use Multi Round-Trip Requests (MRTR) — the server returns a structured "I need input" response, the client gathers it, and sends a follow-up. All stateless. All over plain HTTP. Tool catalogs now carry cache hints and deterministic ordering, so clients can cache them and keep upstream prompt caches stable across reconnects. No more re-fetching everything on every connection. There's also a formal extensions framework now — Tasks for long-running work, MCP Apps for server-rendered UIs, and Enterprise Managed Authorization for orgs that need it. Why this matters: MCP went from "cool protocol for local dev tools" to "production-ready infrastructure for the entire AI agent ecosystem" in one release. The deployment story is now as simple as any REST API. If you've been holding off on building MCP servers because the infrastructure overhead felt like too much — that excuse is gone. TypeScript, Python, Go, and C# SDKs are all updated. Migration notes are live. The breaking changes have a 12-month deprecation window. What MCP servers are you building — or planning to build — now that serverless is on the table?

• 
  Salina Mendoza (@inababi) reported 18 minutes ago

  @Cloudflare can you talk to your customers here? This is such a bad look for the feature that is only meant to be used as an emergency. There is zero reason to have this on 100% of the time and it seems they cannot figure out how to turn it off

• 
  high priestess of tomatoes (@ActualMuscovite) reported 19 minutes ago

  cloudflare is really just an intrusive nightmare on all levels now, it's at the point where it wants to verify me every time i use a basic search function in firefox like is there anyway for me to lobotomize the damn thing

• 
  Syed Balkhi (@syedbalkhi) reported 19 minutes ago

  @carlhancock Yup. I have multiple WooCommerce stores in many millions in annual revenue, and I know several customers who're much bigger using Woo. If a Woo store can't scale, it's likely a hosting infrastructure problem. We just switched our WooCommerce to @LevamoHosting and the speed is incredible with Cloudflare Enterprise, Auto-scaling, Redis Object cache, etc. Other hosts like Rocket, Pressable, etc all offer solid Woo hosting options that will scale.

• 
  kirua (@aquipongoalgo2) reported 20 minutes ago

  @a63738464 1.1.1.1 as issa cloudflare service

• 
  Apple Chomping Unc (@CigSmokingMill) reported 25 minutes ago

  Every social media app is throwing the Flock hysteria in your face. No one is getting banned, de-monetized, groups shut down, deflockdotorg shut down by cloudflare or ICANN, etc. That alone tells you all you need to know

• 
  Wealth Sage (@GetRichStayRich) reported 25 minutes ago

  Bullish: Cloudflare ($NET) Five-Year Return: +126% With a massive network spanning more than 310 cities in over 120 countries, Cloudflare (NYSE:NET) provides a global network that delivers security, performance and reliability services to protect websites, applications, and corporate networks. Why Are We Bullish on $NET? 1Billings growth has averaged 34.2% over the last year, indicating a healthy pipeline of new contracts that should drive future revenue increases 2Market share will likely rise over the next 12 months as its expected revenue growth of 28.4% is robust 3Fast payback periods on sales and marketing expenses allow the company to invest heavily and onboard many customers concurrently

• 
  Jacky Chou (buying online businesses up to $1m) (@indexsy) reported 25 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 ↓

• 
  Evadne W. (@evadne) reported 26 minutes ago

  Not very happy with @Cloudflare Workers AI so far. Previously the Kimi K2.7 endpoint would fail for some time and they wanted to close the issue after telling me to use another model. Now I have found they have not added pricing to some embedding models. Loosey goosey behaviour

• 
  Albert Clownstein (@ClownYouAllDay) reported 27 minutes ago

  @NotNordgaren What ******** is this thread? Doesn’t everyone know you have to call cloudflare for localhost issues if using cloudflare dns settings on your pc so they can issue a new certificate for it?