[mrkurt]

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.

[jmartens]

How can we solve this as customers, or push the vendor to do better?

[mrkurt]

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).

[encryptluks2]

Stop being a customer of crappy vendors

[copperx]

What cloud provider does better status pages than AWS?

[drusepth]

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.

[mst]

stop.lying.cloud is the accurate AWS status page.