News for hackers. Stuff that matters.
Re:GitHub incident 2022-03-23 by mrkurt on Wednesday March 23, 2022 @11:42AM (#30779636)
If you want companies to be honest on their status pages (I do!), you can't just count incidents like that. Status pages can be an amazing place to communicate all kinds of problems.

Most issues have a relatively narrow impact, but the impacted people _still_ benefit from seeing them listed.

Re:GitHub incident 2022-03-23 by jmartens on Wednesday March 23, 2022 @11:54AM (#30779785)
How can we solve this as customers, or push the vendor to do better?
Re:GitHub incident 2022-03-23 by mrkurt on Wednesday March 23, 2022 @11:56AM (#30779813)
Use vendors who do a good job communicating status, basically. I don't think you can change AWS behavior. But if you find a hosting company who does an amazing job with their status updates, put some apps there (_my_ company does an ok job with status page updates, we're getting better, it's not amazing yet).
Re:GitHub incident 2022-03-23 by encryptluks2 on Wednesday March 23, 2022 @12:03PM (#30779884)
Stop being a customer of crappy vendors
Re:GitHub incident 2022-03-23 by copperx on Wednesday March 23, 2022 @12:47PM (#30780446)
What cloud provider does better status pages than AWS?
Re:GitHub incident 2022-03-23 by drusepth on Wednesday March 23, 2022 @04:25PM (#30782885)
The snarky answer is "literally all of them", but one real answer is that I've been pretty happy with GCP's status reporting for the past year-ish I've used them. I've only noticed a few incidents, but every time I've checked the status it was already updated. They also occasionally provide workarounds on the live incident pages if you need to be back up before the issue is fixed on their end.
Re:GitHub incident 2022-03-23 by mst on Thursday March 24, 2022 @01:37AM (#30786651)
stop.lying.cloud is the accurate AWS status page.