That's just an automated status check, the above comment is referring to an incident which contains prose and updates from the ops team to describe what's actually happening.
FWIW, the API and Git operations are indeed still functioning, so if for example you have the GitHub mobile app you can still read your issues and whatnot.
Is it just me or is this happening more and more often recently, i.e. since Microsoft acquired GitHub?
It's also very shady that they don't even seem to detect these incidents properly.
You know you could actually use a self-hosted GitLab for your team's projects. Which is why projects like Xfce [0], GNOME, etc are still up and running and don't suffer from this.
Also if I were a school sys-admin I would self-host and use GitLab.
> price/comfort, built-in tools, decent security without having to do your own, etc.
It's more about control and ownership of your own server and data and this same argument can be made for hosting your own website (price, tools, security) which is maintained by you.
You control everything on the server and deal with downtime yourself or as with the context of schools, companies, open-source projects have 'sys-admins' to do this work.
GitHub does not fit with everyone's requirements to do source-code management on a centralized infrastructure, which is why some users have mirrors to Github from their self-hosted solution. (Google, Mozilla, Apple, Linux kernel developers, etc)
If you can self-host your own website, then you should be able to self-host a Gitlab, Gittea, etc solution.
Git the version control system is (well, its "distributed"), but GitHub not so much since the repos themselves are stored central, afaik. I think the most they manage are servers for different countries.
down from South Asia as well.