GitHub is the most popular code repository used by a huge number for developers and software companies. So whenever GitHub hits a technical snag and the site goes down, lots of users across the world are left exasperated.
Even though GitHub already has an old Status Page which indicates the working status of the website, it fails to accurately report whether an issue is affecting a standalone service or a cluster of interrelated components.
This is why GitHub has come up with a new Status Page which will communicate any issues to users on a granular level. The latest status site now displays a list of individual component statuses of the website.
Now users can subscribe to know the real-time statuses of components that matter most to them and get Notifications for the same.
For instance, Git operations has been split from API requests, and Pages builds can be tracked independently. So in case the site or any functionality faces service slowdown, the same could be conveyed accurately and reliably.
Over the course of the next three months, GitHub will continue to support the old status site, as well as its API. So you will get sufficient time to move any integrations over to the new site.
At the end of February, the old API will be shut down completely and all web traffic will be redirected to the new status page.
The blog post further states GitHub will be running a test of new incident response workflow at 10:00 PST (18:00 UTC) on December 18, 2018. Therefore, services might appear degraded on the status site.