Looking for an update now? Check the current status, or follow GitHub for future changes.
69.4%of 49 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
76.7%
30
7
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.
investigating
We are experiencing degraded availability for the Grok 4.6 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.<br />
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
investigating
One of our model providers has confirmed an incident on their end. We have provided them details to help identify the issue. We are starting to see recovery.
investigating
Copilot is experiencing a higher rate of errors for OpenAI models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4, and the gpt-5.6 family of models. Other models are not impacted. <br />
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
investigating
We are experiencing degraded availability for the Kimi K3 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.
investigating
We are investigating reports of degraded availability for Copilot AI Model Providers
No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause.
investigating
Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since the previous update. We will provide another update as the investigation progresses.
investigating
Our mitigation is still holding as we continue to investigate to find the root cause.
investigating
We are continuing to monitor the mitigation that we have applied for the billing page disruption.
investigating
We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered.
investigating
We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions.
investigating
We are investigating reports of impacted performance for some GitHub services.
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
investigating
We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.
investigating
We are investigating reports of degraded performance for Actions and Pull Requests
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.
investigating
We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.
investigating
Pages is operating normally.
investigating
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.
investigating
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
investigating
We've identified an issue with a database primary and are failing over to a replica immediately
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of degraded availability for Actions
We are investigating reports of impacted performance for some GitHub services.
Legacy Incident Archive
128 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
May 2026
Incident with Pull Requests
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
Creation of new Pull Request threads (including line and file comments) continues to be affected although we are seeing partial recovery.<br /><br />A mitigation is being applied to continue to accelerate recovery with complete recovery expected by 8:00pm UTC.<br /><br />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
Creation of new Pull Request threads (including line and file comments) continues to be affected. <br /><br />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. <br /><br />A mitigation is being applied. Recovery is expected to be gradual, with complete recovery expected by 8:00pm UTC.
investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
investigating
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
We are investigating failures for new thread creation on Pull Requests. Responses to existing pull request threads are unaffected.
investigating
We are investigating reports of degraded performance for Pull Requests
Disruption with some GitHub services
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating issues with the ability to start Copilot Cloud Agent sessions and view them.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Actions, we are investigating reports of degraded availability
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
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.
investigating
Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue
investigating
We are investigating reports of degraded availability for Actions
Increased Latency and Failures for SSH Git Operations
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
investigating
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.
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
monitoring
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
We are investigating reports of impacted performance for some GitHub services.
Incident with Actions
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
investigating
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
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
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
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
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
We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs
investigating
We are investigating reports of degraded availability for Actions
Incident with Issues and Webhooks
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
investigating
Pull Requests is operating normally.
investigating
Pages is operating normally.
investigating
Latency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.
investigating
Actions and Packages are operating normally.
investigating
Git Operations is operating normally.
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
investigating
Codespaces is experiencing degraded performance. We are continuing to investigate.
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
investigating
Packages is experiencing degraded performance. We are continuing to investigate.
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating Increased latency and timeouts across multiple GitHub services.
investigating
We are investigating reports of degraded performance for Issues and Webhooks
April 2026
Incomplete pull request results in repositories
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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
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
Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.
investigating
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
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.<br /><br />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
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
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.<br /><br />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
We are investigating reports of degraded performance for Pull Requests
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Less than 1% of hosted ubuntu-latest runs are delayed. We’re working through remaining steps to restore runner capacity.
investigating
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
We've applied a mitigation to unblock running Actions. We're continuing to monitor.
investigating
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
Actions is experiencing degraded performance. We are continuing to investigate.
monitoring
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
We are investigating reports of impacted performance for some GitHub services.
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We've found the issue and are working on deploying a solution to get Codex agent runs working again.
investigating
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
We are investigating reports of impacted performance for some GitHub services.
GitHub search is degraded
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The degradation affecting Actions, Issues, Packages and Pull Requests has been mitigated. We are monitoring to ensure stability.
investigating
We've applied a mitigation and continuing to monitor
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
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
Pull Requests is experiencing degraded availability. We are continuing to investigate.
investigating
We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause
investigating
Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs.<br /><br />We are still investigating and attempting mitigations. We will provide further updates.
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
Packages is experiencing degraded performance. We are continuing to investigate.
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
investigating
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
We are investigating reports of degraded performance for Actions
