Incident with Actions
Update - We are continuing to work on an issue affecting multiple GitHub services.

Workflow runs are still failing, and jobs may remain queued for an extended period before starting or may time out. Jobs using GitHub-hosted runners are particularly affected while capacity is constrained.

Customers using self-hosted runners may see errors or rate limiting when runners register.

Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed.

Recovery is taking longer than we expected, and engineers remain actively engaged.
Aug 06, 2026 - 18:46 UTC
Update - We are continuing to work on an issue affecting multiple GitHub services.

Workflow runs are still failing or delayed in starting, and some queued jobs may time out.

Customers using self-hosted runners may see errors or rate limiting when runners register.

Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected.

Webhook deliveries may be delayed.

Engineers have applied further mitigations and are continuing to work towards full recovery.
Aug 06, 2026 - 18:11 UTC
Update - We are continuing to work on an issue affecting multiple GitHub services.

Workflow runs are failing or delayed in starting, and some queued jobs may time out.

Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected.

Webhook deliveries may be delayed.

Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now.
Aug 06, 2026 - 17:40 UTC
Update - We are continuing to work on the issue affecting GitHub Actions.

Workflow runs are still failing or delayed in starting, and some queued jobs may time out.

Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures.

Our engineers have applied several mitigations and are rolling out a further fix now.
Aug 06, 2026 - 17:02 UTC
Update - Actions and Pages are experiencing degraded availability. We are continuing to investigate.
Aug 06, 2026 - 16:33 UTC
Update - We are continuing to work on the issue affecting GitHub Actions.

Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors.

Customers running migrations with GitHub Enterprise Importer may also see failures.

Engineers are actively working towards full recovery.
Aug 06, 2026 - 16:27 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.
Aug 06, 2026 - 16:27 UTC
Update - Pages is operating normally.
Aug 06, 2026 - 16:19 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.
Aug 06, 2026 - 15:53 UTC
Update - We are investigating errors affecting GitHub Actions. Some workflow runs are failing to start or failing partway through, and some requests to the Actions REST API are returning errors.

Some customers may also see unexpected rate limiting in their workflows.

Engineers have identified the source of the disruption and are actively working on a mitigation
Aug 06, 2026 - 15:45 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.
Aug 06, 2026 - 15:41 UTC
Investigating - We are investigating reports of degraded performance for Actions
Aug 06, 2026 - 15:22 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
90 days ago
99.99 % uptime
Today
Webhooks Operational
90 days ago
100.0 % uptime
Today
Visit www.githubstatus.com for more information Operational
API Requests Operational
90 days ago
99.91 % uptime
Today
Issues Operational
90 days ago
99.98 % uptime
Today
Pull Requests Operational
90 days ago
99.98 % uptime
Today
Actions Major Outage
90 days ago
99.66 % uptime
Today
Packages Operational
90 days ago
100.0 % uptime
Today
Pages Major Outage
90 days ago
99.88 % uptime
Today
Copilot Operational
90 days ago
99.93 % uptime
Today
Codespaces Operational
90 days ago
99.97 % uptime
Today
Copilot AI Model Providers Operational
90 days ago
99.88 % uptime
Today
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.

Aug 6, 2026

Incident with Pages - Deployment Lag
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.
Aug 6, 16:22 UTC
Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
Aug 6, 15:50 UTC
Investigating - We are investigating reports of degraded performance for Pages
Aug 6, 15:03 UTC

Aug 5, 2026

Some Copilot Cloud Agent jobs not starting
Resolved - On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected.

The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic.

We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.
Aug 5, 13:00 UTC
Update - Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
Aug 5, 12:10 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Aug 5, 12:01 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Aug 5, 11:38 UTC

Aug 4, 2026

No incidents reported.

Aug 3, 2026

Incident with Copilot
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.
Aug 3, 11:25 UTC
Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
Aug 3, 11:19 UTC
Update - We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.
Aug 3, 10:35 UTC
Update - We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.
Aug 3, 09:54 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Aug 3, 09:53 UTC

Aug 2, 2026

No incidents reported.

Aug 1, 2026

Incident with Copilot AI Model Providers
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.
Aug 1, 18:44 UTC
Update - The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces.

We will continue monitoring to ensure stability, but mitigation is complete.
Aug 1, 18:23 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Aug 1, 18:20 UTC
Update - We are experiencing degraded availability for the Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Aug 1, 18:20 UTC
Update - We are seeing increased error rates from specific upstream AI Model Providers
Aug 1, 18:03 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Aug 1, 18:03 UTC
Degraded availability GPT 5.6 Luna
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.
Aug 1, 12:30 UTC
Update - The issues with our upstream model provider have been resolved, and GPT-5.6 Luna is once again available in Copilot products and IDE surfaces.
We will continue monitoring to ensure stability, but mitigation is complete.
Aug 1, 12:29 UTC
Update - We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability.
Aug 1, 12:13 UTC
Update - We are experiencing degraded availability for the GPT-5.6 Luna model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot
Aug 1, 11:20 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Aug 1, 11:16 UTC

Jul 31, 2026

No incidents reported.

Jul 30, 2026

Copilot model Claude Fable 5 experiencing elevated errors
Resolved - On July 30, 2026, the Claude Fable 5 model in GitHub Copilot experienced degraded availability for approximately 73 minutes, from 08:33 to 09:46 UTC. During this time, requests to Claude Fable 5 in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for Claude Fable 5 fully recovered once the provider resolved their outage at 09:46 UTC, and we confirmed resolution at 10:12 UTC.
Jul 30, 10:12 UTC
Update - The issues with our upstream model provider have been resolved, and Claude Fable 5 is once again available in Copilot products and IDE surfaces.

We will continue monitoring to ensure stability, but mitigation is complete.
Jul 30, 10:11 UTC
Update - We are experiencing degraded availability for the Claude Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jul 30, 09:17 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Jul 30, 09:07 UTC

Jul 29, 2026

Incident with Copilot AI Model Providers
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.
Jul 29, 21:51 UTC
Update - The external ai model provider has resolved the issues, and we have verified Copilot's traffic is fully recovered.
Jul 29, 21:51 UTC
Update - The external AI model provider is continuing to investigate.
Jul 29, 21:08 UTC
Update - The external AI model provider has identified the issue and is working to resolve.
Jul 29, 20:38 UTC
Update - We are investigating increased error rates affecting GitHub Copilot requests to external AI model providers. Some users may experience failures or degraded performance when using Copilot features.
Jul 29, 20:18 UTC
Update - We are seeing increased error rates with requests to specific model providers.
Jul 29, 20:07 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Jul 29, 20:07 UTC
Incident with Actions
Resolved - On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an under-provisioned internal Actions service in that site: under increased load its instances ran out of memory and became unresponsive, and because Actions API requests wait synchronously on that service, requests routed through the affected site stalled and timed out. During the incident, approximately 2% of workflows were delayed. Requests served by other sites remained unaffected. Both standard and larger hosted runners routed through the affected site could see delayed job starts.

The issue was mitigated by scaling out the runner-administration service in the affected site and increasing the replica count, which restored API availability and returned workflow run starts to normal. We are working to add horizontal autoscaling, memory-saturation alerting, and scaling-forecast monitoring for this service, along with responder playbooks, to reduce the likelihood of similar issues in the future.
Jul 29, 16:00 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 29, 15:40 UTC
Update - We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure.
Jul 29, 15:34 UTC
Investigating - We are investigating reports of degraded availability for Actions
Jul 29, 15:26 UTC

Jul 28, 2026

No incidents reported.

Jul 27, 2026

Incident with GraphQL API Requests
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.
Jul 27, 04:09 UTC
Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Jul 27, 04:09 UTC
Investigating - We are investigating reports of degraded performance for API Requests
Jul 27, 03:53 UTC

Jul 26, 2026

No incidents reported.

Jul 25, 2026

Actions run failures and delays
Resolved - Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8
Jul 25, 13:13 UTC
Update - We have seen recovery in GitHub Actions performance following our earlier mitigation. Workflow runs are processing normally, though jobs queued before 12:40 UTC may still experience failures and will need to be retried.
Jul 25, 13:12 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 25, 12:59 UTC
Update - We have applied a mitigation for the infrastructure issue affecting GitHub Actions. Workflow run failures and delays are improving but not yet fully resolved. Our engineering team continues to work on restoring full functionality across all affected infrastructure.
Jul 25, 12:58 UTC
Update - We are experiencing issues with GitHub Actions that are causing workflow run failures and delays for some users. Our engineering team is actively investigating the infrastructure issue and working to restore full functionality.
Jul 25, 12:34 UTC
Investigating - We are investigating reports of degraded availability for Actions
Jul 25, 12:31 UTC
Several GPT models degraded
Resolved - On July 25, 2026, between 09:07 and 10:04 UTC, the GPT-5.2, GPT-5.3-Codex, GPT-5.4, GPT-5.4 Mini, GPT-5.6 Sol, GPT-5.6 Terra and GPT-5.6 Luna models experienced degraded availability in GitHub Copilot products and IDE surfaces. Requests to these models had an average failure rate of 5.6%. Other Copilot models remained available as alternatives.

The degradation was caused by an issue with an upstream model provider. Success rates returned to normal after the upstream issue was mitigated, and we continued monitoring before resolving the incident. We are working on improving the automated failover for the affected models to prevent similar incidents in the future.
Jul 25, 10:11 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Jul 25, 10:04 UTC
Update - We are experiencing degraded availability for the GPT-5.2, GPT-5.3-Codex, GPT-5.4, GPT-5.4 Mini, GPT-5.6 Sol, GPT-5.6 Terra, and GPT-5.6 Luna models in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jul 25, 09:48 UTC
Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers
Jul 25, 09:42 UTC
Incident with Actions
Resolved - On July 25, 2026, GitHub Actions experienced two related periods of degradation that caused some workflow runs to be delayed by more than 5 minutes or end with infrastructure failures.

First period (08:45 – 09:13 UTC): During planned maintenance on a critical-path Redis cluster for Actions, one participating region was left in a degraded state. Separately, an independent capacity operation temporarily removed another region from the cluster and redirected its traffic to the degraded region. This created cross-region inconsistencies in job-assignment state, causing workflow runs to be delayed, exhaust retries, or fail outright. At peak, about 7% of runs were delayed by more than 5 minutes, and 25% of runs failed with an infrastructure error during the course of the incident. We mitigated the incident at 09:13 UTC by returning traffic to its normal distribution.

Second period (12:08 – 12:48 UTC): As part of mitigating the first incident, traffic was returned to the regional instance that was still undergoing its capacity increase. Multiple Redis nodes in the scaling region experienced failures, increasing traffic to healthy nodes and causing connection limits to be reached on many nodes. At peak, 30% of runs were delayed by more than 5 minutes, and 60% of runs failed with an infrastructure error during the course of the incident. We mitigated the incident at 12:48 UTC by redirecting workflow traffic away from the scaling region.

We are adding stronger regional health and capacity checks before maintenance and requiring a stable observation period before restoring traffic. We are also improving automated connection resiliency, and partnering with our platform dependency to automatically detect and remediate unhealthy cluster members and shard imbalance. More generally, we already had work underway to improve the resiliency and scale of this piece of Actions infrastructure.
Jul 25, 09:25 UTC
Update - We identified an issue causing delays in GitHub Actions run starts. Some users may have experienced longer than expected wait times when triggering workflow runs. We have applied mitigations and have recovered. Our team continues to monitor and investigate the root cause.
Jul 25, 09:20 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 25, 09:13 UTC
Investigating - We are investigating reports of degraded performance for Actions
Jul 25, 08:59 UTC

Jul 24, 2026

Incident with Pull Requests
Resolved - Between July 24, 19:17 UTC and July 24, 20:02 UTC, users were unable to create pull requests due to a database schema change. In total, 113,930 pull request creation attempts were impacted across 50,904 users, with an average error rate of 1.75% and a maximum error rate of 2.25% for all requests to Pull Requests service. Existing pull requests and other GitHub functionality were not affected. The issue was resolved by reverting the change to the affected database, upon which pull request creation immediately resumed.

The root cause was related to a backfill workflow into the Vitess keyspace hosting Pull Request data. The backfill Vitess command encountered errors and increased VReplication lag, and the workflow was canceled at 19:17 UTC. The cancellation executed a misunderstood Vitess codepath that dropped the backing table to the target keyspace, leaving a non-existent reference that resulted in errors creating Pull Requests. The mitigation was executing a command to drop the vschema reference to the dropped table, allowing Pull Request creation to resume.

We are adding stronger pre-flight validation to our tooling to prevent similar issues and expanding lower-environment support to provide better test coverage end-to-end before promoting them to production. We're also fixing our backfill migration tooling to protect from this specific codepath.
Jul 24, 20:23 UTC
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Jul 24, 20:02 UTC
Update - We have applied a mitigation and are monitoring for recovery
Jul 24, 19:59 UTC
Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.
Jul 24, 19:43 UTC
Update - We are investigating errors creating pull requests
Jul 24, 19:40 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Jul 24, 19:37 UTC
Disruption with some GitHub services
Resolved - On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in each compute cage, and an aggregation layer interconnecting the spines from each cage within each AZ. The loss of connectivity affected links between one cage’s spine switches and the aggregation layer within that specific AZ.

Workloads depending on compute resources in this cage became degraded due to packet loss, and exhibited intermittent errors:

- Actions saw 10% of jobs fail during the impact window, and 5% of jobs succeeded but with delayed starts.
- 27% of GitHub issues interactions saw slow requests or timeouts.
- 4% of GitHub Copilot requests experienced errors, though most automatically retry.
- 4% of git push operations saw impacts during the affected window.
- Authentication requests saw increased latency during the affected window, but error rates, while elevated, were < 1% in all cases.

We were able to mitigate the outage by re-routing affected connections to available fiber paths that were allocated for future capacity upgrades. Sufficient network capacity to eliminate packet loss was restored at 17:07, with most services showing full recovery by 17:16. All paths were restored and services healthy at 17:36.

This incident affected 25% of available network interconnect capacity. Older cages utilize a 100Gbps network interface standard. To remove risk of reoccurrence, a planned upgrade to 400Gbps interfaces is being accelerated as much as possible, ensuring increased bandwidth available at all layers of the switch fabric for resiliency to path or device loss.
Jul 24, 17:36 UTC
Update - We are seeing recovery across all services
Jul 24, 17:24 UTC
Update - The degradation affecting API Requests, Actions, Copilot, Issues, Pages and Pull Requests has been mitigated. We are monitoring to ensure stability.
Jul 24, 17:16 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:41 UTC
Update - We have applied a mitigation and are monitoring for recovery
Jul 24, 16:40 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.
Jul 24, 16:28 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:27 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:26 UTC
Update - We are investigating timeouts to some GitHub services
Jul 24, 16:22 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:20 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Jul 24, 16:19 UTC
Investigating - We are investigating reports of degraded performance for API Requests and Issues
Jul 24, 16:17 UTC
Incident With Blocked GitHub.com Traffic
Resolved - Between July 23, 2026 at 18:45 UTC and July 24, 2026 at 11:19 UTC, an abuse mitigation update caused some legitimate customers whose traffic was routed through our Central Europe and South America edge locations to be incorrectly blocked from GitHub.com. We estimate that approximately 0.25% of GitHub.com requests were affected during this period.

This was caused by an abuse mitigation configuration that incorrectly classified legitimate traffic. We mitigated the incident by reverting the update. We are adding validation and safeguards to prevent similar incorrect blocking in the future.
Jul 24, 11:00 UTC

Jul 23, 2026

Latency issues across a number of services
Resolved - On July 23, 2026, between 07:08 and 09:39 UTC, several services experienced delays: 8% of actions workflow runs experienced an average run start delay of 10 minutes, 5% of webhook deliveries exceeded SLO, and code scanning, repos, notifications, issues and pull requests experienced increased latency over the life of the incident.

The root cause of the incident was a node of our background job processing system which did not recover after entering scheduled host maintenance. The incident was mitigated by identifying the problematic shard and restoring its correct state, after which queue backlogs drained and services recovered.

To speed mitigation, we have added monitors for nodes in this unhealthy state after maintenance operations. To prevent future recurrence, we are adapting our lifecycle automation to verify host rejoin after a scheduled reboot.
Jul 23, 09:39 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:39 UTC
Update - Webhooks is operating normally.
Jul 23, 09:35 UTC
Update - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:27 UTC
Update - We identified the source of latency affecting multiple services and applied a fix. Issues and Actions are recovering, and remaining affected services are seeing improvement as processing backlogs clear. We are actively monitoring recovery across all services.
Jul 23, 09:22 UTC
Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:19 UTC
Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Jul 23, 09:18 UTC
Update - We're currently investigating latency across multiple services. This can show as Actions jobs taking longer to start, Issues search serving stale results, and other listed services being similarly impacted.
Jul 23, 08:34 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Jul 23, 08:25 UTC
Investigating - We are investigating reports of degraded availability for Actions, Issues and Webhooks
Jul 23, 07:53 UTC
← Incident History Powered by Atlassian Statuspage