GitHub Outage History
GitHub is up right nowPingoru has recorded 201 incidents for GitHub: 201 in the last 12 months and 63 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 27 | 135 of 720 (19%) |
| May 2026 | 22 | 34 of 744 (5%) |
| June 2026 | 24 | 54 of 720 (8%) |
| July 2026 | 27 | 43 of 744 (6%) |
| August 2026 | 27 | 75 of 744 (10%) |
| September 2026 | 14 | 46 of 720 (6%) |
| October 2026 | 25 | 54 of 744 (7%) |
| November 2026 | 0 | 0 of 14 (0%) |
Incidents, newest first
Minor May 20, 2026 Incident with Actions 3h 15m Actions
Started May 20, 2026, 04:58 PM UTC· resolved May 20, 2026, 08:14 PM UTC
- investigating May 20, 2026, 04:58 PM UTC
We are investigating reports of degraded performance for Actions
- investigating May 20, 2026, 05:46 PM UTC
A subset of runners are taking longer than expected to connect, which may delay some jobs from beginning execution. We are actively working to mitigate the issue.
- monitoring May 20, 2026, 05:52 PM UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- monitoring May 20, 2026, 06:17 PM UTC
We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
- monitoring May 20, 2026, 07:41 PM UTC
Customer impact has fully subsided. We are maintaining yellow status while we deploy a permanent fix to prevent recurrence.
- resolved May 20, 2026, 08:14 PM UTC
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.
Notice May 19, 2026 Incident with Copilot –
Started May 19, 2026, 05:30 AM UTC· resolved May 19, 2026, 05:30 AM UTC
- resolved May 28, 2026, 12:40 PM UTC
On May 19, 2026, between 05:30 UTC and 14:50 UTC, GitHub Copilot API requests supporting completions, chat sessions, and agent interactions experienced elevated error rates. At peak impact, approximately 13% of API requests failed, and approximately 24% of remote sessions failed to initialize. A partial mitigation at 08:16 UTC reduced the Copilot API error rate to approximately 0.3%, but intermittent failures persisted until a full fix was deployed at 14:15 UTC and recovery was verified by 14:50 UTC. The incident was caused by an internal rate limit being exceeded on a dependency shared by two Copilot backend services. A recently enabled feature increased call volume to this dependency, and both services were counted under the same rate limit scope. The combined volume exceeded the limit as traffic increased during business hours. We mitigated the incident by deploying a caching layer to reduce call volume. To prevent recurrence, we are separating rate limit scopes between services, fixing monitoring gaps for internal dependency rate limiting, and reducing redundant calls.
Critical May 15, 2026 Actions is experiencing degraded availability 34m Actions, Pages
Started May 15, 2026, 08:13 AM UTC· resolved May 15, 2026, 08:48 AM UTC
- investigating May 15, 2026, 08:13 AM UTC
We are investigating reports of degraded availability for Actions
- investigating May 15, 2026, 08:14 AM UTC
Pages is experiencing degraded availability. We are continuing to investigate.
- investigating May 15, 2026, 08:26 AM UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- investigating May 15, 2026, 08:27 AM UTC
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
- investigating May 15, 2026, 08:29 AM UTC
We are monitoring an issue that was affecting GitHub Actions and causing downstream issues in GitHub Coding Agent and GitHub Code Review Agent. The issue has resolved now but we are closely monitoring our systems for full recovery.
- monitoring May 15, 2026, 08:41 AM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved May 15, 2026, 08:48 AM UTC
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.
Notice May 15, 2026 [Retroactive] Incident with GitHub.com –
Started May 15, 2026, 02:30 AM UTC· resolved May 15, 2026, 02:30 AM UTC
- resolved May 15, 2026, 03:57 AM UTC
Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed. The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the source of the traffic and prevented further disruption.
Minor May 13, 2026 Incident with CodeQL 1h 22m
Started May 13, 2026, 02:41 PM UTC· resolved May 13, 2026, 04:03 PM UTC
- investigating May 13, 2026, 02:41 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating May 13, 2026, 02:43 PM UTC
We are investigating delays affecting CodeQL, the code analysis engine used by Code Scanning. Some users may experience delayed or incomplete code scanning results. Our engineering team is investigating. We will provide another update by 15:15 UTC.
- investigating May 13, 2026, 02:58 PM UTC
We have applied a mitigation to increase processing capacity. We are continuing to monitor to confirm full recovery. We will provide another update by 15:30 UTC.
- monitoring May 13, 2026, 03:26 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring May 13, 2026, 03:30 PM UTC
CodeQL impact has been mitigated. We are continuing to monitor for durable recovery.
- resolved May 13, 2026, 04:03 PM UTC
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.
Minor May 12, 2026 Incident with CodeQL, Webhooks, Notifications, and Slack Integration 3h 5m Webhooks, Actions
Started May 12, 2026, 02:38 PM UTC· resolved May 12, 2026, 05:43 PM UTC
- investigating May 12, 2026, 02:38 PM UTC
We are investigating reports of degraded performance for Actions
- investigating May 12, 2026, 03:13 PM UTC
CodeQL actions are currently experiencing delays, which may result in those actions being stuck in a pending state or having failed due to a timeout.
- investigating May 12, 2026, 03:42 PM UTC
We're continuing to investigate issues with CodeQL actions workflows. We're additionally seeing delays for notifications, webhooks, and the Slack integration.
- investigating May 12, 2026, 03:44 PM UTC
Webhooks is experiencing degraded performance. We are continuing to investigate.
- investigating May 12, 2026, 04:18 PM UTC
We've established that most delays are related to a queuing service and are working to scale out. Early signals from the scale-out are showing signs of recovery for some services. We'll provide an update when services are fully recovered.
- investigating May 12, 2026, 04:28 PM UTC
Webhooks is operating normally.
- investigating May 12, 2026, 04:29 PM UTC
Webhooks have fully recovered. Continuing to work on recovery for the other services.
- investigating May 12, 2026, 04:59 PM UTC
CodeQL has fully recovered. We're continuing to work on recovery for the remaining impacted services.
- investigating May 12, 2026, 05:43 PM UTC
All services have fully recovered.
- resolved May 12, 2026, 05:43 PM UTC
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.
Minor May 11, 2026 Incident with high errors on Git Operations 8m Git Operations
Started May 11, 2026, 02:25 PM UTC· resolved May 11, 2026, 02:33 PM UTC
- investigating May 11, 2026, 02:25 PM UTC
We are investigating reports of degraded performance for Git Operations
- resolved May 11, 2026, 02:33 PM UTC
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.
Critical May 7, 2026 CCR and CCA failing to start for PR comments 1h 54m
Started May 07, 2026, 05:02 AM UTC· resolved May 07, 2026, 06:56 AM UTC
- investigating May 07, 2026, 05:02 AM UTC
We are investigating reports of impacted performance for some GitHub services.
- monitoring May 07, 2026, 06:13 AM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring May 07, 2026, 06:14 AM UTC
Copilot code review and cloud agents are starting again for pull requests, we are monitoring for full recovery.
- resolved May 07, 2026, 06:56 AM UTC
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.
Critical May 6, 2026 Incident with Pull Requests 3h 39m Pull Requests
Started May 06, 2026, 03:25 PM UTC· resolved May 06, 2026, 07:04 PM UTC
- investigating May 06, 2026, 03:25 PM UTC
We are investigating reports of degraded performance for Pull Requests
- investigating May 06, 2026, 03:28 PM UTC
We are investigating failures for new thread creation on Pull Requests. Responses to existing pull request threads are unaffected.
- investigating May 06, 2026, 03:55 PM UTC
Creation of new Pull Request threads (including line and file comments) continues to be affected. We have identified the cause of the issue and have started taking steps to mitigate this issue.
- investigating May 06, 2026, 04:07 PM UTC
Pull Requests is experiencing degraded availability. We are continuing to investigate.
- investigating May 06, 2026, 04:20 PM UTC
Creation of new Pull Request threads (including line and file comments) continues to be affected. Top-level comments on pull requests still function and should remain usable during recovery. Opening and merging pull requests, actions, and other pull request operations remain functional. A mitigation is being applied. Recovery is expected to be gradual, with complete recovery expected by 8:00pm UTC.
- investigating May 06, 2026, 05:52 PM UTC
Creation of new Pull Request threads (including line and file comments) continues to be affected although we are seeing partial recovery. A mitigation is being applied to continue to accelerate recovery with complete recovery expected by 8:00pm UTC. Top-level comments on pull requests still function and should remain usable during recovery. Opening and merging pull requests, actions, and other pull request operations remain functional.
- investigating May 06, 2026, 07:04 PM UTC
Mitigations have been fully applied and we are seeing full recovery of functionality on Pull Request threads. We are continuing to monitor to ensure sustained recovery.
- resolved May 06, 2026, 07:04 PM UTC
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.
Critical May 6, 2026 Disruption with some GitHub services 38m
Started May 06, 2026, 11:21 AM UTC· resolved May 06, 2026, 11:59 AM UTC
- investigating May 06, 2026, 11:21 AM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating May 06, 2026, 11:25 AM UTC
We are investigating issues with the ability to start Copilot Cloud Agent sessions and view them.
- investigating May 06, 2026, 11:59 AM UTC
We have applied a mitigation and Copilot services have recovered.
- resolved May 06, 2026, 11:59 AM UTC
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.
Major May 6, 2026 Incident with Actions, we are investigating reports of degraded availability 2h 25m Actions
Started May 06, 2026, 07:19 AM UTC· resolved May 06, 2026, 09:44 AM UTC
- investigating May 06, 2026, 07:19 AM UTC
We are investigating reports of degraded availability for Actions
- investigating May 06, 2026, 08:00 AM UTC
Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue
- investigating May 06, 2026, 09:08 AM UTC
We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.
- monitoring May 06, 2026, 09:19 AM UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- monitoring May 06, 2026, 09:44 AM UTC
Actions wait times have fully recovered.
- resolved May 06, 2026, 09:44 AM UTC
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.
Minor May 5, 2026 Increased Latency and Failures for SSH Git Operations 1h 46m Git Operations
Started May 05, 2026, 04:49 PM UTC· resolved May 05, 2026, 06:35 PM UTC
- investigating May 05, 2026, 04:49 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- monitoring May 05, 2026, 04:54 PM UTC
Between approximately 14:00 and 16:10 UTC, customers using SSH-based Git operations may have experienced elevated latency and failures. HTTP-based operations were not impacted. We've identified a suspected root cause and are working to implement a mitigation to prevent further impact.
- investigating May 05, 2026, 05:23 PM UTC
Git Operations is experiencing degraded performance. We are continuing to investigate.
- investigating May 05, 2026, 05:26 PM UTC
We're continuing to work on preventing further impact from the earlier issue. No SSH-based impact is expected at this time. We'll post new updates if impact recurs or once our mitigation is in place.
- monitoring May 05, 2026, 06:25 PM UTC
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
- monitoring May 05, 2026, 06:35 PM UTC
We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.
- resolved May 05, 2026, 06:35 PM UTC
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.
Critical May 5, 2026 Incident with Actions 3h 48m Actions
Started May 05, 2026, 01:37 PM UTC· resolved May 05, 2026, 05:26 PM UTC
- investigating May 05, 2026, 01:37 PM UTC
We are investigating reports of degraded availability for Actions
- investigating May 05, 2026, 01:48 PM UTC
We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs
- investigating May 05, 2026, 02:14 PM UTC
We are investigating elevated queue times and failures on Actions Jobs running on Hosted Runners in East US affecting 8% of runs. Hosted Runners with private networking can fail over to a different Azure region to mitigate the issue.
- investigating May 05, 2026, 03:12 PM UTC
We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US region affecting 10% of runs. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.
- investigating May 05, 2026, 03:54 PM UTC
We've applied a mitigation for long queue times and failures on Standard Hosted Runners and are monitoring for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.
- investigating May 05, 2026, 04:33 PM UTC
We've seen signs of recovery for Standard Hosted Runners and are continuing to monitor for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue working with our compute provider to restore capacity.
- investigating May 05, 2026, 05:11 PM UTC
Standard hosted runners have now reached full recovery. Hosted Runners with Private Networking in the East US region remain degraded as we continue working with our compute provider to restore capacity. Hosted Runners with private networking can fail over to a different Region to mitigate the issue.
- investigating May 05, 2026, 05:11 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- resolved May 05, 2026, 05:26 PM UTC
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.
Critical May 4, 2026 Incident with Issues and Webhooks 54m Git Operations, Webhooks, Issues, Pull Requests and 4 more
Started May 04, 2026, 03:45 PM UTC· resolved May 04, 2026, 04:40 PM UTC
- investigating May 04, 2026, 03:45 PM UTC
We are investigating reports of degraded performance for Issues and Webhooks
- investigating May 04, 2026, 03:48 PM UTC
We are investigating Increased latency and timeouts across multiple GitHub services.
- investigating May 04, 2026, 03:48 PM UTC
Git Operations is experiencing degraded performance. We are continuing to investigate.
- investigating May 04, 2026, 03:50 PM UTC
Packages is experiencing degraded performance. We are continuing to investigate.
- investigating May 04, 2026, 03:51 PM UTC
Pull Requests is experiencing degraded availability. We are continuing to investigate.
- investigating May 04, 2026, 03:51 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating May 04, 2026, 03:56 PM UTC
Pull Requests is experiencing degraded performance. We are continuing to investigate.
- investigating May 04, 2026, 04:05 PM UTC
Codespaces is experiencing degraded performance. We are continuing to investigate.
- investigating May 04, 2026, 04:06 PM UTC
Pages is experiencing degraded performance. We are continuing to investigate.
- investigating May 04, 2026, 04:25 PM UTC
Git Operations is operating normally.
- investigating May 04, 2026, 04:28 PM UTC
Actions and Packages are operating normally.
- investigating May 04, 2026, 04:29 PM UTC
Latency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.
- investigating May 04, 2026, 04:29 PM UTC
Pages is operating normally.
- investigating May 04, 2026, 04:32 PM UTC
Pull Requests is operating normally.
- investigating May 04, 2026, 04:34 PM UTC
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
- investigating May 04, 2026, 04:35 PM UTC
The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
- investigating May 04, 2026, 04:35 PM UTC
Webhooks is operating normally.
- monitoring May 04, 2026, 04:36 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved May 04, 2026, 04:40 PM UTC
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.
Minor April 28, 2026 Incomplete pull request results in repositories 2d 13h Pull Requests
Started Apr 28, 2026, 02:17 PM UTC· resolved May 01, 2026, 04:15 AM UTC
- investigating Apr 28, 2026, 02:17 PM UTC
We are investigating reports of degraded performance for Pull Requests
- investigating Apr 28, 2026, 02:51 PM UTC
After yesterday’s incident, we are investigating cases where /pulls and /repo/pulls pages are not showing all indexed pull requests. This is because our Elasticsearch cluster does not currently contain all indexed documents. No pull request data has been lost. As pull requests are updated, they will be reindexed. We are also working on accelerating a full reindex so these pages return complete results again.
- investigating Apr 28, 2026, 03:58 PM UTC
We are actively reindexing the remaining ElasticSearch indexes. Our priority is ensuring correctness and avoiding further impact. We are taking a measured approach to safely backfill data and will share additional updates as progress continues.
- investigating Apr 28, 2026, 09:43 PM UTC
Elastic search reindexing of pull requests is continuing. All data is preserved, but may not be available on pages relying on elasticsearch until the reindex is complete. Pages and APIs that do not rely on elasticsearch, including the GitHub CLI (gh pr list) and API (/repos/{owner}/{repo}/pulls), are not impacted and can be used to retrieve pull request data in the interim.
- investigating Apr 28, 2026, 10:46 PM UTC
We have made an interim mitigation to improve availability for some impacted repositories while reindexing continues, and we are actively monitoring the indexing progress.
- investigating Apr 29, 2026, 12:40 AM UTC
Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.
- investigating Apr 29, 2026, 10:22 PM UTC
We have restored search/indexing functionality for over 99% of impacted pull requests. We are continuing to address the remaining affected pull requests and are reviewing outstanding gaps as part of the restoration process.
- investigating Apr 30, 2026, 03:49 AM UTC
We have repaired the missing search records for affected Pull Requests and are working to identify and repair records left in a stale state after the recovery.
- investigating May 01, 2026, 04:11 AM UTC
This incident has been resolved. Search and indexing functionality for pull requests are now fully restored. 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.
- resolved May 01, 2026, 04:15 AM UTC
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.
Minor April 28, 2026 Disruption with some GitHub services 3h 9m Actions
Started Apr 28, 2026, 01:59 PM UTC· resolved Apr 28, 2026, 05:09 PM UTC
- investigating Apr 28, 2026, 01:59 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- monitoring Apr 28, 2026, 01:59 PM UTC
Actions is experiencing capacity constraints with hosted ubuntu-latest and ubuntu-24.02, leading to high wait times. Other hosted labels and self-hosted runners are not impacted.
- investigating Apr 28, 2026, 02:02 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 28, 2026, 02:49 PM UTC
We're still investigating the root cause for run start delays and failures for Actions hosted Ubuntu jobs, around 5% of jobs are impacted as of now.
- investigating Apr 28, 2026, 03:20 PM UTC
We've applied a mitigation to unblock running Actions. We're continuing to monitor.
- investigating Apr 28, 2026, 03:41 PM UTC
Currently less than 2% of hosted ubuntu-latest and ubuntu-24.04 runs are delayed or failing. We are continuing to monitor for full recovery.
- investigating Apr 28, 2026, 04:36 PM UTC
Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.
- monitoring Apr 28, 2026, 05:08 PM UTC
Actions is operating normally.
- resolved Apr 28, 2026, 05:09 PM UTC
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.
Critical April 27, 2026 GitHub search is degraded 6h 15m Issues, Pull Requests, Actions, Packages
Started Apr 27, 2026, 04:31 PM UTC· resolved Apr 27, 2026, 10:46 PM UTC
- investigating Apr 27, 2026, 04:31 PM UTC
We are investigating reports of degraded performance for Actions
- investigating Apr 27, 2026, 04:33 PM UTC
Customers across GitHub are experiencing failures with searches. Examples include: workflow run failures, projects failing to load, and timed out search requests. This is due to an ongoing infrastructure issue that we have been investigating.
- investigating Apr 27, 2026, 04:36 PM UTC
Issues is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 27, 2026, 04:39 PM UTC
Packages is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 27, 2026, 04:53 PM UTC
Pull Requests is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 27, 2026, 05:35 PM UTC
Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs. We are still investigating and attempting mitigations. We will provide further updates.
- investigating Apr 27, 2026, 06:17 PM UTC
We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause
- investigating Apr 27, 2026, 06:19 PM UTC
Pull Requests is experiencing degraded availability. We are continuing to investigate.
- investigating Apr 27, 2026, 07:50 PM UTC
We have identified the source of the additional load causing stress on our ElasticSearch clusters. We have disabled the source of that load and are seeing signs of recovery
- investigating Apr 27, 2026, 08:06 PM UTC
Pull Requests is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 27, 2026, 09:32 PM UTC
We've applied a mitigation and continuing to monitor
- monitoring Apr 27, 2026, 09:33 PM UTC
The degradation affecting Actions, Issues, Packages and Pull Requests has been mitigated. We are monitoring to ensure stability.
- monitoring Apr 27, 2026, 10:35 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- monitoring Apr 27, 2026, 10:44 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved Apr 27, 2026, 10:46 PM UTC
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.
Minor April 27, 2026 Disruption with some GitHub services 2h 35m
Started Apr 27, 2026, 04:27 PM UTC· resolved Apr 27, 2026, 07:02 PM UTC
- investigating Apr 27, 2026, 04:48 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Apr 27, 2026, 05:01 PM UTC
Copilot Cloud Agent (CCA) jobs using the Codex agent are failing after starting. To avoid this issue, please choose a different agent. We are investigating the cause and working towards remediation
- investigating Apr 27, 2026, 05:26 PM UTC
We've found the issue and are working on deploying a solution to get Codex agent runs working again.
- monitoring Apr 27, 2026, 07:01 PM UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved Apr 27, 2026, 07:02 PM UTC
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.
Minor April 24, 2026 Delays with Actions Jobs for Larger Runners using VNet Injection in the East US region 5h 33m
Started Apr 24, 2026, 07:02 PM UTC· resolved Apr 25, 2026, 12:36 AM UTC
- investigating Apr 24, 2026, 07:02 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Apr 24, 2026, 07:09 PM UTC
We are investigating reports of degraded performance for Larger Runners with vnet injection in East US and we are working with our service provider on mitigation.
- investigating Apr 24, 2026, 07:14 PM UTC
This is related to the public impact, "Multiservice impact for Azure Workloads in East US" shared at https://azure.status.microsoft/
- resolved Apr 25, 2026, 12:36 AM UTC
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.
Minor April 23, 2026 Incident with Pull Requests – Pull Requests
Started Apr 23, 2026, 09:43 PM UTC· resolved Apr 23, 2026, 09:43 PM UTC
- investigating Apr 23, 2026, 07:50 PM UTC
We are investigating reports of degraded performance for Pull Requests
- investigating Apr 23, 2026, 07:58 PM UTC
We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.
- investigating Apr 23, 2026, 08:47 PM UTC
Pull Requests is operating normally.
- investigating Apr 23, 2026, 09:18 PM UTC
We have resolved a regression present when using merge queue with either squash merges or rebases. If you use merge queue in this configuration, some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC. This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.
- resolved Apr 23, 2026, 09:43 PM UTC
This incident has been resolved and we've contacted repository administrators via email who have impacted branches. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will also be shared as soon as it is available.
Minor April 23, 2026 Disruption with users unable to start Claude and Codex agent task from the web 13m
Started Apr 23, 2026, 07:28 PM UTC· resolved Apr 23, 2026, 07:42 PM UTC
- investigating Apr 23, 2026, 07:28 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Apr 23, 2026, 07:33 PM UTC
We have identified the root cause of the issue and are working on mitigation.
- resolved Apr 23, 2026, 07:42 PM UTC
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.
Critical April 23, 2026 Incident with multiple GitHub services 1h 18m Webhooks, Actions, Copilot
Started Apr 23, 2026, 04:12 PM UTC· resolved Apr 23, 2026, 05:30 PM UTC
- investigating Apr 23, 2026, 04:12 PM UTC
We are investigating reports of degraded availability for Copilot and Webhooks
- investigating Apr 23, 2026, 04:19 PM UTC
We are investigating multiple unavailable services.
- investigating Apr 23, 2026, 04:34 PM UTC
Actions is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 23, 2026, 04:52 PM UTC
We have identified the root problem and are working on mitigation.
- investigating Apr 23, 2026, 05:03 PM UTC
The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.
- investigating Apr 23, 2026, 05:04 PM UTC
Many services are mitigated and are validating the remaining services.
- investigating Apr 23, 2026, 05:10 PM UTC
Webhooks is operating normally.
- resolved Apr 23, 2026, 05:30 PM UTC
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.
Minor April 23, 2026 Investigating errors on GitHub 38m Actions, Packages, Codespaces, Copilot
Started Apr 23, 2026, 02:40 PM UTC· resolved Apr 23, 2026, 03:18 PM UTC
- investigating Apr 23, 2026, 02:40 PM UTC
We are investigating reports of degraded performance for Actions
- investigating Apr 23, 2026, 02:41 PM UTC
Packages is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 23, 2026, 02:42 PM UTC
Codespaces is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 23, 2026, 02:44 PM UTC
Copilot is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 23, 2026, 02:51 PM UTC
Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.
- investigating Apr 23, 2026, 03:02 PM UTC
A mitigation was applied and services have recovered. Actions is working through queued work before fully recovering.
- monitoring Apr 23, 2026, 03:02 PM UTC
The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.
- resolved Apr 23, 2026, 03:18 PM UTC
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.
Minor April 22, 2026 Disruption with some GitHub services 2h 50m Issues
Started Apr 22, 2026, 07:53 PM UTC· resolved Apr 22, 2026, 10:43 PM UTC
- investigating Apr 22, 2026, 07:53 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Apr 22, 2026, 07:55 PM UTC
Issues is experiencing degraded performance. We are continuing to investigate.
- investigating Apr 22, 2026, 08:02 PM UTC
Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.
- investigating Apr 22, 2026, 08:37 PM UTC
We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. Copilot @-mentions on pull requests are not being processed, and some issue-related functionality may be degraded. A fix has been developed and is being applied.
- investigating Apr 22, 2026, 10:09 PM UTC
We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.
- resolved Apr 22, 2026, 10:43 PM UTC
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.
Critical April 22, 2026 Disruption with Copilot chat and Copilot Coding Agent 3h 42m
Started Apr 22, 2026, 03:35 PM UTC· resolved Apr 22, 2026, 07:18 PM UTC
- investigating Apr 22, 2026, 03:35 PM UTC
We are investigating reports of impacted performance for some GitHub services.
- investigating Apr 22, 2026, 03:43 PM UTC
We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.
- investigating Apr 22, 2026, 04:24 PM UTC
We continue to work on mitigation for Copilot chat and cloud agent.
- investigating Apr 22, 2026, 04:58 PM UTC
Mitigation is progressing for Copilot chat and cloud agent.
- investigating Apr 22, 2026, 05:40 PM UTC
Mitigation is progressing for Copilot chat and cloud agent recovery.
- investigating Apr 22, 2026, 05:49 PM UTC
We are now seeing recovery for Copilot cloud agent.
- investigating Apr 22, 2026, 06:05 PM UTC
Copilot cloud agent and chat are mitigated for github.com.
- resolved Apr 22, 2026, 07:18 PM UTC
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.