Subscribe to UpdatesSubscribe
Get email notifications whenever GitHub creates, updates or resolves an incident.
Get text message notifications whenever GitHub creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever GitHub creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
All Systems Operational
About This Site
Check GitHub Enterprise Cloud status by region:
- Australia: au.githubstatus.com
- EU: eu.githubstatus.com
- Japan: jp.githubstatus.com
- US: us.githubstatus.com
Uptime over the past 90 days. View historical uptime.
Git Operations
Operational
90 days ago
99.99
% uptime
Today
Webhooks
Operational
90 days ago
99.99
% uptime
Today
Visit www.githubstatus.com for more information
Operational
API Requests
Operational
90 days ago
99.81
% uptime
Today
Issues
Operational
90 days ago
99.88
% uptime
Today
Pull Requests
Operational
90 days ago
99.88
% uptime
Today
Actions
Operational
90 days ago
99.33
% uptime
Today
Packages
Operational
90 days ago
100.0
% uptime
Today
Pages
Operational
90 days ago
99.65
% uptime
Today
Copilot
Operational
90 days ago
99.64
% uptime
Today
Codespaces
Operational
90 days ago
99.97
% uptime
Today
Copilot AI Model Providers
Operational
90 days ago
99.88
% uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Aug 18, 2026
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Aug 18, 11:42 UTC
Aug 18, 11:42 UTC
Update -
We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.
Aug 18, 11:24 UTC
Aug 18, 11:24 UTC
Update -
We have identified the source of a communication issue between Actions services and are working toward mitigation. Customers may experience failure to load runner groups and runner-related permissions issues when using Larger Runners.
Aug 18, 10:41 UTC
Aug 18, 10:41 UTC
Monitoring -
We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.
Aug 18, 07:40 UTC
Aug 18, 07:40 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 18, 07:40 UTC
Aug 18, 07:40 UTC
Resolved -
This incident was posted in error. GitHub Actions workflows were not impacted, and we have confirmed that workflow runs continued to operate normally throughout this period.
Aug 18, 10:23 UTC
Aug 18, 10:23 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 18, 09:36 UTC
Aug 18, 09:36 UTC
Aug 17, 2026
Resolved -
On August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot. At peak, web/API error rates were approximately 20%, while archive and raw-content downloads reached approximately 50%. SAML/OIDC authentication, SCIM, and Team Sync were also affected, as well as Actions workflows in GHEC with Data Residency that depend on public workflow step definitions hosted on GitHub.com. Most services recovered by 16:36 UTC as our Central US datacenter recovered; Actions was degraded until approximately 18:03 UTC; and Copilot Token Service fully recovered by 21:02.
Some of the failing traffic was moved from Central US to Northern Virginia where it was served successfully until the network failure in Central US was debugged and resolved. Delayed replies to a single internal endpoint triggered a latent retry bug in VS Code that amplified traffic by approximately 10x and caused delayed recovery for the Copilot Token Service.
The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers. Pausing HAProxy on those nodes simultaneously produced immediate broad recovery.
The retry storm in Northern VA was fixed by 1) temporarily reducing gateway retry logic with a PR and 2) blocking inbound Copilot Token Service token requests at the load balancers with a 403, and then gradually ramping back up traffic per-site to allow callers to succeed.
Residual Copilot authentication failures continued because client retry behavior amplified load: a failed token operation could generate many extra requests and enter a retry loop. Copilot Token Service traffic increased from a normal 7–9K RPS to 70–100K RPS. Reducing gateway authentication retries and blocking retry-triggering responses stabilized Copilot Token Service and completed recovery.
Complicating factors that impeded recovery included a number of scraping attacks on codeload endpoints.
To prevent recurrence, our follow-up actions include:
- Correcting autoscaling policies to account for service-mesh sidecar concurrency and capacity.
- Auditing Istio request, concurrency, and scaling limits across affected services.
- Reviewing retry limits and backoff behavior across gateways and clients.
- Addressing the VS Code retry behavior that amplified Copilot token traffic.
- Improving load-balancer capacity monitoring and regional failover safeguards.
Aug 17, 21:15 UTC
Some of the failing traffic was moved from Central US to Northern Virginia where it was served successfully until the network failure in Central US was debugged and resolved. Delayed replies to a single internal endpoint triggered a latent retry bug in VS Code that amplified traffic by approximately 10x and caused delayed recovery for the Copilot Token Service.
The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers. Pausing HAProxy on those nodes simultaneously produced immediate broad recovery.
The retry storm in Northern VA was fixed by 1) temporarily reducing gateway retry logic with a PR and 2) blocking inbound Copilot Token Service token requests at the load balancers with a 403, and then gradually ramping back up traffic per-site to allow callers to succeed.
Residual Copilot authentication failures continued because client retry behavior amplified load: a failed token operation could generate many extra requests and enter a retry loop. Copilot Token Service traffic increased from a normal 7–9K RPS to 70–100K RPS. Reducing gateway authentication retries and blocking retry-triggering responses stabilized Copilot Token Service and completed recovery.
Complicating factors that impeded recovery included a number of scraping attacks on codeload endpoints.
To prevent recurrence, our follow-up actions include:
- Correcting autoscaling policies to account for service-mesh sidecar concurrency and capacity.
- Auditing Istio request, concurrency, and scaling limits across affected services.
- Reviewing retry limits and backoff behavior across gateways and clients.
- Addressing the VS Code retry behavior that amplified Copilot token traffic.
- Improving load-balancer capacity monitoring and regional failover safeguards.
Aug 17, 21:15 UTC
Update -
We are continuing to apply mitigations to address sporadic Copilot authentication failures in some applications. We expect full recovery within the next 30 minutes. Copilot usage via the GitHub CLI and GitHub App are unaffected.
Aug 17, 20:45 UTC
Aug 17, 20:45 UTC
Update -
Issues is operating normally.
Aug 17, 20:22 UTC
Aug 17, 20:22 UTC
Update -
We are continuing to investigate sporadic failures affecting Copilot authentication in some applications. Copilot usage via the GitHub CLI and GitHub App are unaffected.
Aug 17, 20:08 UTC
Aug 17, 20:08 UTC
Update -
We are continuing to investigate sporadic authentication failures. We have partially disabled authentication token retries and have seen improvement, and we are monitoring impact before fully applying this mitigation.
Aug 17, 19:13 UTC
Aug 17, 19:13 UTC
Update -
API Requests is operating normally.
Aug 17, 19:01 UTC
Aug 17, 19:01 UTC
Update -
API Requests is experiencing degraded availability. We are continuing to investigate.
Aug 17, 18:48 UTC
Aug 17, 18:48 UTC
Update -
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
Aug 17, 18:23 UTC
Aug 17, 18:23 UTC
Update -
We identified the problematic component and have taken corrective actions, but we are seeing residual impact in the form of sporadic authentication failures. We are continuing to apply additional mitigations and investigate the remaining impact.
Aug 17, 18:11 UTC
Aug 17, 18:11 UTC
Update -
Issues is experiencing degraded performance. We are continuing to investigate.
Aug 17, 17:36 UTC
Aug 17, 17:36 UTC
Update -
We identified the problematic component and have taken corrective actions, but we are seeing residual impact across numerous services. We are continuing to apply additional mitigations and investigate the remaining impact.
Aug 17, 17:34 UTC
Aug 17, 17:34 UTC
Update -
Git Operations is experiencing degraded performance. We are continuing to investigate.
Aug 17, 17:30 UTC
Aug 17, 17:30 UTC
Update -
The degradation affecting API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
Aug 17, 16:59 UTC
Aug 17, 16:59 UTC
Update -
We identified the problematic component and have taken corrective actions. There are strong signs of recovery but we are still working to completely restore service, with error rates still remaining slightly elevated. We will post further updates as recovery continues.
Aug 17, 16:36 UTC
Aug 17, 16:36 UTC
Update -
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are still working to identify the root cause and will continue to post updates as we learn more and perform mitigation.
Aug 17, 16:16 UTC
Aug 17, 16:16 UTC
Update -
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently performing mitigations and will post updates as we progress.
Aug 17, 15:42 UTC
Aug 17, 15:42 UTC
Update -
Webhooks is experiencing degraded performance. We are continuing to investigate.
Aug 17, 15:40 UTC
Aug 17, 15:40 UTC
Update -
Git Operations is experiencing degraded performance. We are continuing to investigate.
Aug 17, 15:21 UTC
Aug 17, 15:21 UTC
Update -
Pages is experiencing degraded performance. We are continuing to investigate.
Aug 17, 15:10 UTC
Aug 17, 15:10 UTC
Update -
API Requests is experiencing degraded availability. We are continuing to investigate.
Aug 17, 15:01 UTC
Aug 17, 15:01 UTC
Update -
Webhooks is experiencing degraded availability. We are continuing to investigate.
Aug 17, 14:58 UTC
Aug 17, 14:58 UTC
Update -
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently performing mitigations based on our investigation thus far and are monitoring for improvement.
Aug 17, 14:58 UTC
Aug 17, 14:58 UTC
Update -
Actions is experiencing degraded availability. We are continuing to investigate.
Aug 17, 14:58 UTC
Aug 17, 14:58 UTC
Update -
Pull Requests is experiencing degraded availability. We are continuing to investigate.
Aug 17, 14:54 UTC
Aug 17, 14:54 UTC
Update -
Issues is experiencing degraded availability. We are continuing to investigate.
Aug 17, 14:49 UTC
Aug 17, 14:49 UTC
Update -
Pull Requests is experiencing degraded availability. We are continuing to investigate.
Aug 17, 14:45 UTC
Aug 17, 14:45 UTC
Update -
Copilot is experiencing degraded availability. We are continuing to investigate.
Aug 17, 14:31 UTC
Aug 17, 14:31 UTC
Update -
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. Investigations are on-going and we will continue to provide updates as we discover more information.
Aug 17, 14:24 UTC
Aug 17, 14:24 UTC
Update -
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. Investigations are on-going into the root cause, and updates will continue to be provided as we investigate.
Aug 17, 14:04 UTC
Aug 17, 14:04 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Aug 17, 13:58 UTC
Aug 17, 13:58 UTC
Update -
Issues is experiencing degraded performance. We are continuing to investigate.
Aug 17, 13:46 UTC
Aug 17, 13:46 UTC
Update -
We are seeing an approximate 20% error rate across numerous experiences including Pull Requests, Issues, and others. Investigations are currently under way and we will be posting updates as they become available
Aug 17, 13:45 UTC
Aug 17, 13:45 UTC
Update -
Webhooks is experiencing degraded performance. We are continuing to investigate.
Aug 17, 13:44 UTC
Aug 17, 13:44 UTC
Update -
Actions is experiencing degraded performance. We are continuing to investigate.
Aug 17, 13:42 UTC
Aug 17, 13:42 UTC
Update -
API Requests is experiencing degraded performance. We are continuing to investigate.
Aug 17, 13:41 UTC
Aug 17, 13:41 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 17, 13:40 UTC
Aug 17, 13:40 UTC
Aug 16, 2026
No incidents reported.
Aug 15, 2026
No incidents reported.
Aug 14, 2026
No incidents reported.
Aug 13, 2026
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Aug 13, 18:27 UTC
Aug 13, 18:27 UTC
Update -
We have deployed a mitigation. At this time GHEC Team Sync has recovered for enterprises with personal accounts. Teams syncing to IdP groups have returned to their normal cadence.
Aug 13, 18:27 UTC
Aug 13, 18:27 UTC
Update -
GHEC Team Sync is currently degraded for enterprises with personal accounts, causing delays when syncing teams to IdP groups. We have identified the cause of the delays and are working on a mitigation. We will provide an update on our progress at 20:00 UTC.
Aug 13, 16:21 UTC
Aug 13, 16:21 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 13, 16:21 UTC
Aug 13, 16:21 UTC
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Aug 13, 15:47 UTC
Aug 13, 15:47 UTC
Update -
The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces.
We will continue monitoring to ensure stability, but mitigation is complete.
Aug 13, 15:47 UTC
We will continue monitoring to ensure stability, but mitigation is complete.
Aug 13, 15:47 UTC
Update -
We are seeing modest recovery, but are still 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.
Aug 13, 15:23 UTC
Aug 13, 15:23 UTC
Update -
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.
Aug 13, 14:50 UTC
Aug 13, 14:50 UTC
Investigating -
We are investigating reports of degraded performance for Copilot AI Model Providers
Aug 13, 14:43 UTC
Aug 13, 14:43 UTC
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Aug 13, 15:36 UTC
Aug 13, 15:36 UTC
Update -
We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.
Aug 13, 15:33 UTC
Aug 13, 15:33 UTC
Monitoring -
The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
Aug 13, 15:33 UTC
Aug 13, 15:33 UTC
Update -
We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies to prevent recurrence.
Aug 13, 14:58 UTC
Aug 13, 14:58 UTC
Update -
Packages is experiencing degraded performance. We are continuing to investigate.
Aug 13, 14:56 UTC
Aug 13, 14:56 UTC
Update -
Git Operations is experiencing degraded performance. We are continuing to investigate.
Aug 13, 14:46 UTC
Aug 13, 14:46 UTC
Update -
Issues is experiencing degraded performance. We are continuing to investigate.
Aug 13, 14:46 UTC
Aug 13, 14:46 UTC
Update -
Pull Requests is experiencing degraded performance. We are continuing to investigate.
Aug 13, 14:46 UTC
Aug 13, 14:46 UTC
Investigating -
We are investigating reports of degraded performance for Webhooks
Aug 13, 14:45 UTC
Aug 13, 14:45 UTC
Aug 12, 2026
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Aug 12, 22:56 UTC
Aug 12, 22:56 UTC
Update -
We have identified the root cause and are working on mitigation. Errors on the login page and downloading release assets have decreased, but we are not fully mitigated. We will continue to provide updates.
Aug 12, 22:22 UTC
Aug 12, 22:22 UTC
Update -
We are investigating issues with Login and when downloading Release Assets. We will continue to keep users updated on progress towards mitigation.
Aug 12, 21:43 UTC
Aug 12, 21:43 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 12, 21:39 UTC
Aug 12, 21:39 UTC
Resolved -
Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors.
Aug 12, 16:41 UTC
Aug 12, 16:41 UTC
Update -
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.
Aug 12, 16:38 UTC
Aug 12, 16:38 UTC
Monitoring -
The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
Aug 12, 16:35 UTC
Aug 12, 16:35 UTC
Update -
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.
Aug 12, 16:24 UTC
Aug 12, 16:24 UTC
Investigating -
We are investigating reports of degraded performance for Issues and Pull Requests
Aug 12, 16:16 UTC
Aug 12, 16:16 UTC
Aug 11, 2026
Resolved -
On August 11, 2026, between 14:00 UTC and 16:00 UTC the GraphQL API service was degraded and customers in saw higher than normal timeouts. On average, the timeout rate was 0.06% and peaked at 0.14% of requests routing to the service.
This was due to increased utilization at one of our sites which caused resource contention across our dependencies, leading to an increase in timeouts for GraphQL requests. We mitigated the incident by increasing capacity to alleviate the capacity bottleneck.
We are working to improve our monitoring so that we can proactively reduce the impact of high consumption requests in addition to scaling up; Additionally, we will improve our time to detection and mitigation of issues like this one in the future.
Aug 11, 20:06 UTC
This was due to increased utilization at one of our sites which caused resource contention across our dependencies, leading to an increase in timeouts for GraphQL requests. We mitigated the incident by increasing capacity to alleviate the capacity bottleneck.
We are working to improve our monitoring so that we can proactively reduce the impact of high consumption requests in addition to scaling up; Additionally, we will improve our time to detection and mitigation of issues like this one in the future.
Aug 11, 20:06 UTC
Update -
We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident.
Aug 11, 20:06 UTC
Aug 11, 20:06 UTC
Monitoring -
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
Aug 11, 16:49 UTC
Aug 11, 16:49 UTC
Update -
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.
Aug 11, 16:49 UTC
Aug 11, 16:49 UTC
Update -
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
Aug 11, 15:28 UTC
Aug 11, 15:28 UTC
Investigating -
We are investigating reports of degraded performance for API Requests
Aug 11, 14:50 UTC
Aug 11, 14:50 UTC
Aug 10, 2026
Resolved -
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Aug 10, 21:50 UTC
Aug 10, 21:50 UTC
Update -
We have deployed and validated the fix to prevent immediate reoccurrence. We will be performing additional work to limit these kinds of failures in the future.
Aug 10, 21:50 UTC
Aug 10, 21:50 UTC
Update -
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.
Aug 10, 21:19 UTC
Aug 10, 21:19 UTC
Update -
The degradation has been mitigated. We are monitoring to ensure stability.
Aug 10, 20:49 UTC
Aug 10, 20:49 UTC
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.
Aug 10, 20:39 UTC
Aug 10, 20:39 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 10, 20:27 UTC
Aug 10, 20:27 UTC
Resolved -
On August 10, 2026, between 17:16 and 18:21 UTC, users were unable to create new fine-grained personal access tokens (FG PAT) through the GitHub website. When a user submitted the FG PAT creation form, they were returned to the FG PAT list without an error message and no FG PAT was created. Creating classic personal access tokens, as well as editing or deleting existing FG PAT were not affected.
The cause was a change to how the website loads certain front-end JavaScript that was enabled for all users at 17:15 UTC; the change interacted with an issue in the token creation form's confirmation step that prevented it from running, so the final submission that actually creates the token never completed. Because the page still loaded and the server returned a normal response, the failure produced no error message. GitHub mitigated the incident by disabling the change at 18:21 UTC, at which point token creation recovered immediately, and the incident was resolved at 18:46 UTC.
To reduce the chance of recurrence, GitHub is adding monitoring and alerting for anomalies in the FG PAT creation success rate and is removing the issue in the FG PAT creation form that prevented the confirmation step from running. GitHub is also adding automated detection of the issue so other areas of the GitHub front end do not repeat the problem.
Aug 10, 18:46 UTC
The cause was a change to how the website loads certain front-end JavaScript that was enabled for all users at 17:15 UTC; the change interacted with an issue in the token creation form's confirmation step that prevented it from running, so the final submission that actually creates the token never completed. Because the page still loaded and the server returned a normal response, the failure produced no error message. GitHub mitigated the incident by disabling the change at 18:21 UTC, at which point token creation recovered immediately, and the incident was resolved at 18:46 UTC.
To reduce the chance of recurrence, GitHub is adding monitoring and alerting for anomalies in the FG PAT creation success rate and is removing the issue in the FG PAT creation form that prevented the confirmation step from running. GitHub is also adding automated detection of the issue so other areas of the GitHub front end do not repeat the problem.
Aug 10, 18:46 UTC
Update -
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.
Aug 10, 18:22 UTC
Aug 10, 18:22 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Aug 10, 18:21 UTC
Aug 10, 18:21 UTC
Update -
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.
Aug 10, 18:09 UTC
Aug 10, 18:09 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 10, 18:02 UTC
Aug 10, 18:02 UTC
Aug 9, 2026
No incidents reported.
Aug 8, 2026
No incidents reported.
Aug 7, 2026
Resolved -
On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were affected. At peak, 71% of workflow runs experienced infrastructure failures and 75% of the remaining workflow runs were delayed by more than 5 minutes.
The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services.
These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events.
As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work.
This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation.
Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases.
Some jobs created during the incident were also left stuck unable to be retried or canceled. CLI and UI solutions for customers to address these were shared at https://github.com/orgs/community/discussions/204152#discussioncomment-17946043.
To prevent recurrence, we are making improvements to deployment and capacity safeguards for the affected services, strengthening monitoring for the conditions that preceded the incident, improving the resiliency and recovery of queued work and runner assignment, and adding automatic recovery for self-hosted runners affected by similar failure conditions. We are also making additional improvements to reduce the risk of cascading failures and accelerate recovery during large-scale Actions disruptions.
Aug 7, 02:04 UTC
The incident was triggered by a routine deployment to an internal Actions service responsible for processing events and generating Actions jobs. The deployment exposed an existing capacity and concurrency weakness. As pods were replaced during the deployment, remaining capacity became saturated, causing services to crash and triggering a cascading impact across multiple clusters and downstream services.
These services recovered at 17:00 after expanding capacity, throttling incoming webhook-triggered work to allow the system to recover, and increasing processing capacity for the backlog of affected events.
As the incident progressed, a backlog of work accumulated across the systems responsible for assigning jobs to runners. Due to a latent bug in one of the services responsible for job assignment, runners were getting assigned jobs that were no longer valid and then getting stuck retrying those jobs, preventing them from picking up valid work.
This second stage of impact was mitigated by deploying changes to prevent runners from repeatedly attempting to acquire invalid jobs. These mitigations allowed the accumulated queues to drain and Actions to recover to normal operation.
Some Actions Runner Controller (ARC) runners remained stuck after the incident. A mitigation deployed during the incident inadvertently affected these runners, causing some to remain offline until they were manually recovered. We subsequently rolled back the change and are adding automatic recovery in upcoming Runner and ARC releases.
Some jobs created during the incident were also left stuck unable to be retried or canceled. CLI and UI solutions for customers to address these were shared at https://github.com/orgs/community/discussions/204152#discussioncomment-17946043.
To prevent recurrence, we are making improvements to deployment and capacity safeguards for the affected services, strengthening monitoring for the conditions that preceded the incident, improving the resiliency and recovery of queued work and runner assignment, and adding automatic recovery for self-hosted runners affected by similar failure conditions. We are also making additional improvements to reduce the risk of cascading failures and accelerate recovery during large-scale Actions disruptions.
Aug 7, 02:04 UTC
Update -
During the incident, some Actions Runner Controller (ARC) runner pods became stuck in an idle state. Affected users can delete those pods using kubectl or redeploy their Actions Runner Controller application. ARC will automatically create replacement runners.
The next releases of Actions Runner and Actions Runner Controller will include an automatic recovery mechanism, preventing the need for these manual steps in the future.
Some workflow-triggering events, including push and pull request events, were not processed during the incident and cannot be replayed automatically. Customers may need to repeat the triggering action by pushing a new commit, updating the pull request, or manually re-running the workflow where applicable.
Aug 7, 02:03 UTC
The next releases of Actions Runner and Actions Runner Controller will include an automatic recovery mechanism, preventing the need for these manual steps in the future.
Some workflow-triggering events, including push and pull request events, were not processed during the incident and cannot be replayed automatically. Customers may need to repeat the triggering action by pushing a new commit, updating the pull request, or manually re-running the workflow where applicable.
Aug 7, 02:03 UTC
Update -
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.
Aug 7, 00:59 UTC
Aug 7, 00:59 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Aug 7, 00:06 UTC
Aug 7, 00:06 UTC
Update -
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
Aug 7, 00:05 UTC
Aug 7, 00:05 UTC
Update -
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.
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.
We are monitoring all affected services for sustained recovery and will provide another update shortly.
Aug 7, 00:01 UTC
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.
We are monitoring all affected services for sustained recovery and will provide another update shortly.
Aug 7, 00:01 UTC
Update -
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.
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.
We are monitoring all affected services for sustained recovery and will provide another update shortly.
Aug 7, 00:01 UTC
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.
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.
We are monitoring all affected services for sustained recovery and will provide another update shortly.
Aug 7, 00:01 UTC
Update -
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.
We are gradually restoring throughput for webhook-triggered Actions workflows and monitoring system stability. We have deployed a fix for self-hosted runners that were not picking up jobs and are enabling it incrementally.
GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused.
We continue to monitor recovery across all affected services and will provide another update as conditions improve.
Aug 6, 23:13 UTC
We are gradually restoring throughput for webhook-triggered Actions workflows and monitoring system stability. We have deployed a fix for self-hosted runners that were not picking up jobs and are enabling it incrementally.
GitHub Pages, Copilot code review, and Copilot coding agent may still experience intermittent failures or delays. Migrations using GitHub Enterprise Importer remain paused.
We continue to monitor recovery across all affected services and will provide another update as conditions improve.
Aug 6, 23:13 UTC
Update -
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.
Webhook triggers remain throttled to support recovery. Many push and pull request events are not yet triggering new workflow runs, and we are working to safely restore full throughput.
GitHub Pages, Copilot code review, and Copilot coding agent may still experience failures or delays. Migrations using GitHub Enterprise Importer remain paused.
We are continuing to monitor recovery and will provide another update as conditions improve.
Aug 6, 22:18 UTC
Webhook triggers remain throttled to support recovery. Many push and pull request events are not yet triggering new workflow runs, and we are working to safely restore full throughput.
GitHub Pages, Copilot code review, and Copilot coding agent may still experience failures or delays. Migrations using GitHub Enterprise Importer remain paused.
We are continuing to monitor recovery and will provide another update as conditions improve.
Aug 6, 22:18 UTC
Update -
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.
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.
Copilot code review, Copilot coding agent, and GitHub Pages may experience failures or delays. Migrations using GitHub Enterprise Importer have been paused to support mitigation efforts.
Aug 6, 21:30 UTC
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.
Copilot code review, Copilot coding agent, and GitHub Pages may experience failures or delays. Migrations using GitHub Enterprise Importer have been paused to support mitigation efforts.
Aug 6, 21:30 UTC
Update -
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.
We have narrowed the remaining impact to runners that are stuck retrying jobs that are no longer available. Both GitHub-hosted and self-hosted runners are affected, and we are working to recover them.
Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected.
Aug 6, 20:34 UTC
We have narrowed the remaining impact to runners that are stuck retrying jobs that are no longer available. Both GitHub-hosted and self-hosted runners are affected, and we are working to recover them.
Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected.
Aug 6, 20:34 UTC
Update -
We are continuing to work on an issue affecting GitHub Actions.
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.
Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed.
Our engineers remain actively engaged.
Aug 6, 19:43 UTC
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.
Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed.
Our engineers remain actively engaged.
Aug 6, 19:43 UTC
Update -
We are continuing to work on an issue affecting multiple GitHub services.
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.
Customers using self-hosted runners may see errors or rate limiting when runners register.
Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed.
Recovery is taking longer than we expected, and engineers remain actively engaged.
Aug 6, 18:46 UTC
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.
Customers using self-hosted runners may see errors or rate limiting when runners register.
Copilot code review, Copilot coding agent, and migrations using GitHub Enterprise Importer may also be affected. Webhook deliveries may be delayed.
Recovery is taking longer than we expected, and engineers remain actively engaged.
Aug 6, 18:46 UTC
Update -
We are continuing to work on an issue affecting multiple GitHub services.
Workflow runs are still failing or delayed in starting, and some queued jobs may time out.
Customers using self-hosted runners may see errors or rate limiting when runners register.
Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected.
Webhook deliveries may be delayed.
Engineers have applied further mitigations and are continuing to work towards full recovery.
Aug 6, 18:11 UTC
Workflow runs are still failing or delayed in starting, and some queued jobs may time out.
Customers using self-hosted runners may see errors or rate limiting when runners register.
Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer may also be affected.
Webhook deliveries may be delayed.
Engineers have applied further mitigations and are continuing to work towards full recovery.
Aug 6, 18:11 UTC
Update -
We are continuing to work on an issue affecting multiple GitHub services.
Workflow runs are failing or delayed in starting, and some queued jobs may time out.
Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected.
Webhook deliveries may be delayed.
Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now.
Aug 6, 17:40 UTC
Workflow runs are failing or delayed in starting, and some queued jobs may time out.
Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also affected.
Webhook deliveries may be delayed.
Engineers have applied a number of mitigations and are rolling out a further fix across all affected systems now.
Aug 6, 17:40 UTC
Update -
We are continuing to work on the issue affecting GitHub Actions.
Workflow runs are still failing or delayed in starting, and some queued jobs may time out.
Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures.
Our engineers have applied several mitigations and are rolling out a further fix now.
Aug 6, 17:02 UTC
Workflow runs are still failing or delayed in starting, and some queued jobs may time out.
Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see failures.
Our engineers have applied several mitigations and are rolling out a further fix now.
Aug 6, 17:02 UTC
Update -
Actions and Pages are experiencing degraded availability. We are continuing to investigate.
Aug 6, 16:33 UTC
Aug 6, 16:33 UTC
Update -
We are continuing to work on the issue affecting GitHub Actions.
Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors.
Customers running migrations with GitHub Enterprise Importer may also see failures.
Engineers are actively working towards full recovery.
Aug 6, 16:27 UTC
Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors.
Customers running migrations with GitHub Enterprise Importer may also see failures.
Engineers are actively working towards full recovery.
Aug 6, 16:27 UTC
Update -
Pages is experiencing degraded performance. We are continuing to investigate.
Aug 6, 16:27 UTC
Aug 6, 16:27 UTC
Update -
Pages is operating normally.
Aug 6, 16:19 UTC
Aug 6, 16:19 UTC
Update -
Pages is experiencing degraded performance. We are continuing to investigate.
Aug 6, 15:53 UTC
Aug 6, 15:53 UTC
Update -
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.
Some customers may also see unexpected rate limiting in their workflows.
Engineers have identified the source of the disruption and are actively working on a mitigation
Aug 6, 15:45 UTC
Some customers may also see unexpected rate limiting in their workflows.
Engineers have identified the source of the disruption and are actively working on a mitigation
Aug 6, 15:45 UTC
Update -
Actions is experiencing degraded availability. We are continuing to investigate.
Aug 6, 15:41 UTC
Aug 6, 15:41 UTC
Investigating -
We are investigating reports of degraded performance for Actions
Aug 6, 15:22 UTC
Aug 6, 15:22 UTC
Aug 6, 2026
Resolved -
On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased.
At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC.
Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments.
We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward.
Aug 6, 16:22 UTC
At 12:09 UTC, latency crossed the alerting threshold and the team began investigating. We reverted the invalid configuration and applied additional mitigations, including reducing status deployment processing to lower the load on our Redis cluster. Latency returned to normal levels at 15:40 UTC.
Customer impact occurred from 11:34 to 15:32 UTC. During this period, we failed to process approximately 128,000 deployments.
We have updated our alerts to detect elevated processing latency sooner and to notify us immediately when latency causes deployment processing failures. We've confirmed this incident was not fully captured by our availability metrics. In the coming days, we'll update how GitHub Pages availability is measured so incidents like this are accurately reflected going forward.
Aug 6, 16:22 UTC
Monitoring -
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
Aug 6, 15:50 UTC
Aug 6, 15:50 UTC
Investigating -
We are investigating reports of degraded performance for Pages
Aug 6, 15:03 UTC
Aug 6, 15:03 UTC
Aug 5, 2026
Resolved -
On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected.
The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic.
We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.
Aug 5, 13:00 UTC
The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic.
We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.
Aug 5, 13:00 UTC
Update -
Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
Aug 5, 12:10 UTC
Aug 5, 12:10 UTC
Monitoring -
The degradation has been mitigated. We are monitoring to ensure stability.
Aug 5, 12:01 UTC
Aug 5, 12:01 UTC
Investigating -
We are investigating reports of impacted performance for some GitHub services.
Aug 5, 11:38 UTC
Aug 5, 11:38 UTC
Aug 4, 2026
No incidents reported.
Subscribe to our developer newsletter
Get tips, technical guides, and best practices. Twice a month. Right in your inbox.
Subscribe