GitHub Outage History

Started Aug 18, 2026, 07:40 AM UTC· resolved Aug 18, 2026, 11:42 AM UTC

1. investigating Aug 18, 2026, 07:40 AM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. monitoring Aug 18, 2026, 07:40 AM UTC

   We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.

3. monitoring Aug 18, 2026, 10:41 AM UTC

   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.

4. monitoring Aug 18, 2026, 11:24 AM UTC

   We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.

5. resolved Aug 18, 2026, 11:42 AM UTC

   On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. The issue was caused by failures in backend requests reading runner and runner group data. The failures were caused by an expired authentication certificate unique to this service. The certificate had been rotated in KeyVault, but a step to enable use at runtime had been paused to prevent recurrence of previous incidents triggered by this operation. The impact was mitigated by completing the enablement of the new certificate in the backend system. We have added additional monitoring to this and other certificates. This service is also in the process of being replaced as part of our availability and scale work, bringing this authentication path and secret management in line with patterns across all GitHub services.

Read the full incident report →

Started Aug 17, 2026, 01:40 PM UTC· resolved Aug 17, 2026, 09:15 PM UTC

1. investigating Aug 17, 2026, 01:40 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. investigating Aug 17, 2026, 01:41 PM UTC

   API Requests is experiencing degraded performance. We are continuing to investigate.

3. investigating Aug 17, 2026, 01:42 PM UTC

   Actions is experiencing degraded performance. We are continuing to investigate.

4. investigating Aug 17, 2026, 01:44 PM UTC

   Webhooks is experiencing degraded performance. We are continuing to investigate.

5. investigating Aug 17, 2026, 01:45 PM UTC

   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

6. investigating Aug 17, 2026, 01:46 PM UTC

   Issues is experiencing degraded performance. We are continuing to investigate.

7. investigating Aug 17, 2026, 01:58 PM UTC

   Pull Requests is experiencing degraded performance. We are continuing to investigate.

8. investigating Aug 17, 2026, 02:04 PM UTC

   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.

9. investigating Aug 17, 2026, 02:24 PM UTC

   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.

10. investigating Aug 17, 2026, 02:31 PM UTC

    Copilot is experiencing degraded availability. We are continuing to investigate.

11. investigating Aug 17, 2026, 02:45 PM UTC

    Pull Requests is experiencing degraded availability. We are continuing to investigate.

12. investigating Aug 17, 2026, 02:49 PM UTC

    Issues is experiencing degraded availability. We are continuing to investigate.

13. investigating Aug 17, 2026, 02:54 PM UTC

    Pull Requests is experiencing degraded availability. We are continuing to investigate.

14. investigating Aug 17, 2026, 02:58 PM UTC

    Actions is experiencing degraded availability. We are continuing to investigate.

15. investigating Aug 17, 2026, 02:58 PM UTC

    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.

16. investigating Aug 17, 2026, 02:58 PM UTC

    Webhooks is experiencing degraded availability. We are continuing to investigate.

17. investigating Aug 17, 2026, 03:01 PM UTC

    API Requests is experiencing degraded availability. We are continuing to investigate.

18. investigating Aug 17, 2026, 03:10 PM UTC

    Pages is experiencing degraded performance. We are continuing to investigate.

19. investigating Aug 17, 2026, 03:21 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

20. investigating Aug 17, 2026, 03:40 PM UTC

    Webhooks is experiencing degraded performance. We are continuing to investigate.

21. investigating Aug 17, 2026, 03:42 PM UTC

    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.

22. investigating Aug 17, 2026, 04:16 PM UTC

    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.

23. investigating Aug 17, 2026, 04:36 PM UTC

    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.

24. investigating Aug 17, 2026, 04:59 PM UTC

    The degradation affecting API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

25. investigating Aug 17, 2026, 05:30 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

26. investigating Aug 17, 2026, 05:34 PM UTC

    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.

27. investigating Aug 17, 2026, 05:36 PM UTC

    Issues is experiencing degraded performance. We are continuing to investigate.

28. investigating Aug 17, 2026, 06:11 PM UTC

    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.

29. investigating Aug 17, 2026, 06:23 PM UTC

    The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.

30. investigating Aug 17, 2026, 06:48 PM UTC

    API Requests is experiencing degraded availability. We are continuing to investigate.

31. investigating Aug 17, 2026, 07:01 PM UTC

    API Requests is operating normally.

32. investigating Aug 17, 2026, 07:13 PM UTC

    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.

33. investigating Aug 17, 2026, 08:08 PM UTC

    We are continuing to investigate sporadic failures affecting Copilot authentication in some applications. Copilot usage via the GitHub CLI and GitHub App are unaffected.

34. investigating Aug 17, 2026, 08:22 PM UTC

    Issues is operating normally.

35. investigating Aug 17, 2026, 08:45 PM UTC

    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.

36. resolved Aug 17, 2026, 09:15 PM UTC

    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.

Read the full incident report →

Started Aug 13, 2026, 04:21 PM UTC· resolved Aug 13, 2026, 06:27 PM UTC

1. investigating Aug 13, 2026, 04:21 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. investigating Aug 13, 2026, 04:21 PM UTC

   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.

3. investigating Aug 13, 2026, 06:27 PM UTC

   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.

4. resolved Aug 13, 2026, 06:27 PM UTC

   On August 13, 2026, from 15:31:21 UTC to 18:27:55 UTC, GitHub Enterprise Cloud team synchronization was degraded for enterprises using personal accounts. Organization teams experienced delays of up to 3 to 13 hours (median 8 hours) when syncing with IdP groups, resulting in delayed access grants or removals for enterprise users across 2.8% of teams. A temporary change introduced to address a previous issue due to increased usage of this feature remained active after it was intended to be removed, causing synchronization delays during periods of high volume. We removed the temporary change and provisioned additional resources to handle the increased volume.

Read the full incident report →

Started Aug 13, 2026, 02:45 PM UTC· resolved Aug 13, 2026, 03:36 PM UTC

1. investigating Aug 13, 2026, 02:45 PM UTC

   We are investigating reports of degraded performance for Webhooks

2. investigating Aug 13, 2026, 02:46 PM UTC

   Pull Requests is experiencing degraded performance. We are continuing to investigate.

3. investigating Aug 13, 2026, 02:46 PM UTC

   Issues is experiencing degraded performance. We are continuing to investigate.

4. investigating Aug 13, 2026, 02:46 PM UTC

   Git Operations is experiencing degraded performance. We are continuing to investigate.

5. investigating Aug 13, 2026, 02:56 PM UTC

   Packages is experiencing degraded performance. We are continuing to investigate.

6. investigating Aug 13, 2026, 02:58 PM UTC

   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.

7. monitoring Aug 13, 2026, 03:33 PM UTC

   The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.

8. monitoring Aug 13, 2026, 03:33 PM UTC

   We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.

9. resolved Aug 13, 2026, 03:36 PM UTC

   Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with smaller impact to Git operations, pull requests, issues, packages, sign-in, and Copilot. Impact cleared on its own at about 14:53 UTC once the job finished; we resolved the incident at 15:36 UTC. Affected users may have experienced a brief increase in errors and slower responses, primarily when creating, listing, or updating webhooks, with smaller impacts to pull requests, issues, packages, and Git operations. Failures peaked at about 1% for several minutes around 14:37 UTC. To prevent future incidents, we've already shipped an update that turns on the safer deletion path for organizations, along with caps on deletion holds on databases. Building on these changes, we're auditing all bulk deletion and cleanup jobs that write to shared databases to prevent similar issues in future.

Read the full incident report →

Started Aug 13, 2026, 02:43 PM UTC· resolved Aug 13, 2026, 03:47 PM UTC

1. investigating Aug 13, 2026, 02:43 PM UTC

   We are investigating reports of degraded performance for Copilot AI Model Providers

2. investigating Aug 13, 2026, 02:50 PM UTC

   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.

3. investigating Aug 13, 2026, 03:23 PM UTC

   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.

4. investigating Aug 13, 2026, 03:47 PM UTC

   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.

5. resolved Aug 13, 2026, 03:47 PM UTC

   On August 13th, 2026, between approximately 14:06 and 15:47 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates, peaking at 43% and averaging 12%. Users who selected Auto or alternative models were unaffected. The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.

Read the full incident report →

Started Aug 12, 2026, 09:39 PM UTC· resolved Aug 12, 2026, 10:56 PM UTC

1. investigating Aug 12, 2026, 09:39 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. investigating Aug 12, 2026, 09:43 PM UTC

   We are investigating issues with Login and when downloading Release Assets. We will continue to keep users updated on progress towards mitigation.

3. investigating Aug 12, 2026, 10:22 PM UTC

   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.

4. resolved Aug 12, 2026, 10:56 PM UTC

   On August 12 and 13, 2026, some anonymous (logged-out) requests to github.com experienced HTTP 5xx errors when loading pages like the sign-in page, and when downloading release assets, due to an unusual traffic pattern that repeatedly overloaded a part of our infrastructure that serves these types of requests. There were three windows of impact: (1) August 12 from 16:34 to 18:34 UTC, with an average error rate of 16.16% that peaked at 28.6%; (2) August 12 from 19:00 to 22:56 UTC, with an average error rate of 16.55% that peaked at 24.18%; and (3) August 13 from 06:19 to 08:05 UTC, with an average error rate of 2.01% that peaked at 7.49%. Requests from signed-in users were unaffected. We mitigated the incidents by applying traffic controls at our network edge that limited any requests matching the pattern identified previously, thereby preventing overload on our systems. Since these incidents occurred, we have tightened our monitoring systems to alert server-side errors that affect logged-out traffic. We are also working to further strengthen our edge protections and reduce the time to detect and mitigate similar incidents.

Read the full incident report →

Started Aug 12, 2026, 04:16 PM UTC· resolved Aug 12, 2026, 04:41 PM UTC

1. investigating Aug 12, 2026, 04:16 PM UTC

   We are investigating reports of degraded performance for Issues and Pull Requests

2. investigating Aug 12, 2026, 04:24 PM UTC

   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.

3. monitoring Aug 12, 2026, 04:35 PM UTC

   The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

4. monitoring Aug 12, 2026, 04:38 PM UTC

   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.

5. resolved Aug 12, 2026, 04:41 PM UTC

   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.

Read the full incident report →

Started Aug 11, 2026, 02:50 PM UTC· resolved Aug 11, 2026, 08:06 PM UTC

1. investigating Aug 11, 2026, 02:50 PM UTC

   We are investigating reports of degraded performance for API Requests

2. investigating Aug 11, 2026, 03:28 PM UTC

   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

3. investigating Aug 11, 2026, 04:49 PM UTC

   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.

4. monitoring Aug 11, 2026, 04:49 PM UTC

   The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

5. monitoring Aug 11, 2026, 08:06 PM UTC

   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.

6. resolved Aug 11, 2026, 08:06 PM UTC

   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.

Read the full incident report →

Started Aug 10, 2026, 08:27 PM UTC· resolved Aug 10, 2026, 09:50 PM UTC

1. investigating Aug 10, 2026, 08:27 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. monitoring Aug 10, 2026, 08:39 PM UTC

   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.

3. monitoring Aug 10, 2026, 08:49 PM UTC

   The degradation has been mitigated. We are monitoring to ensure stability.

4. monitoring Aug 10, 2026, 09:19 PM UTC

   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.

5. monitoring Aug 10, 2026, 09:50 PM UTC

   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.

6. resolved Aug 10, 2026, 09:50 PM UTC

   On August 10, 2026, between 19:48 UTC and 20:49 UTC, GitHub Copilot users saw an incomplete list of available models. During this window, the service could return as few as one model instead of the full catalog. Requests that tried to use a model missing from that shortened list failed with a "model not found" error. Copilot requests that used an available model were not affected. This did not affect customers on data-residency (Proxima) environments. The issue was caused by a change to how model data was published, which our systems could not read back correctly and fell back to a limited default list. We mitigated the incident by 20:49 UTC and deployed a fix to prevent immediate recurrence by 21:50 UTC. We are adding validation and retry safeguards so that model data is verified before it is served. We apologize for the disruption.

Read the full incident report →

Started Aug 10, 2026, 06:02 PM UTC· resolved Aug 10, 2026, 06:46 PM UTC

1. investigating Aug 10, 2026, 06:02 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. investigating Aug 10, 2026, 06:09 PM UTC

   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.

3. monitoring Aug 10, 2026, 06:21 PM UTC

   The degradation has been mitigated. We are monitoring to ensure stability.

4. monitoring Aug 10, 2026, 06:22 PM UTC

   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.

5. resolved Aug 10, 2026, 06:46 PM UTC

   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.

Read the full incident report →

Started Aug 06, 2026, 03:22 PM UTC· resolved Aug 07, 2026, 02:04 AM UTC

1. investigating Aug 06, 2026, 03:22 PM UTC

   We are investigating reports of degraded performance for Actions

2. investigating Aug 06, 2026, 03:41 PM UTC

   Actions is experiencing degraded availability. We are continuing to investigate.

3. investigating Aug 06, 2026, 03:45 PM UTC

   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

4. investigating Aug 06, 2026, 03:53 PM UTC

   Pages is experiencing degraded performance. We are continuing to investigate.

5. investigating Aug 06, 2026, 04:19 PM UTC

   Pages is operating normally.

6. investigating Aug 06, 2026, 04:27 PM UTC

   Pages is experiencing degraded performance. We are continuing to investigate.

7. investigating Aug 06, 2026, 04:27 PM UTC

   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.

8. investigating Aug 06, 2026, 04:33 PM UTC

   Actions and Pages are experiencing degraded availability. We are continuing to investigate.

9. investigating Aug 06, 2026, 05:02 PM UTC

   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.

10. investigating Aug 06, 2026, 05:40 PM UTC

    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.

11. investigating Aug 06, 2026, 06:11 PM UTC

    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.

12. investigating Aug 06, 2026, 06:46 PM UTC

    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.

13. investigating Aug 06, 2026, 07:43 PM UTC

    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.

14. investigating Aug 06, 2026, 08:34 PM UTC

    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.

15. investigating Aug 06, 2026, 09:30 PM UTC

    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.

16. investigating Aug 06, 2026, 10:18 PM UTC

    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.

17. investigating Aug 06, 2026, 11:13 PM UTC

    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.

18. investigating Aug 07, 2026, 12:01 AM 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.

19. investigating Aug 07, 2026, 12:01 AM 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.

20. investigating Aug 07, 2026, 12:05 AM UTC

    The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

21. monitoring Aug 07, 2026, 12:06 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

22. monitoring Aug 07, 2026, 12:59 AM UTC

    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.

23. monitoring Aug 07, 2026, 02:03 AM UTC

    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.

24. resolved Aug 07, 2026, 02:04 AM UTC

    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.

Read the full incident report →

Started Aug 06, 2026, 03:03 PM UTC· resolved Aug 06, 2026, 04:22 PM UTC

1. investigating Aug 06, 2026, 03:03 PM UTC

   We are investigating reports of degraded performance for Pages

2. monitoring Aug 06, 2026, 03:50 PM UTC

   The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

3. resolved Aug 06, 2026, 04:22 PM UTC

   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.

Read the full incident report →

Started Aug 05, 2026, 11:38 AM UTC· resolved Aug 05, 2026, 01:00 PM UTC

1. investigating Aug 05, 2026, 11:38 AM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. monitoring Aug 05, 2026, 12:01 PM UTC

   The degradation has been mitigated. We are monitoring to ensure stability.

3. monitoring Aug 05, 2026, 12:10 PM UTC

   Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.

4. resolved Aug 05, 2026, 01:00 PM UTC

   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.

Read the full incident report →

Started Aug 03, 2026, 09:53 AM UTC· resolved Aug 03, 2026, 11:25 AM UTC

1. investigating Aug 03, 2026, 09:53 AM UTC

   We are investigating reports of degraded performance for Copilot

2. investigating Aug 03, 2026, 09:54 AM UTC

   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.

3. investigating Aug 03, 2026, 10:35 AM UTC

   We are still seeing intermittent errors with Copilot, and are continuing to investigate and consider mitigations.

4. monitoring Aug 03, 2026, 11:19 AM UTC

   The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.

5. resolved Aug 03, 2026, 11:25 AM UTC

   On 2026-08-03, between 06:52 and 11:25 UTC, some GitHub Copilot users experienced errors when using chat and agent features. Requests to list the available models failed, and because every chat or agent interaction begins by retrieving the list of models, affected users saw their requests fail. On average about 3% of these model-listing requests failed during the incident (roughly 97% succeeded), but failures were significantly higher during peak-traffic periods, at times approaching 100% for the affected internal lookups. Approximately 4,066 users were affected in a single 60-minute window, concentrated among IDE-based clients. The underlying AI models themselves remained healthy throughout. The incident was caused by an increase in how often clients requested the model list, which pushed an internal user-authorization lookup past a rate limit; the rate-limited responses were surfaced to users as errors. We mitigated the impact by increasing how long Copilot caches that authorization lookup, which reduced load on the internal service, and we have additional capacity and rate-limit changes in progress. To prevent recurrence we are improving monitoring for this class of failure, adjusting cache and rate-limit settings, and coordinating with client teams on request patterns.

Read the full incident report →

Started Aug 01, 2026, 06:03 PM UTC· resolved Aug 01, 2026, 06:44 PM UTC

1. investigating Aug 01, 2026, 06:03 PM UTC

   We are investigating reports of degraded performance for Copilot AI Model Providers

2. investigating Aug 01, 2026, 06:03 PM UTC

   We are seeing increased error rates from specific upstream AI Model Providers

3. investigating Aug 01, 2026, 06:20 PM UTC

   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.

4. monitoring Aug 01, 2026, 06:20 PM UTC

   The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.

5. monitoring Aug 01, 2026, 06:23 PM UTC

   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.

6. resolved Aug 01, 2026, 06:44 PM UTC

   On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained available. This was caused by degradation of an upstream model provider. The affected endpoint recovered, and we monitored the service until error rates and latency returned to normal levels. We are working to add endpoint redundancy to mitigate similar provider issues in the future.

Read the full incident report →

Started Aug 01, 2026, 11:16 AM UTC· resolved Aug 01, 2026, 12:30 PM UTC

1. investigating Aug 01, 2026, 11:16 AM UTC

   We are investigating reports of degraded performance for Copilot AI Model Providers

2. investigating Aug 01, 2026, 11:20 AM UTC

   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

3. investigating Aug 01, 2026, 12:13 PM UTC

   We keep working with our upstream model provider, and are observing recovery. We continue monitoring to ensure stability.

4. investigating Aug 01, 2026, 12:29 PM UTC

   The issues with our upstream model provider have been resolved, and GPT-5.6 Luna is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

5. resolved Aug 01, 2026, 12:30 PM UTC

   On August 1st, 2026, the GPT-5.6 Luna model in GitHub Copilot experienced degraded availability in intermittent time intervals between ~08:05 UTC and ~16:30 UTC. Specifically the timeframes observed were 10:00-10:20 UTC, 10:45-11:50 UTC, 13:00-14:25 UTC, and 16:00-16:30 UTC. During this time, requests to GPT-5.6 Luna in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for GPT-5.6 Luna fully recovered once the provider resolved their outage at 16:30 UTC.

Read the full incident report →

Started Jul 30, 2026, 09:07 AM UTC· resolved Jul 30, 2026, 10:12 AM UTC

1. investigating Jul 30, 2026, 09:07 AM UTC

   We are investigating reports of degraded performance for Copilot AI Model Providers

2. investigating Jul 30, 2026, 09:17 AM UTC

   We are experiencing degraded availability for the Claude 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.

3. investigating Jul 30, 2026, 10:11 AM UTC

   The issues with our upstream model provider have been resolved, and Claude Fable 5 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

4. resolved Jul 30, 2026, 10:12 AM UTC

   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.

Read the full incident report →

Started Jul 29, 2026, 08:07 PM UTC· resolved Jul 29, 2026, 09:51 PM UTC

1. investigating Jul 29, 2026, 08:07 PM UTC

   We are investigating reports of degraded performance for Copilot AI Model Providers

2. investigating Jul 29, 2026, 08:07 PM UTC

   We are seeing increased error rates with requests to specific model providers.

3. investigating Jul 29, 2026, 08:18 PM UTC

   We are investigating increased error rates affecting GitHub Copilot requests to external AI model providers. Some users may experience failures or degraded performance when using Copilot features.

4. investigating Jul 29, 2026, 08:38 PM UTC

   The external AI model provider has identified the issue and is working to resolve.

5. investigating Jul 29, 2026, 09:08 PM UTC

   The external AI model provider is continuing to investigate.

6. investigating Jul 29, 2026, 09:51 PM UTC

   The external ai model provider has resolved the issues, and we have verified Copilot's traffic is fully recovered.

7. resolved Jul 29, 2026, 09:51 PM UTC

   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.

Read the full incident report →

Started Jul 29, 2026, 03:26 PM UTC· resolved Jul 29, 2026, 04:00 PM UTC

1. investigating Jul 29, 2026, 03:26 PM UTC

   We are investigating reports of degraded availability for Actions

2. investigating Jul 29, 2026, 03:34 PM UTC

   We are investigating an issue affecting GitHub Actions. Some customers may experience timeouts or failures with runner registration and workflow runs may be delayed during startup. Our team is actively working to mitigate the impact by scaling capacity across additional infrastructure.

3. monitoring Jul 29, 2026, 03:40 PM UTC

   The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

4. resolved Jul 29, 2026, 04:00 PM UTC

   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.

Read the full incident report →

Started Jul 27, 2026, 07:31 PM UTC· resolved Jul 27, 2026, 07:37 PM UTC

1. investigating Jul 27, 2026, 07:31 PM UTC

   We are investigating reports of impacted performance for some GitHub services.

2. investigating Jul 27, 2026, 07:31 PM UTC

   This is just a test of our systems. Please ignore.

3. resolved Jul 27, 2026, 07:37 PM UTC

   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.

Read the full incident report →

Started Jul 27, 2026, 03:53 AM UTC· resolved Jul 27, 2026, 04:09 AM UTC

1. investigating Jul 27, 2026, 03:53 AM UTC

   We are investigating reports of degraded performance for API Requests

2. monitoring Jul 27, 2026, 04:09 AM UTC

   The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.

3. resolved Jul 27, 2026, 04:09 AM UTC

   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.

Read the full incident report →

Started Jul 25, 2026, 12:31 PM UTC· resolved Jul 25, 2026, 01:13 PM UTC

1. investigating Jul 25, 2026, 12:31 PM UTC

   We are investigating reports of degraded availability for Actions

2. investigating Jul 25, 2026, 12:34 PM UTC

   We are experiencing issues with GitHub Actions that are causing workflow run failures and delays for some users. Our engineering team is actively investigating the infrastructure issue and working to restore full functionality.

3. investigating Jul 25, 2026, 12:58 PM UTC

   We have applied a mitigation for the infrastructure issue affecting GitHub Actions. Workflow run failures and delays are improving but not yet fully resolved. Our engineering team continues to work on restoring full functionality across all affected infrastructure.

4. monitoring Jul 25, 2026, 12:59 PM UTC

   The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

5. monitoring Jul 25, 2026, 01:12 PM UTC

   We have seen recovery in GitHub Actions performance following our earlier mitigation. Workflow runs are processing normally, though jobs queued before 12:40 UTC may still experience failures and will need to be retried.

6. resolved Jul 25, 2026, 01:13 PM UTC

   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.

Read the full incident report →

Started Jul 25, 2026, 09:42 AM UTC· resolved Jul 25, 2026, 10:11 AM UTC

1. investigating Jul 25, 2026, 09:42 AM UTC

   We are investigating reports of degraded availability for Copilot AI Model Providers

2. investigating Jul 25, 2026, 09:48 AM UTC

   We are experiencing degraded availability for the GPT-5.2, GPT-5.3-Codex, GPT-5.4, GPT-5.4 Mini, GPT-5.6 Sol, GPT-5.6 Terra, and GPT-5.6 Luna models 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.

3. monitoring Jul 25, 2026, 10:04 AM UTC

   The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.

4. resolved Jul 25, 2026, 10:11 AM UTC

   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.

Read the full incident report →

Started Jul 25, 2026, 08:59 AM UTC· resolved Jul 25, 2026, 09:25 AM UTC

1. investigating Jul 25, 2026, 08:59 AM UTC

   We are investigating reports of degraded performance for Actions

2. monitoring Jul 25, 2026, 09:13 AM UTC

   The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

3. monitoring Jul 25, 2026, 09:20 AM UTC

   We identified an issue causing delays in GitHub Actions run starts. Some users may have experienced longer than expected wait times when triggering workflow runs. We have applied mitigations and have recovered. Our team continues to monitor and investigate the root cause.

4. resolved Jul 25, 2026, 09:25 AM UTC

   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.

Read the full incident report →

Started Jul 24, 2026, 07:37 PM UTC· resolved Jul 24, 2026, 08:23 PM UTC

1. investigating Jul 24, 2026, 07:37 PM UTC

   We are investigating reports of degraded performance for Pull Requests

2. investigating Jul 24, 2026, 07:40 PM UTC

   We are investigating errors creating pull requests

3. investigating Jul 24, 2026, 07:43 PM UTC

   Pull Requests is experiencing degraded availability. We are continuing to investigate.

4. investigating Jul 24, 2026, 07:59 PM UTC

   We have applied a mitigation and are monitoring for recovery

5. monitoring Jul 24, 2026, 08:02 PM UTC

   The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

6. resolved Jul 24, 2026, 08:23 PM UTC

   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.

Read the full incident report →