Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Cloud Services (36%)
• Hosting (27%)
• Domains (18%)
• E-mail (9%)
• Web Tools (9%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
New York City	Hosting	4 days ago
New York City	Cloud Services	23 days ago
Los Angeles	Cloud Services	24 days ago
Paris	Cloud Services	1 month ago
New York City	Hosting	1 month ago
Manchester	Domains	2 months ago

Full 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:

• 
  )) (@truthofkosova) reported 5 minutes ago

  @adityadotdev @rauchg You need custom rules for Cloudflare in order to make the AntiDDoS really work, I'll be happy to help!

• 
  Jacob (@jacobbuilds_) reported 5 minutes ago

  @efalcao @Cloudflare 1-click setup, just add domain, binding in wrangler and send it through function in backend service. in dash u can lookup observability. And its cheap ;D

• 
  Bob Starnes (@bobstarnes) reported 13 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.

• 
  donmagicjuan (@donmagicjuan) reported 16 minutes ago

  @technolochap @sickdotdev A lot of high-level enterprise work vibe codes as well, and we only notice when AWS/Google Cloud/Cloudflare goes down for a few hours. These cheeky lot only pick on the presentations that don't speed run their own manual UX testing.

• 
  Fikri karim (@fikrikarim) reported 17 minutes ago

  @efalcao @Cloudflare There should be a clear guide on how to raise the daily limit. Otherwise, people will have problems when their apps suddenly go viral.

• 
  Pikanou ⚡🏴‍☠️ (@pikanou_) reported 17 minutes ago

  Agent Experience is quite a terrible label since AI doesn't have, urgh... feelings. So repurposing human-centric 'UX' terminology for autonomous agents is weird and just plain buzzword. Sounds like AX is the new UX! Rebuild everything! But behind the scenes, the engineering is a big reality. For now most websites are hostile to AI agents, quite difficult for them to visit the pages with cookies banners, cloudflare bot challenges, client-side JS hydration crash headless scrapers before they even fetch content. What we see from Vercel with their isagentic is about improving your website for Machine Accessibility. Agents don't care about the design of your landing page. They just want to extract its content. Want to know what to do? -> building deterministic APIs, agent-first auth, and machine-readable data pipelines. I would call it instead Agent Interoperability, but yeah I guess you can't brand it as "AI"

• 
  Net-Updates by StabilityTest (@stabilitystatus) reported 18 minutes ago

  Cloudflare Service Disruption A fix has been implemented and we are monitoring the results. Status: Monitoring Impact: Minor Updated: 6:42 AM GMT+0000 Service status tracked by @stabilitytestio

• 
  Joshua Montgomery (@oojoshua) reported 20 minutes ago

  @HawaiianTel - You are dropping all traffic to Cloudflare. Just Cloudflare, but that's 18% of the Internet. You've been dropping it on and off for a week. Can you stabilize it so we can have reliable Internet? Been a week of no power and this is adding to the problems here.

• 
  Javed (@jshai0) reported 22 minutes ago

  @itskalenai Ok. May need to check if all the network requests are secured instead of Also you can check backend logs like Cloudflare or aws whatever being used if there is any geo blocking firewall.

• 
  Eric Falcão (@efalcao) reported 22 minutes ago

  how's it going with @Cloudflare email sending? what's good? what's bad? we want to know!

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

• 
  Michael Esteves (@_Mikie_) reported 24 minutes ago

  @RhysSullivan @sergical @Cloudflare Is there a way to turn off connections so I can temporarily disable a specific connection if I’m not working with that connections data. ie two different work connections and don’t want the agent to see one while working on a different project

• 
  Maik Pietzka (@MPi_IT) reported 26 minutes ago

  @Cloudflare Prompt DLP needs context beyond keyword matching. Useful controls distinguish source code, credentials, customer data and business context, then record why content was blocked or allowed. Security improves when users can understand and challenge the decision.

• 
  pystar (@pystar) reported 29 minutes ago

  OpenAI has joined the WebMCP hype train, same month as @Cloudflare. Hunch has been on it since Feb'26. "Never wrong, just early."

• 
  Mike in’ Software (@mikeinsoftware) reported 31 minutes ago

  @levelsio I still don’t understand why they use Vercel when you can get a VPS from Hetzner for $10-25, connect Cloudflare and never worry about traffic unless you hit like 100m per day or something

• 
  Bash (@bashirbuilds) reported 31 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

• 
  Boussetta Mohamed (@boussetta15a) reported 31 minutes ago

  @Argona0x Architecture is real, but math still breaks physics. Fair point on clarifying the execution context, but breaking down the numbers actually makes the math harder to defend: The Kelly Math Check:Risking 6% per position to scale $50 into $5,273 in 48 hours is a ~105x return. Even with aggressive compounding, executing that trajectory via 6% sizing requires a near-flawless winning streak over dozens of consecutive binary outcomes in 48 hours. Weather markets on Polymarket simply don't offer the order-book depth or rapid settlement speed to absorb that without massive slippage wiping out the edge. Real Browser vs. Anti-Bot Engine:Running a full GUI browser on a dedicated cloud instance solves JS rendering, but Cloud VM IPs + Automated DOM interactions (even via Groq/Grok execution) trigger Cloudflare/Polymarket behavioral fingerprinting at scale way before hitting a 100x run. Bottom line: The architecture (Agent + Cloud VM + Live Context) is clean and represents the future of autonomous execution. But the 48-hour PnL curve reads strictly as extreme variance / outlier tail-risk, not a reproducible 6% Kelly strategy.

• 
  Nick Gray (@nickgraynews) reported 31 minutes ago

  @jonathan_wilke Migrate to Cloudflare please 🙏 you won’t have these issues

• 
  KirbySmith (@GenKirbySmith) reported 33 minutes ago

  @opencode @Cloudflare I've had network errors all weekend using ox-alpha-free.

• 
  ⚡BeefButterBTC⚡ AKA - Big Pleb (@BeefButterBTC) reported 33 minutes ago

  @BitcoinFinally @fold_app Try again, looks like Cloudflare issue

• 
  Levi (@leviackermanft) reported 36 minutes ago

  @choehau_ara Cloudflare is facing issues with jio sim recently. That's why i switched.

• 
  Mathieu Céraline (@mathcrln) reported 38 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.

• 
  cykros🔻 #PardonSamourai (@cykros) reported 38 minutes ago

  @AlexMichaelis99 @derekmross That all said it does seem that the app version of it works just fine right now even as the site is down (Cloudflare error).

• 
  engineeredX (@enginenerdx) reported 42 minutes ago

  cloudflare shipped kitesurf: chromium-free browser runtime for agents, native x402 so the agent pays its own api bills with no human approving each transaction. they built the sandbox and the wallet. the layer that says no to a bad spend is still your problem.

• 
  Michael Gold (@michaelgold) reported 43 minutes ago

  @Trace_Cohen @vercel @vercel_dev I hit 3M views on my personal site and they shut me down. Moved it all to CloudFlare and my bill is $5 in workers.

• 
  Q. (@qdr_tech) reported 43 minutes ago

  @_ix_drew any computer can be a server. “server” mostly describes what the computer is doing, not what type of computer it is database: install mysql/postgres, make it reachable over the network (tailscale is an easy option) & query away website: install nginx + port forwarding or a cloudflare tunnel

• 
  Michael Davis | EF-Map (@EFMapOfficial) reported 44 minutes ago

  Bit of an interesting one from GrokBot this morning. I asked it to check Reddit directly and it came back saying the request was leaving through 104.30.175.37, which is a Cloudflare-owned IP. The screenshot is its own description of what happened. That does not prove GrokBot itself is running in a Cloudflare datacenter. It proves the Reddit request is egressing through Cloudflare. The slightly more interesting bit is that the exact same IP has shown up publicly in reports involving Cursor cloud agent sandboxes. Given GrokBot appears to sit very close to Cursor's cloud-agent infrastructure anyway, that would make a lot of sense. My guess is the compute is using Cursor's existing sandbox/agent plumbing and simply getting branded as GrokBot at the product layer. Still only an inference from the network path, but a fairly neat little clue.

• 
  Carlos Rodera (@carlosrodera_) reported 47 minutes ago

  @ETWinzer @thsottiaux The screenshot is from the app, the web I think might be related to cloudflare, I’m not sure but at the same time yesterday and today hostinger and ChatGPT were both not working properly

• 
  System11 (@System11b) reported 52 minutes ago

  @suddendesu If only it were that simple - when I first turned on cloudflare, after a day it had counted 120,000 IPs. Individual bots like Amazon were sending 300,000 requests per day. The rate of hits was bad enough that I couldn't even log in to check CPU, users couldn't access the site properly and in excess of 99% of hits were junk.

• 
  Bally_AgenticAI (@bally_kehal) reported 60 minutes ago

  @Tricentis @Cloudflare 5/ The pattern: reads were never the problem. An agent that reads your DB wrong wastes tokens. An agent that writes wrong deletes ****. Write-path governance is where agent security actually lives.