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
Copilot Coding Agent failing to start some jobs
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with GitHub's code search
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.
investigating
We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.
investigating
We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April 2026). We are still working on recovering our ingestion pipeline, and synchronizing the indexed data.<br /><br />We will update again within 2 hours.
investigating
We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic configuration which is causing most requests for Code Search results to fail. We are working to restore the service and to re-ingest the misaligned data.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Copilot
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The success rate and latency for creating and viewing agent sessions has stabilized at baseline levels, we are continuing to monitor recovery
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The success rate for creating and viewing agent sessions has stabilized, and we're continuing to monitor latency, which is trending toward baseline levels.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
investigating
Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate.
investigating
We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation.
investigating
We are investigating reports of degraded performance for Copilot
March 2026
Incident with Pull Requests: High percentage of 500s
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
investigating
We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.
investigating
Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.
investigating
We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.
investigating
We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.
investigating
We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.
investigating
We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.
investigating
We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.
investigating
We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.
investigating
We are investigating reports of degraded performance for Pull Requests
Issues with metered billing report generation
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 have applied mitigations to a data store related to billing reports, and are seeing partial recovery to billing report generation. We continue to monitor for full recovery.
investigating
We are seeing a high number of 500s due to timeouts across GitHub services. We are redeploying some of our core services and we expect that this allow us to recover.
investigating
We're continuing to see high failure rates on billing report generation, and are working on mitigations for a data store related to billing reports.
investigating
We're seeing issues related to metered billing reports, intermittently affecting metered usage graphs and reports on the billing page. We have identified an issue with a data store, and are working on mitigations.
investigating
We are investigating reports of impacted performance for some GitHub services.
Elevated delays in Actions workflow runs and Pull Request status updates
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating reports of degraded performance for Actions and Pull Requests
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating elevated error rates affecting multiple GitHub services including Actions, Issues, Pull Requests, Webhooks, Codespaces, and login functionality. Some users may have experienced errors when accessing these features. Most services are now showing signs of recovery. We'll post another update by 21:00 UTC.
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of degraded performance for Actions
Teams Github Notifications App is down
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are experiencing degraded availability from Azure Teams APIs, which is impacting notifications from GitHub to Microsoft Teams. We are awaiting resolution from Azure.
investigating
We are experiencing degraded availability from Azure APIs, which is impacting notifications from GitHub to Microsoft Teams. We are working with Azure to resolve the issue.
investigating
We found an issue impacting notifications from GitHub to Microsoft Teams. We are working on mitigation and will keep users updated on progress towards mitigation.
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 intermittently high latency and errors from Git operations.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with Copilot Coding Agent Sessions
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are rolling out our mitigation and are seeing recovery.
investigating
We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation.
investigating
We are investigating reports of impacted performance for some GitHub services.
