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 (30%)
• Domains (30%)
• Web Tools (17%)
• Hosting (13%)
• E-mail (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:

• 
  NeilXbt (@neil_xbt) reported 48 seconds ago

  Miguel, CTO of camelAI, describes rebuilding their agent's entire execution model to get off virtual machines, moving it into a Cloudflare Durable Object and swapping bash for JavaScript! > The original Claude Code harness required a full VM per user, which was too expensive to scale with always-on machines and attached disk > Step one moved the agent's "brain" into a Durable Object while VMs stayed as remote "hands," which fixed latency but not cost > Step two replaced the VM filesystem entirely with Durable Object SQLite plus R2 for larger files, using Cloudflare's Shell project > Step three removed bash completely, replacing it with JavaScript run through Code Mode in fresh V8 isolates that boot in milliseconds > Credentials never enter the sandbox; the agent calls pre-loaded connection methods and authentication happens server-side > Builds and Python notebooks still run in short-lived containers, since those genuinely need Linux > Cheaper models perform noticeably better with a narrower, explicit method set than with open-ended bash access The result: thousands of executions now cost about what a few minutes of container time used to. Bookmark so you do not lose it! Follow @neil_xbt for more breakdowns of how teams are architecting AI agents for real scale.

• 
  Gabe Fletcher (@gabefletcher) reported 2 minutes ago

  picks up phone dials 1800 @Cloudflare yeah hi. could you please fix the gateway for MCP authing, its currently more dead than a day 30 day old vibe coder and cant auth anything. okthx

• 
  Ben Badejo (@BenjaminBadejo) reported 3 minutes ago

  If you are debugging something that involves networking for hours and you don’t check for outages/maintenance from Cloudflare / AWS and so forth…you’re gonna have a bad time. Sometimes, the problem isn’t you. It’s them. 🙃

• 
  a_skin2 🔺 (@a_skin2) reported 5 minutes ago

  The Avax C-Chain API on @KoinlyOfficial seems to be malfunctioning (Cloudflare 502). Won't let me sync my txs since July 10. This is affecting my oldest wallet, the other ones seem to be working to some extent (missing ERC-20 txs and only tracking avax txs). Is anyone experiencing the same issue?

• 
  EzQ (@__EzX__) reported 5 minutes ago

  @Cloudflare Please fix your eth gateway first

• 
  Onyx_Digital (@OnyxAudit) reported 7 minutes ago

  Spent 2 hours reverse engineering Cloudflare. Downloaded pages. Compared MD5s. Diffed HTML. Inspected __CF$cv$params. Compared cf-ray headers. Trying to figure out why Cloudflare was returning: Cloudflare Ray ID: 000000000000000 Your IP: 0.0.0.0 Root cause: $ protonvpn disconnect Site loaded immediately. I have become the Layer 8 problem. @ProtonVPN @theXSSrat I definitely need to join your classes.

• 
  flavio (@flaviocopes) reported 9 minutes ago

  @dnnskr91 Yeah but I’m doing all on Cloudflare these days from domain to compute and database for new apps so not an issue for me rn

• 
  arsh  NAmen (@arshgoyal13) reported 14 minutes ago

  there's about 50 people across 3 reddit posts and my tweets (that I've found) for whom this issue is happening, because they're in NorCal using AT&T Fiber cloudflare warp or a VPN both work as solutions FINALLY I CAN PLAY RANKED SOLO DUO. MY CRACK IS BACK.

• 
  Klaus Arent (@klausarent) reported 17 minutes ago

  Cloudflare returned error 7003. The message reads like a permissions problem, so that is what my agent debugged: it rotated the API token, widened the scope, checked the account id, and came back twenty minutes later with a token that had more rights and the same error. The actual cause was one character in the path. I had written dns/records where the API expects dns_records. A malformed path produced an error that described a credential problem. An error message is a hypothesis written by someone who could not see your bug. Agents treat it as a diagnosis, because it arrives in the authoritative position: last thing printed, right after the failure. The ordering that fixed this for me: 1. verify the request itself against the current docs 2. reproduce with one known-good call to the same host 3. only then touch credentials Credentials are the most expensive thing to change and the easiest thing to blame. Any error that suggests you widen access deserves the request checked first.

• 
  Mila Chervenkova 🍩 (@MilaChervenkova) reported 25 minutes ago

  @_maxantonov @GoDaddy @Cloudflare I use NameCheap and I am super happy with their support.

• 
  GrainStats 🌾 (@GrainStats) reported 30 minutes ago

  @HTSCommodities @bfl_ai @NousResearch anything is possible right now i'm betting on agentic flows being monetized. there is a market for this, it will take time, but it will get done. that and IP rights being monetized (e.g. buy my chart, limited to 100 views) most of our traffic is bots these days anyway...maybe charge them a nickel per visit? surely cheaper than burning tokens for no reason no doubt in my mind that *everything* and i mean everything of value will be paywalled and locked down in the next few years (also thesis to long Cloudflare)

• 
  Mihai Lucian Tudor (@TudorML) reported 32 minutes ago

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

• 
  Ryzm (@Goeun_6121) reported 32 minutes ago

  52% of identified crawler requests were for AI training. More than 36% came from mixed-use bots. That second bucket may be the harder business problem. The same crawler can train a model, feed search and help an agent act. Those jobs don't create the same value. Cloudflare can price the request. Pricing the intent behind it is still unresolved. For a small publisher, this shifts the moat from archive size to update frequency. Rates, inventory or regulation can make yesterday's answer stale by morning, giving the bot a reason to return. The shortest shelf life may carry the highest crawl price.

• 
  rohin (@rohinlohe) reported 32 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

• 
  Patrik Tang (@_patriktang) reported 34 minutes ago

  @anupamrjp Started on AWS, realised it sucks. Cloudflare all the way.

• 
  MarkQuarter (@MarkQuarter) reported 35 minutes ago

  @kit_sats @JWWeatherman_ There are other complicated factors: JW is completely right about all the scams With COLD CARD: can be: A. Inside Job B. Accident C. Undetected, complex entropy down grade attack or similar Finance Infrastructure gets tons of attacks 24/7 -- this will hopefully lead to better Practices to prevent that & better Quantum Safe Tech for both $BTC & Traditional Finance: because as is bitcoin is working on Quantum Safe: however neither Finance Infrastructure or some Blockchains are Quantum Safe yet [ note: bitcoin uses 256 bit elliptic curve cryptography ---- while 256 bit AES is not breakable by the near future Quantum: the 256 bit elliptic is breakable in the future, possibly early 2030s, so bitcoin is upgrading It's not as simple as either: Coding or the User trying to make a complicated enough Wallet or Seed : One of the continuous defense necessities is from those Entropy Downgrade Attacks ] Then: you got some of those Exchange Scams or other Insider Scams incentivized by undetected attacks as well: that's with... from $GOOGL: "Automated and Global Threat Volumes 600 million+ daily signals: Major tech platforms like Microsoft intercept and block hundreds of millions of automated global malware, botnet, and phishing attempts daily Billions of web blocks: Large cloud and security infrastructure providers like Cloudflare routinely filter out tens to hundreds of billions of hostile background scans and suspicious connection requests across the broader internet daily" So: some of the "Scams" can be more complicated than they appear : far better 24/7 defense for Infrastructure is needed As of yet COLD CARD doesn't appear to be Inside Job.. & regardless it strongly appears there will be some attention on & following of that bitcoin to find out who hacked it ... unfortunately as it is though Recovery , in practice is not such a perfected process: However hopefully it is possible & is done with the COLD CARD attack

• 
  Aiden (@WallisDev) reported 41 minutes ago

  Wait does cloudflare not support custom domains for preview deployments? Wtf lol

• 
  Blake Whittle (@BlakeWhittle7) reported 42 minutes ago

  @KristenSousa I have several 16GB servers that run 55 (~200-500 views per day) sites, and that’s about the ceiling give or take, so yeah a 2GB server with 1 site with minimal traffic can handle it no problem. Most important things are: 1. Use lightning stack 2. Turn on CRON Optimizer 3. Use cloudflare with Chinese bots blocked

• 
  Pete Stewart (@pj_stew) reported 42 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 👇

• 
  utopiaken (@utopiaken76) reported 43 minutes ago

  @JeffKazzee Could you help to teach me what is the steps to setup Cloudflare free AI models into my Zo Computer? I try and error many times, but it still didn't work. :(

• 
  Turbo Monkey (@graycode007) reported 44 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.

• 
  WIV Reports — Uncensored (@WIVReports) reported 45 minutes ago

  Any first-year network engineer knows the playbook: see a 429 with a CF-Ray ID, log into the Cloudflare dashboard, check the WAF/Rate Limiting logs for that ray ID, and adjust the rule. It’s literally a 2-minute fix. Instead, they insisted Cloudflare wasn't blocking anything, claimed DevTools were wrong, and issued a partial refund rather than taking 120 seconds to look at their edge logs. Pure laziness.

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

  @e_kaspersky Cloudflare Workers and GitHub Pages as scam hosting works because the trust signal is domain reputation, not content review.

• 
  Dane Knecht 🦭 (@dok2001) reported 46 minutes ago

  Twice in nine days. OpenAI's models chained a zero-day to get out of an eval environment. Anthropic just found three incidents of the same shape. This is what capable models do. Every reachable path is an invitation. Credit to both for publishing. We rebuilt Cloudflare OS, our internal agent platform, assuming exactly this. Sandboxes have no network path out. Agents don't get every MCP tool up front, each workspace gets only what it needs. And instead of stopping for every approval until someone gives up and enables auto-approve, the platform simulates pending actions so the agent keeps working, then queues the real ones for review at the end. The app side goes further. Apps carry no auth code at all, the sandbox provides it, so there is no auth logic to get wrong. Multi-document apps are isolated per document, so a bug can't leak between separately shared items. Anyone viewing an app must have direct permission to each of its data sources, so a dashboard on sensitive data can't overshare. Actions need the user's own permission or an approval from someone who has it, so an app can't escalate its author's privileges. And everything an app does is logged, even when the service it calls doesn't support logging. Most companies are about to point agents at real systems. Build for what the models actually do. We will open source this next week!

• 
  Anıl Soylu (@anilsoylu) reported 53 minutes ago

  @MarkDGeorge @Cloudflare I don’t think so. They’re clearly abusing Cloudflare’s systems. Hopefully, Cloudflare fixes this issue soon.

• 
  WIV Reports — Uncensored (@WIVReports) reported 54 minutes ago

  There is no greater love than Christian hate. Gab, a company that constantly preaches its "Christian values" responds to a long term paying customer with pure disdain the second they get called out on technical incompetence. After dropping slurs and throwing a tantrum over standard DevTools logs, their CTO sent this email and immediately blocked my account on Gab so I couldn't reply. I am also sharing the email notification I received. Here is the full timeline of how Gab handles paying subscribers reporting a legitimate bug: 1: Socket io connections failed and looped infinitely, triggering a Cloudflare 429 Too Many Requests status code at their edge. 2: Support claimed a Cloudflare 429 signed by Cloudflare IPs was an issue with my "home Wi-Fi." A VPN on that same Wi-Fi instantly bypassed it, proving it was a server-side edge filter. 3: Instead of checking their WAF rules, their CTO claimed checking origin logs for 6 hours was "VIP treatment," accused me of using AI, and threw a fit. 4: I deleted my gab ai account, posted the DevTools receipts, and told him to fix his edge. 5: He sent a profanity-laden, slur-filled email, blocked me on the platform, and tried to hide it. Never once did I name-call or throw insults, I just posted raw HTTP response headers. This is how Gab treats the people who keep their lights on. Absolute amateur hour You can see the entire unfolding here on my X account, as I posted everything said verbatim. And again, here are the screenshots of the HTTP responses showing the issue is on them.

• 
  MAULIK MANDALI (@AnalogPvt) reported 54 minutes ago

  @michellechen @OpenRouter @kevin_flansburg {"errors":[{"message":"AiError: Ai: This account is not allowed to access this model. (c4747cae-bcf3-4c29-b867-48f3eab4d97f)","code":5018}],"{}","messages":[]} (Tested with: Cloudflare | deepseek/deepseek-v4-flash-20260731)

• 
  Adam Thyer (@AdamThyer) reported 54 minutes ago

  @Cloudflare Your pace and quality of innovation is impressive. We're about to go all in with CloudFlare. Please, never pivot to a high cost high margin model!

• 
  Benjamin Shelton (@zancarius) reported 56 minutes ago

  @kwrob24 Yeah... I have most of my blogs behind Cloudflare specifically for this reason, but for historical (read: lazy) reasons, this instance lives on a domain I use for a *lot* of personal projects and home-lab-esque sort of things, even if most of it has been migrate to cloud services. It's not really a huge problem, and it's not (yet) consuming a bunch of egress traffic. But, this isn't the first time I've had issues with AI-related crawlers. I may be forced to move this to another domain at some point.

• 
  John (@johncalhooon) reported 59 minutes ago

  Interesting, no BSV, only EVM chains. Might have to cook a wrapped USDC/USDT on $BSV Then send github issue to Cloudflare repo.