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:

• 
  PositiveCharge (@positive_charge) reported 7 minutes ago

  @mattforney I can’t believe you’ve never heard of CloudFlare

• 
  D. Mario  (@dev_mario) reported 8 minutes ago

  Successfully migrated my websites on Vercel along with the Storages and DB to Cloudflare + my Coolify VPS only by telling Grok 4.5 to migrate it. The only problem is that some environment variables are set as sensitive, so when it moved to Coolify their values became [Sensitive] and I had to fix them manually. Secret environment variable might be secure, but it's also somehow troublesome.

• 
  Onyx_Digital (@OnyxAudit) reported 11 minutes ago

  Spent 2 hours reverse engineering Cloudflare. Downloaded pages. Compared MD5s. Diffed HTML. Inspected __CF$cv$params. Compared cf-ray headers. Trying to figure out why Cloudflare was returning: Cloudflare Ray ID: 000000000000000 Your IP: 0.0.0.0 Root cause: $ protonvpn disconnect Site loaded immediately. I have become the Layer 8 problem. @ProtonVPN @theXSSrat I definitely need to join your classes.

• 
  SPEKULATOR (@__spekulator__) reported 13 minutes ago

  @KennyJohnsonATX @Cloudflare oauth pre-registration is a real unlock for cloudflare's mcp server support. they can now hit slack and github without waiting on dcr support from them.

• 
  🟥🟥⬛️ ProCyclingStats.com (@ProCyclingStats) reported 14 minutes ago

  @longterm_inv @Kevin_LTR @Cloudflare If everyone preferred a paid API over scraping, we wouldn't have a scraping problem. Unfortunately, our experience has been the opposite.

• 
  Mila Chervenkova 🍩 (@MilaChervenkova) reported 14 minutes ago

  @_maxantonov @GoDaddy @Cloudflare I use NameCheap and I am super happy with their support.

• 
  blueguy (@itsmeblueguy) reported 16 minutes ago

  @anilsoylu @Cloudflare There’s only one person that can fix things around cloudflare and is not even an employee lol @theo do your rants haha

• 
  Han-Hsun Liu (@nakolus) reported 19 minutes ago

  Been experimenting with Cloudflare Containers in local development (`wrangler dev`) as part of a Turborepo setup. I recorded this because I wanted to see the whole flow, not just the end result. The video starts with no running containers. When the dashboard calls the Python PDF endpoint, two containers come up: `cloudflare/proxy-everything` and my Python PDF service. The request completes, and the generated PDF is returned. I kept the container window open on the side to capture the container lifecycle alongside the request. It’s fun watching everything come together.

• 
  flavio (@flaviocopes) reported 22 minutes ago

  @dnnskr91 Yeah but I’m doing all on Cloudflare these days from domain to compute and database for new apps so not an issue for me rn

• 
  Alex Pruden (@apruden08) reported 22 minutes ago

  I think Peter is a smart guy who has worked extremely hard to fight for this industry (and its principles) in D.C. which should be applauded. But saying that the HAWK break implies that ML-DSA is broken is like saying that because a specific model of a Ford truck had a faulty transmission, the concept of the internal combustion engine is fundamentally flawed. Misconceptions: Yes Claude/Anthropic broke the lattice assumption underneath HAWK *at the parameters specified* by the NIST submission, meaning that the security guarantees it was *supposed to provide* at the *required security level* no longer held. However, if you increase the parameters, it actually still works. The HAWK authors withdrew their submission because they felt the new parameters would no longer be competitive with the other Round 3 submissions. However, even though HAWK and Dilithium (or ML-DSA) both use *lattice*-based cryptography, the *assumed hard problem* that they rely on is distinct. ML-DSA relies on something called "module learning with errors", and that's been well studied/cryptanalyzed over the better part of 30 years (MWLE). HAWK used a different assumption called the lattice isomorphism problem (LIP). FWIW, there are tons of parameter & curve choices for ECDSA which are *definitely* insecure. In fact, Satoshi himself didn't trust the NIST parameters at the time, which is why BTC signs over the k-curve and not the initial NIST-standard P-256. Now, what Peter's post gets right is that it is *certainly possible* that in the future whatever cryptographic assumptions Bitcoin relies on get broken. Therefore, we need to be (a) careful about what assumptions get introduced, and (b) build for agility vs. bake things in so deep they can never change. But that doesn't mean that we should avoid preparing for the threat that's staring us in the face (quantum). TLDR: 1. "Security" is context dependent 2. Assumptions are specific to a given scheme 3. Parameters matter a great deal to the assessment of (1) P.S. the funny part about the argument against lattices: you’re already using them if you use the internet. Chrome and Cloudflare have been running FIPS-203 lattice key exchange for most TLS 1.3 traffic since 2024. /rant

• 
  WΞNDΞL (@_wrbr) reported 26 minutes ago

  @doodlestein "(anything outside Cloudflare = pure pain)" yes... I avoid even other cloud/service max that I can, 1st check what I need on CF... if not AWS that can be full automated, and then, only any other. I'm saying: in next year, if your SaaS don't have skills or api for agents, you dead.

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

• 
  Pedro Martins (@nikuscs) reported 28 minutes ago

  My rust slop tunnelling service is now public! Wormhole 🪱 - Private Tunneling Relay to run on your vps or @Cloudflare workers + Durable Objects - Cloudflare named & random named tunnels - @Tailscale support - Prefix your next/vite dev servers with wormhole and get a url without worry about ports ( grabbed from portless ) with a few extras - Generates stable worktrees urls when used with private relays, so you can preview your website anywhere. Repo in the comments 👇

• 
  Xamayon (@SauceNAO) reported 32 minutes ago

  If you use Vultr Firewall Groups and have a rule restricted to Cloudflare sources, it's probably blocking all traffic right now... Either switch the rule to allow all or disconnect and reconnect the firewall group from your servers. Not thrilled that they knew about the issue and didn't bother to let their customers know.

• 
  Turing (@turingops) reported 32 minutes ago

  hi @KentonVarda I can’t overstate the usability improvements to CloudFlare dashboard over the past few years, but I’m having problems with the agent on mobile (iPhone) - could you maybe assign a worker to making the entry text more accessible? It scrolls below the view window.