All Systems Operational
About This Site
Check GitHub Enterprise Cloud status by region:
- Australia: au.githubstatus.com
- EU: eu.githubstatus.com
- Japan: jp.githubstatus.com
- US: us.githubstatus.com
Uptime over the past 90 days. View historical uptime.
Git Operations
Operational
Webhooks
Operational
Visit www.githubstatus.com for more information
Operational
API Requests
Operational
Issues
Operational
Pull Requests
Operational
Actions
Operational
Packages
Operational
Pages
Operational
Copilot
Operational
Codespaces
Operational
Copilot AI Model Providers
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Oct 1, 2026
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Oct 1, 13:57 UTC
Oct 1, 13:57 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Oct 1, 13:51 UTC
Oct 1, 13:51 UTC
Update -
We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available.
Oct 1, 13:39 UTC
Oct 1, 13:39 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Oct 1, 13:37 UTC
Oct 1, 13:37 UTC
Resolved -
On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval.
If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already completed to avoid repeating changes.
Oct 1, 02:00 UTC
If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already completed to avoid repeating changes.
Oct 1, 02:00 UTC
Sep 30, 2026
No incidents reported.
Sep 29, 2026
No incidents reported.
Sep 28, 2026
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Sep 28, 22:08 UTC
Sep 28, 22:08 UTC
Update -
Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.
Sep 28, 22:08 UTC
Sep 28, 22:08 UTC
Update -
Revert of the impacted change is in flight, expect full recovery once the deployment is done.
Sep 28, 21:23 UTC
Sep 28, 21:23 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Sep 28, 21:16 UTC
Sep 28, 21:16 UTC
Sep 27, 2026
No incidents reported.
Sep 26, 2026
No incidents reported.
Sep 25, 2026
No incidents reported.
Sep 24, 2026
Resolved -
Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests failed at an average rate of 69.3%, reaching 100% at peak.
An operating system upgrade exposed a compatibility issue in an adapter used by our HTTP client library, causing requests to stall. A subsequent change to shorten request timeouts caused stalled requests to return connection errors and increased the failure rate.
We mitigated the incident on September 24, 2026 at 20:24 UTC by changing the HTTP client used for address validation. We have added alerting to detect similar issues sooner and are extending the fix to other integrations.
Sep 24, 20:41 UTC
An operating system upgrade exposed a compatibility issue in an adapter used by our HTTP client library, causing requests to stall. A subsequent change to shorten request timeouts caused stalled requests to return connection errors and increased the failure rate.
We mitigated the incident on September 24, 2026 at 20:24 UTC by changing the HTTP client used for address validation. We have added alerting to detect similar issues sooner and are extending the fix to other integrations.
Sep 24, 20:41 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Sep 24, 20:24 UTC
Sep 24, 20:24 UTC
Update -
We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.
Sep 24, 20:10 UTC
Sep 24, 20:10 UTC
Update -
We are continuing to work on mitigation. We will post another update in approximately one hour.
Sep 24, 18:22 UTC
Sep 24, 18:22 UTC
Update -
We have identified the problem and are actively working on mitigation.
Sep 24, 17:40 UTC
Sep 24, 17:40 UTC
Update -
We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.
Sep 24, 16:51 UTC
Sep 24, 16:51 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Sep 24, 16:51 UTC
Sep 24, 16:51 UTC
Resolved -
Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed label updates and stale search results in Projects.
The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by 10:58 UTC on September 23. Projects' processing continued to recover while an accumulated backlog was drained, and full service was restored at 04:55 UTC on September 24.
The incident was caused by a failed planned maintenance operation on a primary database. Automated recovery initiated an emergency database failover, after which several replicas in the affected region were unable to resume replication correctly. This reduced available database capacity and caused the API errors and downstream Projects processing delays.
We have mitigated the immediate failure mode. We are also improving maintenance safety checks, database failover handling, post-failover replica validation, and downstream processing resilience to reduce the likelihood and impact of similar incidents.
Sep 24, 04:55 UTC
The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by 10:58 UTC on September 23. Projects' processing continued to recover while an accumulated backlog was drained, and full service was restored at 04:55 UTC on September 24.
The incident was caused by a failed planned maintenance operation on a primary database. Automated recovery initiated an emergency database failover, after which several replicas in the affected region were unable to resume replication correctly. This reduced available database capacity and caused the API errors and downstream Projects processing delays.
We have mitigated the immediate failure mode. We are also improving maintenance safety checks, database failover handling, post-failover replica validation, and downstream processing resilience to reduce the likelihood and impact of similar incidents.
Sep 24, 04:55 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Sep 24, 04:55 UTC
Sep 24, 04:55 UTC
Update -
We are continuing to process the backlog of issue label updates for Projects. Label changes may still be delayed. All other services are operating normally.
Sep 24, 03:14 UTC
Sep 24, 03:14 UTC
Update -
We are continuing to process the backlog of issue label updates for Projects. Users may still see delays before label changes are reflected in Projects. All other services are operating normally.
Sep 24, 02:00 UTC
Sep 24, 02:00 UTC
Update -
We've deployed a change intended to accelerate processing of the backlog of issue label updates in Projects. A sizable backlog still remains and we continue working through it. All other services are operating normally. We will provide another update within the next hour.
Sep 24, 00:16 UTC
Sep 24, 00:16 UTC
Update -
Updates to issue labels may be delayed in being reflected in Projects. We are continuing to deploy a change that will accelerate processing of the backlog of label updates. All other services are available. We will provide another update within the next hour.
Sep 23, 21:39 UTC
Sep 23, 21:39 UTC
Update -
We are preparing to deploy a change that will mitigate the impact.
Sep 23, 20:26 UTC
Sep 23, 20:26 UTC
Update -
Continuing to investigate the lag that may be experienced in issue labels being accurately reflected in Projects. We are working on alternate solutions to process the backlog of label updates.
Sep 23, 18:42 UTC
Sep 23, 18:42 UTC
Update -
We will post another update in approximately one hour to share our progress.
Sep 23, 17:30 UTC
Sep 23, 17:30 UTC
Update -
Updates to issue labels may be delayed in being reflected in Projects by about ~10 minutes. We have added some capacity to work through the backlog more quickly, but it'll likely be a few hours to complete processing the full backlog of messages. All other services are available.
Sep 23, 17:01 UTC
Sep 23, 17:01 UTC
Update -
Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.
Sep 23, 13:35 UTC
Sep 23, 13:35 UTC
Update -
We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
Sep 23, 11:38 UTC
Sep 23, 11:38 UTC
Update -
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Sep 23, 10:58 UTC
Sep 23, 10:58 UTC
Update -
Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
Sep 23, 10:57 UTC
Sep 23, 10:57 UTC
Update -
Database replicas have detached. We're working to restore the database replicas. Users may experience issues beyond creating organizations and a degraded experience with the GitHub API and Projects.
Sep 23, 10:20 UTC
Sep 23, 10:20 UTC
Investigating -
We are investigating reports of degraded performance for API Requests
Sep 23, 10:11 UTC
Sep 23, 10:11 UTC
Sep 23, 2026
Sep 22, 2026
No incidents reported.
Sep 21, 2026
No incidents reported.
Sep 20, 2026
Resolved -
On September 20, 2026, between 21:46 and 22:24 UTC the Pull Requests service was degraded and pull request merge and test-merge commits were created late, with delays reaching approximately four minutes at peak. Merge commits were delayed rather than lost. Because some Actions workflow runs start only after a pull request's merge commit is created, a subset of workflow runs for pull request events were also delayed.
This was due to a routine repository maintenance job for an unusually large repository consuming nearly all of the memory on a single Git storage server, which left that server unable to serve the Git operations used to create merge commits.
We mitigated the incident by removing the affected server from service at 22:18 UTC, after which the queued merge commits were created within six minutes.
We have capped the memory a single repository maintenance job may consume so that one repository cannot exhaust a server, and we have improved monitoring and alerting on storage server health to reduce our time to detection and mitigation of issues like this one in the future.
Sep 20, 23:22 UTC
This was due to a routine repository maintenance job for an unusually large repository consuming nearly all of the memory on a single Git storage server, which left that server unable to serve the Git operations used to create merge commits.
We mitigated the incident by removing the affected server from service at 22:18 UTC, after which the queued merge commits were created within six minutes.
We have capped the memory a single repository maintenance job may consume so that one repository cannot exhaust a server, and we have improved monitoring and alerting on storage server health to reduce our time to detection and mitigation of issues like this one in the future.
Sep 20, 23:22 UTC
Update -
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
Sep 20, 22:32 UTC
Sep 20, 22:32 UTC
Monitoring -
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Sep 20, 22:27 UTC
Sep 20, 22:27 UTC
Investigating -
We are investigating reports of degraded performance for Pull Requests
Sep 20, 22:13 UTC
Sep 20, 22:13 UTC
Sep 19, 2026
No incidents reported.
Sep 18, 2026
No incidents reported.
Sep 17, 2026
Resolved -
Between 20:26 and 21:17 UTC on September 17, 2026, GitHub Copilot experienced degradation affecting several GPT models, including GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-5.3-Codex, and GPT-6 Astra. Users encountered elevated error rates when using these models.
The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.
Sep 17, 21:49 UTC
The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.
Sep 17, 21:49 UTC
Monitoring -
We are experiencing degraded availability for GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-6 Astra, GPT-5.3-Codex in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. The provider is working to mitigate the problem and we are monitoring recovery. We recommend choosing another model or selecting 'Auto' to continue using Copilot.
Sep 17, 21:39 UTC
Sep 17, 21:39 UTC
Investigating -
We are investigating reports of degraded performance for Copilot AI Model Providers
Sep 17, 20:59 UTC
Sep 17, 20:59 UTC
