Its more likely his backend node went down or had some connectivity issue, and he didn't property restart Alby Hub. I've seen this with a lot of self-hosted Alby configs, especially those using Start9.

Replies (1)