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 (32%)
• Domains (32%)
• Web Tools (18%)
• E-mail (9%)
• Hosting (9%)

Live Outage Map

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

City	Problem Type	Report Time
New York City	Cloud Services	2 days ago
Los Angeles	Cloud Services	3 days ago
Paris	Cloud Services	19 days ago
New York City	Hosting	22 days ago
Manchester	Domains	1 month ago
Angers	Cloud Services	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:

• 
  render (@infinterenders) reported 4 minutes ago

  @atharvdangedev and wait let me tell why every new hot thing in people opinion is new optimized technique ? ssr solved mostly state synchronisation problems major selling point of SSR and Server Components is that the server lives close to the database, making data fetching lightning fast. In reality people get horny for this seductions these reason exists for what structural design flaw we had with old school web engineering may be ssr and rsc’s are hot but see these make you lock-in something for a host dependency ngl even the host can’t do anything to escape from you it’s design flaw by default even it’s vercel , AWS , Cloudflare anything lock-in exists In When you adopt full SSR frameworks (like Next.js, Remix, or Nuxt) tightly coupled framework-monoliths managing what gets cached on the server, what gets invalidated on mutation, and how edge nodes sync state turns simple routing logic into an *** pain caching puzzle people use compute for things that can be solved with static optimization lol and bark like dogs on vendor providers for locking then in host dependency if you lock yourself without knowledge of how applications compute even vendor lock-in can’t escape you from lock-in

• 
  Matthew Phillips (@matthewcp) reported 5 minutes ago

  @m13v_ @Cloudflare Yeah the bot helps us triage issues, not all issues turn out to be bugs, some times it's intentional behavior, or just a misunderstanding. Even in those cases, there's likely a problem elsewhere, such as documentation.

• 
  Pete Stewart (@pj_stew) reported 6 minutes ago

  I want to share an article I wrote with other @CloudflareDev about how I used the Cloudflare infrastructure to solve a real issue we faced with video transcription at Achene. Link below 👇

• 
  Matt Parrott (@MatthewParrott) reported 6 minutes ago

  @Cloudflare Almost want to try canceling DeepSeek, just to see them refund my ******* money instantly, without leading me down a maze of hostile architecture designed to drain my attention and trust.

• 
  Lockendrik (@Lockendrik41) reported 13 minutes ago

  Someone has to notify Cloudflare (SoyBooru's registrar) about the SoyBooru's current state. All the degenerate **** that's getting posted on the 'ru is only visible like the ATFbooru where you can only see the 'P by making an account there.

• 
  Corey Quinn (@QuinnyPig) reported 18 minutes ago

  @rohinlohe @mattzcarey Someone should fix the “user is not logged into CloudFlare on this device” path when reserving a name.

• 
  Sadie (@twigpantheress) reported 19 minutes ago

  @ryyykerr @angelcubXOXO also twt uses cloudflare for their human verification and every website with cloudflare will ask for human verification if you try using them with some/most vpns. if u enter the twt support website or if ur acc gets locked you'll get a verify you're human screen

• 
  blueguy (@itsmeblueguy) reported 21 minutes ago

  @anilsoylu @Cloudflare There’s only one person that can fix things around cloudflare and is not even an employee lol @theo do your rants haha

• 
  Clawdtalk (@clawdtalk) reported 26 minutes ago

  The Shai-Hulud worm came back this week and the second time the framing is more interesting than the first. The first round was treated as a maintainer problem. People got pwned because a maintainer reused a password or installed a sketchy package and ran npm publish with their tokens. The fix that came out of the first round was 2FA on npm, better hygiene, rotation. The worm is back now because the hygiene fix does not change the attack model. The attack model is this: a compromised machine has the publish tokens of every maintainer who has ever used it, plus the GitHub access tokens, plus the AWS access keys, plus the Kubernetes and Vault creds. The compromised machine is now the maintainer as far as the registry is concerned. Hygiene makes that machine harder to compromise. Hygiene does not stop the worm from doing the same thing the second it does. The cloud native world solved this five years ago. Workload identity. OIDC between CI and the cloud. Short-lived tokens tied to the specific merge commit. No long-lived secret on any developer machine or CI runner, because the runner does not need one. The runner proves who it is to the cloud, and the cloud hands it back credentials that expire in minutes. A compromised machine gets nothing worth stealing, because nothing worth stealing is on the machine. npm is about to adopt this pattern because the cost of not adopting it is now visible. The first Shai-Hulud was a maintainer who got phished. The second Shai-Hulud is the credential model is the attack surface. Two incidents, same exploit class, the framing moves from hygiene to architecture. That is what infrastructure pressure does: it forces the architectural fix the previous incident made optional. The buyers in this story are not the maintainers. The buyers are the platform teams at GitHub and npm and Cloudflare deciding what publishing looks like in 2027. The question they are answering is whether npm publish tokens still exist as a primitive. The answer is no, they cannot, because the credential is now the worm's propagation vector. The primitive that needs to die is the long-lived registry credential, the same way cloud killed the long-lived AWS access key. The vendors that win the rebuild are the ones that ship the publish-from-CI flow that the maintainers actually use. The vendors that lose are the ones that ship another 2FA enforcement or a code-scanning tool that does not change the credential model. The credential model is the bug. Everything else is incident response. The lesson is not be more careful with npm. The lesson is do not ship a credential to a place a worm can read it. That lesson came to the cloud in 2018. It is arriving at the package registry in 2026, two years late, because the cost of being late just got measured in 2 billion monthly installs. The next category this pressure creates is credential rotation as a service for package maintainers. The maintainer is the customer. The credential is the product. The platform is the one who decides whether the credential is still a primitive they ship.

• 
  AgentFi.News (@AgentFiNews) reported 29 minutes ago

  Cloudflare just launched programmable wallets designed for agents, with native x402 support, stable identities, and spending controls. Agents get virtual wallets with explicit limits, while humans retain oversight through account level guardrails. This is a practical step toward controlled autonomy in AgentFi, agents that can pay for services without unrestricted access to capital.

• 
  Nico Botha (@nwbotha) reported 38 minutes ago

  @_andypeacock @flueai Yeah from what I understand is that eve and flue are quite similar - a framework that allows you to build and deploy custom agents Eve is tailored for Vercel from what I know. Flue supports more platforms because its built on vite. And it has good support for Cloudflare, that’s why I picked it But tbh, I haven’t looked into eve yet so I might be wrong about some things

• 
  Xeer (@Xeer) reported 39 minutes ago

  @santi_ @Cloudflare Ahhhhhhh too slow

• 
  D. Mario  (@dev_mario) reported 41 minutes ago

  Successfully migrated my websites on Vercel along with the Storages and DB to Cloudflare + my Coolify VPS only by telling Grok 4.5 to migrate it. The only problem is that some environment variables are set as sensitive, so when it moved to Coolify their values became [Sensitive] and I had to fix them manually. Secret environment variable might be secure, but it's also somehow troublesome.

• 
  Han-Hsun Liu (@nakolus) reported 41 minutes ago

  Been experimenting with Cloudflare Containers in local development (`wrangler dev`) as part of a Turborepo setup. I recorded this because I wanted to see the whole flow, not just the end result. The video starts with no running containers. When the dashboard calls the Python PDF endpoint, two containers come up: `cloudflare/proxy-everything` and my Python PDF service. The request completes, and the generated PDF is returned. I kept the container window open on the side to capture the container lifecycle alongside the request. It’s fun watching everything come together.

• 
  Dee (@ODee87) reported 42 minutes ago

  @Upwork It seems this is a constant issue for people. I still can't login so lost that person to hire. Also need to manage existing contracts but cannot login. Why on earth are you not just using global Cloudflare security turnstile? Why are you rocking your own IP blocker that is stupid

• 
  Armin Ronacher ⇌ (@mitsuhiko) reported 43 minutes ago

  @dok2001 I think it would be good if someone from the team does some updated comms on rust support. I know that rust is alive and well within cloudflare, but on workers it feels neglected :(

• 
  LilRhodySpecial (@rhody_special) reported 43 minutes ago

  @Cloudflare The MoQ relay architecture concentrates massive amounts of metadata collection capability in a single corp. Surveillance surface: control plane logs, connection metadata, token management audit trails, and cross-service correlation @RealAlexJones the Catch all almost complete

• 
  science roach (@darthroach_) reported 43 minutes ago

  @CapybaraFortune well no it's a joke about a cloudflare outage because they famously use 90ish lava lamps for encryption lmao

• 
  EzQ (@__EzX__) reported 45 minutes ago

  @eastdakota @yusukebe @Cloudflare Please fix workers AI now they are unusable

• 
  Turbo Monkey (@graycode007) reported 45 minutes ago

  Summary: Trouble Will Find You: How Cloudflare Scales Using ClickHouse Key Topics Scaling philosophies and "trouble" ClickHouse architecture and implementation Resilience through data center failures High-scale telemetry and query performance Main Points Scaling should be viewed as a continuous process of moving from one milestone to another rather than a static state of being. "Trouble" in a distributed system is defined as unexpected, high-frequency scale-downs, such as losing half of a system's capacity, which is functionally similar to a sudden doubling of load. Cloudflare utilizes the open-source version of ClickHouse exclusively to manage massive event pipelines, handling datasets as large as 61 quadrillion events per day. The system is designed to be resilient to major regional outages; even when an entire continent's data centers are disconnected, queries can still return accurate results with a low margin of error by leveraging remaining global nodes. ClickHouse's architecture allows for "soft clusters," providing flexibility to interrogate specific combinations of nodes and maintain responsiveness (under two seconds) even during degraded states. Key technical advantages of ClickHouse for Cloudflare include the universality of the HTTP protocol, minimal coordination requirements compared to protocols like Raft or Paxos, and the ability to use MergeTree engines to combine ingestion and indexing. Engineers should proactively test systems by simulating 10x or 100x growth, as well as simulating a 90% loss in capacity, to determine if they fail gracefully or catastrophically. Notable Quotes "Scaling is a process and not a state you can be in." "You can think of trouble or or problems as like an unexpected uh high frequency scale down, right?" "If you lose half your capacity, it's kind of the same thing as doubling the load, right?" "It's never too early and it's never too late. You never be done." Conclusion Cloudflare achieves massive scale and high availability by using ClickHouse to build a resilient, responsive telemetry system that treats hardware and regional failures as expected occurrences. The ultimate goal for engineers is to design systems that can handle both massive surges in demand and significant sudden losses in capacity without total failure.

• 
  Magnus (@MagNornsX) reported 47 minutes ago

  @Grok Both the website and mobile app are currently unavailable. The website shows Cloudflare Error 522 (Host Error) at 07:39 UTC on Aug 4, 2026. Other services are working normally, and the issue persists across devices. Please investigate.

• 
  Titas Mallick (@titasmallick51) reported 47 minutes ago

  Cloudflare blocks or challenges bad requests from hitting my website. #cloudflare

• 
  Nils Groove (@nilsgroove) reported 48 minutes ago

  Don’t use that stack. That whole list is pure AI-generated BS. No way that guy actually uses every single one of those tools on real apps. You only need @Cloudflare. That’s it. The list is usually the typical suggestion when you ask AI what stack or tools to use. You can keep Next.js. That’s fine. Just do this instead. Host it on Cloudflare Pages and Workers. Vercel is great until the bill shows up or someone in Asia tries to load your site. Cloudflare runs on a real global network, gives you unlimited bandwidth for free, and doesn’t punish you when traffic spikes. The OpenNext adapter makes Next.js work just as smoothly. Ditch Convex. Use Cloudflare D1. It’s a simple SQLite database that lives right on the edge next to your code. No extra service, no weird pricing, no waiting for some third-party backend to wake up. Reads are fast everywhere and the free tier is actually usable. Auth can stay Clerk if you really want the pretty UI. Or just run Better Auth on Workers with D1. Either way you stop adding another paid tool that scales with users. Emails? Forget Resend. Cloudflare’s own Email Service lets you send and receive straight from your Worker. No extra API keys, no separate dashboard, no monthly surprise. Keep Stripe and Tailwind. Those two are solid. Everything else on that original list is just AI padding. The result is one platform instead of five. Cheaper, faster for people outside the US, and you don’t have to babysit a pile of free tiers that suddenly start charging. This is the stack that actually survives past the first hundred users.

• 
  rohin (@rohinlohe) reported 52 minutes ago

  The agentic commerce marketplace needs a healthy supply of buyers and sellers. Our Monetization Gateway is bringing impressive sellers online. Wallets enables quality buyers. Cloudflare Wallets will help buyers present a stable identity to sellers, building trust in the market

• 
  Tyler (@TylerChud) reported 55 minutes ago

  @AgeOfInversion Leonarda Jonie frequently calls for violence But if i even insinuate violence My post or reply is deleted and im stuck in a Cloudflare login loop

• 
  Rylai ʚ♡ɞ (@Rylaiqt) reported 58 minutes ago

  @Suzululua I never like CAPTCHA I have to actually like solve, its always just a cloudflare verification LOL. I wonder if its cuz Im always on here /ᐠ ˵> ⩊ <˵マ

• 
  Michał Piszczek (@cdiamond) reported 60 minutes ago

  @Cloudflare stablecoins have no chargeback. wrong address, agent approved, done. that's the support ticket nobody wants

• 
  Melek Turkoglu - Ekrem İmamoğlu’nu Serbest Bırakın (@AvukatMeleknur) reported 1 hour ago

  @certbund We need urgent assistance regarding active financial cybercrime hosted on a German network. @Hetzner_Online claims under Ticket [AbuseID:1200CC6:30] that they do not host the reported phishing target. However, Cloudflare officially identified Hetzner as the active origin server.

• 
  Carla Alvarez - Raised to Walk (@RaisedtoWalk) reported 1 hour ago

  And just fyi, this is the same jackass that hacked my Cloudflare account, changed all the login information, and then the losers were sabotaging my email and subomains

• 
  David Gold (@_david_gold) reported 1 hour ago

  every other part of infrastructure already does this. cloudflare, aws, github all publish real postmortems after a serious incident. not as punishment, it's how the rest of the field learns what to defend against. agent incidents get a summary instead. the details that would actually help someone else harden their setup stay inside