3 ms·
Yep. I tend to agree that we could have gone faster. The difficulty is that getting clear information out fast when you are dealing with a difficult situation i
by jgrahamc 7y ago
Yep. I tend to agree that we could have gone faster. The difficulty is that getting clear information out fast when you are dealing with a difficult situation is hard.
But, I guess we could have put some status up quicker.
- kevcampb 7y agoThanks for the acknowledgement. Appreciate it's hard, false positives etc. Glad you see our PoV.
- jgrahamc 7y agoI do. I'm irritated, however, that you picked on Cloudflare as a bad actor here when we strive to be transparent and quick to get out full information whereas others (e.g. Amazon) are slow as mud. But I get that being on the other side of this is difficult when you don't have information.
- umanwizard 7y agoWell, it's understandable, if OP has been burned by Cloudflare's slowness in the past, and not by Amazon's.
- kevcampb 7y agoAmazon, Google, seem far far worse. I wasn't intending for my post to me representative, just that the CF outage is recent and affects me more personally than the others atm. Also, I had zero expectation my comment would actually be read, this is quite a surprise. If it's any incentive, if the status page had any inkling that something was wrong, I'd be first on here posting "omg their status page is real".
- jgrahamc 7y agoFair enough. Thanks for making the comment. Made me think about how fast we act in terms of public status pages. And sorry that route leak affected you.