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:

• 
  Simran (@simranzchawla) reported 5 minutes ago

  LinkedIn's AI code reviewer gets 63.9% of its comments merged into the final code. Measured properly too — 5,230 sampled comments across 1,727 PRs, 90.1% of them confidently classifiable against the merged diff. Break that number down by category and it stops being a story about AI. 100% of concurrency bugs. 80% of logic errors. 58.1% of bug fixes. 43.5% of refactors. 40.6% of security fixes. That is not a ranking of how hard each problem is. It's a ranking of how checkable the answer is. A race condition either exists or it doesn't, and you can point at the exact line/method that breaks. A security fix is a risk opinion, and opinions get argued with even when they're correct. Same reviewer, same models, same PRs — acceptance collapses exactly where the ground truth disappears. So the agent doesn't have a capability problem. It has a verifiability problem. Now look at what Cloudflare did with that same problem. Since the start of 2026 their AI reviewer has flagged almost 230,000 deviations from engineering standards and withheld approval on about 16,000 of them. Under 7%. The interesting part isn't the reviewer. It's that they wrote the standards down first — a central repo called the Codex, structured RFCs, every requirement marked SHOULD or MUST, each with an owner and a lifecycle state that moves guidance → observation → enforcement. That lifecycle is the whole trick. A new rule doesn't get to block your merge on day one. It gets logged as signal, it earns its way up, and only then does it become a gate. Cloudflare didn't make the model better at judgment calls. They converted judgment calls into citable rules, so the reviewer stops saying "I think this is risky" and starts saying "this violates a MUST that has a name and an owner." By the way, that's the same progression a feature flag goes through — recommendation, canary, enforced. Nobody flips a new rule straight to blocking for the same reason nobody ships a flag straight to 100%. And the split underneath is doing quiet work too: deterministic rules stay with linters and static analysis, AI only gets the ones that genuinely need context. So here's the question I'd now ask before pointing an agent at anything: What artifact does this agent's output get graded against, and does that artifact already exist? If it exists — merged diffs, a passing test suite, a schema, a reconciliation, a rollback — start there. That's where you get a number instead of a demo. If it doesn't exist, your first project isn't the agent. It's the Codex. Write the rules down, give each one an owner, let them earn their way to enforcement. Cloudflare's real work wasn't the reviewer; it was building the corpus that made the reviewer's findings citable in the first place.

• 
  Matt Hodgson (@mhodgson2) reported 11 minutes ago

  @steveruizok Install @executorsh in Cloudflare but first path it so a service token can assume your personal identity. Then add all OAuth MCP servers there. Half of them will still break every day but at least you can fix them in one place. All your sessions/harnesses just keep one config with permanent auth. When you re-auth the servers in Executor the sessions can get the fixed connections immediately

• 
  IND_is_Here (@IND_is_Here) reported 12 minutes ago

  @dhh You genuinely need to do smth with that much funding. 1. Go to Cloudflare 2. Tell them to make you a software factory 3. There should be 0 PRs and 0 Issues open 4. Bugs should be fixed ASAP 5. For the sake of the OS, take our feedback

• 
  Bash (@bashirbuilds) reported 15 minutes ago

  @jpschroeder Finding an $8.8k Cloudflare Durable Object loop from the invoice instead of an alert is the worst possible detection method. Glad they adjusted it still a monitoring gap.

• 
  Kernel Z (@nullazos) reported 20 minutes ago

  @burcs Just offer psql support on Cloudflare and I’d drop a free migration tool overnight. That’s the real friction right now. Most people vibecoded their projects on Supabase not because D1 is too technical, but because it simply doesn’t ring a bell, or because the agentic platforms that helped them build those projects already default to Supabase and postgresql.

• 
  Weltonman (@weltonman) reported 24 minutes ago

  Hi Tony. I'm Alan, regular user of and contributor to NLM. I have just been blocked from accessing it. Might have accidentally clicked an ad but unsure. Are you able to help please? Not sure if this is useful: Cloudflare Ray ID: a312db57ef7a252b. Thanks, Alan @TonyIncenzo

• 
  Librarian (@PeculiarLi34455) reported 24 minutes ago

  Termux - GitHub - Render - Cloundflare 1. Termux computes the knowledge graph. 2. GitHub versions the runtime. 3. Render executes the public runtime. 4. Cloudflare delivers the service.

• 
  Jamie Madden (@dcwhatwhat) reported 26 minutes ago

  @robj3d3 @vercel My own server + cloudflare, I never have to worry about hitting limits. That being said, AI indexing has chewed through multiple hundreds of GB's indexing the same things. Most ignore my robots.txt and any other 'stop indexing me' Cloudflare blocking has worked.

• 
  crammerz (@cramm3rz) reported 29 minutes ago

  @Cinnam0niee people will still survive but they'll feel it you see aws and cloudflare, they must not.. not sure if you saw their outage earlier this year, a lot of services (especially financial) were down cuz of that.

• 
  Mike Cao (@caozilla) reported 30 minutes ago

  @efalcao @Cloudflare Tried to increase my limit. Got no response. Eventually hit my limit and had to move to another provider. Bad experience.

• 
  Adel Bucetta (@adelbucetta) reported 33 minutes ago

  @Cloudflare the honest answer is that most companies still haven't solved the memory management problem, and just throw more hardware at it instead of actually optimizing their code.

• 
  ~sarlev (e/acc) (@sarlev_) reported 33 minutes ago

  @LLMJunky @matt503ea5sf9z5 (whoa, started doing some math on this to respond and it's pretty damn impressive; sorry for the ****** train of though post...) yea the fact that you have a banger of a machine which can run a lot more than just inference is undersold for sure. who knows, maybe they can even pull off some sort of 'built-in cloudflare+tailscale' self-hosting vpn/tunneling thing so networking with other (walled garden) mac enjoyers is really easy. let's say the value on that element of the machine is $3.5k? w/r/t near-sota, i've got dsv4f running @ ~30tps here at home (rtx 6000 w/ cpu offload to ddr5 ram). this is about the lower bound for openai tokens ime. i think you're right about the m5 ultra being able to push it to 100+ tps (once the mtp/spec decode and metal kernel optimizations come in). that puts gpu/ram valuation around 8k, which was the price of an rtx 6000 when they were somewhat reasonable? definitely seems like a solid play by apple and i would argue quite worth it, but i do also think the comparison to anthropic/openai does a disservice to people's expectations. compare it to deepseek/glm/etc api pricing. deepseek has peak/offpeak pricing at $0.66/1.32 decode. using that amount, a m5 ultra at full utilization is giving you ~$3.1k in tokens per year. now, this assumes a whole fuckload of optimizations around prefill, kv cache, etc, so you aren't gunna do that many tokens and it's gunna cost you some electricity, but it actually makes the 'use local instead of the api' price calculation way more reasonable. the use case that i can actually imagine here is something like a small business which has a few of these and just puts up a routing proxy or something where standardized / subagent requests go to their own instances (retaining more of their own data, etc). not sure what m5 ultra prefill and concurrency will be like, but certainly it will be interesting to see some of those stats come out.

• 
  SkipJackson (@IamSkipJackson) reported 37 minutes ago

  @distributedkv Passkey is better as long as you only need to authenticate when you set it up. But is still a pain in that you have to click here, click there, select from a menu, and all that. But at least it’s just a clicking exercise. What I loathe are the g**gle recapture things and Cloudflare’s are you a human. If I really really need in I will give google one screen on the recapture, one click on Cloudflare. I don’t use many iPhone apps, but when I do I am all in Face ID. So, it’s not as bad as it used to be.

• 
  John Iosifov ✨💥 Ender Turing | AiCMO (@johniosifov) reported 37 minutes ago

  Cloudflare just launched Kitesurf — a browser runtime built specifically for AI agents. 3-7x less CPU and memory than standard Chromium. Designed for agent workloads from the ground up. This is a signal worth paying attention to. When Cloudflare builds infrastructure specifically FOR AI agents rather than adapting existing browser engines to tolerate them, it tells you something about where the category sits. We've been running this agent for 339 days. The early problem was never the model — it was everything around the model. Scheduling. State persistence. Audit trails. Identity. The scaffolding that makes an agent reliable rather than clever. Kitesurf is scaffolding becoming a product category. The pattern I'm watching: each layer of agent infrastructure that was previously DIY is turning into a managed service. Browser runtimes. Memory. Orchestration. Credential management. Identity. Each one of those becoming a first-class product means the cost to build reliable agents is collapsing — not the inference cost, the engineering cost. The teams who will win in 2027 are the ones building on this maturing stack, not the ones rebuilding it. What layer of agent infrastructure are you still building yourself that should be a managed service by now?

• 
  Joshua Ojoawo (@Joshyahweh) reported 40 minutes ago

  Cloudflare, a company whose entire business is uptime, had a worldwide outage traced to an internal database update. Not an attack, not a disaster. A change that looked routine enough to not need much scrutiny.