Enhanced Two-Factor Authentication (2FA) experience is now Generally Available. Previously, we had announced a set of improvements in our public beta. Further to this we have made the following new…
In June, we experienced four incidents resulting in significant impact to multiple GitHub.com services. This report also sheds light into an incident that impacted several GitHub.com services in May.
In May, we experienced three distinct incidents resulting in significant impact to multiple services across GitHub.com. This report also sheds light into the billing incident that impacted Actions and Codespaces users in April.
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.
Maintainers can now manage the repository-level “Allow auto-merge” setting. This setting, which is off by default, controls whether auto-merge is available on pull requests in the repository. Previously, only admins…
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…
GitHub Advanced Security helps you create secure applications with a community-driven, developer-first approach. Today, we are excited to announce two updates: Beta of the new security overview for organizations and…
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…
Introduction In January, we experienced one incident resulting in significant impact and degraded state of availability for the GitHub Actions service. January 28 04:21 UTC (lasting 3 hours 53 minutes)…
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Last chance: Save $700 on your IRL pass to Universe and join us on Oct. 28-29 in San Francisco.
