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 (36%)
• Cloud Services (31%)
• Hosting (18%)
• Web Tools (10%)
• E-mail (5%)

Live Outage Map

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

City	Problem Type	Report Time
Angers	Cloud Services	6 days ago
London	Domains	8 days ago
Noida	Hosting	21 days ago
Jewar	E-mail	21 days ago
Braga	Web Tools	21 days ago
Noida	Cloud Services	22 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:

• 
  Black Press USA (@BlackPressUSA) reported 11 minutes ago

  Technical issues are temporarily blocking access to @BlackPressUSA as @Cloudflare reports an SSL handshake failure. Work is underway.

• 
  zeb (@zebassembly) reported 14 minutes ago

  @astuyve @boristane Not to get too into the weeds but the concern is where the trace context gets inherited and where we check the users tracing configuration. Before a request ever goes to the Workers runtime there's our FL2 (essentially the Cloudflare webserver) that actually accepts the http connection for various reasons we want that part that isn't entirely related to Workers to be aware of tracing so we can do cool things in the future. This entails creating a way for FL2 to fetch the user's tracing config (sampling, if they want to enable propogation, etc), passing that context through FL2, passing it to the Workers runtime, and then when the Worker does a fetch we need to pass it back through to FL2 so we can potentially attach the context header. None of this is strictly about just parsing that trace context header, more about threading configuration and ceoss-service communication.

• 
  Kaspar Poland (@kasparfp) reported 17 minutes ago

  @QuinnyPig @vmg__0 @Cloudflare They just imported the AWS Account problem and ignored the GCP Solution.

• 
  ∱ (@Fallibilist) reported 18 minutes ago

  @ni5arga Yeah, not working on network DNS, cloudflare works

• 
  Nikhil Agarwal (@nikhildp) reported 19 minutes ago

  @dinasaur_404 @Cloudflare Yes looking for billing cap. How do you test dynamic workers as well as dynamic workflows in local dev? We had a disastrous outcome of losing $800 because the deployed code ran into infinite loop using dynamic workflow. Support team was not at all helpful.

• 
  KAMWI TECHNOLOGIES (@kamwifi) reported 20 minutes ago

  Stopping the bad guys with Cloudflare: 159 malicious requests blocked or challenged in the last month #cloudflare

• 
  special k | CEO of stressed out era (@specialkdelslay) reported 21 minutes ago

  @HeadmasterDuck We have cloudflare pro acc which does mitigate some of this. The cloudflare dependency everyone has is a problem tho

• 
  The Pajeet Files with Yasha (@khyimiq) reported 22 minutes ago

  Gotta love how Indians climb into high positions with fake degrees and then immediately start hiring other Indians with equally fake degrees. Then Cloudflare and AWS eat **** for an entire day and we’re all supposed to act shocked.

• 
  Mundo Trading (@DonPepeVaquito) reported 25 minutes ago

  Is cloudflare down or it's just me?

• 
  tcpdump (@dump_tcp) reported 25 minutes ago

  @EddCoates if need any help with cloudflare I can help with some rules also it seems you're webserver code is bottlenecking you causing that error usually due to not being able to handle that many connections or to much cpu usage the webserver process dies i suggest using #golang best lang

• 
  Command Code (@CommandCodeAI) reported 25 minutes ago

  We're aware of an ongoing incident. Partial outages at Cloudflare and Supabase are causing Command Code CLI to experience intermittent connection issues. We're actively investigating and working on a fix. Thanks for bearing with us.

• 
  Viktor Lazarov (@viktor_techness) reported 26 minutes ago

  @EddCoates Doesn't Cloudflare anti-bot help? They have a setting specifically for scrapers + robots.txt attachment for a legal notice.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 30 minutes ago

  HERMES AGENT JUST TURNED WHATSAPP INTO A REAL AI WORKER But one tiny setup mistake can leave the entire bot completely silent. What Just Dropped: → Official WhatsApp Business Cloud integration → Run Hermes as a private assistant, team bot, or customer support agent → Text one WhatsApp number and get AI replies directly inside the chat Built Like A Proper App: ✓ Secure webhooks and official Meta support ✓ Voice notes, media, read receipts, and typing indicators ✓ Interactive approval buttons when Hermes needs confirmation The Setup: → Run `hermes whatsapp cloud` → Connect your Meta Business account and WhatsApp number → Use Cloudflare Tunnel to expose your local Hermes gateway securely Three Mistakes To Avoid: ✓ Use the 15–17 digit Phone Number ID, not your real phone number ✓ Replace the 24-hour test token with a permanent system-user token ✓ Subscribe to the `messages` webhook field or the bot will never receive anything For a reliable WhatsApp agent, use the official Cloud API path instead of the unofficial personal-account bridge.

• 
  bigdatachads (@bigdatachads) reported 38 minutes ago

  I've been building AI phone agents on @Cloudflare for a while now. v1. a Python container, fighting for every millisecond. v2. no container, the whole call on the edge. that was the real work. now that I have the stack down, I spent last weekend messing around. this is v3, a cartoon you talk to that remembers you and gets heckled by a second AI. all on Cloudflare primitives. three teardowns, first one tomorrow. follow along. @CloudflareDev

• 
  Nick Sunny (@suny_nick) reported 39 minutes ago

  @EddCoates I had similar issues. If you use Cloudflare, you can do what I did

• 
  Kolorguide (@Kolorguide) reported 40 minutes ago

  @Hostinger Yesterday I upgraded my hosting plan. My website was operating normally before the upgrade. Immediately after the upgrade, the site became unavailable with Cloudflare 525 errors. DNS, SSL and server checks have been completed, but human support and ticket escalation are currently unavailable due to a reported support platform issue. Can someone from Hostinger please review this case or advise how customers can obtain technical assistance during the support platform outage? #Hostinger #WebHosting #Support

• 
  Ann the cat herder (@ann1knit) reported 43 minutes ago

  If cloudflare is so buggy and easily broken or hacked, why the frell hasn't someone come up with a better system or solution?

• 
  Michael Williamson (@BeachTruck) reported 44 minutes ago

  @EddCoates There's always Cloudflare. It kind of sucks having to give up SSL encrypted content to a 3rd party (they re-issue another SSL connection), but sucks less than getting ddos's by these stupid clanker suckbots.

• 
  DownWithBigBrother (@DWBB1984) reported 48 minutes ago

  @ultrasxiv Fair on bandwidth being a real cost, but the 2GB figure is a long way out. Cheapest DO droplet includes 500GB+ outbound, Hetzner 20TB+. At 600-700GB household use you’re a pound or two over on DO, zero on Hetzner. Stays around the base £4-5 for most, not £300. And “un-bannable” was the precise word, not hyperbole. A commercial VPN is bannable because it’s a named brand with known IPs, a company that can be pressured or blocked. That’s the weakness. Self-hosting removes the target entirely. There’s no technical category called “a VPS used as a VPN.” It’s a rented server running standard encryption (WireGuard, IPsec), the same protocols carrying every bank settlement, ATM link and corporate tunnel on earth. To ban it you’d have to block those protocols (killing Visa, every corporate VPN, all remote work) or blacklist the datacentre IP ranges (AWS, Hetzner, OVH) that host the actual internet: payment gateways, banking backends, Stripe, Cloudflare, gov services. You can’t separate “server someone might tunnel through” from “server running the shop you’re buying from.” The second and third-order effects would cripple e-commerce, open banking and logistics, all riding the same cloud backbone. That’s the sovereignty point. You can ban a brand. You can’t ban the capability of renting a server and encrypting your own traffic, not without taking modern commerce down with it.

• 
  Ozgur Ozer (@ozgrozer) reported 48 minutes ago

  Today I decided to archive some of my failed projects. I never made money from them so it's time to let them go. I spent more than a year and some money on these 5 failed projects but still it's not a lose. I learned a lot about idea validation. I started my indie hacker journey 2 years ago with Next AI Tool directory. I scraped the internet so the site wouldn't look empty. There were 46k AI tools in the website on launch but a couple of weeks later Google blocked the domain on the search results lol. I made my first internet dollar with AI Renamer so it teached me lots of things about making a useful product, educating and supporting customers, marketing etc. It made $7k in the last year and still making a little so I'll keep it. Now my focus is on Grape, the AI note taking app. I only made one post on Reddit about the beta version of desktop app and since then it made 5 lifetime sales and currently has 1 active subscription. Now working on the mobile app. The failed projects, they were on my VPS using the CPU and memory. I removed their auth and dashboards to only keep their landing pages. That way I turned them into static sites and moved them from my VPS to Cloudflare Pages to host free. I'll still renew the domains because I still want to see them in the future. I can fail again but always will be learning from my mistakes and keep building until I make it.

• 
  Nav Toor (@heynavtoor) reported 55 minutes ago

  The Dead Internet Theory was a conspiracy. The idea that the internet is no longer human. That bots and AI have quietly replaced real people. It started on anonymous message boards in 2019. Most people dismissed it. Stanford, Imperial College London, and the Internet Archive just measured it. They used the Wayback Machine to scan every new website published between 2022 and 2025. Thirty-three months of the internet, captured and classified. They applied one of the most advanced AI text detectors in the world to every page. 35.3% of all newly published websites were AI-generated or AI-assisted. 17.6% were completely AI-generated. No human involvement at all. In late 2022, before ChatGPT launched, that number was zero. In three years, more than a third of the new internet became synthetic. Not over decades. Not over a generation. Three years. Then they measured what that is doing to the internet itself. Semantic diversity is falling. The range of ideas, perspectives, and ways of saying things is narrowing. As AI content increases, the internet sounds more and more like one voice. Because it is one voice. The same models producing the same patterns across millions of pages. Positive sentiment is rising. Everything sounds upbeat. Polished. Confident. Helpful. The internet is getting friendlier while getting emptier. The tone improves as the substance disappears. The lead researcher, Jonáš Doležal at Imperial College London, said this to 404 Media: "I find the sheer speed of the AI takeover of the web quite staggering. After decades of humans shaping it, a significant portion of the internet has become defined by AI in just three years." Separately, Cloudflare reported that nearly a third of all internet traffic now comes from bots. Imperva reported that automated traffic surpassed human traffic for the first time in 2024. If you read my previous threads on Model Collapse and Retrieval Collapse, this is the final chapter. Model Collapse showed that AI trained on AI gets dumber. Retrieval Collapse showed that search engines indexing AI content get emptier. This paper shows the source of both problems. The internet itself is being replaced. The researchers are now working with the Internet Archive to build a live monitoring tool. A real-time tracker of how much of the internet is human and how much is not. The fact that we need a tool to measure how much of the internet is still real is the finding.

• 
  dr.dimitru (@smart_egg) reported 55 minutes ago

  If you use CloudFlare — what feature you use the most? What do you like or don’t like about their service?

• 
  Axel Hardy (@fraxool) reported 55 minutes ago

  Just like last time, the Shopify API seems extremely slow and is timing out. It might be related to Cloudflare. I'll probably postpone the expiring token migration I planned for today, as a failure mid-process could leave some users with broken tokens.

• 
  Puneet Patwari (@system_monarch) reported 55 minutes ago

  Tweet 3/5 Picking the algorithm is half the decision. The other half is: where do you enforce the limit? Most teams slap rate limiting at the API gateway and call it done. That's one layer. Production systems need at least two. Here's why. Layer 1: API Gateway (the front door) This is your first line of defense. Every request passes through here. Set global rate limits: "no client can exceed 1000 requests per minute." This catches: - Runaway scripts - Misconfigured clients - Basic abuse - Your own batch jobs (ask me how I know) Tools: Kong, NGINX, AWS API Gateway, Cloudflare. All have rate limiting built in. Layer 2: Per-service limits (noisy neighbour protection) You have 10 microservices. Your search service can handle 5000 rps. Your export service can handle 50. Without per-service limits, one client hammering /export at 200 rps takes that service down. And because /export is down, health checks fail, the circuit breaker trips, and suddenly other things start breaking too. Per-service rate limits prevent one endpoint from eating the capacity of another. Layer 3: Per-user limits (fair usage) One user is making 10,000 API calls per minute. Every other user is making 50. Without per-user limits, that one power user is consuming 99% of your capacity. Per-user limits: "each API key gets 100 requests per minute." Fair. Predictable. No single user can starve everyone else. This is also where you differentiate pricing tiers. Free tier: 100 rpm. Pro: 1000 rpm. Enterprise: 10,000 rpm. Rate limiting is literally your pricing enforcement. Layer 4: Per-endpoint limits (not all endpoints are equal) Your /search endpoint can handle 10,000 rps. It's fast, cached, lightweight. Your /generate-report endpoint does a 30-second database aggregation. It can handle maybe 10 concurrent requests before the database starts crying. Same global rate limit for both? That's a disaster waiting to happen. The heavy endpoints need tighter limits. The rule: at minimum, use two layers. Gateway-level for global protection. Per-endpoint or per-user for granular control.

• 
  JustAnotherUser_4 (@JAU_4) reported 56 minutes ago

  @EddCoates Cloudflare firewall, thank me later. I blocked entire countries. Solved so many problems.

• 
  Decoded (@decoded_dev) reported 59 minutes ago

  @EddCoates A lot can be done for free. If you use nginx, page caching helps a lot. Identify query strings that aren't used by your site but are actively being crawled and block them in cloudflare - *?*weirdstring*. This can help block bots that try to bypass the page cache. Use cloudflare to block user agents of bots that you don't need crawling your website. If you put the painful effort of going through your logs now then this problem (your server not responding) will rarely happen in the future. Where are you hosting your site?

• 
  Tsinoiz Itna (@TsinoizItna) reported 59 minutes ago

  @QuinnyPig @Cloudflare Try adding an IP access rule sometime... Google-level poor UI.

• 
  Sina Meraji (@sinasanm) reported 1 hour ago

  totally forgot i can replace the scrappy cf onboarding in kimiflare with the new "login with cloudflare" oauth thingy

• 
  Symedia (@Symedia_) reported 1 hour ago

  @rickyrickyriri @SimonAlmers @AliGrids it's not a work email but a domain email look at tld-list buy a 1$ domain and get a cloudflare email. fixed the problem in few hours.

• 
  dukeo (@dukeo) reported 1 hour ago

  @EddCoates Had the same issue on one of our sites receiving millions of hits from scrapers while getting just a few thousands legit visitors per day. The only way is to be extremely aggressive in your Cloudflare setup.