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 successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
investigating
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 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.
