GitHub is the most popular code repository, used by a huge number of developers and software companies. So whenever GitHub experiences a technical issue and the site is down, it results in many users around the world being surprised and frustrated.
Although GitHub already has an old Status Page, which indicates the site's operational status, it does not accurately report whether an issue affects a standalone service or a cluster of interconnected services.
That's why GitHub has created a new Status Page, which will notify users of any issues that arise and report each one individually. The latest Status site, displays a list of the individual statuses of the site's services.
Now users can sign up to know the status of the items that interest them most, in real time, and receive notifications about them.
For example, Git operations are decoupled from API requests, and pages being generated can be monitored independently. So, if the site or any function experiences a service slowdown, users will be informed accurately and reliably.
Over the next three months, GitHub will continue to support the old status site, as well as its API. At the end of February, the old API will be completely shut down and all web traffic will be moved to the new Status Page.
The blog post further states that GitHub will be testing an incident response workflow on December 18, 2018, at 10:00 AM PST (18:00 UTC). As a result, you may see degraded services on the status site.
