GitHub Availability Report

In April, we experienced three distinct incidents resulting in significant impact and degraded state of availability for Codespaces and GitHub Packages.

In March, we experienced several incidents resulting in significant impact to multiple GitHub services.

In February, we experienced one incident resulting in significant impact to multiple GitHub services.

In January, we experienced no incidents resulting in service downtime to our core services.

In December, we experienced no incidents resulting in service downtime to our core services.

In November, we experienced one incident resulting in significant impact and degraded state of availability for multiple services.

In October, we experienced one incident resulting in significant impact and degraded state of availability for the GitHub Codespaces service.

In September, we experienced no incidents resulting in service downtime to our core services.

In August, we experienced two distinct incidents resulting in significant impact and degraded state of availability for Git operations, API requests, webhooks, issues, pull requests, GitHub Pages, GitHub Packages, and GitHub Actions services.

In July, GitHub experienced no incidents resulting in service downtime to our core services.

In June, we experienced no incidents resulting in service downtime to our core services.

In May, we experienced two incidents resulting in significant impact to multiple GitHub services.

In April, we experienced two incidents resulting in significant impact and degraded state of availability for API requests and the GitHub Packages service, specifically the GitHub Packages Container registry service.…

In March, we experienced three incidents resulting in significant impact and degraded state of availability for issues, pull requests, webhooks, API requests, GitHub Pages, and GitHub Actions services. Follow up…

Introduction In February, we experienced no incidents resulting in service downtime to our core services. This month’s GitHub Availability Report will provide initial details around an incident from March 1…