GitHub Status

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.

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

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

Investigating: 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.

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

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

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

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

Investigating: We are investigating reports of degraded performance for Webhooks

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.

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

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

Investigating: 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.

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

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

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

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

Investigating: We are investigating reports of degraded performance for Webhooks

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.

Monitoring: 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.

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

Investigating: We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.

Investigating: We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information

Investigating: We are investigating reports of degraded performance for API Requests

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.

Monitoring: We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.

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

Investigating: We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.

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

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.

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

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

Investigating: 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.

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

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

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

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

Investigating: We are investigating reports of degraded performance for Webhooks

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.

Monitoring: We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.

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

Investigating: We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.

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

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.

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

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

Investigating: 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.

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

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

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

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

Investigating: We are investigating reports of degraded performance for Webhooks

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.

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

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

Investigating: 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.

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

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

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

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

Investigating: We are investigating reports of degraded performance for Webhooks

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.

Investigating: 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.

Investigating: 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.

Investigating: We are experiencing degraded availability for the Fable 5 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

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