Search results for: Availability Report

In August, we experienced one incident resulting in significant impact to Codespaces. We’re still investigating that incident and will include it in next month’s report. This report also sheds light into an incident that impacted Codespaces in July.

In July, we experienced one incident that resulted in degraded performance for Codespaces. This report also acknowledges two incidents that impacted multiple GitHub.com services in June.

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.

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…

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)…

In December, we experienced no incidents resulting in service downtime. This month’s GitHub Availability Report will provide a summary and follow-up details on how we addressed an incident mentioned in November’s report.