GitHub Enterprise Cloud

All Systems Operational

About This Site

For the status of GitHub.com, please visit: githubstatus.com

Git Operations Operational

Webhooks Operational

API Requests Operational

Issues Operational

Pull Requests Operational

Actions Operational

Packages Operational

Pages Operational

Copilot Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Past Incidents

Jul 15, 2025

No incidents reported today.

Jul 14, 2025

No incidents reported.

Jul 13, 2025

No incidents reported.

Jul 12, 2025

No incidents reported.

Jul 11, 2025

No incidents reported.

Jul 10, 2025

No incidents reported.

Jul 9, 2025

EU - Incident with Actions

Resolved - On July 9th, 2025, between 14:20 UTC and 16:56 UTC, GitHub Actions was degraded. During this period, 2% of in-progress workflow runs failed and 21% workflow runs failed to start. This incident was caused by a deployment issue where a failed update to our container infrastructure prevented some of the service instances from restarting properly, resulting in reduced capacity in one of the core Actions services. We are implementing safeguards to prevent this failure mode and have added additional monitoring to reduce detection and mitigation time for similar incidents in the future.
Jul 9, 16:52 UTC

Update - Actions is operating normally.
Jul 9, 16:51 UTC

Investigating - We are investigating reports of degraded performance for Actions
Jul 9, 16:31 UTC

Jul 8, 2025

No incidents reported.

Jul 7, 2025

No incidents reported.

Jul 6, 2025

No incidents reported.

Jul 5, 2025

No incidents reported.

Jul 4, 2025

No incidents reported.

Jul 3, 2025

EU - Disruption with some GitHub services

Resolved - On 7/3/2025, between 5:21:17 AM and 7:11:49 AM UTC, customers were prevented from SSO authorizing Personal Access Tokens and SSH keys via the GitHub UI. Approximately 1300 users were impacted.

A code change modified the content type of the response returned by the server, causing a lazily-loaded dropdown to fail to render, prohibiting the user from proceeding to authorize. No authorization systems were impacted during the incident, only the UI component. We mitigated the incident by reverting the code change that introduced the problem.

We are making improvements to our release process and test coverage to catch this class of error earlier in our deployment pipeline. Further, we are improving monitoring to reduce our time to detection and mitigation of issues like this one in the future.

Jul 3, 07:12 UTC

Update - The rollback has been deployed successfully on all environments. Customers should now be able to SSO authorize their Classic Personal Access Tokens and SSH keys on their GitHub organizations.
Jul 3, 07:11 UTC

Update - The root cause for the rendering bug that prevented customers from SSO authorizing Personal Access Tokens and SSH keys has started rolling out. We are continuously monitoring this rollback.
Jul 3, 06:46 UTC

Update - We have identified the root cause for the rendering bug that prevented customers from SSO authorizing Personal Access Tokens and SSH keys.The changes that caused the issue are being rolled back.
Jul 3, 06:07 UTC

Update - We are investigating an issue with SSO authorizing Classic Personal Access Tokens and SSH keys.
Jul 3, 05:45 UTC

Investigating - We are currently investigating this issue.
Jul 3, 05:39 UTC

Jul 2, 2025

EU - Disruption with some GitHub services

Resolved - On July 2nd, 2025, between approximately 08:40 and 10:16 UTC, the Copilot service experienced degradation due to an infrastructure issue which impacted the Claude Sonnet 4 model, leading to a spike in errors. No other models were impacted.

The issue was mitigated by rebalancing load within our infrastructure. GitHub is working to further improve the resiliency of the service to prevent similar incidents in the future.
Jul 2, 10:16 UTC

Update - We are no longer experiencing degradation—Claude Sonnet 4 is once again available in Copilot Chat and across IDE integrations.

We will continue monitoring to ensure stability, but mitigation is complete.
Jul 2, 10:16 UTC

Investigating - We are currently investigating this issue.
Jul 2, 09:57 UTC

Jul 1, 2025

No incidents reported.