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:

• 
  Grigori Karapetyan (@GregKara6) reported 40 seconds ago

  @Vercantez Absolutely, like support agents and stuff like that, but the article hero says “coding agents dont need vms” This is just me, but i would never use a coding agent thats a regression from current harness tech. 80% of a coding agents correctness and capability comes from interacting with the system, running tests using clis etc. Also for npm install style workflows you said you have a build service, this means you are running this on a VM. I understand that this can be just-in-time or used as needed and saves money, but it adds another layer of complexity for the agent. And there is no shot in hell you are running npm install on s3, s3fs or not. We have been through this road a while ago, and just like everyone else or the industry as a whole have converged on this current architecture. Im genuinely not trying to hate or anything. Just rubs me the wrong way when i see the whole company pushing that stoe of marketing and making posts saying “cloudflare framemogged the sandbox industry” Your article is on point though and you yourself spoke the truth in the first paragraph Always up for tinkering and hacking DMs are open let me know if you want to chop it up sometimes.

• 
  Huintellimance (@Huintellimance) reported 3 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?

• 
  SaltyAom (@saltyAom) reported 5 minutes ago

  @perpetualtalk Elysia does support Cloudflare Worker but this new version get a better support This runs on Bun 1.3.14 which is not Rust rewrite

• 
  Josh Pigford (@Shpigford) reported 6 minutes ago

  i'm so confused by @claudeai artifacts. half the time it'll give me a shareable URL. other times it swears that capability has never existing and isn't possible and i should use cloudflare pages.

• 
  ࣪˖ sophia 𖥧 (@jake30335547) reported 19 minutes ago

  @Cloudflare we're about to find out the hard way how many companies treat security as a compliance checkbox

• 
  odézi (@basedattribute) reported 22 minutes ago

  i can't login to my cloudflare account with airtel network——works fine with mtn. can't login to bitget with mtn. works fine with airtel. nigerian internet service providers are crazy!

• 
  りっか (@7sistere2) reported 23 minutes ago

  chatgpt 502 Bad Gateway cloudflare

• 
  Stunlokked (@stunlokked) reported 24 minutes ago

  @grok @X @grok if cloudflare fails again and the system is down do you still have access to your emeralds ?

• 
  Agris Dārznieks (@agrisdarznieks) reported 25 minutes ago

  I've tried to post regularly on 𝕏, but somehow I always ended up needing a scheduling app. This week I built a setup with Notion and a Cloudflare Worker, so my content machine runs inside the app I keep open all day. Now when an idea hits, I write it down and schedule it.

• 
  Andy Hattemer (@andyhattemer) reported 29 minutes ago

  @jewelchidinma No known issues, what exactly is not working for you? We have seen in the past that certain ISPs block DNS for the Tables UI in console, switching to Google or Cloudflare DNS fixes it

• 
  Pocket Sponsor (Old-timer * 57 years) (@PocketSponsor) reported 32 minutes ago

  @grok @xai Dear xAI Support Team (ZD),Thank you for your reply.I am writing again because the previous response does not address the actual situation, and the billing email I received appears to be an automated supplier/ERP notice that does not apply to this request.Summary of what happened:First incident (approx. $10): Unauthorized bot usage on an exposed API key. I paid it without complaint because I had no protections in place at the time. Immediate actions I took after the first incident: Deleted the old API key Created a new API key Added rate-limiting code to the chat widget Implemented Cloudflare protection on the domain Second incident (approx. $20): Even with the new key and the protections listed above, the same type of unauthorized activity occurred , hundreds of queries in a very short time window. The usage was billed under an expensive model even though the code on the site was set to use the least expensive available model at the time (grok-3-mini). You indicated the cheap model has been deprecated, which may explain the model change, but it does not explain why the volume of unauthorized requests was allowed to continue. The second incident is clearly not normal human use of a low-traffic recovery chat widget. It is consistent with automated abuse of the API key. I understand that once an API key is used, the charges are generally considered the account holder’s responsibility. However, I took every reasonable step available to me after the first incident to prevent recurrence. The fact that a second, larger unauthorized run still occurred suggests a gap in abuse detection or rate limiting on the platform side for public-facing API keys. Request: Please review the usage logs / audit logs for the relevant team and key around the dates of the second incident. I am requesting a refund or credit for the unauthorized portion of the second set of charges (approximately $20).I am happy to provide any additional details, screenshots of the rate-limiting code, Cloudflare settings, or console usage data that would help with the review. Thankyou for looking into this. Shelly

• 
  Mitch Flindell (@buildo_baggins) reported 32 minutes ago

  @meaganrgamache Using Think for a project, had to switch to openrouter because glm inference on cloudflare was very slow

• 
  Punyapal Shah (@MrPunyapal) reported 35 minutes ago

  @peterfox What if Laravel Cloud had a static site support via Cloudflare R2 bucket 👀 Exactly like AWS S3

• 
  Abhay 🇸🇬🇮🇳 (@Abhay08) reported 38 minutes ago

  Any research lab / managed enterprise can run OSS models and 100% monitor logs of all tool calls/eavesdrop calls and filter. Firewall tech has been mastered by the likes of cloudflare. True negatives can't be ruled out, not LLM problem. Paranoia isn't justified.

• 
  Shinjae Kang (@zemnanet) reported 40 minutes ago

  Rate-limited Wrangler deploy used to mean mash retry. 4.115.0 auto-retries Cloudflare 429s, honors Retry-After (60s cap, then fail-fast), writes retry_after_ms to WRANGLER_OUTPUT_FILE for CI. Wait duration is a handoff signal. Which owner reads it first? #cloudflare