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.
March 2026
Git operations for users in the west coast are experiencing an increase in latency
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are seeing early signs of improvement. We are working on one more small change to further improve traffic routing on the west coast.
investigating
We have completed the rollout of our new network path and are monitoring its impact.
investigating
We are beginning the rollout of our new network path. During this change, users will continue to see higher latency from the west coast. We will provide another update when the rollout is complete.
investigating
We are working to enable a new network path in the west coast to reduce load and will monitor the impact on latency for Git Operations
investigating
We are still seeing elevated latency for Git operations in the west coast and are continuing to investigate
investigating
We are redirecting traffic back to our Seattle region and customers should see a decrease in latency for Git operations
investigating
We are investigating reports of degraded performance for Git Operations
Issues with Copilot Coding Agent
majorSource not attested
Last archived state: resolved
View archived record details
investigating
Copilot is operating normally.
investigating
We are investigating reports that Copilot Coding Agent session logs are not available in the UI.
investigating
Copilot is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with Copilot Coding Agent sessions
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have rolled out our mitigation and are seeing recovery for Copilot Coding Agent sessions
investigating
We are seeing widespread issues starting and viewing Copilot Agent sessions. We have a hypothesis for the cause and are working on remediation.
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 continue to investigate the slow performance of Git Operations affecting the US West Coast.
investigating
We continue to investigate degraded performance for git operations from the US West Coast.
investigating
We are continuing to investigate degraded performance for git operations from the US West Coast.
investigating
We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of impacted performance for some GitHub services.
Webhook delivery is delayed
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are seeing recovery and are continuing to monitor the latency for webhook deliveries
investigating
We are investigating reports of degraded performance for Webhooks
Errors starting and connecting to Codespaces
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of users experiencing errors when starting or connecting to Codespaces. Some users may be unable to access their development environments during this time. We are working to identify the root cause and will implement a fix as soon as possible.
investigating
We are investigating reports of impacted performance for some GitHub services.
Degraded performance for various services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have deployed mitigations and are actively monitoring for recovery. We'll post another update by 17:00 UTC.
investigating
We are investigating intermittent performance degradation affecting Actions, Feeds, Issues, Package Registry, Profiles, Registry Metadata, Star, and User Dashboard. Users may experience elevated error rates and slower response times when accessing these services. We have identified a potential cause and are implementing mitigations to restore normal service. We'll post another update by 16:15 UTC.
investigating
Packages is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of issues with service(s): Actions, Feeds, Issues, Profiles, Registry Metadata, Star, User Dashboard. We will continue to keep users updated on progress towards mitigation.
investigating
We are investigating reports of degraded performance for Actions and Issues
Degraded Codespaces experience
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Codespaces IPs are no longer being blocked from Visual Studio Marketplace operations and we are monitoring for full recovery
investigating
We're seeing intermittent failures downloading from the extension marketplace from codespaces, caused by IP blocks for some codespaces. We're working to remove those blocks.
investigating
We're seeing intermittent failures downloading from the extension marketplace from codespaces and are investigating.
investigating
We're seeing partial recovery for the issue affecting extension installation in newly created Codespaces. Some users may still experience degraded functionality where extensions hit errors. The team continues to investigate the root cause while monitoring the recovery.
investigating
We have deployed a fix for the issue affecting extension installation in newly created Codespaces. New Codespaces are now being created with working extensions. We'll post another update by 15:30 UTC.
investigating
We are continuing to investigate an issue where extensions fail to install in newly created Codespaces. Users can create and access Codespaces, but extensions will not be operational, resulting in a degraded experience. The team is working on a fix. All newly created Codespaces are affected. We'll post another update by 15:00 UTC.
investigating
We're investigating an issue where extensions fail to install in newly created Codespaces. Users can still create and access Codespaces, but extensions will not be operational, resulting in a degraded development experience. Our team is actively working to identify and resolve the root cause. We'll post another update by 14:00 UTC.
investigating
We are investigating reports of degraded performance for Codespaces
