GitHub availability report: February 2026
… We recognize the impact these outages have had on teams, workflows, and overall confidence in our platform. …
… We recognize the impact these outages have had on teams, workflows, and overall confidence in our platform. …
… Services with recently cached entries continued operating normally, which is why overall impact was limited to approximately 5–7% of traffic rather than a complete outage. After an initial configuration rollback did not resolve the issue, we restarted the affected DNS infrastructure. …
… We are also working on improved alerting to catch misconfigured load balancers before it becomes an incident. Additionally, we are updating the Redis client configuration in Actions to improve resiliency to brief cache interruptions. …
… We understand the impact these outages have had on your teams, your workflows, and your confidence in our platform. …
… Suppose a MySQL outage occurs, which causes GitHub to be unable to serve release data from repositories. To resolve the incident, we need to roll out a configuration change to the stateful MySQL nodes that are impacted. This configuration change is applied by executing a deploy script on each node. …