Status Page Now Shows Live Service Health

GitHub recorded no downtime incidents in August 2020. The main change this month affects how users see service health: the status page has been revised to focus on real-time conditions rather than historical summaries.

Previously, the page opened with a 90-day availability breakdown per service. That view could distract from the most pressing information during an active incident. The updated page instead leads with the current state of each service and streams live updates from the team as incidents are created or resolved. The historical data is still available—it now lives under an “incident history” link.

Animation showing new GitHub Status page

Changes Made After the July 13 Incident

GitHub also followed up on the incident reported in July, outlining two specific changes to its Kubernetes deployment practices designed to reduce dependence on the Docker registry during container restarts.

Removing Image Pull Configurations

First, the engineering team audited all Kubernetes deployments in production and removed every use of the ImagePullPolicy of Always configuration.

The approach is part of a broader philosophy: Kubernetes configuration should make it easy for internal teams to ship code while staying aligned with best practices. To that end, GitHub implemented a system that automatically replaces the ImagePullPolicy of Always setting across all Kubernetes-deployed applications. Users with specific needs can opt out of the automation.

Sidecar Injection by Image Digest

Second, GitHub introduced a mechanism similar to Kubernetes mutating admission controllers. The new system injects the latest version of sidecar containers, identifying them by the SHA256 digest of the image rather than by tag reference.

Together, these steps sever the strong coupling between Kubernetes Pods and the availability of the Docker registry when containers need to restart. GitHub indicates that further improvements are in the pipeline to increase the resilience of its Kubernetes deployments. Further details will be shared in future reports.