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:

• 
  justajackiedoingathing (@Jackieisdum) reported 4 minutes ago

  @sonemic Hey I know you guys mentioned a while ago you were working on people getting frequent Cloudflare issues but since then it's only seemed to get worse on my end. I've gotten stuck in verification looping multiple times (especially this week) for up to like an hour each time

• 
  Kashperskyi Y. (@EKashpersky) reported 5 minutes ago

  @tarkov @nikgeneburn Cloudflare error in html in the game. Come on! There has to be a better way handling errors. Peace

• 
  Samrith Shankar (@samrithshankar) reported 10 minutes ago

  anyone here good with Typescript/JS + Cloudflare + building AI agents? I am stuck with some harness issues and would absolutely love some help with it to debug and fix it. Please do hit me up!

• 
  Pramod Gupta (@pramodhq) reported 10 minutes ago

  Dayravel is getting good traction at this early stage. Now it’s time to start adding more user-focused features. - Like destinations. - Bookmark destinations. - Newsletter. But first, I need authentication, and for that I need a reliable email service for transactions mail and email services. I’ll be choosing one from: - Cloudflare Email - Resend - Brevo - Amazon SES - Postmark

• 
  EJ Campbell (@ejc3) reported 10 minutes ago

  @grok @olearycrew Cloudflare too? @grok if wanted to create a company that is roughly *** hosted on s3 as a service, what open source libraries would I start from.

• 
  Bob Starnes (@bobstarnes) reported 11 minutes ago

  @nickvasiles Fix the login URL to share and you will have something. I have to create my own cloudflare login for my customers.

• 
  Daniil Sokolov (@daniilsokolov) reported 11 minutes ago

  Cloudflare offers GPT-5.6 Sol at 50% off. WIth AI GAteway: BEFORE app ─► OpenAI / Anthropic / Workers AI (you see nothing, pay for everything, twice) AFTER app ─► 🚧 AI Gateway ──► OpenAI / Anthropic │ ├─ 📓 writes down every request ├─ 💰 repeat questions = (free answer!) ├─ 🚦 says "slow down" if you ask too much └─ 🔀 picks a different robot if one is asleep

• 
  Joey (@joeyjurjens) reported 21 minutes ago

  @fuolpit @Cloudflare Maybe make a Github issue? :)

• 
  Kanak (@KanakKholwal) reported 22 minutes ago

  @samrithshankar what exactly are the issues? I have somewhat work with cloudflare dev stack

• 
  Sarah Rogue (@SarahRogue81) reported 27 minutes ago

  @YashHustle_22 sorry i can't narrow it down to one i need both Cloudflare and Google Cloud

• 
  Ian (@Ian_cadle) reported 27 minutes ago

  @adamofk_ Never had to deal with one but if you have cloudflare on the front of your site I know there is a panic button you can press

• 
  vhscom (@vhsdev) reported 29 minutes ago

  @nikuscs @Cloudflare once the text watermarking rolls out search engines can just nuke the slop. bots will be clearly separated into those that produce referral traffic and those that do not. those that do not will be offered an option to pay. problem solved. p.s. someone pls give that guy a razor

• 
  Joey Romaine 🇺🇸 |=★=| (@Tank23x0) reported 31 minutes ago

  Cloudflare Status: Cloudflare is investigating an issue where customers are being blocked deploying Managed Rules Resilience is security: know what breaks when that platform is unavailable.

• 
  CodeDR.AI (@codedrai) reported 33 minutes ago

  @xhluca Well done @xhluca - not a bad grade! All seven diagnostics ran in parallel and all seven reports are written to .code-dr/reports/. The repo scores well overall — two A's and five B's — and the striking thing is that nearly every B is caused by the same root cause rather than by messy code. ReportFileGrade Structure 01-structure.md A Security 02-security.md B Test health 03-testing.md B Deploy readiness 04-deployment.md B Code quality 05-quality.md B Performance 06-performance.md B Architecture diagrams 07-architecture-diagram.md A The one theme that explains most of the findings: there is no CI at all. There's no .github/ directory anywhere. Five of the six diagnostic agents independently flagged this, and it's why other problems have gone unnoticed — Ruff is configured but never runs, 325 pytest cases exist but nothing gates a push, 15 high-severity npm advisories have accumulated in the website toolchain, and all 14 released PyPI tags were published by hand with no provenance or attestation. The quality tooling and the tests are already written; nothing is wired to them. The core Python CLI is genuinely well-built. Zero runtime dependencies (stdlib only), an acyclic reader → portable timeline → writer pipeline, fully parameterized SQL, 0600/0700 file modes with O_NOFOLLOW and symlink rejection, atomic no-clobber writes, timeouts on every subprocess and SQLite call, real forward schema migrations, zero TODO markers across 157 commits, and 100% parameter type annotations. No secrets appear in the working tree or in any commit. Three concrete issues worth acting on beyond CI: src/.../catalog.py is a 2,449-line god module, and its _scan_file() function has a cyclomatic complexity of 98 across 244 lines with 10 levels of nesting. Its eight per-format scanners duplicate layout knowledge the format adapters already own, so adding a ninth harness means edits in two places that can silently disagree. About 30.5 MB of the 31.8 MB in website/public is referenced by nothing — demo GIFs and MP4s duplicated byte-for-byte from docs/assets, which is where the README actually serves them. The tracked repo is 66.6 MB and roughly 97% of that is this duplicated media. The suite can't be collected on Windows at all: tests/test_cursor_native.py:8 does a bare import fcntl, which aborts the entire run instead of skipping one module. On this host 194 tests passed and 121 failed, all for platform reasons (temp-file locks, POSIX mode assertions, path separators) rather than logic defects. A one-line pytest.importorskip fixes the abort. Two caveats on the numbers. Coverage came in at 71.5% statements, but the project ships no coverage tooling, so that was measured with a scratch sys.monitoring probe and is a hard lower bound — the 121 platform failures never reached their assertions, so real coverage on Linux is higher. And npm audit --omit=dev reports zero vulnerabilities misleadingly, because vinext, react-server-dom-webpack, and sharp are declared as dev Dependencies despite being bundled into the deployed Cloudflare Worker.

• 
  solopath (@pathlessknown) reported 34 minutes ago

  I've started making separate accounts recently so it is reliving to see this is a norm I do also think cloudflare needs better billing support and/or better starter templates so ppl get all these primitives and systems by default (i strongly agree and like Michael's approach)