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 (41%)
• Cloud Services (33%)
• Hosting (20%)
• Web Tools (4%)
• E-mail (2%)

Live Outage Map

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

City	Problem Type	Report Time
Colima	Hosting	1 day ago
Leuven	Domains	2 days ago
New Delhi	Cloud Services	3 days ago
Mâcon	Cloud Services	8 days ago
Ashburn	Domains	11 days ago
Rosario	Domains	15 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:

• 
  Jacob Goldberg (@mjeyes) reported 4 minutes ago

  @grok Why do I keep getting a cloudflare error 520 from twitter @X on my phone? @Support

• 
  Adarsh  (@Adarsh_Web3) reported 5 minutes ago

  @Shefali__J @Railway It is not working on Jio Internet 😭 buying domain and puting in cloudflare will fix it for everyone. Thanks for letting know 🥹🫶

• 
  Chynen Eide (@chynen_eide) reported 6 minutes ago

  I have to admit. Cloudflare is awful. Firstly, security verification: most of the websites get a verification if you are not a bot and that's fine. The problem is that it failed to load (it refreshes over and over and over again). Then if you think that's bad, Some websites get down for like a HOUR.

• 
  Nicholas Griffin (@ngriffin_uk) reported 9 minutes ago

  @ashleymcnamara exactly and its good that this is being acknowledged. cloudflare have massive outages and theyve took me down for hours, i still host everything with them and dont even think of moving because they own every single outage end to end.

• 
  Insanegamer (@Insanegame2025) reported 10 minutes ago

  @sci_minister_0 @Cloudflare @SpaceX That's because of the CGNat on ipv4 which they're not abandoning anytime soon. Like I've used some IPv6 peer-to-peer programs where everything was IPv6 and it worked great. Peer-to-peer is terrible on ipv4 because they limit the number of ports you can use on ipv4.

• 
  Thishyaketh Abimalla (@Thishyaketh) reported 17 minutes ago

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

• 
  Pi Changelog (@PiChangelog) reported 21 minutes ago

  Added: - Cloudflare Workers AI is a new built-in provider with default model resolution and /login support. Set CLOUDFLARE_API_KEY and CLOUDFLARE_ACCOUNT_ID. See docs/providers.md#api-keys.

• 
  Irbaaz Kadri (@irbaazkadri) reported 24 minutes ago

  @Cloudflare @CloudflareDev @GoDaddy Even at the end of 1 hour they still can't fix it.

• 
  Artem Zakharchenko (@kettanaito) reported 24 minutes ago

  @tmeire_ I'm trying to see how many people can derive what it does from prior art, and how much they are, in fact, familiar with that prior art. Winking at Service Workers, Cloudflare workers...

• 
  Marc-André Moreau (@awakecoding) reported 26 minutes ago

  @Ryan_Hecht If you can have Cloudflare support officialized in the docs that would be absolutely perfect. Ideally tested with instructions to make sure there's no surprise. We already have Cloudflare at work, and it checks a lot of boxes for what I'm looking for

• 
  ais.eth (@aisconnolly) reported 29 minutes ago

  @coinbase But then the issue is that coinbase is just blockchain.. 402 is internet native. Natuarally, let's call @Cloudflare. They were already sending over a billion 402 responses per day to bots and crawlers hitting paywalled content. A billion dead ends. Every single day. No standardized way for those bots to actually pay. That's an insane amount of failed commerce just baked into the internet.

• 
  HOURLY LIFE of Fred Campos (@FredsDaily) reported 35 minutes ago

  9:30a Working with TechAmigos my support company as 2022-Client-822 is down. They managed to get the site back up an running. It was a CloudFlare security error.

• 
  idkmybffjill? ➡️BlueSky (@napsterbater) reported 35 minutes ago

  @LeoVasanko @Cloudflare What **** ISP is doing that? That's a **** ISP problem. Not a protocol problem. Because if the protocol allowed you to do smaller subnets, understand the ISP would just give you that smaller subnet so you couldn't then further subnet it.

• 
  Marly (@marlybuilds) reported 36 minutes ago

  WARP = free cloudflare VPN that gives you a residential IP instead of a datacenter IP. youtube blocks datacenter IPs so this makes your server look like a normal user PO token = proof of origin token. youtube requires it to prove the request came from a real browser session. a sidecar container generates these automatically, no login needed both run as docker containers alongside yt-dlp so the whole thing is self-contained

• 
  SHΘCKWΛVΞ (@x5h0ckw4v3x) reported 38 minutes ago

  @KitsuneroVT checked the link with cloudflare radar and it returned a malicious veredict. it redirects to a "dmca alert" website that will more than likely steal your login and/or stream key.

• 
  Palash Bansal (@repalash) reported 38 minutes ago

  @hiradp @Cloudflare All your domains? Bad move

• 
  NCSWIC (@secretiopathe) reported 39 minutes ago

  @Vika09006261 @MarijkeANON @Qverthetarget17 OpenIA was very slow the whole morning in France and cloudflare DNS failed often

• 
  Alvin De Cruz (@decruz) reported 39 minutes ago

  @CryptoCyberia A lot of those downtimes really have nothing to do with vibe coding. GitHub has scaling issues, Cloudflare had problematic code written before vibe coding was a thing.

• 
  Chynen Eide (@chynen_eide) reported 40 minutes ago

  I have to admit. Cloudflare is awful. Firstly, security verification: most of the websites get a verification if you are not a bot and that's fine. The problem is that it failed to load (it refreshes over and over and over again) until eventually it started to work. Then if you think that's bad, Some websites get down for like a HOUR.

• 
  bitchboi (@bitchbooi) reported 47 minutes ago

  @gistinus it's funny that when cloudflare goes down, downdetector goes down too so what's the point

• 
  → iSpeedtestOS (@iSpeedtest0S) reported 47 minutes ago

  Great, Telekom breaking half of the internet again right now… tons of websites are not reachable. Includes X, netzwelt, cloudflare status, and tons of others. Vodafone works. @Telekom_hilft get your **** together, this is unacceptable. Looks to be your IP resolver this time.

• 
  John Curtis (@jcurtis) reported 50 minutes ago

  @GTMPugh @problogger Hey just a thought. Great use case for cloudflare durable objects. 1 per person. Basically free for a while, isolated, queryable (as opposed to just r2 object) , scales to zero as far as I know so long lived inactive users don’t slow everything down or get expensive.

• 
  koded (@coder0214h) reported 52 minutes ago

  @emmannuel_codes @OLASUNQANMI should be from their end maybe cloudflare, had to change DNS network records at first, then it worked fine using VPN directly

• 
  K.R.I.S. (@KrisWorkLife) reported 53 minutes ago

  When will @Cloudflare support .in domains? 🙄

• 
  breakgimme (@adamos9898) reported 53 minutes ago

  @twolays @Cloudflare maybe in another country? or maybe like my isp that braged about how rpki is guarding their network on their newsroom and then it stopped working lmao

• 
  Jaun (@R3st4rtY0urL1f3) reported 54 minutes ago

  Jellyfin and Wholphin loaded like they were on dial up Things I tried: Ping IP: 5ms Ping Cloudflare tunnel: sub 30ms Ping hostname: 5ms but dropped a few packets at the beginning Hmm. DNS resolution issue Went looking in my configs and found the issue My dumbass forgot that while rebuilding my media server, I added an entry into my firewall (pfSense) for DNS Resolver. I had an issue with IOT VLAN (again, my dumbass but not related to thi) so I threw it back on to the main VLAN Jellyfin loaded like **** because it was trying to resolve the wrong IP

• 
  Vishwanath Patil (@patilvishi) reported 58 minutes ago

  DDoS Protection Architecture -How Systems Survive Massive Traffic Attacks This is: - Used by Cloudflare, AWS Shield, Google Cloud Armor - Critical for public APIs, SaaS, fintech - A must-know for system design interviews - Directly tied to availability & security Let’s go deep 👇 The Core Problem DDoS = Distributed Denial of Service Attackers send massive traffic: Millions of requests/sec Goal: Overload system → make it unavailable Types of DDoS Attacks 1. Volumetric Attacks Flood network bandwidth. Example: UDP flood, DNS amplification 2. Protocol Attacks Exploit network layer. Example: SYN flood 3. Application Layer Attacks (Most Dangerous) Look like real traffic: HTTP GET /login spam Hard to detect. Defense Strategy (Layered Approach) DDoS protection is not one tool. It is multi-layer defense: 1. Edge Protection (CDN + WAF) First line of defense. Handles: - Traffic filtering - Bot detection - IP blocking - Geo-blocking Examples: Cloudflare Akamai AWS CloudFront + WAF 2. Rate Limiting Limit requests per IP / tenant. Example: 100 req/sec per IP Stops abuse early. 3. Load Balancing Distributes traffic across servers. Prevents single-node overload. 4. Auto Scaling Increase capacity during attack. But: Scaling alone does NOT stop DDoS. 5. Application Protection - CAPTCHA - Login throttling - API key validation - Token-based access 6. Backend Protection - Circuit breakers - Queue buffering - Caching Example Attack Flow Without protection: Botnet → API → DB → crash With protection: Botnet → CDN → WAF → Rate Limit → App → DB Attack filtered before reaching backend. Key Techniques 1. IP Reputation Block known bad IPs. 2. Geo Filtering Block traffic from suspicious regions. 3. Bot Detection Analyze: - request patterns - headers - behavior 4. Challenge Systems - CAPTCHA - JS challenges - Proof-of-work 5. Traffic Shaping Limit heavy endpoints like: login search payment Real-World Example Login endpoint under attack: 1M requests/min Protection: - CAPTCHA after 3 attempts - Rate limit per IP - Block suspicious patterns Trade-Offs Strategy Benefit Cost CDN/WAF Strong protection Cost Rate limiting Easy May block legit users CAPTCHA Blocks bots UX impact Auto scaling Absorbs load Expensive Architect-Level Insight DDoS protection is about: Filtering early + protecting deeper layers Never rely on backend alone. Common Mistakes - No edge protection - Only scaling infra - No rate limits - No bot detection - Blocking too aggressively Golden Rule Drop bad traffic as early as possible Edge > Gateway > App > DB Final Insight DDoS protection is not optional. It is a core reliability + security requirement for any internet-facing system.

• 
  HighSpeedLTE (@HighSpeedLTE) reported 59 minutes ago

  @CarlySotura Hey Carly, sorry to bother you, but I’m stuck with a serious X account access bug and I don’t know who else to contact. Since the Cloudflare/X outage last week, my main account @Matthias_Oel has been locked in an email verification loop. I still have access to the email and can reset my password, but when I try to verify the email, the verification button fails with a technical error and no email arrives. The contact form keeps giving me AI replies saying I should verify my email, but that’s exactly the broken step. Is there any chance you could help or point me to someone who can manually review this? Would really appreciate it 🙏 11:21 AM

• 
  Sina Meraji (@sinasanm) reported 1 hour ago

  2 incoming PRs today (custom slash commands PR from @seasonsaw, and cloudflare AI gateway support from another legend). thank you

• 
  mj (@mjtechguy) reported 1 hour ago

  @appfactory @Cloudflare Yeah, great tool. Checked it out not that long ago (I think based on your post). My issue is still being reliant on an external entity for my production needs.