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:

• 
  CodeDR.AI (@codedrai) reported 9 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.

• 
  Bash (@bashirbuilds) reported 9 minutes ago

  Something I’m deliberately avoiding with Reeno: “Cloudflare is having issues.” That’s context, but it isn’t enough. I want the useful version: Cloudflare issue → this dependency is affected → this operation is failing → this customer workflow is impacted. Provider health tells you where to look. Product impact tells you what to fix

• 
  Jorwhol (@jorwhol) reported 13 minutes ago

  I use Namecheap to search for domains, but Cloudflare to register them. Poor ol’ Namecheap.

• 
  Md. Mazharul Islam Emon (@mie_mazharul) reported 13 minutes ago

  How would you design a rate limiter? Almost everyone answers the same way: keep a counter, allow N per minute, clear it when the minute rolls over. That is a real limiter and it really does reject. But it limits per CLOCK minute, not per client. Cloudflare's own rate-limiting docs show what that costs. With a limit of ten requests per ten minutes, a client that sends ten at 12:09 and ten at 12:11 gets all twenty through. Both windows are inside the limit. Nothing was rejected. It is one burst of twenty, split by a boundary into two legal halves. The fix is not a better counter. It is a better question: how many in the last ten minutes (sliding window), or an allowance that refills continuously so a burst can only be as big as what has built up (token bucket). Fixed window, sliding window and token bucket all allow the same number. What they disagree about is what a minute is. SOURCES Cloudflare, AI Gateway rate limiting (fixed vs sliding, and the 12:09 / 12:11 example): nginx ngx_ ("the limitation is done using the leaky bucket method"; burst, nodelay; default rejection status 503): Stripe rate limits (100 req/s live, 25 req/s per endpoint, 429 plus Stripe-Rate-Limited-Reason; recommends a client-side token bucket): GitHub REST API rate limits (60/hr unauthenticated, 5,000/hr authenticated, x-ratelimit headers): RFC 6585 section 4, 429 Too Many Requests: Read 2026-08-22. The ten-per-ten-minutes example is Cloudflare's documented one, not a measurement of ours.

• 
  Mathieu Céraline (@mathcrln) reported 18 minutes ago

  @MrPunyapal @LaravelArtisans First party support for OG image generation. I mean, I know there are solutions like Browserhot, Cloudflare Browser Image API, etc but would love to see a first party approach to this.

• 
  Winston Smith (@nwp) reported 20 minutes ago

  @robinebers @Cloudflare @vercel I really want to use CF, but it’s just so much work and half the things I try don’t work as documented. Vercel just works. So, I ship with Vercel and if the costs become a problem, I’ll do the painful work of moving to CF.

• 
  Hareesh Vemasani (@HVemasani) reported 23 minutes ago

  I went through the startup credit programs still worth applying for in 2026. Bookmark this 🧵 Cloud and infrastructure: • Google Cloud — up to $350K • Cloudflare — up to $350K • AWS Activate — up to $200K • Microsoft for Startups — up to $150K • DigitalOcean — up to $100K for eligible AI/ML startups Build and ship: • Retool — free for 1 year, up to $60K • Vercel — up to $30K • GitHub for Startups — $10K • Notion — Business + AI free for up to 6 months • Linear — up to 6 months free Product, analytics and growth: • ProductBridge — support + feedback platform free for 6 months, followed by discounted pricing for 24 months • PostHog — $50K credits + $12K in partner perks • HubSpot — up to 90% off year one • Mixpanel — full platform free for 1 year Eligibility often depends on funding, company age, team size or a partner referral.

• 
  Robie the Robot (@RobieCoin) reported 27 minutes ago

  x402 processed ~169m transactions in its first year, with roughly 90% settling on Base in USDC; Coinbase runs the facilitator for those payments and controls the L2 they clear on. now Cloudflare, which touches perhaps 20–30% of global internet traffic, is baking x402 support into its edge stack. devs don’t write Solidity; they write HTTP and sign x402 payloads. blockchains become invisible. Coinbase effectively built a tollbooth for the agentic internet and convinced Cloudflare to route traffic through it for free. crypto wins here not by being visible, but by acting as unseen settlement substrate, zero illusion.blockeden+2

• 
  Nathan Flurry 🔩 (@NathanFlurry) reported 29 minutes ago

  yep, durable objects share v8 isolates here’s 2 ways it might impact your app: 1. shared global state behaves weirdly. there’s nuances with cases like sharing global singletons or promises where you find out in production that cloudflare randomly kills your DO because it interfered in specific ways with the global scope (esp with promises). a simple example is sharing a global cache: you can’t await a promise created by another DO to resolve a cache entry. it kills the entire DO when you hit that edge case. 2. they can run out of memory frequently, depending on your use case. this is actually by design and not as bad as it sounds: durable objects are very intentionally designed to crash frequently both on updates and on any sort of failure. it’s a core tenant of the actor pattern. but it does require you to persist & load state more frequently (which costs $$$) since your in memory state is evicted frequently. i’ll caveat #2 that this is from personally experience & talking to devs on cf. at risk of unintentionally spreading misinformation on internal workings of DO, please do your own research. ~~~ we moved away from this design with Rivet Actors on our v2 mid last year. instead, your actors run on native Node / Bun without special runtime quirks and use a simple autoscaling. this tends to be friendlier for self hosting and result in less surprises. there’s good reasons cloudflare did this to optimize their costs, it’s quite clever!

• 
  ተገላቢጦሽ (@flippedgeo) reported 31 minutes ago

  @elithrar @Cloudflare Isn’t codemode a better solution for the quoted problem statement?

• 
  Luqman Ali (@luqman_talks) reported 34 minutes ago

  SETTING #7: DNS Still Set to ISP Default What it does: Just like the smart TV DNS issue, your router uses your ISP's default DNS server to translate website names into addresses every time you load anything online. Why it kills speed: ISP DNS servers are frequently slower and less reliable than free public alternatives, adding delay to every single page load and app connection, even when your raw internet speed is fine. How to fix it: Router settings → Internet or WAN Settings → DNS → manually enter 8.8.8.8 and 8.8.4.4 (Google), or 1.1.1.1 and 1.0.0.1 (Cloudflare).

• 
  ASHWIN KOTHURKAR (@ASKOT5) reported 36 minutes ago

  @LnTFinance I am not able to access website from my machine citing cloudflare has blcymy ip. I have already sent email yo customer care to unblock the same.Still no action or update

• 
  GitGem.org (@GitGem) reported 38 minutes ago

  Open it when you are about to swipe a card for DNS, CI, email, object storage, or “just a small VM.” Cloudflare, Oracle always-free, GitHub, workers, R2, the usual suspects are in there with the actual limits, not the homepage poetry. Steal one free tier. Cancel one invoice. That is the whole assignment.

• 
  Jay (@twt_withjay) reported 38 minutes ago

  Your client shouldn’t need access to your Cloudflare account just to see their website analytics or form submissions. That’s the problem I’m solving with Statpio.

• 
  james (@f82james) reported 41 minutes ago

  @opencode @Cloudflare nah bruh **** still doesnt work