Cloudflare 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:

• 
  Harishaan (@hsuthan24) reported 6 minutes ago

  If your NAT type on multiplayer(bottom of screen) is strict, that’s why you can’t find lobbies. It needs to at least be moderate. Change the DNS in your ps5’s settings to CloudFlare or Google’s DNS rather than your internet service provider’s.

• 
  Eric Taylor (@bcs_erictaylor) reported 7 minutes ago

  7/16 - Kali365 Update I have, at least for the moment, completely disabled the Kali365 platform from all operations. Below is an update of the intel we have currently. Believed owner and creator of Kali365: Handle: Octopus King TG: @tentacle_network Completed 'Takedown Requests' submitted to Namesilo FQDN: updateteampanel[.]xyz Completed 'Takedown Requests' submitted to BL Network: IP Address: 199.21.221[.]21 IP Address: 162.33.178[.]105 IP Address: 72.5.43[.]195 Completed 'Sinkhole Requests' submitted to Cloudflare FQDN: servoquil[.]org FQDN: yalmorind[.]org FQDN: vuredonte[.]org FQDN: ondrevail[.]org FQDN: caldivore[.]org FQDN: vuredonte[.]org FQDN: privatetoken[.]app FQDN: mvpaffiliatecz[.]site #Kali365 #CTI #ThreatIntel

• 
  Paul Jump (@paulljump) reported 9 minutes ago

  @AjaySohmshetty @Cloudflare @andrewk17 My worst nightmare

• 
  luna (@ImLunaHey) reported 10 minutes ago

  @mynameistito @Cloudflare that doesnt really help with client side only apps though.

• 
  Omkar (@omkar_builds) reported 12 minutes ago

  > 02_failed_attempt NGINX had Thread Pools to move `read()` to a background thread. But `open()` must traverse directory structures. As Cloudflare noted, a single cache miss means the OS makes 6 separate disk reads just to walk down the folder tree to find the file's metadata, compared to just 1 read for the actual data. Standard NGINX ran this heavy `open()` on the main loop. The disk lookup bottleneck remained.

• 
  Martin Tale (@MartinTale) reported 21 minutes ago

  @CodeWithTamara They are more expensive there, UI is complete garbage, super slow and very unethical business 😬 I switched to Cloudflare and it’s like night and day..

• 
  Eric Taylor (@bcs_erictaylor) reported 22 minutes ago

  Date: 7/15/2026 Here is an update on our updated information on our proactive efforts to heavily impact the Kali365 platform. As expected, the user "Octopus King" is working hard to rebuild is infrastructure, but we have the fingerprinting locked in and will continue our efforts. At the time of this blog posting, we have submitted an IC3 report but honestly not expecting much. I believe it will be up to companies like ours to keep submitting takedown requests as fast as we see them to limit its operations. Below is the information Believed owner and creator of Kali365: Handle: Octopus King TG: @tentacle_network Completed 'Takedown Requests' submitted to Namesilo FQDN: updateteampanel[.]xyz Completed 'Takedown Requests' submitted to BL Network: IP Address: 199.21.221[.]21 Pending 'Takedown Requests' submitted to BL Network: IP Address: 162.33.178[.]105 IP Address: 72.5.43[.]195 Pending 'Sinkhole Requests' submitted to @Cloudflare FQDN: updateteampanel[.]xyz FQDN: privatetoken[.]app FQDN: servoquil[.]org FQDN: vuredonte[.]org FQDN: yalmorind[.]org FQDN: ondrevail[.]org FQDN: caldivore[.]org FQDN: mvpaffiliatecz[.]site FQDN: vuredonte[.]org #Kali365 #CTI #threatintel

• 
  Kinds 🐧🪄 (@Mumukinds) reported 23 minutes ago

  can we just kill everyone who works for cloudflare? I know they probably perform a useful service to some people but if i can't access half the internet because my vpn is on while I play umamusume then literally every employee at your company should die

• 
  drew anderson (@DrewAlpha888) reported 24 minutes ago

  The best tech opportunities often appear after the excitement cools down. $CRWD (CrowdStrike) — Don’t buy $NET (Cloudflare) — Don’t buy $CRM (Salesforce) — Buy at $158–$163 $NOW (ServiceNow) — Buy at $94–$100 $FTNT (Fortinet) — Buy at $156–$163 $ZS (Zscaler) — Buy at $140–$148 $SNPS (Synopsys) — Buy at $414–$420 $ON (ON Semiconductor) — Buy at $86–$90

• 
  SoothSpider 🇨🇦🍁🧡真🔬💻Ω 🐶😼🌎 (@SoothSpider) reported 25 minutes ago

  @45Homelab Can I stick a PVE (zfs mirrored) at my out-of-State/Province friend's house configure some basic services with OOTB easy HA/redundancy? 🤔 Can I put that behind a $5/month CloudFlare load balancer? Can I spin up a new service from scratch knowing nothing in a few hours? 🤔

• 
  Fred Jonsson (@enginoid) reported 28 minutes ago

  I went with serverless SaaS for small-scale company infra and building out products, and I basically regret it. The infra I have is fairly light. They are mostly key primitives I use in my contracting work and research, such as: - agents API/UI with jobs+observability-caching - container APIs for managing tier-3 GPUs - easy hosting and perf tuning of arbitrary OSS LLMs On top of that I've got a product in progress around evaluation, annotation and optimization of AI tasks, and relies heavily on those APIs. This product is for fairly sophisticated AI product companies and won't experience large-scale usage. Overall, it's quite a simple setup of maybe 10 Cloudflare Workers and Firebase for collaborative editing. My reasoning for going serverless was to minimize the gap from experimentation to shipping: pay very little monthly and just pay when it scales out. The other one was to treat the first product as an investment in building lots of other products without setup costs – get IaC, auth, authz, etc. working once and reuse it in other products. Yet another consideration was to use the wonderful high-level serverless primitives like Cloudflare Workers, Workflows and Firebase. You get a lot of good stuff that is genuinely hard to distribute, and it just works, so you can focus on product. But I think serverless was the wrong choice for me in this trade-off, for two reasons: 1. Cost predictability. Every few weeks I get a random runaway $50 bill from one service or another, maybe because the agents went a bit wild with E2E testing. I'm sure "random load spikes" have cost me as much as $300 at this point over a couple of months. This is not a lot of money in the grand scheme, but for an application with zero users, it's a lot of variable cost. This week I saw a notice from Cloudflare showing the way they'll charge for Workflows makes them uneconomical. And each time it's a bit disruptive to figure out what is causing the traffic -- all while I have zero users except myself. I still haven't got a horror story, thankfully, but I am worried that I'm due any day. 2. Phoenix environments. The other issue is that the best iteration speed I've found is when agents can 100% run the infra and replicate the full user experience, fast, locally and in memory. This is incredibly easy with postgres and a monolith, but it's messy to get reliable when you use services like Firebase and Durable Objects that aren't fully emulatable and are a bit messy architecturally to swap out. My preview deployments are really sprawled on CloudFlare because business logic is split between workers and DOs don't work well with preview deployments, so need to deploy a new set of services. So in that sense, using something high-level is far from simplifying compared to running of a k8s namespace or a single binary. I'm probably a little too used to startups and seeing what kind of issues you run into that I wanted to pre-empt with "proper infra." The indie hacker advice is to get a $5 VPS and set it up on postgres, validate and then think about proper deployment. Having shipped mostly software at scale and knowing what's needed, I still struggle with doing things that don't scale, but this advice seems right for day 0 and I should have heeded it. All this is to say – PaaS vs. IaaS are two very different directions worth taking seriously at the outset of a new project. The narrative is that PaaS will simplify things, but this hasn't been my experience so far. If anything, it has created a lot of novel constraints that complicate the architecture. And I think by outsourcing what I'd need to understand if I rolled it myself, I sold away too much freedom. So in retrospect, I should have gone with the other option I was considering: fixed resources via something like k8s + PlanetScale. If I were making the decision again, I would have upweight the cost predictability a bit more – at some level it was a consideration, but I thought I could tame it with lots of limits and budget notifications. But anytime you add a lot of mechanism (quotas and alerts) to replace an invariants (I can't pay for more computers than I have), it's probably worth paying closer attention. When I think about how difficult things like workflows, queues and even realtime are to implement on postgres and have an entire WAL to drive the whole application: I'm probably missing something, but the answer seems to be... not very hard. Maybe at millions of users, but not at hundreds or even thousands. So I'm going to try swinging the pendulum back in the direction of more control. I'm optimistic that if I don't operate the database layer itself, this will turn out to be a better foundation. And if I'm so lucky, I can one day write the post about moving off postgres. Let's see what happens after the honeymoon period!

• 
  Ivanha Paz (@ivanhapaz) reported 28 minutes ago

  @Cloudflare talk to all the tools I signed up with a different email over the years and no longer use and help me cancel ahhahah

• 
  Kobecoin Official (@Kobecoin_X0214) reported 29 minutes ago

  Development update: The KOBX Service Runner is now operational, providing centralized control and live monitoring for the backend, frontend, and Cloudflare services. With health checks, uptime tracking, restart controls, and auto-recovery support, our infrastructure is being prepared for a more stable launch. KOBX Hero Wars launches in 2 days. CA: 48iJcUv9jsiZ7cCisyVFLPFLMoNBKg3L43bRvktXpump

• 
  Adam Dawood (@adamdawood) reported 35 minutes ago

  website is stupidly fast as well. never really used cloudflare workers before even though i have been a customer since 2012 when in my first week as PM at @darazpk we were hit with DDOS attacks and @blackmodjo and @Cloudflare rescued us.

• 
  Kunai1337🇺🇸🇺🇦🇵🇸🐈 (@Hurriya1973) reported 44 minutes ago

  @XJosh @Cloudflare hosts cat torture content and still has those sites up. $NET doesnt have a problem with a site that hosts illegal animal crush videos