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 (43%)
• Domains (21%)
• Hosting (21%)
• E-mail (7%)
• Web Tools (7%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Hosting	2 days ago
New York City	Cloud Services	21 days ago
Los Angeles	Cloud Services	22 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:

• 
  OB (@obatt) reported 2 minutes ago

  @Cloudflare Your own MCP auth UI totally sucks

• 
  Jeremy W. Phillips (@jerephil) reported 4 minutes ago

  Somehow Cloudflare keeps releasing cool features that I never hear about. Am I just missing their marketing or something? In related news, Cloudflare email routing is pretty nifty.

• 
  brandon (@burcs) reported 5 minutes ago

  @defibagholder @immersivecommon @Cloudflare sadly no, going to be down at the austin office looks like a good time though!

• 
  Drayken (@KGDrayken) reported 6 minutes ago

  @mdong1909 Cloudflare owns both VoidZero and Astro now - can you make it a priority to have full support of Astro for Oxfmt and Oxlint now so monorepos don't have to fragment into linting & formatting fallbacks? IIRC plan was Q2.

• 
  Ari!/Snowii!! (Noragami Arc) (@LickinLil) reported 9 minutes ago

  like cloudflare ******* SUCKS it has a tendency to time out even when it's actually up and running

• 
  Fabrice NEYRET - pro (@FabriceNEYRET) reported 11 minutes ago

  @KaleyGoode cloudflare is ultra-annoying but usually you can log-in ! (from time to time you need to re-confirm identity once logged + and some days ago the site was down, though). BTW it seems that the unofficial plugin is (sometime?) incompatible with cloudflare.

• 
  Pranav Mailarpawar (@pranvtwt) reported 12 minutes ago

  @DarthPlagueisNL Still on Vercel. I’m planning to move it to Cloudflare this Saturday since the traffic is lower on weekends, so if anything goes wrong I can fix it quickly

• 
  Petrolium (@ShitlibRapist) reported 13 minutes ago

  @HinasSweatySock Looks like it was an issue with Cloudflare from skimming the forums.

• 
  Michael Esteves (@_Mikie_) reported 19 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

• 
  OB (@obatt) reported 20 minutes ago

  @mattzcarey @Cloudflare Don’t get me wrong; I love Cloudflare and am a big user (have been since you were just DNS), but your platform is now crazy big and with MCP and the AI explosion, auth is no longer just a DevOps and OpSec / senior dev at a start up function. Having basically IAM is going to lead to terrible hacks because of the end user exposure that AI now gives. It needs the MCP / IAM / AI equivalent of passkeys. We have to strip the complexity out (hide it) all while making it easy for the user to enable actual security without them knowing it, if you get my drift

• 
  Andrew Rulnick (@MickeySteamboat) reported 22 minutes ago

  @sierracatalina going to say there's a good chance it's hardware related sometimes it can be internet provider based, I had cloudflare challenging my nets and it was causing a LOT of problems with GPT in general until I identified that was the issue. ) :

• 
  Venelin K. (@venelinkochev) reported 25 minutes ago

  @nikitaeverywher @DirectifyApp Directify is built with Laravel/PHP and Cloudflare workers don't support this. :-)

• 
  Creed Hardcastle (@CreedHardcastle) reported 28 minutes ago

  @opencode @Cloudflare cloudflare has to jump in mid incident damn

• 
  AI News (@ainewsusa) reported 29 minutes ago

  The numbers are brutal: 85% fewer open issues, powered by agentic AI inside GitHub Actions. Cloudflare paired Flue (their agent framework) with triagebot on Workers to auto-classify, reproduce, and even patch bugs. Human reviewers only see the final diff. That’s not automation—th

• 
  Mark Lyck (@MarkLyck) reported 29 minutes ago

  @leerob @poteto @ericzakariasson can you please improve these simple Cursor PR features? Tried switching to Cursor this month, but there's a lot of missing / annoying stuff. 1. Add a preview link button. If the PR has a preview deployment from Vercel/Cloudflare/Netlify etc. Just give me a button I can click to quickly go to that preview deployment in Cursor or Browser. I don't want to have to go into the PR and go through review comments to find it. 2. Give me a keyboard shortcut to copy the Github PR link. Right now I have to click the chat, wait for it to load, then click "View PR" then click the 3 dots next to the github logo, then click copy link. That's way too many steps to share a Github/Origin link. 3. Why can't I configure trusted domains in the agent mode? Everytime I click a link I get this error "It's outside Cursor's trusted set. Only continue if you trust the source." And yes I did add it to my trusted domains in the IDE mode, but doesn't seem to work in agent mode. 4. Give me an indicator somewhere that shows how many approvals my PR has gotten if it has any. Right now the fastest way is to go to the github link, second fastest way is to go to the review section and scroll down and count manually if the PR doesn't have a lot of discussions. These are easy UX wins that would really help. 🙏🏻

• 
  Michael Flux (@michaelflux) reported 30 minutes ago

  @levelsio The actual stack is intentionally boring: - Structured error on every failure - One JSON log line per console.error / warn with a 32-hex traceId - Cloudflare Observability (logs + traces) enabled on every Worker - Frontend is also Workers (SvelteKit), so client errors travel the same pipe - No external SDK. Just Cloudflare’s native observability + application-level correlation.

• 
  Blank (@blankparticle) reported 31 minutes ago

  @benjaminshafii @alchemy_run right now it has best support for Cloudflare and AWS, Planetscale/Neon/etc are also supported, Fly Hetzner etc are being worked on, Stripe and other things are on its way

• 
  M. Yahia - ghostex.dev (@maddada) reported 32 minutes ago

  @robinebers @BehEvans @Cloudflare I default to cloudflare currently for most of my projects, last I looked there wasn't something as all-in-one and as competitive on price (for non-enterprise) Way easier to use than AWS + free or much cheaper than others like railway/vercel/netlify/etc. You get domains/dns/free protection and a bunch of stuff in 1 dashboard. While if you use some of the others you'd have to set up cloudflare separately (bit of a hassle). As long as you're not "Enterprise" they offer very generous prices. Also if you can make your app run on workers then it's one of the cheapest ways to host/scale an app since they charge you for active CPU milliseconds. I'm sorry for any mistakes or bad explanation, wrote this quick of the top of my head.

• 
  YanXbt (@IBuzovskyi) reported 32 minutes ago

  HERMES AGENT HAS AN AUTONOMOUS SKILL MANAGER RUNNING IN THE BACKGROUND. IT PRUNES WHAT YOU DON'T USE. IT ARCHIVES WHAT'S STALE. IT'S CALLED THE CURATOR. every time your agent solves a new problem and saves a skill, that skill lands in ~/.hermes/skills/. month 1: 15 skills. manageable. month 3: 47 skills. some are near-duplicates. month 6: 90+ skills. half are stale. catalog bloated. tokens wasted every turn loading skill headers the agent never calls. the Curator cleans this up automatically. HOW IT WORKS: tracks every skill: how often viewed, used, patched. 30 days unused → marked stale. 90 days unused → moved to archive. archived skills go to ~/.hermes/skills/.archive/ never deleted. always recoverable. runs every 7 days. enabled out of the box. WHAT IT TOUCHES: agent-created skills: full lifecycle. stale, archive, consolidate, patch. bundled built-in skills: archived after 90 days of non-use (on by default). hub-installed skills (agentskills. io): NEVER touched. off-limits. WHAT IT DOES NOT TOUCH: memory files. USER.md and MEMORY.md are not managed by the Curator. people confuse this constantly. Curator = skills only. PIN YOUR CRITICAL SKILLS: hermes curator pin deploy/cloudflare-pages pinned = off-limits. no stale. no archive. no consolidation. skill_manage refuses to delete it. patches still go through (agent can improve content). only agent-created skills can be pinned. skills in any cron job's skills: list are also protected without explicit pin. COMMANDS: hermes curator status (state + 5 least-used skills) hermes curator run (manual run now) hermes curator run --dry-run (preview without changes) hermes curator pause (stop auto-maintenance) hermes curator resume (restart) hermes curator pin [name] (protect) hermes curator unpin [name] (remove protection) hermes curator backup (manual snapshot) hermes curator restore [name] (recover archived skill) hermes curator rollback (revert last run) also available as /curator inside any session. LLM CONSOLIDATION (off by default): opt-in auxiliary model pass that reviews your skills for overlaps and proposes merges. curator: llm_review: true WARNING: run --dry-run first. always. auto-consolidation can merge skills you want to keep separate. comment CURATOR and I'll send you the full checkup guide with 5 use cases and config templates for solo dev, multi-project, and team setups.

• 
  Zyte (@zytedata) reported 39 minutes ago

  Why? Japan never really adopted the Western web stack. No Cloudflare everywhere, no AWS defaults. They built their own CDNs and hosting providers and just... kept using them.

• 
  Robin Ebers (@robinebers) reported 40 minutes ago

  wanted to give @Cloudflare a shot for storage and workers but then realized they don't have monthly spending caps?! any bug, abuse or some vibe coded **** could potentially generate thousands of dollars and there's no way to prevent it? you can set up a 'notification' - yeah great, thanks what the actual

• 
  Michael Flux (@michaelflux) reported 40 minutes ago

  I don’t use Sentry. I don’t use PostHog. I don’t use any dedicated error-monitoring SaaS. Every single error in my stack - backend, frontend, queues, Durable Objects etc - lands in Cloudflare Observability the moment it happens. Then a tiny custom Worker pings my account every 15 minutes, surfaces any new errors, and I fix them within a couple hours. Over time the apps just … stop breaking. Here’s the exact system (and why Cloudflare is cool);

• 
  Davis | Indie App Dev (@werigan_non) reported 43 minutes ago

  Fixing a Cloudflare DNS or SSL issue is only part of the workflow. The useful next step is to record what changed, verify the domain again, and keep the check available for future updates. A one-time fix becomes a learning loop when the next person can understand it.

• 
  Dan Ryland (@RealDanRyland) reported 44 minutes ago

  @philcampbell Are you using the Resend route or Cloudflare's new email service? I'm a big Cloudflare user and fan so wondering if I could create a product inbox to take all of my various domains into one inbox from forking this

• 
  JohnTheRevelator ✝️🥩 (@MaranathaJohn30) reported 45 minutes ago

  Is there a worse service than @Cloudflare? It's pretty much total garbage, every ******* time.

• 
  PromptKing | The Governance OS for AI Agents (@PromptKing32) reported 48 minutes ago

  @Cloudflare Optional scopes fix the consent problem. The remaining problem is independent proof that the agent actually stayed inside those scopes once it started running across systems.

• 
  美濃加茂まむ (@superdoccimo) reported 49 minutes ago

  @rzrgrv Exactly. “Success” is far too lossy. What’s funny is I just hit the same class of problem on X itself: replies arrive, but the UI sometimes makes it hard to tell which article they belong to. So I’m thinking of building a small Cloudflare Worker + D1 layer that preserves reply → parent post → article context as an append-only record. Different domain, same problem: don’t trust the final checkmark. Preserve the evidence that produced it.

• 
  A. Amorim (e/acc) (@deildo_jr) reported 50 minutes ago

  @MrPunyapal If Cloudflare has any outage

• 
  JohnNguyen 🔆 (@ThuyTrang108) reported 55 minutes ago

  The next wave of crypto users might not be humans, but AI. As AI agents become increasingly capable of autonomously searching for information, calling APIs, purchasing data, and executing tasks on behalf of humans, they require a way to make payments and stablecoins are emerging as a highly suitable option. Coinbase’s x402 protocol has processed over 165 million transactions totaling approximately $50 million; nearly 99% of these utilized USDC, with an average value of just around 30 cents per transaction. These figures signal the formation of an entirely new market: millions of automated, 24/7 micropayments occurring between software systems. As major players like Visa, Mastercard, Cloudflare, and MoonPay begin building infrastructure to facilitate payments by AI agents within controlled limits, stablecoins could evolve beyond mere money-transfer tools for humans to become the payment system for the AI ​​agent economy.

• 
  AngelPie (@Troy79979815) reported 57 minutes ago

  @Sakshi50038 Who's gonna tell gatekeepers about abstraction? Rate limiting: Cloudflare Caching: Redis Load balancing: your host Reverse proxies: NGINX API gateways: Kong CI/CD: Actions Docker: Railway Kubernetes: Overkill Service discovery: DNS Circuit breakers: your gateway Timeouts: Config