Earlier quoted context omitted.
and https://downdetectorsdowndetectorsdowndetector.com is down
which is at least detected by https://downdetectorsdowndetectorsdowndetectorsdowndetector....
This is now my favorite post on HN
Untitled topic
31–40 of 59 posts
Re: undefined
#32According to UpDog [0], the incident only lasted 35 minutes (8:40 - 9:15). And the Cloudflare status page seems to validate this timeline. While down times are not ideal, that's quite an impressive achievement to be able to resolve an incident of this scale in minutes - not hours. [0]: https://updog.ai/status/cloudflare
it affected CDN services as well, i don't know or understand why that's not mentioned in the status page.
Re: undefined
#33According to UpDog [0], the incident only lasted 35 minutes (8:40 - 9:15). And the Cloudflare status page seems to validate this timeline. While down times are not ideal, that's quite an impressive achievement to be able to resolve an incident of this scale in minutes - not hours. [0]: https://updog.ai/status/cloudflare
Having this kind of outage on a friday after what happened last month though is not a good thing... Props to them for getting back up so quickly but come on, these kinds of outages were not a thing a while back.
Re: undefined
#34Raise your hands if you don't use Cloudflare in your stack and are proud of your decision. You are the future of the operational internet!
I’d argue that the big 3 cloud providers have more outages than this, only cloudflare actually lets you know.
I've been operating a relatively small digital platform for 15 years. We don't use Cloudflare, for bots, we use tirreno (1), which we specifically created to filter malicious traffic.
For hosting, we use a local and sovereign EU provider.
If tomorrow Cloudflare, Amazon, and Microsoft were to somehow disappear or go permanently down, I wouldn't even notice.
Re: undefined
#35Re: undefined
#36Re: undefined
#37This needs to be changed, whole web was stopped working - it's a big responsibility and Cloudflare should acknowledge it.
Re: undefined
#38According to UpDog [0], the incident only lasted 35 minutes (8:40 - 9:15). And the Cloudflare status page seems to validate this timeline. While down times are not ideal, that's quite an impressive achievement to be able to resolve an incident of this scale in minutes - not hours. [0]: https://updog.ai/status/cloudflare
> “only” lasted 35 minutes
That single incident drops their uptime to four nines. Combine it with other recent incidents and they’re probably at three nines. That’s amateur level.
> that's quite an impressive achievement
No it isn’t. Good grief.
Re: undefined
#39Another Option::unwrap incident perchance?
Re: undefined
#40Chess dot com was affected, I got a Cloudflare internal server error at the end of one of my matches.
Will you consider it a stalemate if no party is able to make any further moves?
I would have probably considered whoever was up material as the winner, as long at there was sufficient time left.
I guess it had an active connection through the game end though, maybe web sockets. I was afraid it wasn't recorded because I played quite well!