Search results for: Availability Report

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.