Cloudflare Network Performance Issues • Hacker News Board

Re: Cloudflare Network Performance Issues

#251

Post by antsar » Tue, Jul 02, 2019, 2:49 PM UTC

Scirra_Tom wrote: post #167

dessant wrote: post #95

A great example for why you shouldn't transfer your domain to Cloudflare Registrar if you're also using their CDN. Those who have transferred their domains cannot change DNS servers to mitigate the outage.

No good if your Registrar (Namecheap) is behind CF as well!

That would seem like a solid reason to avoid Namecheap.

Edit: Wait, do they use Cloudflare?

  $ dig namecheap.com +short
  198.54.117.250

whois:

  CIDR:           198.54.112.0/20
  NetName:        NAMEC-4
  Organization:   Namecheap, Inc. (NAMEC-4)
  Updated:        2015-11-13

https://whois.arin.net/rest/net/NET-198-54-112-0-1.html

Re: Cloudflare Network Performance Issues

#252

Post by btown » Tue, Jul 02, 2019, 2:50 PM UTC

profmonocle wrote: post #231

Once cloudflare.com came back I decided to check out their business SLA, and it's not very encouraging: > For any and each Outage Period during a monthly billing period the Company will provide as a Service Credit an amount calculated as follows: Service Credit = (Outage Period minutes * Affected Customer Ratio) ÷ Scheduled Availability minutes - https://www.cloudflare.com/business-sla/ So assuming an outage affects…

This doesn't surprise me at all - SLA's are widely overrated. No SLA will cover damages incurred by lost business due to an outage. What you likely want is some kind of third-party insurance for downtime caused by outages out of your control - but I'm not even sure this exists.

Re: Cloudflare Network Performance Issues

#253

Post by MrGilbert » Tue, Jul 02, 2019, 2:52 PM UTC

matt_oriordan wrote: post #232

buildbuildbuild wrote: post #152

Cloudflare: Your status page showed "all systems operational" for over 20 minutes while your primary domain was returning a 502 error. Please change this to update automatically, many other engineering teams depend on you. https://i.imgur.com/qHBM2JW.png

Sadly this reminds me of AWS outages too where the same applies. How is it that hundreds of developers know there's an issue before AWS do, or Cloudflare in this instance. See my blog post on similar AWS uptime reporting issues at https://www.ably.io/blog/honest-status-reporting-aws-service . At Ably, our status site had an incident update about Cloudflare issues being worked on (by routing away from CF) before Cloud…

slightly off-topic: Nice and clean, yet detailed enough status page. I like it. :)

Re: Cloudflare Network Performance Issues

#254

Post by bwb » Tue, Jul 02, 2019, 2:53 PM UTC

yuchi wrote: post #8

Either downforeveryoneorjustme.com is itself served by Cloudflare too, or has been hugged to death.

Yep, we are 100% on CF workers :)

Here is a quick image of the peak downtime on downforeveryoneorjustme.com:

https://ibb.co/PZ9BMRc

Re: Cloudflare Network Performance Issues

#255

Post by zymhan » Tue, Jul 02, 2019, 2:54 PM UTC

profmonocle wrote: post #231

Once cloudflare.com came back I decided to check out their business SLA, and it's not very encouraging: > For any and each Outage Period during a monthly billing period the Company will provide as a Service Credit an amount calculated as follows: Service Credit = (Outage Period minutes * Affected Customer Ratio) ÷ Scheduled Availability minutes - https://www.cloudflare.com/business-sla/ So assuming an outage affects…

They reserve the best SLA for Enterprise, naturally.

https://www.cloudflare.com/plans/enterprise/

> 100% uptime and 25x Enterprise SLA

> In the rare event of downtime, Enterprise customers receive a 25x credit against the monthly fee, in proportion to the respective disruption and affected customer ratio.

Re: Cloudflare Network Performance Issues

#256

Post by profmonocle » Tue, Jul 02, 2019, 2:55 PM UTC

jeroen wrote: post #248

profmonocle wrote: post #231

Once cloudflare.com came back I decided to check out their business SLA, and it's not very encouraging: > For any and each Outage Period during a monthly billing period the Company will provide as a Service Credit an amount calculated as follows: Service Credit = (Outage Period minutes * Affected Customer Ratio) ÷ Scheduled Availability minutes - https://www.cloudflare.com/business-sla/ So assuming an outage affects…

25/(31 * 24 * 60) == 0.056%, not 5.6%.

Fixed, thanks. Like I said about the coffee. :)

Re: Cloudflare Network Performance Issues

#257

Post by dictum » Tue, Jul 02, 2019, 2:55 PM UTC

pmlnr wrote: post #72

Good. I'm tired of people not learning that trusting a single gateway with 50% of the internet is bad. Yes, I know, free DDOS protection. There has to be another way of doing this, some mesh based DDOS protection or so.

I agree on principle, but as an end user, I must selfishly disagree. I find life after Cloudflare to be better than before it.

There's a Cloudflare location right next to me, and that improves latency across many of the websites I use, and makes their public DNS service the fastest.

I just wish they had active competition in the same space. CDNs have network locations nearby but they don't offer an easy UX for relatively unexperienced website owners, and DDoS protection services usually have less network locations than content CDNs.

Re: Cloudflare Network Performance Issues

#258

Post by jmngomes » Tue, Jul 02, 2019, 2:55 PM UTC

buildbuildbuild wrote: post #227

btown wrote: post #192

Earlier quoted context omitted.

If cloudflarestatus.com isn't serving text content as Cache-Control: no-cache, that's itself an egregious bug.

Their status page is hosted on Cloudfront, perhaps adding an unintended caching layer.

Cloudfront supports Cache-Control: no-cache

Re: Cloudflare Network Performance Issues

#259

Post by svirelka » Tue, Jul 02, 2019, 2:55 PM UTC

Update - Cloudflare has implemented a fix for this issue and is currently monitoring the results.

Description: Major outage impacted all Cloudflare services globally. We saw a massive spike in CPU that caused primary and secondary systems to fall over. We shut down the process that was causing the CPU spike. Service restored to normal within ~30 minutes. We’re now investigating the root cause of what happened.

Re: Cloudflare Network Performance Issues

#260

Post by profmonocle » Tue, Jul 02, 2019, 2:57 PM UTC

lukevp wrote: post #246

profmonocle wrote: post #231

Once cloudflare.com came back I decided to check out their business SLA, and it's not very encouraging: > For any and each Outage Period during a monthly billing period the Company will provide as a Service Credit an amount calculated as follows: Service Credit = (Outage Period minutes * Affected Customer Ratio) ÷ Scheduled Availability minutes - https://www.cloudflare.com/business-sla/ So assuming an outage affects…

That's the business SLA. The Enterprise one is 100% uptime with a 25x payback so those are the ones they are focusing on keeping up. We were with Verizon before CloudFlare and their SLA was a similar pay back for outage. I think this is pretty typical, what service did you have that had a different setup for the SLA?

Amazon EC2 has an SLA like I mentioned: https://aws.amazon.com/compute/sla/