It's a small project with a clear and limited scope which makes it a good "hello world" project for developers. Just like we have a good selection of static site generators and blog frameworks used by one person only, nothing wrong with that.

In the end what makes a status page successful isn't the code of the status page itself, but the reliability, the integration with existing tools (PagerDuty etc.) and all the checkboxes needed to sell to bigger companies.

I got similar comments when I launched OnlineOrNot.

My paying customers say there was indeed a need for a 200th uptime monitoring/status page service.

As many as people want to make.

Considering 99% of existing software is pure crap - we need a lot more.