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
We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
investigating
Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.
investigating
Pull Requests is operating normally.
investigating
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
investigating
Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.
investigating
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
Incident with Git Operations, Issues, Actions and Pull Requests
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
investigating
We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
Incident with Git Operations, Pull Requests and Actions
Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
monitoring
We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
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 degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
investigating
We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
investigating
Actions is operating normally.
investigating
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
investigating
Git Operations is operating normally.
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
investigating
We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
investigating
Issues 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 availability for Actions, Git Operations and Pull Requests
We are deploying a mitigation and plan to resume migrations shortly thereafter
investigating
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
investigating
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
investigating
Pull Requests is operating normally.
investigating
Webhooks is operating normally.
investigating
We are investigating reports of degraded performance for Pull Requests and Webhooks
Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
investigating
We are investigating reports of impacted performance for some GitHub services.
We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
investigating
In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
investigating
We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
investigating
We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
investigating
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
investigating
We are investigating reports of degraded performance for Actions
GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.
investigating
We are currently applying a mitigation and anticipate recovery within thirty minutes.
investigating
We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.
investigating
We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
investigating
Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.
investigating
We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.
investigating
We are investigating reports of degraded performance for Actions
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.
investigating
We are continuing to work on mitigation. We will post another update in approximately one hour.
investigating
We have identified the problem and are actively working on mitigation.
investigating
We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.
investigating
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 have isolated a problematic component in our infrastructure and are working to mitigate. We will continue to post updates as we work toward resolution.
investigating
We are experiencing an issue that impacts approximately 10% of traffic to the web, resulting in slow and failed calls. We are investigating and will continue to post updates as we work toward mitigation.
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Codespaces
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
investigating
Our provider is implementing a mitigation and we are seeing signs of recovery.
investigating
We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.
investigating
Codespaces is experiencing degraded availability. We are continuing to investigate.
investigating
We are experiencing degraded performance in Codespaces related to creating a new Codespace or starting an existing Codespace from the VS Code editor. SSH connections to Codespaces are not impacted. We are working toward mitigation and will continue to keep you updated on progress.
investigating
We are investigating reports of degraded performance for Codespaces
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We identified an issue that impacts the Copilot Dashboard on the Insights tab and are working on mitigation. We will continue to keep you updated on progress.
investigating
The team continues to investigate issues accessing with Copilot Dashboard on the Insights tab. We will continue providing updates on the progress towards mitigation.
investigating
The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.
investigating
Degradation of Service - Insights Page
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Pages
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have mitigated the issue with Pages.
monitoring
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
investigating
We are investigating reports of issues with Pages. We will continue to keep users updated on progress towards mitigation.
investigating
We are investigating reports of degraded availability for Pages
Disruption with some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We have identified the root cause and are rolling out a fix for Copilot. The services should now be in recovery, with expected full recovery in 5 to 10 minutes.
investigating
We are investigating reports of impacted performance for some GitHub services.
Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with some GitHub services
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We continue to investigate periodic delays in Copilot Cloud Agent job processing
investigating
We are continuing to investigate Copilot Cloud Agent job delays
investigating
Copilot Cloud Agent jobs are being processed and we are monitoring recovery
investigating
We are investigating delays processing Copilot Cloud Agent jobs
investigating
We are experiencing issues where jobs are being delayed to start for copilot coding agent
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with some GitHub services
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We are investigating an issue affecting GitHub Copilot coding agent. Users may experience significant delays when starting new agent sessions, with jobs remaining queued longer than expected. Our team has identified increased load as a contributing factor and is actively working to restore normal performance.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with GitHub notifications
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 some GitHub services
minorSource not attested
Last archived state: resolved
View archived record details
investigating
Although we are observing recovery once again, we expect continued periods of degradation. <br /><br />Work that is queued during times of degradation does eventually get processed. <br /><br />We continue to investigate and find a mitigation, and will update again within 2 hours.
investigating
This issue has recurred. Customers will once again experience false job starts when assigning tasks to Copilot Cloud Agent. <br /><br />We are still investigating and trying to understand the pattern of degradation.
investigating
We are once again seeing recovery with Copilot Cloud Agent job starts. <br /><br />We are keeping this open while we verify this won't recur.
investigating
When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running.<br /><br />We are investigating.
investigating
We are investigating reports of impacted performance for some GitHub services.
