GitHub Availability Report

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.

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.