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.

• Domains (42%)
• Cloud Services (24%)
• Hosting (18%)
• Web Tools (11%)
• E-mail (4%)

Live Outage Map

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

City	Problem Type	Report Time
Noida	Hosting	10 days ago
Jewar	E-mail	10 days ago
Braga	Web Tools	10 days ago
Noida	Cloud Services	11 days ago
Paris	Cloud Services	11 days ago
Prievidza	Domains	12 days 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:

• 
  vp.net (@vpnet_official) reported 5 minutes ago

  @rhody_special 2/ Cloudflare is dumb transport. Your traffic runs in an end-to-end encrypted tunnel inside that connection, so it proxies ciphertext, never your browsing destinations, and strips your IP before it reaches us. American or not, it can't hand over what it can't see.

• 
  Rohan Paul (@rohanpaul_ai) reported 11 minutes ago

  Bots have overtaken humans online, and the internet was never prepared for this. - bots generate 57.4% of worldwide HTML requests - humans at 42.6%. The biggest shift is economic: traffic can rise while monetizable human attention falls, which weakens CPM, CPC, conversion-rate models, and analytics built before this agent wave. Cloudflare measures bot traffic, not only agentic AI traffic, but AI agents are a major suspect because one user task can trigger thousands of machine visits. The old web assumed a human loaded a page, saw ads, clicked links, filled carts, and created signals that publishers, stores, and SaaS companies could price. AI agents break that model because they read pages on behalf of people while skipping the ad views, session time, and click behavior that funded the web.

• 
  Ben Reinhart (@benjreinhart) reported 13 minutes ago

  I'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?

• 
  0xcommunity (@spaceroo83) reported 14 minutes ago

  Cloudflare needs to go down on the weekend so people can have some rest from x

• 
  mega (@MegaMiyamori) reported 14 minutes ago

  Is cloudflare this bad on other browsers or is it just chrome?

• 
  J Filipe (@jrmromao) reported 17 minutes ago

  @giordanorandone You're right — it's already here. Uber, Cloudflare, Microsoft all capping token spend per developer. The problem is everyone's measuring consumption but nobody's measuring output per token. That's the missing metric.

• 
  Jack (@jackcoder0) reported 18 minutes ago

  The neighbor's final advice was the most actionable. He sat down and wrote out a list of 6 things every internet customer should do: 1. Turn off the public Xfinity hotspot (or your ISP's equivalent Spectrum, Optimum, and Cox all do this too) 2. Manually set your Wi-Fi channel instead of "Auto" 3. Disable QoS / Smart Network "optimization" features 4. Change your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8) 5. Buy your own modem and router, stop renting from the ISP 6. Test your speed with fast. com or speedtest. net using a non-ISP server, never trust your ISP's own speed test Total cost: $150-300 in equipment, paid back within a year. Total time: One afternoon of setup. Total impact: Often 2-5x improvement in real-world speeds. The customer went from paying $90/month for "fast" internet that crawled to paying $60/month for the same internet that finally worked.

• 
  Squatch (@PantsStanky) reported 19 minutes ago

  @ponetang @CryptoCulgin @grok I dint care about that bro. How many times has AWS gone down? X? Google Cloud? Cloudflare? AT&T? Verizon? Microsoft Services? Do we questiin thier value to everyday life? Nope. Ehtereum tbh does very simple things. Sui is very broad in its capabilities, much more technically capable. Ethereum does blockchain defi very well, that's about all. The world needs more than defi out of blockchain.

• 
  NTR of Pharaoh Khonshu Heru (@AtreyuBastian84) reported 20 minutes ago

  The number of AI agents and automated bots online has surpassed human activity, changing how the internet works. According to data from cybersecurity and network firms like Cloudflare and HUMAN Security, non-human entities now generate more global web traffic than real people.

• 
  Matthew Prince 🌥 (@eastdakota) reported 22 minutes ago

  Two of our worst VC stories: 1. A Sequoia partner passed on Cloudflare because he didn’t think a woman could lead a security infrastructure company. Seriously. 🙄 2. I got introduced to @pmarca. Meeting got scheduled for a Monday, which should have been a clue. I thought it was just a casual meeting. He thought it was a pitch and brought the whole @a16z partnership team. Hilarity ensued. 🤪 At one point one of them said: “You don’t seem very prepared.” Which was true because I wasn’t. I framed the rejection letter they sent.

• 
  Jean (@JohnStrongHodl) reported 22 minutes ago

  @sal_ash_ ok, will try, but as a fellow dev: it won't help preventing scraping unless you have some guard in place (maybe Cloudflare, would be better to ask AI) nor bots now onto checking out your tool, cheers

• 
  Andrew Rulnick (@MickeySteamboat) reported 26 minutes ago

  50/50 it's cloudflare and clawbot related. how much do you want to bet? can't wait to get the post-mortem on this attack. Might be an hour, hang tight.

• 
  Ryan Kubanka (@Ryan_Kubanka) reported 27 minutes ago

  So basically: 1. Pay to crawl is the future 2. Authenticity will win. Double down on it in every way you can 3. Bullish CloudFlare

• 
  Steve Krouse (@stevekrouse) reported 31 minutes ago

  "Codex Sites" is literally just the Cloudflare plugin in a trenchcoat It solves exactly 1 problem: creating your own Cloudflare account If only there were a protocol to let agents create their own accounts or pay for things... Oh wait! Stripe Projects and x402. I am so excited for the world to come when these protocols win, and all software is composable with every other software, and we don't have to build wrappers or marketplaces or integrations by hand any more

• 
  Jack (@jackvebo) reported 33 minutes ago

  @PegasusPS5 Akia is not support it says now. Also you need to manually check the cloudflare

• 
  School Reading List (@SchoolReading) reported 37 minutes ago

  @Cloudflare @CloudflareHelp @awscloud We've also referred to the same issue in Case #02165422

• 
  psankar (@psankar) reported 39 minutes ago

  Hetzner OVH offer bare metal servers but their VPS suffer the same perf issues still cheaper than the three big players. Cloudflare went on a tangential serverless way and metered billing, ala heroku types that I am not a fan of. May be MetaCloud will build something appealing.

• 
  Tony Spiro (@tonyspiro) reported 39 minutes ago

  Cloudflare just bought VoidZero (the team behind Vite). The most important line in the announcement is not about the deal: "Developers used to be the only users of dev servers, bundlers, linters, formatters, and CLIs. That is no longer true: agents are using them too, constantly." Your dev tools have a second user now. It iterates 10x more than your engineers, reads errors literally, and needs consistent CLIs or it spirals. The stacks that win this year are the ones an agent can drive without a human in the loop. Fast feedback, clear errors, scriptable everything. Is your service agent-ready?

• 
  Vijay (@unk_data) reported 40 minutes ago

  @fit_fr_nothing So now I can do things like make a website generator and with "sign in with Cloudflare" I can host it on their Cloudflare pages? Cool.

• 
  OpinionEver (@opinionever) reported 41 minutes ago

  @MickamiousG I bet it connects to the internet. Stops working if Cloudflare has an outage. Bricks itself on firmware updates. Or if it is working it analyses your passings which you can view in an app, which it also sends back to the government if it detects drugs.

• 
  Miguel Borja (@closesim) reported 48 minutes ago

  After I realized the mistake, then the link sent me to the Google One page as normal (I always use right-click - Open Link). WTF. I'm currently using Cloudflare Family DoH on my network; how did this happen?

• 
  Anshuman Prasad Mahanta (@Anshuman_P_M) reported 50 minutes ago

  @kulkarni_ai @sidhant_sarthak Yes that's why Cloudflare hates Indian ISP for bad routing

• 
  ZOHEB THE DEV (@devheb) reported 51 minutes ago

  @threepointone @nevikashah Me when I login in with Cloudflare with Cloudflare

• 
  Nilmani Prashant (@NILMANIPRASHANT) reported 54 minutes ago

  Rate limiting isn't about blocking requests. It's about **protecting system invariants under adversarial load** — including your own code doing something stupid at 2am. --- **The precise definition most people skip:** A rate limiter is a policy enforcement mechanism that maps an identity (user, IP, API key, service) × resource (endpoint, DB, queue) × time window to an allowed request budget. Miss any of those three dimensions and your limiter is incomplete. --- **The five algorithms — and what they actually trade:** **Fixed Window** — simplest. Bucket resets on clock boundary. Problem: 2x burst at the seam. If your limit is 100 req/min, a client sends 100 at :59 and 100 at :01. You've served 200 in 2 seconds. This is how Cloudflare's early DDoS protection got punched through. **Sliding Window Log** — stores each request timestamp. Exact, no burst artifact. Cost: O(n) memory per user. At Stripe's API scale (~500M requests/day), storing per-request timestamps across even 1% of users is untenable without aggressive TTL management. **Sliding Window Counter** — approximation using two fixed windows weighted by overlap. Formula: `current_count + previous_count × ((window_size - elapsed) / window_size)`. Stripe uses this. ~0.003% error rate in practice. Memory: O(1) per user. **Token Bucket** — refill at constant rate, allow burst up to capacity. AWS API Gateway uses this. 10,000 req/s steady-state, 5,000 burst above that. Requests consume tokens; tokens refill at rate R. Good for bursty-but-average-bounded traffic. **Leaky Bucket** — requests queue, drain at fixed rate. Smooths output regardless of input shape. Netflix uses this on their Zuul edge layer to protect downstream microservices from thundering herd. Queue depth becomes your config ****. --- **Where this actually lives in distributed systems:** Local in-process: fast (~1μs), but worthless in a multi-node fleet. Node A doesn't know what Node B allowed. Centralized Redis: ~1-3ms round trip. Use Lua scripts for atomicity — `INCR` + `EXPIRE` in a single script. Redis's single-threaded command execution gives you linearizability for free. This is what most Stripe, GitHub, and Twilio rate limiters use at the storage layer. Gossip/eventually consistent: each node tracks local counts, syncs async. Allows ~N× over-serving where N = node count before sync. Acceptable for soft limits (analytics APIs), not for billing or security enforcement. --- **The senior engineer gotcha:** You set a 1000 req/min limit. Load test passes. You ship. Three months later, you get paged. Latency on your downstream DB is 40× normal. Your rate limiter is working perfectly — 1000 req/min per user, 10,000 users, that's 166 req/s aggregate, which was fine in testing with 100 users. **You rate-limited per identity but never modeled aggregate load.** The limiter protected individual users from themselves but said nothing about what your system can actually handle. You needed a global ceiling, not just per-user quotas. Google's SRE book calls this the difference between *demand-side limiting* (per user) and *supply-side limiting* (per resource). You need both. Stripe enforces per-API-key limits AND global concurrency limits per endpoint via a token bucket at the load balancer level. --- **When NOT to rate limit at the application layer:** If your bottleneck is CPU-bound work (ML inference, crypto ops), rate limiting requests doesn't help — you need a work queue with backpressure. If you rate limit, you'll drop valid requests while the remaining 10% still saturate your CPU. This is why Google's Bard/Gemini API uses quota + async job queues for expensive inference calls, not synchronous rate limiting alone. --- **Numbers worth memorizing:** Redis INCR throughput: ~100K ops/sec single node, ~1M/sec with clustering. Lua atomic script overhead: ~15% vs raw INCR. P99 latency on Redis rate-check in same-region AWS: 800μs–2ms. Sliding window counter error

• 
  Virtually Fun (@virtuallyfun) reported 55 minutes ago

  @OneCloudEmoji I got pissed when blogspot went down for a week, I'd been self hosting on wordpress for like 15 years now? A simple VPS + cloudflare and you're good to go. Plus you 100% own your content. I've moved hosts dozens of times, even at one point hosting at home with WSLv1 pptp'd to a VPS.. it's the best/most flexible. I'm tempted to move to a cellphone using usermode at some point, more so just because I can..

• 
  Abdulkadir | Cybersecurity (@cyber_razz) reported 57 minutes ago

  57% of internet traffic is now bots. The internet was built for humans. Humans are now the minority on it. Cloudflare blocked 416 billion AI bot requests since July last year. At website owners’ request. The CEO predicted this would happen in 2027. It happened this week. A single AI agent shopping for a camera visits thousands of websites. A human visits five. The web shrank from 2015 to 2025. Then AI agents arrived and inflated the traffic numbers back up. With nobody actually reading anything. Your website analytics are lying to you. Most of your visitors are not people. They never were.

• 
  Vladislav Kyslik (@VKyslik) reported 59 minutes ago

  @THBitcoinBuddha @Investanswers Some companies are already transitioning to post-quantum cryptography; e.g. Cloudflare has largely already made the shift. They don’t have a problem. The problem with BTC is that old addresses won’t be possible to migrate, which is why there are proposals like BIP361 or BIP360.

• 
  Bhargav Shivarthy (@bshivarthy) reported 59 minutes ago

  A lot of my internet habits still feel very human. I keep tabs open because I am afraid I will lose the thread. I send myself links I may never reopen. I reread the same page twice because I forgot why I came there. I ask someone, “do you remember where we saw that?” That is the web I grew up with. It was built for people trying to find, compare, remember, and decide. @eastdakota just pointed to Cloudflare Radar showing bot traffic passing human traffic for worldwide HTML requests. I think this is one of those moments we will point back to. Not because a line moved on a chart. Because the web started serving a new audience. Software is now a reader too. That can sound cold, but I do not think it has to be. Every time we scale an audience, we have to build new ways to support that audience. More readers means more surfaces, more formats, more infrastructure, more trust, more context. This is not zero sum. There will be uncertainty. There will be dislocations. Change always creates some discomfort before the new workflows feel obvious. But I do not think this means there is less to do. I think it means there is much more we can finally do. There are too many problems bottlenecked by attention, memory, monitoring, translation, coordination, and follow-through. Health needs more eyes on more signals. Science needs more ways to connect scattered work. Climate needs more systems that notice change early. Companies need better context. Governments need better feedback loops. People need tools that help them keep up. The next audience for the web will not only click and skim. It will watch, compare, trace, and act. That is going to change how information is published, structured, trusted, and maintained. Our 20s is not slowing down. If anything, it is just getting us warmed up.

• 
  Matteo Ricci (@MatteoRicciT) reported 60 minutes ago

  @CryptoThannos Cloudflare infra upgrade while price at support is actual alpha hiding in plain sight

• 
  replify (@replifyco) reported 1 hour ago

  🚨 THE INTERNET JUST CROSSED A POINT OF NO RETURN For the first time in human history, AI bots and autonomous agents are generating MORE internet traffic than actual humans. Cloudflare CEO Matthew Prince revealed new data showing machines are officially dominating the web. The internet is no longer primarily a human network — it’s becoming an AI-to-AI ecosystem. The age of human-driven internet is ending faster than anyone expected. @replifyco