Several services are degraded
Update - We are working towards a mitigation that will allow us to resume processing enterprise migrations.
Oct 06, 2026 - 21:29 UTC
Investigating - All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
Oct 06, 2026 - 20:57 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Oct 06, 2026 - 20:26 UTC
Update - A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
Oct 06, 2026 - 20:22 UTC
Update - Pull Requests is operating normally.
Oct 06, 2026 - 20:12 UTC
Update - Webhooks is operating normally.
Oct 06, 2026 - 20:04 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests and Webhooks
Oct 06, 2026 - 19:57 UTC

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.

No incidents or maintenance related to this downtime.

Oct 6, 2026

Disruption with some GitHub services
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 6, 01:32 UTC
Update - Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
Oct 6, 00:05 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 5, 23:47 UTC

Oct 5, 2026

Incident with Actions
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 5, 22:49 UTC
Update - Pages is operating normally.
Oct 5, 22:40 UTC
Update - Actions is operating normally.
Oct 5, 21:54 UTC
Update - We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
Oct 5, 21:32 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Oct 5, 21:31 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.
Oct 5, 21:22 UTC
Update - In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
Oct 5, 21:09 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.
Oct 5, 20:47 UTC
Update - We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
Oct 5, 20:39 UTC
Update - We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
Oct 5, 19:50 UTC
Update - We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
Oct 5, 19:15 UTC
Investigating - We are investigating reports of degraded performance for Actions
Oct 5, 19:11 UTC

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

No incidents reported.

Oct 1, 2026

Actions Job Delays
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, 17:56 UTC
Update - GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.
Oct 1, 17:50 UTC
Update - We are currently applying a mitigation and anticipate recovery within thirty minutes.
Oct 1, 16:48 UTC
Update - We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.
Oct 1, 16:10 UTC
Update - We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.
Oct 1, 15:29 UTC
Investigating - Actions is experiencing degraded performance. We are continuing to investigate.
Oct 1, 15:20 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Oct 1, 15:10 UTC
Update - Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.
Oct 1, 15:02 UTC
Update - We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.
Oct 1, 14:54 UTC
Investigating - We are investigating reports of degraded performance for Actions
Oct 1, 14:47 UTC
Elevated request latency
Resolved - On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returned to normal as the traffic subsided, and we have since applied additional traffic filtering to protect against similar traffic. We are improving alerting for delays in our traffic-handling infrastructure and strengthening our automated traffic protections to reduce our time to detection and mitigation.
Oct 1, 13:57 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
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
Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 1, 13:37 UTC
[Retroactive] Actions workflow run failures after deployment gate approvals
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

Sep 30, 2026

No incidents reported.

Sep 29, 2026

No incidents reported.

Sep 28, 2026

Copilot Code Review is unable to complete reviews
Resolved - On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot Code Review needs to complete a review. Review completion is an inherently delayed signal, because each review job takes time to start and finish, so it took longer to detect the impact.

We mitigated the incident by reverting the change.

We are working to add a faster signal for reviews that fail to complete, add deployment validation that confirms a Copilot Code Review completes end to end, improve how we track internal dependencies between services, and make our deployment pipeline more reliable to reduce our time to detection and mitigation of issues like this one in the future.
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
Update - Revert of the impacted change is in flight, expect full recovery once the deployment is done.
Sep 28, 21:23 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
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

Disruption with billing information updates
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
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
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
Update - We are continuing to work on mitigation. We will post another update in approximately one hour.
Sep 24, 18:22 UTC
Update - We have identified the problem and are actively working on mitigation.
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
Investigating - We are investigating reports of impacted performance for some GitHub services.
Sep 24, 16:51 UTC
Incident across several services
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
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
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
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
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
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
Update - We are preparing to deploy a change that will mitigate the impact.
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
Update - We will post another update in approximately one hour to share our progress.
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
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
Update - We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
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
Update - Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
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
Investigating - We are investigating reports of degraded performance for API Requests
Sep 23, 10:11 UTC

Sep 23, 2026

Sep 22, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage