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.
Your Lightning address is broken nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309aex2mrp0yhxummnw3ezucn89ur9eu8h. Don't tell me you're still not using Alby Hub and missed the deadline for switching from the custodial wallet.
Discussion
If there's anyone who can make sure services are running properly on their Start9, it's nostr:nprofile1qqs8fl79rnpsz5x00xmvkvtd8g2u7ve2k2dr3lkfadyy4v24r4k3s4sppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg4waehxw309aex2mrp0yhxummnw3ezucn89ur9eu8h. He's helped me out of a jam on a few occasions now.
I think it's a Alby Hub issue. And Alby is aware of it. When the backend node goes down, Alby Hub isn't always able to restart services, and manual intervention is required to re-initialize the connection between the backend node and Alby Hub.