Search results for: availability

In August, we experienced five incidents that resulted in degraded performance across GitHub services.

More GitHub Enterprise Cloud customers can now start a self-serve GitHub Advanced Security trial to evaluate GitHub Code Security and GitHub Secret Protection. Eligibility has expanded from enterprises with up…

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.

GitHub Enterprise Cloud with Enterprise Managed Users (EMUs) can now enforce GitHub’s native IP allow list configuration across user namespaces. This feature is now generally available. EMUs allow the enterprise…

Editor’s note (June 5, 2026): Removed the waitlist link and updated the links to the GitHub Copilot app. The GitHub Copilot app technical preview is now available to all existing…

In April, we experienced 10 incidents that resulted in degraded performance across GitHub services.

Here’s what we’ve done—and what we’re still doing—to improve our availability and reliability.

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.

GitHub recently experienced several availability incidents. We understand the impact these outages have on our customers and are sharing details on the stabilization work we’re prioritizing right now.

Here’s how we made the search experience better, faster, and more resilient for GHES customers.

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.