GitHub availability report: July 2026
In July, we experienced eight incidents that resulted in degraded performance across GitHub services.
Author
JO
Jakub Oleksy
55 articles by Jakub Oleksy.
55 articles by Jakub Oleksy.
In July, we experienced eight incidents that resulted in degraded performance across GitHub services.
In June, we experienced six incidents that resulted in degraded performance across GitHub services.
In May, we experienced nine incidents that resulted in degraded performance across GitHub services.
In April, we experienced 10 incidents that resulted in degraded performance across GitHub services.
Changes to the status page will provide more specific data, so you’ll have better insight into the overall health of the platform.
In March, we experienced four incidents that resulted in degraded performance across GitHub services.
In February, we experienced six incidents that resulted in degraded performance across GitHub services.
In January, we experienced two incidents that resulted in degraded performance across GitHub services.
In December, we experienced five incidents that resulted in degraded performance across GitHub services.
In November, we experienced three incidents that resulted in degraded performance across GitHub services.
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
In September, we experienced three incidents that resulted in degraded performance across GitHub services.
In August, we experienced three incidents that resulted in degraded performance across GitHub services.
In July, we experienced one incident that resulted in degraded performance across GitHub services.
In June, we experienced three incidents that resulted in degraded performance across GitHub services.
In May, we experienced three incidents that resulted in degraded performance across GitHub services.
In April, we experienced three incidents that resulted in degraded performance across GitHub services.
In March, we experienced one incident that resulted in degraded performance across GitHub services.
In February, we experienced two incidents that resulted in degraded performance across GitHub services.
In January, we experienced two incidents that resulted in degraded performance across GitHub services.
In December, we experienced two incidents that resulted in degraded performance across GitHub services.
In November, we experienced one incident that resulted in degraded performance across GitHub services.
In October, we experienced one incident that resulted in degraded performance across GitHub services.
In September, we experienced three incidents that resulted in degraded performance across GitHub services.
In August, we experienced one incident that resulted in degraded performance across GitHub services.
In July, we experienced four incidents that resulted in degraded performance across GitHub services.
In June, we experienced two incidents that resulted in degraded performance across GitHub services.
In May, we experienced one incident that resulted in degraded performance across GitHub services.
In April, we experienced four incidents that resulted in degraded performance across GitHub services.
In March, we experienced two incidents that resulted in degraded performance across GitHub services.
In February, we experienced two incidents that resulted in degraded performance across GitHub services.
In January, we experienced three incidents that resulted in degraded performance across GitHub services.
In December, we experienced three incidents that resulted in degraded performance across GitHub services.
In November, we experienced one incident that resulted in degraded performance across GitHub services.
In October, we experienced two incidents that resulted in degraded performance across GitHub services.
In September, we experienced two incidents that resulted in degraded performance across GitHub services.
In August, we experienced two incidents that resulted in degraded performance across GitHub services.
In July, we experienced one incident that resulted in degraded performance across GitHub services.
In June, we experienced two incidents that resulted in degraded performance across GitHub services. June 7 16:11 UTC (lasting 2 hours 28 minutes) On June 7 at 16:11 UTC, GitHub…
In May, we experienced four incidents that resulted in degraded performance across GitHub services. This report also sheds light into three April incidents that resulted in degraded performance across GitHub services.
In April, we experienced four incidents that resulted in degraded performance across GitHub services. This report also sheds light into three March incidents that resulted in degraded performance across GitHub services.
In March, we experienced six incidents that resulted in degraded performance across GitHub services. This report also sheds light into a February incident that resulted in degraded performance for GitHub Codespaces.
In February, we experienced three incidents that resulted in degraded performance across GitHub services. This report also sheds light into a January incident that resulted in degraded performance for GitHub Packages and GitHub Pages and another January incident that impacted Git users.
In January, we experienced two incidents, one that resulted in degraded performance for Packages and Pages and another that impacted Git users.
In December, we did not experience any incidents that resulted in degraded performance across GitHub services. This report sheds light into an incident that impacted customers using GitHub Packages and GitHub Pages in November.
In November, we experienced two incidents that resulted in degraded performance across GitHub services. This report also sheds light into an incident that impacted Codespaces in October.
In October, we experienced four incidents that resulted in degraded performance across GitHub services. This report also sheds light into an incident that impacted Codespaces in September.
In September, we experienced one incident that resulted in degraded performance across GitHub services. We also experienced one incident resulting in significant impact to Codespaces. We are 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 August and an incident that impacted Actions in August.
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.