Details on this incident: https://www.dockerstatus.com/pages/history/533c6539221ae15e3...
Unacceptable level of communication during critical downtime; I know no one who was able to access or use Docker but it is still listed in the history as partial service degradation
....
It gives this error:
> Error during service call to update.install: Error updating Matter Server: Can't install homeassistant/aarch64-addon-matter-server:8.1.1: 401 Client Error for http+docker://localhost/v1.51/images/create?tag=8.1.1&fromImage=homeassistant%2Faarch64-addon-matter-server&platform=linux%2Farm64: Unauthorized ("unauthorized: authentication required")
From the "localhost" in the URL I assumed it was an error with a local Docker instance but I have no idea how HA actually works under the hood. I used the install method where you use the Raspberry Pi Imager to make a bootable HA RPi image and that takes complete control of the RPi. There's a Linux in there, but I've got no login on it. It is a complete black box to me with all my interaction through their web interface or the mobile app. Presumably it has to get 8.1.1 of the Matter server from somewhere, and if that is failing maybe it makes the localhost Docker fail too?
I wonder why isn't it automated
The decision to post anything about outages comes from the executive chain in many orgs lest they miss out on bonus compensation for the year.
This is the same reason services like docker and aws will very rarely call an outage an 'outage' - it's always 'service degradation', even when dockerhub is completely useless as it is right now.
Often you’d have dozens if not hundreds of services on a status page. If you have a major networking outage for example, then everything is technically down. Someone screen shots the sea of red that your automated status page is showing and tweets “lol everything is down at [insert company]. Then you get a million imverysmart people posting about single point of failure or whatever.
As a result status pages, in every place I know, require a human to actually declare the outage there. Internal ones are usually automated, but if your service is down due to dependency on another service, you don’t mark yourself as down.
Also most places I know of have moved away from public status alerts anyway. You get a customized alert in your account or email if you happen to be impacted by a particular outage. The public ones are for the very very _very_ bad outages.