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 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.
August 2026
Incident with Pull Requests and Issues
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.
monitoring
The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
investigating
We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.
investigating
We are investigating reports of degraded performance for Issues and Pull Requests
Incident with GraphQL API Requests
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
investigating
We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.
investigating
We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information
investigating
We are investigating reports of degraded performance for API Requests
Disruption with Copilot for access to some models
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue has been mitigated across all affected environments. We are currently deploying on a fix to prevent reoccurrence. We will provide another update once the fix has been deployed.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
monitoring
We are currently investigating reports of some Copilot users experiencing issues accessing certain models. Affected users may see errors or degraded functionality when attempting to use specific models. We are actively working on a fix and will provide updates as we have more information.
investigating
We are investigating reports of impacted performance for some GitHub services.
Disruption with creation of fine grained personal access tokens
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created.
investigating
We are investigating reports of impacted performance for some GitHub services.
Incident with Actions
criticalSource not attested
Last archived state: resolved
View archived record details
monitoring
We’re investigating reports that some Actions Runner Controller runners are taking longer than expected to recover. We’ll provide an update as our investigation progresses.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
investigating
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
investigating
System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will provide ...
investigating
<br />System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out.<br /><br />Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and Copilot coding agent are showing recovery. Migrations using GitHub Enterprise Importer remain paused as a precaution.<br /><br />We are monitoring all affected services for sustained recovery and will pr...
investigating
We have deployed fixes that address runners being assigned invalid jobs and are taking additional steps to clear the backlog of affected jobs. Job completion rates for running workflows have improved significantly, with success rates now at 99%. Global queues for hosted runner assignment are nearly burned down and concurrency queues for customers are being processed. Another change was deployed to accelerate processing the backlog of job requests.<br /><br />We are gradually restoring through...
investigating
We continue to make progress on the issue affecting GitHub Actions. We have deployed a fix that addresses runners being assigned jobs that are no longer valid, and are seeing improvement in job completion rates. For workflow runs that are starting, success rates have increased significantly and are now at 97%. Standard and larger runners are now draining queued work. A change is also in progress to mitigate issues with existing self-hosted runners that are not picking up jobs.<br /><br />Webh...
investigating
We are continuing to work on an issue affecting GitHub Actions. Webhook triggers remain throttled to aid recovery, so many push and pull request events are not triggering new workflow runs.<br /><br />We identified runners being assigned jobs that are no longer valid and are deploying a change to address this issue. Both GitHub-hosted and self-hosted runners are affected.<br /><br />Copilot code review, Copilot coding agent, and GitHub Pages may experience failures or delays. Migrations using...
investigating
We are continuing to work on an issue affecting GitHub Actions. Webhook triggers are currently throttled to help with recovery and and we are processing approximately 15% of webhooks, so many events such as pushes and pull requests are not triggering workflow runs. Of jobs queued, approximately 65% are succeeding, improved from a low of 30 to 40% earlier in this incident.<br /><br />We have narrowed the remaining impact to runners that are stuck retrying jobs that are no longer available. Bot...
investigating
We are continuing to work on an issue affecting GitHub Actions. <br /><br />Capacity remains constrained and jobs may still be delayed or fail while it recovers gradually. Customers using self-hosted runners may see errors or rate limiting when runners register. <br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed. <br /><br />Our engineers remain actively engaged.
investigating
We are continuing to work on an issue affecting multiple GitHub services. <br /><br />Workflow runs are still failing, and jobs may remain queued for an extended period before starting or may time out. Jobs using GitHub-hosted runners are particularly affected while capacity is constrained. <br /><br />Customers using self-hosted runners may see errors or rate limiting when runners register. <br /><br />Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer...
investigating
We are continuing to work on an issue affecting multiple GitHub services. <br /><br />Workflow runs are still failing or delayed in starting, and some queued jobs may time out. <br /><br />Customers using self-hosted runners may see errors or rate limiting when runners register. <br /><br />Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected. <br /><br />Webhook deliveries may be delayed.<br /><br />Engineers have app...
investigating
We are continuing to work on an issue affecting multiple GitHub services.<br /><br />Workflow runs are failing or delayed in starting, and some queued jobs may time out. <br /><br />Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected. <br /><br />Webhook deliveries may be delayed. <br /><br />Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now.
investigating
We are continuing to work on the issue affecting GitHub Actions. <br /><br />Workflow runs are still failing or delayed in starting, and some queued jobs may time out. <br /><br />Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures. <br /><br />Our engineers have applied several mitigations and are rolling out a further fix now.
investigating
Actions and Pages are experiencing degraded availability. We are continuing to investigate.
investigating
We are continuing to work on the issue affecting GitHub Actions. <br /><br />Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors. <br /><br />Customers running migrations with GitHub Enterprise Importer may also see failures. <br /><br />Engineers are actively working towards full recovery.
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
investigating
Pages is operating normally.
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
investigating
We are investigating errors affecting GitHub Actions. Some workflow runs are failing to start or failing partway through, and some requests to the Actions REST API are returning errors. <br /><br />Some customers may also see unexpected rate limiting in their workflows. <br /><br />Engineers have identified the source of the disruption and are actively working on a mitigation
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
investigating
We are investigating reports of degraded performance for Actions
Incident with Pages - Deployment Lag
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
investigating
We are investigating reports of degraded performance for Pages
Some Copilot Cloud Agent jobs not starting
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
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 degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
investigating
We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.
investigating
We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.
investigating
We are investigating reports of degraded performance for Copilot
Incident with Copilot AI Model Providers
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces.<br /><br />We will continue monitoring to ensure stability, but mitigation is complete.
monitoring
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
investigating
We are experiencing degraded availability for the Fable 5 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 seeing increased error rates from specific upstream AI Model Providers
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
Degraded availability GPT 5.6 Luna
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability.
investigating
We are experiencing degraded availability for the GPT-5.6 Luna 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 performance for Copilot AI Model Providers
