The thing about status pages is they have to be up when you're down, and (if your service is non trivial) they have to be able to handle a traffic profile that basically looks like DDOS. So, you're paying for the hosting infra more than the software.

SaaS is dead because large chunks of the industry can't do work or understand their codebase without depending on a proprietary AI model from a single provider.

And you thought GitHub or us-east-1 outages were bad.

Agree with your statement overall but to be honest, status pages are the only SaaS which might make sense. For example, some hosting providers themselves who sell VPS etc. won't run their own website in their VPS and I asked one of the providers why and they mentioned because if they do and the servers go down, their website would 404 too, so they host on other infra in a sense for better redundancy.

Isn't there a thought here that you don't host your status page on your infra itself, and if for example they are using hetzner etc. and hosting their own vibe coded one, then they might need an engineer so might as well have Saas whose whole job is this.

I could've maybe recommended one of those status software[0] which actually runs on github actions but github themselves seem to have some downtime :p

[0]: https://github.com/upptime/upptime (for anyone interested)