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.
June 2026
Disruption with some GitHub services in the EU region
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Packages is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of impacted performance for some GitHub services.
EU Network Maintenance
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We are conducting routine maintenance on our network infrastructure in the EU. This will not impact production traffic, but may result in slightly increased latency for the remainder of our work. We expect this to last until 17:00 UTC.
investigating
We are investigating reports of impacted performance for some GitHub services.
Auth issue resulting in API impacts, including some Slack and Teams channel subscriptions
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Additional detail on the scope of impact during the 14:49 UTC to 16:45 UTC window: a small but elevated percentage of authenticated requests to GitHub.com received incorrect authorization failures. We saw a 1 to 2% increase in 4xx responses for a small number of endpoints (/repos/{owner}/{repo}/pulls/{pull_number}, /repos/{owner}/{repo}, /repos/{owner}/{repo}/contents/{path}). The vast majority of requests completed normally; customers who saw errors during the window can retry now and should...
monitoring
We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
During 14:49 UTC to 16:45 UTC, customers may have experienced authorization failures for legitimate requests. This was caused by a recently enabled feature flag, which has now been turned off as a mitigation. Customers should now see normal authorization behavior. This is also the cause of the chat integration issue, and we are exploring options to restore it. In the meantime, customers can manually re-subscribe their repo.
investigating
Customers may see unexpected repo unsubscription events in their Slack or Teams channels.
investigating
We are investigating reports of impacted performance for some GitHub services.
Live updates degraded
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of impacted performance for some GitHub services.
Copilot Code Review Failing
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected. We are continuing to monitor for full resolution.<br /><br /> Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
The mitigation for Copilot Code Review is now fully deployed, and new reviews are working as expected.<br /><br />Customers may need to re-request Copilot Code Review. Copilot Code Review Actions runs running for longer than 20 minutes may be safely cancelled.
investigating
The mitigation for Copilot Code Review is rolling out and we are seeing early signs of recovery.
investigating
We have identified that Copilot Code Review users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress, we expect mitigation in approximately 30m.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.
investigating
We have identified that Copilot Code Review. Users may see "Copilot ran into an error" on Pull Requests that requested Copilot Code Review.<br /><br />A mitigation is in progress.
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
monitoring
Job lag has recovered from a peak of 1.71 days to 9h 9m at 19:29 UTC and continues to decrease. Backlog is draining at a healthy rate with no signs of reversal. New jobs are processing on schedule. Remaining lag will continue to drain over the next few hours as queued work completes; this is expected post-incident catch-up, not active impact. We will continue monitoring and re-engage if lag trend reverses.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We have applied mitigations and are continuing to see improvements in the Dependabot scheduled version updates. <br /><br />Next update in 12 hours.
investigating
We are preparing a mitigation for the delayed Dependabot scheduled version updates.<br /><br />Next update in 2 hours.
investigating
Customers may see delays of up to two days in Dependabot version updates.<br /><br />Dependabot Security updates are not delayed.<br /><br />The team is investigating mitigations for the backlog.<br /><br />Next update in 1 hour.
investigating
We're seeing delays in Dependabot scheduled version update runs. Our team is actively working on a fix and will share updates as the situation develops.
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 are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation.
investigating
We are investigating reports of impacted performance for some GitHub services.<br /><br />---<br />Relevant stamps: dotcom
investigating
We are investigating reports of impacted performance for some GitHub services.
Delays with Code Scanning and Billing
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have identified the root cause and applied mitigations to address delays in billing updates and are continuing to see improvement in the processing rate. We will continue to monitor the progress and will provide an update in few hours.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.<br />
investigating
We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations are continuing to see signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.<br /><br />Next update in 2 hours.
investigating
We are continuing to investigate delayed billing updates, on GitHub.com. We have applied additional mitigations and are seeing some more signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.
investigating
We are continuing to investigate delayed billing updates, on GitHub.com. We have applied multiple mitigations and are seeing some signs of improvement, and are continuing to work to improve the processing rate. We will continue to keep users updated on progress towards mitigation.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.
investigating
We are investigating reports of delayed billing updates, on GitHub.com. We are continuing to investigate delays in our job processing architecture. We are attempting to mitigate at the infrastructure level. Code scanning runs and notifications have recovered. We will continue to keep users updated on progress towards mitigation.<br /><br />GitHub Enterprise Cloud with Data Residency is not impacted.
investigating
We are investigating reports of delayed code scanning runs, billing updates, email and mobile push notifications. We are investigating delays in our job processing architecture. We will continue to keep users updated on progress towards mitigation.
investigating
We are investigating reports of delayed code scanning runs and delayed billing updates. We will continue to keep users updated on progress towards mitigation.
investigating
We are investigating reports of impacted performance for some GitHub services.
May 2026
Disruption with Copilot Cloud Agent and Copilot Code Review
criticalSource not attested
Last archived state: resolved
View archived record details
investigating
Open AI models are currently unavailable. We are shifting requests to other models to reduce impact.
investigating
We are investigating errors with Copilot requests using OpenAI models
investigating
Copilot is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of impacted performance for some GitHub services.
Webhook APIs and UI Degraded
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
investigating
We are investigating reports of degraded performance for Webhooks
