Seems odd to me. Why would I use this as opposed to a normal PHP host, or some kind of Status SaaS that already exists?

And if I want to save money I could create a github page which polls my service via AJAX.

Well, a "normal" PHP host usually has at least some cost attached. This doesn't.

> And if I want to save money I could create a github page which polls my service via AJAX.

I covered that in the first paragraph of the README.

> I covered that in the first paragraph of the README

Not really. Because you can host a static page on a different infrastructure to your main service.

Yes, really. I specifically talked about GitHub pages:

> Static pages can be hosted for free with GitHub pages, but these can only contain client-side code.

And your other point:

> you can host a static page on a different infrastructure to your main service

Well, yes. That the point. That's also why the title here says dynamic and server-side.

It is quite ironic that GitHub has a "Major service outage." exactly the day unstatus goes public :)

I can't see any code in the repository. An example would be helpful.

Example for what? The repository holds the source code for hosted status pages. It's empty because no one submitted any pages yet. There's nothing you have to install, build or use.

unstatus.site simple hosts whatever this repository contains. Basically it's a (peer)-reviewed PHP hosting. You make a PR to include your page and that's it :-)

Already understood. Nevertheless an example would be helpful. E.g. with https://unstatus.site/foobar