Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare had a partial outage

cloudflare.com

Post reply on HN
Print view View original

401–410 of 448 posts

Re: Cloudflare had a partial outage

#401

Post by [deleted] »

codethief wrote: post #396
shric wrote: post #384

Earlier quoted context omitted.

An SLA of 100% simply means you agree to compensate your customers (as specified, usually with credit) if your service is down at all, nothing more. Also, SRE here but not for Cloudflare -- I've never seen SREs directly involved in externally published SLAs, they usually come from legal. We deal with SLOs on more fine grained SLIs than overall uptime

> SLA […] SRE […] SLOs […] SLIs I made it to SLA (which I believe stands for service level agreement). What do the other abbreviations stand for?

[deleted]

Re: Cloudflare had a partial outage

#402

Post by chrisweekly »

asddubs wrote: post #388
mproud wrote: post #233

Earlier quoted context omitted.

Yes, this is actual irony, unlike “rain on your wedding day.”

but in regards to singing a whole song about things that are not irony being irony: isn't it ironic? don't you think?

Yes! IRL Alanis is smart and eloquent, and those that think that song's lyrics are evidence to the contrary are missing the joke.

Re: Cloudflare had a partial outage

#403

Post by nsheridan »

codethief wrote: post #396
shric wrote: post #384

Earlier quoted context omitted.

An SLA of 100% simply means you agree to compensate your customers (as specified, usually with credit) if your service is down at all, nothing more. Also, SRE here but not for Cloudflare -- I've never seen SREs directly involved in externally published SLAs, they usually come from legal. We deal with SLOs on more fine grained SLIs than overall uptime

> SLA […] SRE […] SLOs […] SLIs I made it to SLA (which I believe stands for service level agreement). What do the other abbreviations stand for?

SLA - correct. That’s the contract between the operator and the users which describes the penalties for not meeting agreed-upon SLO

SLO - service level objective, the stated availability (or latency or durability etc) of the service. Usually expressed as a value over a period of time (e.g 99.9% availability as measured over a moving 30 average). The SLO is measured by the SLI.

SLI - service level indicator. Simply, the direct measurement of the service (i.e metrics)

SRE - Site Reliability Engineer, usually a member of a team who is responsible for the continued availability of the service and the poor sap who gets paged when it breaches SLO or has an outage or other impactful event.

Re: Cloudflare had a partial outage

#404

Post by chrisweekly »

1123581321 wrote: post #276
phillipseamore wrote: post #268

Earlier quoted context omitted.

I'm talking about this as an option for users like me, that don't have an attack surface, but need the global performance gains of CF.

Probably not many users who need the performance and can handle unexpected failover. There would also be the issue of setting the policy defaults effectively. Most users wouldn’t benefit from this footgun. If you’re serious, you could probably automate this right now with your DNS provider and uptime monitoring.

Typically CF _is_ the DNS provider though, right?

Re: Cloudflare had a partial outage

#405

Post by KarlKode »

codethief wrote: post #396
shric wrote: post #384

Earlier quoted context omitted.

An SLA of 100% simply means you agree to compensate your customers (as specified, usually with credit) if your service is down at all, nothing more. Also, SRE here but not for Cloudflare -- I've never seen SREs directly involved in externally published SLAs, they usually come from legal. We deal with SLOs on more fine grained SLIs than overall uptime

> SLA […] SRE […] SLOs […] SLIs I made it to SLA (which I believe stands for service level agreement). What do the other abbreviations stand for?

SRE: Site reliability engineer

SLI: Service level indicator (Metric to measure the health of a service. For example successful requests per interval / total requests per interval.)

SLO: Service level objective (what performance you expect eg. the previously mentioned SLI is >= 99.5%)

SLA: Servicelevel agreement (legal agreement that defines what happens if a SLO is not met)

Re: Cloudflare had a partial outage

#407

Post by prawn »

jgrahamc wrote: post #357
prawn wrote: post #169

Earlier quoted context omitted.

They're talking about getting accurate information from an employee posting on HN rather than on the status page, rather than the outage itself.

To be fair my information was not accurate. It was fast but when I said it was a problem with our "backbone" I was wrong (it was a networking problem but not the backbone). I favour speed over accuracy here, but the status page wants to be fast and accurate.

My main interest was that you were aware and that a fix was on the way. That's the difference between having to desperately act myself or just sit tight and placate clients. So, I appreciated your original comment!

Re: Cloudflare had a partial outage

#408

Post by [deleted] »

chrisseaton wrote: post #400
greyface- wrote: post #385

Earlier quoted context omitted.

> They aren't saying they guarantee 100% uptime > Cloudflare ("Company") commits to provide a level of service for Business Customers demonstrating: [...] 100% Uptime. The Service will serve Customer Content 100% of the time without qualification. This is a legal commitment to provide 100% uptime. They are guaranteeing 100% uptime and defining penalties for failing to meet that guarantee. The fact that a penalty is d…

> This is a legal commitment to provide 100% uptime. They are guaranteeing 100% uptime I don't think you know what a guarantee is. For example when you buy a new car you get a guarantee that it won't break down. Are they claiming it won't break down? No, of course not. What a guarantee means is that they'll fix it or compensate you if it does.

[deleted]

Re: Cloudflare had a partial outage

#409

Post by adwww »

garyclarke27 wrote: post #368
adwww wrote: post #350

Earlier quoted context omitted.

Cloudflare's pricing has issues. My company was paying $20 a month. We were heavily depended on CF, we'd have been happy to pay more. But... the one feature we wanted was for our accounts team to have their own login so the ops team didn't have to download invoices every month. Nope, that one feature required an enterprise plan which they quoted $4,000 a month for.

Oh dear your poor Ops team, they had to download a few invoices to save $4k and every month! My heart bleeds for them.

You jest, but imagine how time consuming it would be if every app we used was setup like CloudFlare, where only the one super admin can deal with billing.

Also in these days of remote work, it's a problem if the credit card details need updating - either you have to give the company card details over a slack call, or you need to give a card holder your root password.

Re: Cloudflare had a partial outage

#410

Post by selcuka »

acmecorps wrote: post #338
iso1631 wrote: post #224

Earlier quoted context omitted.

My company uses 3 CDNs, although not cloudflare. If one (say Aakami) goes down it gets removed from the pool and life continues.

I'm new to this whole thing. Can u point me on how I don't depend 100% on CF, if its DNS is down? Is there such a service? (kinda like load balancing, but with DNS?)

DNS is easy. You can (and must) have multiple nameservers for your domain. Just use different companies (and different regions) and if one goes down the others will still resolve.
Post reply on HN