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.
Cloudflare had a partial outage
411–420 of 448 posts
Re: Cloudflare had a partial outage
#412Re: Cloudflare had a partial outage
#413Re: Cloudflare had a partial outage
#414Re: Cloudflare had a partial outage
#415Earlier quoted context omitted.
We are not using cloud flare. But our domain is also not accessible. We are using digital ocean's DNS service for propagating our IP. Does the DigitalOcean's DNS service depend on Cloudflare service?
Yes https://www.cloudflare.com/case-studies/digitalocean/
It's bullshit all the way down.
Are there any companies left offering free DNS usable from Terraform that aren't part of the "Internet Five Eyes"?
edit: looks like Linode may be the next best 'not terrible' option
Re: Cloudflare had a partial outage
#416Earlier quoted context omitted.
Thanks for the update, just curious if we will get a report on what happened ? In as much detail as can be of course - morbid curiosity mainly. I love the post reports these events usually bring.
Cloudflare are usually pretty good with posting post mortems. https://blog.cloudflare.com/tag/postmortem/
Re: Cloudflare had a partial outage
#417Earlier quoted context omitted.
The concept of "being down" doesn't really apply to protocols. IPFS/BitTorrent never being down is a bit like saying that TCP/HTTP has never been down. Individual servers/client can have connection issues, but obviously won't affect clients not connected to those, and is not because of the protocols themselves.
But the infrastructures those protocols provide (the IPFS network, torrent swarms) can be an alternative to Cloudflare. Which is why I brought it up
Re: Cloudflare had a partial outage
#418Earlier quoted context omitted.
I'm so serious that I already have failover after 1 hour at the registrar level, but those changes are not immediate and can take up to 24h to roll-in and roll-back due to DNS propagation and caching.
We seem to have hit the nesting maximum 1123581321, but to your point "There is no immediate option with DNS changes." There's a huge difference in changing nameservers for a domain and simply changing host records.
If you want CDN-independent automatic failover, look into anycast with two providers. If one of them is Cloudflare, use the tier that lets you manage your DNS elsewhere.
Re: Cloudflare had a partial outage
#419Re: Cloudflare had a partial outage
#420Earlier quoted context omitted.
Not a useful comment 20 minutes into an outage. The internet is an interconnected web of dependencies. Unless you are Cloudflare/Akamai/Amazon/Google there is no self-hosted anymore. You can host in your basement if you like but you're still dependent on your ISP.
> The internet is an interconnected web of dependencies. Ironically this is exactly what increasingly centralisation weakens. The huge cloud providers have eroded "an interconnected web of dependencies" into few huge server farms servicing everyone else.