GitHub Status - Incident History

Incident with GraphQL API Requests

2026-08-11T20:06:56Z

Aug 11, 20:06 UTC
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 11, 20:06 UTC
Update - We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident.

Aug 11, 16:49 UTC
Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

Aug 11, 16:49 UTC
Update - We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.

Aug 11, 15:28 UTC
Update - We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information

Aug 11, 14:50 UTC
Investigating - We are investigating reports of degraded performance for API Requests

Disruption with Copilot for access to some models

2026-08-10T21:50:43Z

Aug 10, 21:50 UTC
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 10, 21:50 UTC
Update - We have deployed and validated the fix to prevent immediate reoccurrence. We will be performing additional work to limit these kinds of failures in the future.

Aug 10, 21:19 UTC
Update - The issue has been mitigated across all affected environments. We are currently deploying on a fix to prevent reoccurrence. We will provide another update once the fix has been deployed.

Aug 10, 20:49 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.

Aug 10, 20:39 UTC
Monitoring - We are currently investigating reports of some Copilot users experiencing issues accessing certain models. Affected users may see errors or degraded functionality when attempting to use specific models. We are actively working on a fix and will provide updates as we have more information.

Aug 10, 20:27 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with creation of fine grained personal access tokens

2026-08-10T18:46:22Z

Aug 10, 18:46 UTC
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 10, 18:22 UTC
Update - We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery.

Aug 10, 18:21 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Aug 10, 18:09 UTC
Update - We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created.

Aug 10, 18:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Incident with Actions

2026-08-07T02:04:44Z

Aug 7, 02:04 UTC
Resolved - On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes.

The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services.

These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events.

As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work.

This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation.

Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases.

Some jobs created during the incident were also left stuck unable to be retried or canceled. CLI and UI solutions for customers to address these were shared at https://github.com/orgs/community/discussions/204152#discussioncomment-17946043.

To prevent recurrence, we are making improvements to deployment and capacity safeguards for the affected services, strengthening monitoring for the conditions that preceded the incident, improving the resiliency and recovery of queued work and runner assignment, and adding automatic recovery for self-hosted runners affected by similar failure conditions. We are also making additional improvements to reduce the risk of cascading failures and accelerate recovery during large-scale Actions disruptions.

Aug 7, 02:03 UTC
Update - During the incident, some Actions Runner Controller (ARC) runner pods became stuck in an idle state. Affected users can delete those pods using kubectl or redeploy their Actions Runner Controller application. ARC will automatically create replacement runners.

The next releases of Actions Runner and Actions Runner Controller will include an automatic recovery mechanism, preventing the need for these manual steps in the future.

Some workflow-triggering events, including push and pull request events, were not processed during the incident and cannot be replayed automatically. Customers may need to repeat the triggering action by pushing a new commit, updating the pull request, or manually re-running the workflow where applicable.

Aug 7, 00:59 UTC
Update - We’re investigating reports that some Actions Runner Controller runners are taking longer than expected to recover. We’ll provide an update as our investigation progresses.

Aug 7, 00:06 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Aug 7, 00:05 UTC
Update - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

Aug 7, 00:01 UTC
Update - System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.

Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.

We are monitoring all affected services for sustained recovery and will provide another update shortly.

Aug 7, 00:01 UTC
Update -
System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.

Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.

We are monitoring all affected services for sustained recovery and will provide another update shortly.

Aug 6, 23:13 UTC
Update - We have deployed fixes that address runners being assigned invalid jobs and are taking additional steps to clear the backlog of affected jobs. Job completion rates for running workflows have improved significantly, with success rates now at 99%. Global queues for hosted runner assignment are nearly burned down and concurrency queues for customers are being processed. Another change was deployed to accelerate processing the backlog of job requests.

We are gradually restoring throughput for webhook-triggered Actions workflows and monitoring system stability. We have deployed a fix for self-hosted runners that were not picking up jobs and are enabling it incrementally.

GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused.

We continue to monitor recovery across all affected services and will provide another update as conditions improve.

Aug 6, 22:18 UTC
Update - We continue to make progress on the issue affecting GitHub Actions. We have deployed a fix that addresses runners being assigned jobs that are no longer valid, and are seeing improvement in job completion rates. For workflow runs that are starting, success rates have increased significantly and are now at 97%. Standard and larger runners are now draining queued work. A change is also in progress to mitigate issues with existing self-hosted runners that are not picking up jobs.

Webhook triggers remain throttled to support recovery. Many push and pull request events are not yet triggering new workflow runs, and we are working to safely restore full throughput.

GitHub Pages, Copilot code review, and Copilot coding agent may still experience failures or delays. Migrations using GitHub Enterprise Importer remain paused.

We are continuing to monitor recovery and will provide another update as conditions improve.

Aug 6, 21:30 UTC
Update - We are continuing to work on an issue affecting GitHub Actions. Webhook triggers remain throttled to aid recovery, so many push and pull request events are not triggering new workflow runs.

We identified runners being assigned jobs that are no longer valid and are deploying a change to address this issue. Both GitHub-hosted and self-hosted runners are affected.

Copilot code review, Copilot coding agent, and GitHub Pages may experience failures or delays. Migrations using GitHub Enterprise Importer have been paused to support mitigation efforts.

Aug 6, 20:34 UTC
Update - We are continuing to work on an issue affecting GitHub Actions. Webhook triggers are currently throttled to help with recovery and and we are processing approximately 15% of webhooks, so many events such as pushes and pull requests are not triggering workflow runs. Of jobs queued, approximately 65% are succeeding, improved from a low of 30 to 40% earlier in this incident.

We have narrowed the remaining impact to runners that are stuck retrying jobs that are no longer available. Both GitHub-hosted and self-hosted runners are affected, and we are working to recover them.

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

Aug 6, 19:43 UTC
Update - We are continuing to work on an issue affecting GitHub Actions.

Capacity remains constrained and jobs may still be delayed or fail while it recovers gradually. 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.

Our engineers remain actively engaged.

Aug 6, 18:46 UTC
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 6, 18:11 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 6, 17:40 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 6, 17:02 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 6, 16:33 UTC
Update - Actions and Pages are experiencing degraded availability. We are continuing to investigate.

Aug 6, 16:27 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 6, 16:27 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.

Aug 6, 16:19 UTC
Update - Pages is operating normally.

Aug 6, 15:53 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.

Aug 6, 15:45 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 6, 15:41 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.

Aug 6, 15:22 UTC
Investigating - We are investigating reports of degraded performance for Actions

Incident with Pages - Deployment Lag

2026-08-06T16:22:59Z

Aug 6, 16:22 UTC
Resolved - On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased.

At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC.

Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments.

We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward.

Aug 6, 15:50 UTC
Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

Aug 6, 15:03 UTC
Investigating - We are investigating reports of degraded performance for Pages

Some Copilot Cloud Agent jobs not starting

2026-08-05T13:00:25Z

Aug 5, 13:00 UTC
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, 12:10 UTC
Update - Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.

Aug 5, 12:01 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Aug 5, 11:38 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Incident with Copilot

2026-08-03T11:25:12Z

Aug 3, 11:25 UTC
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:19 UTC
Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.

Aug 3, 10:35 UTC
Update - We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.

Aug 3, 09:54 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:53 UTC
Investigating - We are investigating reports of degraded performance for Copilot

Incident with Copilot AI Model Providers

2026-08-01T18:44:28Z

Aug 1, 18:44 UTC
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:23 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:20 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:03 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

Degraded availability GPT 5.6 Luna

2026-08-01T12:30:21Z

Aug 1, 12:30 UTC
Resolved - On August 1st, 2026, the GPT-5.6 Luna model in GitHub Copilot experienced degraded availability in intermittent time intervals between ~08:05 UTC and ~16:30 UTC. Specifically the timeframes observed were 10:00-10:20 UTC, 10:45-11:50 UTC, 13:00-14:25 UTC, and 16:00-16:30 UTC. During this time, requests to GPT-5.6 Luna 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 GPT-5.6 Luna fully recovered once the provider resolved their outage at 16:30 UTC.

Aug 1, 12:29 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:13 UTC
Update - We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability.

Aug 1, 11:20 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:16 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers

Copilot model Claude Fable 5 experiencing elevated errors

2026-07-30T10:12:15Z

Jul 30, 10:12 UTC
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:11 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, 09:17 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:07 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers

Incident with Copilot AI Model Providers

2026-07-29T21:51:26Z

Jul 29, 21:51 UTC
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:08 UTC
Update - The external AI model provider is continuing to investigate.

Jul 29, 20:38 UTC
Update - The external AI model provider has identified the issue and is working to resolve.

Jul 29, 20:18 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:07 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

Incident with Actions

2026-07-29T16:00:54Z

Jul 29, 16:00 UTC
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, 15:40 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Jul 29, 15:34 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:26 UTC
Investigating - We are investigating reports of degraded availability for Actions

Incident with GraphQL API Requests

2026-07-27T04:09:10Z

Jul 27, 04:09 UTC
Resolved - On July 26, 2026 at 21:34 UTC we began seeing intermittent errors on the GitHub GraphQL API. A subset of GraphQL API requests returned HTTP 502 errors in short bursts. During the impact window an average of 0.09% of GraphQL API requests in the affected region failed, with a peak of 0.50% of requests failing during the worst two-minute period at 03:02 UTC on July 27. Requests that failed generally succeeded when retried, and no data was lost or altered. Other GitHub services were not affected.

The errors were traced to a single group of servers handling a share of GraphQL API traffic. Application processes on that group intermittently closed connections before completing responses. Impact ended at 03:52 UTC on July 27 when those processes were replaced, and we resolved the incident at 04:09 UTC on July 27 after confirming error rates had returned to normal.

We are still investigating why those processes closed connections, and that work is being carried out by the team that owns the underlying compute platform. In the meantime we are adding detection and automated mitigation for when a single group of servers behaves differently from its peers.

Jul 27, 04:09 UTC
Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

Jul 27, 03:53 UTC
Investigating - We are investigating reports of degraded performance for API Requests

Actions run failures and delays

2026-07-25T13:13:21Z

Jul 25, 13:13 UTC
Resolved - Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8

Jul 25, 13:12 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, 12:59 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Jul 25, 12:58 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:34 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:31 UTC
Investigating - We are investigating reports of degraded availability for Actions

Several GPT models degraded

2026-07-25T10:11:16Z

Jul 25, 10:11 UTC
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:04 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.

Jul 25, 09:48 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:42 UTC
Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers

Incident with Actions

2026-07-25T09:25:30Z

Jul 25, 09:25 UTC
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:20 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:13 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Jul 25, 08:59 UTC
Investigating - We are investigating reports of degraded performance for Actions

Incident with Pull Requests

2026-07-24T20:23:10Z

Jul 24, 20:23 UTC
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:02 UTC
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Jul 24, 19:59 UTC
Update - We have applied a mitigation and are monitoring for recovery

Jul 24, 19:43 UTC
Update - Pull Requests is experiencing degraded availability. We are continuing to investigate.

Jul 24, 19:40 UTC
Update - We are investigating errors creating pull requests

Jul 24, 19:37 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests

Disruption with some GitHub services

2026-07-24T17:36:50Z

Jul 24, 17:36 UTC
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:24 UTC
Update - We are seeing recovery across all services

Jul 24, 17:16 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, 16:41 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.

Jul 24, 16:40 UTC
Update - We have applied a mitigation and are monitoring for recovery

Jul 24, 16:28 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.

Jul 24, 16:27 UTC
Update - Pages is experiencing degraded performance. We are continuing to investigate.

Jul 24, 16:26 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.

Jul 24, 16:22 UTC
Update - We are investigating timeouts to some GitHub services

Jul 24, 16:20 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.

Jul 24, 16:19 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.

Jul 24, 16:17 UTC
Investigating - We are investigating reports of degraded performance for API Requests and Issues

Incident With Blocked GitHub.com Traffic

2026-07-24T11:00:00Z

Jul 24, 11:00 UTC
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.

Latency issues across a number of services

2026-07-23T09:39:19Z

Jul 23, 09:39 UTC
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:35 UTC
Update - Webhooks is operating normally.

Jul 23, 09:27 UTC
Update - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Jul 23, 09:22 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:19 UTC
Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Jul 23, 09:18 UTC
Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

Jul 23, 08:34 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:25 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.

Jul 23, 07:53 UTC
Investigating - We are investigating reports of degraded availability for Actions, Issues and Webhooks

Disruption with actions hosted runners

2026-07-22T22:09:26Z

Jul 22, 22:09 UTC
Resolved - On July 22, 2026, between 19:36 UTC and 22:04 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition for a subset of workloads. During most of the incident, approximately 15% of workflow runs on hosted runners were delayed by more than 5 minutes, while roughly 1% failed to start.

At 21:49 UTC, we restored the health of the backend data replication system, allowing provisioning to recover and the accumulated workflow backlog to drain. Service performance then returned to expected levels. We are improving provisioning-service resiliency, workload distribution, and capacity balancing to reduce the likelihood and impact of similar incidents.

Jul 22, 22:01 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Jul 22, 22:01 UTC
Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Jul 22, 20:47 UTC
Update - Approximately 3% of GitHub Actions runs on GitHub-hosted runners are experiencing run start delays exceeding 5 minutes. A small portion of these runs may fail after extended delays. We have identified the cause and are working on a mitigation.

Jul 22, 20:43 UTC
Investigating - We are investigating reports of degraded performance for Actions

Some SSH connections using deploy keys are failing

2026-07-21T11:57:01Z

Jul 21, 11:57 UTC
Resolved - On July 21, 2026, between 07:41 UTC and 11:57 UTC, the SSH Authentication service was degraded and some SSH connections failed to authenticate. On average, 12.2% of SSH authentication requests failed, peaking at 15.7%. Both user RSA keys and deploy keys were impacted. This was due to a change in how our SSH service handled one public-key authentication method that caused the affected authentication attempts to be rejected as invalid.

We mitigated the incident by reverting the change, after which SSH authentication returned to normal.

We are working to expand our automated test coverage for our SSH public-key authentication flows to catch more edge cases and to improve observability and alerting on SSH authentication failures, to reduce our time to detection and mitigation of issues like this one in the future.

Jul 21, 11:46 UTC
Update - We have identified a recent code change as a potential cause of the SSH authentication failures affecting deploy key connections. Our engineering team is rolling back this change. Customers using deploy keys for SSH access to repositories may continue to experience intermittent connection failures until the fix is deployed.

Jul 21, 11:04 UTC
Update - We are investigating reports of intermittent SSH authentication failures affecting connections that use deploy keys. Customers may experience failed SSH connections when interacting with repositories via deploy keys. Our engineering team is actively investigating the root cause and working toward resolution.

Jul 21, 10:31 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with GPT 5.3 Codex

2026-07-20T18:37:08Z

Jul 20, 18:37 UTC
Resolved - Between 06:39 and 18:11 UTC on July 20, 2026, the Copilot service experienced a degradation of the GPT 5.3 model due to an issue with our upstream provider. The upstream model provider returned intermittent errors for GPT 5.3 Codex requests, which caused some responses to fail. Auto mode requests that had selected GPT 5.3 Codex were also impacted. On average about 2% of GPT 5.3 Codex requests failed during this window. Copilot automatically routed eligible traffic away from the impacted provider to reduce customer impact. No other models were impacted.

We worked with the upstream provider throughout the incident and confirmed sustained recovery before resolving.

Jul 20, 18:25 UTC
Update - We are seeing signs of sustained recovery from the upstream provider for GPT 5.3 Codex requests. Requests are succeeding as expected. We are awaiting confirmation from the provider that the issue is fully mitigated before resolving this incident.

Jul 20, 17:21 UTC
Update - The upstream provider continues to return intermittent errors for GPT 5.3 Codex requests. Some users may experience failed or interrupted responses when using this model. Traffic continues to be automatically rerouted to reduce impact, and we are actively working with the upstream provider on a resolution. In the meantime, selecting an alternative model will avoid disruption.

Jul 20, 16:39 UTC
Update - We identified that an upstream provider is returning errors for GPT 5.3 Codex requests, causing some users to experience failed or interrupted responses. Traffic is being automatically rerouted to mitigate impact. We are working with the upstream provider to resolve the underlying issue. We recommend using a different model at this time while we resolve the problem.

Jul 20, 16:04 UTC
Update - We are investigating GPT Codex 5.3 performance.

Jul 20, 16:03 UTC
Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers

Incident with GitHub Actions

2026-07-20T04:44:03Z

Jul 20, 04:44 UTC
Resolved - Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.

Jul 20, 04:43 UTC
Update - Actions has fully recovered, and we will continue to monitor the platform to ensure stability.

Jul 20, 03:34 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Jul 20, 03:27 UTC
Update - We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.

Jul 20, 03:03 UTC
Update - API Requests is operating normally.

Jul 20, 02:43 UTC
Update - Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.

Jul 20, 02:23 UTC
Update - API Requests is experiencing degraded performance. We are continuing to investigate.

Jul 20, 02:20 UTC
Update - Issues is operating normally.

Jul 20, 01:37 UTC
Update - Pages is operating normally.

Jul 20, 01:11 UTC
Update - We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.

A separate incident was opened before we understood they were related. We will continue to post updates on this incident.

Jul 20, 00:52 UTC
Update - Issues is experiencing degraded performance. We are continuing to investigate.

Jul 20, 00:49 UTC
Update - Actions and Pages are experiencing degraded performance. We are continuing to investigate.

Jul 20, 00:48 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.

Jul 20, 00:20 UTC
Update - Actions is experiencing degraded availability. We are continuing to investigate.

Jul 20, 00:07 UTC
Update - API Requests is experiencing degraded availability. We are continuing to investigate.

Jul 19, 23:57 UTC
Update - We have identified the cause of failures in GitHub Actions and are working to restore service.

Jul 19, 23:37 UTC
Update - We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.

Jul 19, 23:34 UTC
Investigating - We are investigating reports of degraded performance for Actions

Disruption with some GitHub services

2026-07-20T01:46:02Z

Jul 20, 01:46 UTC
Resolved - Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were not affected. Reconnection traffic from affected runners also increased load on GitHub APIs, resulting in 3-4 seconds of additional average request latency and elevated 5xx error rates.

The incident was caused by a certificate lifecycle management failure in a subset of internal services, resulting in an SSL certificate expiration that disrupted runner connectivity. We restored service by rotating the affected certificate. Recovery began at 02:45 UTC. By 03:55 UTC, queued workflow backlog had been processed and workflow delay rates returned to normal.

To prevent recurrence, we are strengthening certificate renewal automation, adding fallback expiry monitoring and alerting, and improving circuit-breaker protections during runner API disruptions to reduce the risk of cascading impact to other APIs.

Jul 20, 01:45 UTC
Update - Git LFS API success rates have returned to normal. We will continue to monitor the service closely.

Jul 20, 01:15 UTC
Investigating - The Git LFS API issues have been identified as being related to a separate incident where Actions is experiencing degraded availability. We’re consolidating our investigation efforts under that incident.

Jul 20, 00:26 UTC
Update - Some Git LFS operations, and loading files through the API are failing. We are investigating.

Jul 20, 00:25 UTC
Monitoring - Some Git LFS operations, and loading files through the API are failing. We are investigating.

Jul 20, 00:25 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.