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.
April 2026
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of degraded performance for Actions
Delays with Actions Jobs for Larger Runners using VNet Injection in the East US region
minorSource not attested
Last archived state: resolved
View archived record details
investigating
This is related to the public impact, "Multiservice impact for Azure Workloads in East US" shared at https://azure.status.microsoft/
investigating
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
We are investigating reports of impacted performance for some GitHub services.
Incident with Pull Requests
minorSource not attested
Last archived state: resolved
View archived record details
investigating
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. <br /><br />This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.
investigating
Pull Requests is operating normally.
investigating
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
We are investigating reports of degraded performance for Pull Requests
Disruption with users unable to start Claude and Codex agent task from the web
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have identified the root cause of the issue and are working on mitigation.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with multiple GitHub services
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
Webhooks is operating normally.
investigating
Many services are mitigated and are validating the remaining services.
investigating
The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.
investigating
We have identified the root problem and are working on mitigation.
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating multiple unavailable services.
investigating
We are investigating reports of degraded availability for Copilot and Webhooks
Investigating errors on GitHub
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.
investigating
A mitigation was applied and services have recovered. Actions is working through queued work before fully recovering.
investigating
Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.
investigating
Copilot is experiencing degraded performance. We are continuing to investigate.
investigating
Codespaces is experiencing degraded performance. We are continuing to investigate.
investigating
Packages is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of degraded performance for Actions
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have identified the root cause of the disruption affecting Copilot Coding Agent and Issues. A fix is being deployed.
investigating
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. <br />
investigating
Copilot @-mentions on pull requests are currently not being processed by Copilot Cloud Agent. We have found the issue and are investigating remediations.
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with Copilot chat and Copilot Coding Agent
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
Copilot cloud agent and chat are mitigated for github.com.
investigating
We are now seeing recovery for Copilot cloud agent.
investigating
Mitigation is progressing for Copilot chat and cloud agent recovery.
investigating
Mitigation is progressing for Copilot chat and cloud agent.
investigating
We continue to work on mitigation for Copilot chat and cloud agent.
investigating
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
We are investigating reports of impacted performance for some GitHub services.
Disruption with projects service
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue remains mitigated. Users may still experience small delays in changes to projects while we process the backlog of events. We expect a full recovery in approximately two hours.
monitoring
The issue remains mitigated. Users may still experience delays in changes to projects while we process the backlog of events. We expect a full recovery in approximately three hours.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
Recovery from the delays affecting GitHub Projects continues to progress. We have deployed additional mitigations that are accelerating processing of the backlog. Users may still experience delays where changes to projects are not reflected immediately. We expect full recovery within approximately six hours.
investigating
The queues are continuing to decrease and we are working to accelerate the rate of processing through the queues.
investigating
The mitigation is deployed and we are seeing recorvery in the queues and will provide an update as to when full recovery will be realized.
investigating
We are deploying a fix to relieve the queue of delayed data. Some users may still experience delays with GitHub Projects where changes are not reflected immediately as remaining backlogs are processed.
investigating
We continue to investigate delays with GitHub Projects where changes may not be reflected immediately. Our team has identified the cause and applied mitigations to address the issue. We are seeing initial signs of recovery, though some delays may persist as the system works through a backlog of pending updates.
investigating
We are investigating reports of delays with GitHub Projects. Users may notice that changes made to projects are not reflected immediately. Our team has identified the source of the delays and is actively working to resolve the issue.
investigating
We are investigating reports of impacted performance for some GitHub services.
Partial degradation for code scanning default setup and for code quality
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The issue remains mitigated. Issues that were linked to projects during the incident may take approximately three more hours to render correctly while we complete a re-index.
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 has been mitigated. We are monitoring to ensure stability.
investigating
The issue has been mitigated. Newly created issues linked to projects should now function as expected. Issues that were linked to projects during the incident may take approximately five hours to render correctly while we complete a re-index.
investigating
A deployment to fix this issue of new issues not showing up in projects is underway.
investigating
We continue to work on mitigation regarding new issues not showing on project boards.
investigating
We continue to work on mitigation regarding new issues not showing on project boards.
investigating
Code scanning default setup and Code Quality triggers are back up and running. PRs not processed before or during this incident will require a new push to trigger code scanning or code quality analysis.<br /><br />We are seeing problems with new issues not showing on project boards and are working on mitigation.
investigating
We are continuing to work on a mitigation to unblock code scanning default setup and code quality features on pull requests.
investigating
We are currently deploying mitigations that should unblock code scanning default setup and code quality features on pull requests.
investigating
We are actively working to mitigate an issue affecting code scanning default setup and code quality features on pull requests. Users may experience pull request code scanning and code quality analyses not being triggered on new pull requests. Our engineering team has identified the root cause and working on mitigating the issue.
investigating
We are investigating reports of impacted performance for some GitHub services.
