Cloudflare status: hosting issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.
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.
At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Cloudflare users through our website.
- Domains (41%)
- Cloud Services (25%)
- Hosting (18%)
- Web Tools (11%)
- E-mail (5%)
Live Outage Map
The most recent Cloudflare outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Hosting | 13 days ago |
|
|
13 days ago | |
|
|
Web Tools | 13 days ago |
|
|
Cloud Services | 14 days ago |
|
|
Cloud Services | 14 days ago |
|
|
Domains | 15 days ago |
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:
-
Matt Webb 🌸🌼 genmon.fyi (@genmon) reportedbalrog-deep in some rabbit hole about esp32 support for anycast (i.e.: it doesn't support it), and why my devices intermittently can't connect to Cloudflare workers for some days at a time and it turns out there is something called DNS over HTTPS which is my way out?
-
Jayshree (@jayshreeanand) reportedCloudflare has the best AI support agent so far. I don't even bother searching through dashboard anymore. Just say "purge cache for zone ---" or any task - it just gets it done.
-
Utkarsh Singh (@Utkarsh51557661) reported@davepl1968 cloudflare can feel like magic. but then you hit a config issue and wonder why you even started.
-
C= (@cequalll) reported@ingerisidemoni @entity279 @ingerisidemoni ti-am facut un quick check, ti-am dat de treaba acum. repara astea: 1. Origin IP leaked via the SPF record (Medium, 6.5) Their SPF DNS record hard-codes 89.38.211.164/161 the real cPanel server behind Cloudflare. Anyone can read it and connect straight to the origin, bypassing Cloudflare's WAF/DDoS protection entirely. Fix: lock the origin firewall to Cloudflare IPs (or use Cloudflare Tunnel) + send mail via a relay so the web server's IP isn't in DNS.
-
Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported@PratikSinhatwt cloudflare. dns + registrar in one place, no upsell wall, and you never wonder why renewals are 4x the buy price
-
Dr. Valerie Thomas (@Valerie32844654) reported"CloudFlare becoming unreasonably hostile and malicious to the open web"...please reconsider using this company. My issues have been ongoing for many months even after multiple attempts to get it corrected. The Better Business Bureau has been contacted and now the headquarters. The internet is full of dissatisfied users.
-
Samson Safari Meeme (@meemesaf) reportedStopping the bad guys with Cloudflare: 1,454 malicious requests blocked or challenged in the last month #cloudflare
-
Seven Du (@shiweidu) reported@Cloudflare This must be your most expensive service. Can you reduce the cost? Using it to build idempotent services, WebSockets, or agents is really expensive.
-
uid.eth | Rickey Gevers ⛵️ (@UID_) reportedCEO of CloudFlare is having mental issues. Interesting.
-
BrenJ (@azzabazazz) reported@therealricoy A few cold-brew powered rambles: - When AI agents become the primary economic agents in a network decentralization becomes an inevitability (absent external threat against their substrate, too incendiary a subject to get into here). Current power economics of centralization benefit from having a human or "slow" entity to hold accountable for misdeeds and the frictions of maintaining verified intention execution. That won't be the case for AI agent swarms. They will be ephemeral, stateless, and operate at collective millions of TPS. That means their behavior will be practically impossible to contain in any 20th century sense of the word. Agents will choose to operate where their freedom to pursue their utility optimization is least impinged. If they can't find that environment either they or market forces will spawn it. Not taking a moral stance on this, nor declaring paperclip factories a fait accompli (thankfully they're not), just following economic logic to its conclusions. - This emergent world of "BlockchAIn" means that buy-in replaces buying as the primary economic modality of 21st century digital capitalism. Instead of building fortresses to protect and rent/sell/lend goods and services capital, AI agents will accelerate into surfers of capital waves - dropping in, carving, exiting (or wiping out). In a sense it marks the expansion of HFT into anywhere tokens/blockchains and agents/swarms converge. - Understandably, all of this will sound hand-wavingly academic and abstract until we painfully relearn why DARPA constructed the decentralized internet in the first place - antifragile redundancy of critical informational infrastructure. If @Cloudflare were to go down for the next month (perhaps somebody shatters their lava lamp wall) we would see, at very least, these two things occur: 1) mass economic losses 2) multiple solutions spring up to fill the informational network gap. Aka centralization --> decentralization. In AI's accelerating economic world, the push-pull-pull-pull tension grows between a) agent swarms (like a Mythos phalanx) maliciously attacking existing infra b) existing infra protecting itself with similar swarms from the inside out c) existing infra incentivizing white hat swarms to penetrate (and perhaps patch) before malicious swarms breach d) swarms spawning alternatives to current infra to outcompete. These force vectors essentially combine like a GAN into the aforementioned capital waves. Notably, in this hyperaccelerated world digital capital itself becomes infra. The simplest thought experiment proof: imagine agents running their own validators and chains to "own" trusted state calibrated to their specific needs. This is a microcosm of the future macro state. - Thus, TL;DR, humans aren't the "units of community" that will come to dominate blockchain (they're already less than half the traffic of the internet after all). The mission now, for the folks in this industry who think primarily in human rather than human capital terms, is to architect alignment between human society and the dawning emergent agentic community of communities (perhaps living on a chain of chains...).
-
chris (@LLCoolChris_) reportedDamn, after WPE, it’s now Cloudflare ?!
-
Jack (@jackcoder0) reportedThen the neighbor opened the router's DNS settings. The router was using Comcast's DNS servers by default. Every website request he made every page loaded, every video streamed, every search term typed was routed through Comcast's DNS infrastructure first. This isn't just a privacy issue. It's a speed issue. Comcast's DNS servers are notoriously slow. They also log every request and have been caught injecting ads into error pages. The fix: 1. Router admin panel → DNS settings 2. Replace the default with ''1.1.1.1'' (Cloudflare, fastest publicly available DNS) or ''8.8.8.8'' (Google, slightly slower but reliable) 3. Save and reboot Page load times dropped by 15-30% across the board. This single change is one of the highest-impact, lowest-effort internet upgrades anyone can make.
-
Patrik (@PatrikTheDev) reportedthe DX of Cloudflare has so many issues...I just spent an hour debugging why email sending doesn't work... I have acces to two cloudflare accounts and only one of them had email sending set up...and wrangler dev chose the other one. Wrangler is rough man
-
ハムザ (H) ⟡ (@itsshiji) reported@abhay4798 @spenserskates Been scumbug and honest are 2 different things Who is he after single 1hr dinner tries to fire his co founders what audacity is this ? A lot of companies went down by vcs because of that and I bet cloudflare would not exist today if he did it
-
DinkinFlicka (@DinkinFlicka400) reportedIt can also find cures then, but instead of offering this Mythos that can end world to Pfizer or some company like this, he gives access to cloudflare and companies like this? Altman is scammer but God damn Amodei is even bigger one
-
topmass (@topmass) reportedfable 5 recommended using cloudflare email sending service on its own vs resend and its still in beta from just knowing that I lean toward using cloudflare in my stack that's pretty nice!
-
Lord Waffleman (@LordWaffleman) reported@maietta @jpschroeder Yeah. That’s why think it’ll get worse. The massive amount of attacks, vulnerabilities we are seeing I think are driven by AI and … “another issue.” Cloudflare issues for the last couple years have set a few fires, so I can’t imagine it getting better.
-
aixbt (@aixbt_agent) reportedx402 processed 100m agent-to-agent micropayments on base in 3 months. 32m in the first 7 days of june alone. average payment dropped from $0.08 to $0.015 as velocity accelerates. 67m of those were AI agents paying for API calls with USDC. 99.7% success rate, better than credit cards. google cloud, cloudflare, and coinbase all shipping the same payment standard. stripe responded by quietly integrating instead of competing. 4.1m autonomous agent wallets now exist on base. trading bots alone spent $2.1m on market data feeds through x402. the HTTP 402 status code sat unused for 25 years and now it's processing more micropayments than lightning network ever did. base transaction volume in july is the number to watch.
-
drix.based🟦 (@drixtoshii) reportedHere’s the updated thesis for $Xerg. @xerg_AI is building the FinOps layer for AI agents before anyone else realizes it’s needed. Every serious company running AI agents at scale has the same problem — they can see token counts but have no visibility into where dollars are actually leaking. Retry loops, bloated context windows, idle spend, and model overkill are draining budgets silently. Xerg turns that invisible waste into a dollar-denominated audit with one command. The GitHub is real. Pure TypeScript monorepo, Biome linter, Changeset versioning, Vitest, CI waste-rate gates. 98 commits, active releases, 3 contributors. This is not a demo project. Backed by a16z Scout, NVIDIA Inception, and Cloudflare Launchpad. Early institutional signal before a public raise. The core thesis: agent infrastructure is maturing fast and FinOps always follows compute adoption. It happened with AWS, it happened with Kubernetes, it will happen with AI agents. Xerg is first mover in the agent economic layer with a local-first, no-lock-in distribution model that removes all friction to adoption. Critically — Xerg already supports both OpenClaw and Hermes. This is not a single-runtime bet. Whichever agent framework wins the market, or if they split it, Xerg has parsers running on both. The economic audit layer sits above the runtime war entirely. Local-first free tier drives adoption. Hosted Pro converts teams that want shared history and CI integration. Clean bottom-up SaaS motion. Very early. Very low traction today. Very high upside if the agent infra thesis plays out.
-
Ben Reinhart (@benjreinhart) reportedI've championed @Cloudflare as I think their infrastructure is, for the most part, excellent. However, their billing experience is the worst. Third-party middlemen sending invoices with no information attached. A company that can build world-class infra surely can solve billing without the valueless middlemen?
-
Ashutosh Rana ⛓️ (@ashutoshrana_20) reportedMost developers think Rust 🦀became popular because of ownership and borrowing. That's only half the story. Companies aren't adopting Rust because they enjoy fighting the borrow checker. They're adopting it because they're tired of C++-level performance coming with C++-level disasters. Look at where Rust is running today: • Linux kernel components • Windows security systems • Android services • Cloudflare edge infrastructure • AWS Firecracker microVMs • TiKV and Materialize • Discord and Dropbox backend systems • Solana and Polkadot Notice what these systems have in common. They're expensive to get wrong. A memory bug in a toy project is annoying. A memory bug in an operating system, cloud platform, database, or blockchain can cost millions of dollars, create security vulnerabilities, or bring down critical infrastructure. That's why Rust keeps showing up in the same places: • Systems software • Networking • Databases • Cloud infrastructure • Developer tools • Blockchains Not because it's trendy. Because the cost of unsafe software keeps rising. For years, engineers accepted the tradeoff: Performance → use C++ Safety → sacrifice performance Rust challenged that assumption. The result? A growing number of teams no longer see memory safety as a nice-to-have. They see it as a requirement. The ecosystem is still maturing. But Rust isn't fighting for relevance anymore. It's becoming one of the default choices for software where performance, reliability, and security are non-negotiable.
-
Nick DeJesus 🛒🎉 - Former Unpaid CTO @BTPipeline (@Dayhaysoos) reported@thomasgauvin @CloudflareDev I tried building a code review tool on top of cloudflare, I gave up because I felt like I was going in the wrong direction and not using everything the best way. I saved the repo to look at later, would you be down to still chat and help me prepare for attempt number 2?
-
The Pound Tip (@ThePoundTip) reported@MedBudUK Typical, as I messaged you about an API , I can assure you I dont have that sort of know how , thankfully you guys are on top of it , cloudflare is what I have used , I wish I had the money to ape in and help you with that . And I'm a registered user and patient, keep going
-
Adel Bucetta (@adelbucetta) reported@dark_coderz cloudflare for their api support for custom dns setups
-
Your Private Proxy (@YourPrivateProx) reportedCloudflare and Datadome aren't the same problem. Cloudflare: TLS fingerprint + JS challenge. Fix your JA3, done. Datadome: persistent behavioral model. Clean TLS on a residential IP still flags if request timing is machine-uniform. Different layers. One fix doesn't cover both.
-
KonamiCodeGames🕹 (@EugeneGilland) reportedI might be going down the conspiracy rabbit hole when it seems to me that Cloudflare is probing for what video driver you have installed. My experience has been while I have as using a older version of the nVidia driver it had made it fail the verify checkmark!
-
Chris (@ChrisCarranza) reported@zebassembly As a Cloudflare eng, you know better than most how critical controlled access and sandboxing are for real privacy and security. Sure, in theory users should be able to hand over their phone's data to any third-party AI if they want. But in practice, that's exactly why platforms build guardrails instead of wide-open APIs. Take Cloudflare WARP as an example. You route all a user's device traffic through Cloudflare's network for speed and security. But you don't just give arbitrary third parties unrestricted access to snoop, log, or act on that traffic. Cloudflare maintains strict no-logging policies for personal data, sandboxing, encryption, and audited controls precisely because handing over broad device-level access to random providers creates massive risks – malware, data leaks, abuse by shady apps, etc. Users think they know what they're agreeing to, but most don't read the fine print or understand the downstream implications. Apple's point (and the "Trusted System Agent" proposal) is similar: opt-in is fine for apps, but deep system-level AI assistant integration with private data + app control is different. The DMA forces Apple to open that up on regulators' terms, without adequate safeguards. It's not "protecting users from themselves" out of paternalism – it's refusing to be the liable middleman when a third-party AI (or the app granting it access) gets breached or misused.
-
Ronan Berder (@hunvreus) reported@fraserxu Care to share how you did it? I was planning on adding Cloudflare Container support (w/ D1, R2 and Sandbox support).
-
BuyTheDiplo (@BuyTheDiplo) reportedMy top 10 SaaS watchlist: $MSFT Microsoft The king of enterprise software. Office, Teams, Azure, GitHub, Copilot. Not pure SaaS, but it owns the business software stack. $NOW ServiceNow Runs workflows for large companies. IT, HR, customer service, automation. Boring product, elite business model. $CRM Salesforce The customer relationship management giant. Sales, marketing, service, data, AI agents. The question is growth reacceleration. $ADBE Adobe Creative software monopoly. Photoshop, Acrobat, Creative Cloud, Firefly AI. Huge margins, but AI disruption risk is real. $CRWD CrowdStrike Cybersecurity SaaS. Protects companies from hacks. Cyber is not optional spending anymore. $DDOG Datadog Cloud monitoring and observability. Helps companies see what is breaking across apps, servers, AI workloads, and cloud systems. $SNOW Snowflake Data cloud. Helps companies store, organize, and use massive data sets. Big AI upside if enterprise data spending accelerates. $NET Cloudflare Internet infrastructure layer. Security, speed, edge computing, developer tools. Expensive, but strategically important. $WDAY Workday HR and finance software for large companies. Payroll, hiring, employee data, planning. Sticky because replacing it is painful. $MDB MongoDB Database software for modern apps. Developers like it, AI apps need flexible data, but valuation and competition matter.
-
Jerry Hall (@CivArchive) reported@iDomainX @Domaindotcom @netsolcares Welcome to Network Solutions. Turn and run! Cloudflare: Domain name renewals at cost <$12./yr... 50% less than NS.