GitHub Status

Investigating: We continue to investigate delays affecting Actions workflows, Pages deployments, and webhook events, along with errors affecting code search and live updates. We have taken mitigation steps. Actions processing and Pages deployments are showing signs of recovery, but impact has not fully resolved. We are monitoring recovery and investigating the underlying cause.

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

Investigating: We are investigating reports of degraded performance for Actions and 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 saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.

We mitigated the issue and all services have recovered.

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

Investigating: We are investigating reports of degraded performance for API Requests, Actions, 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 saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.

We mitigated the issue and all services have recovered.

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

Investigating: We are investigating reports of degraded performance for API Requests, Actions, 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: The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

Investigating: A temporarily overloaded component triggered a burst of errors between 14:21 and 14:30 UTC across numerous services. Component health has returned to normal and we continue to monitor while investigating the root cause.

Investigating: Issues is operating normally.

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

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

Investigating: We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation.

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

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 saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.

We mitigated the issue and all services have recovered.

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

Investigating: We are investigating reports of degraded performance for API Requests, Actions, 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 saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.

We mitigated the issue and all services have recovered.

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

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

Investigating: We continue to investigate delays affecting Actions workflows, Pages deployments, and webhook events, along with errors affecting code search and live updates. We have taken mitigation steps. Actions processing and Pages deployments are showing signs of recovery, but impact has not fully resolved. We are monitoring recovery and investigating the underlying cause.

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

Investigating: We are investigating reports of degraded performance for Actions and 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: The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

Investigating: A temporarily overloaded component triggered a burst of errors between 14:21 and 14:30 UTC across numerous services. Component health has returned to normal and we continue to monitor while investigating the root cause.

Investigating: Issues is operating normally.

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

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

Investigating: We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation.

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

Investigating: We continue to investigate delays affecting Actions workflows, Pages deployments, and webhook events, along with errors affecting code search and live updates. We have taken mitigation steps. Actions processing and Pages deployments are showing signs of recovery, but impact has not fully resolved. We are monitoring recovery and investigating the underlying cause.

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

Investigating: We are investigating reports of degraded performance for Actions and 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: The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.

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

Investigating: We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon.

Investigating: We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. We have identified the root cause and working to apply a mitigation. While we work to resolve the issue we recommend choosing another model to continue using Copilot.

Investigating: We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash 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 to continue using Copilot.

Investigating: We are experiencing issues with upstream model providers resulting in a degraded experience across Copilot services. The team is actively investigating the issue.

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

Resolved: Between 23:28 and 00:23 UTC on October 27, 2026, GitHub Copilot experienced degradation affecting Grok 4.6 and Grok 4.7 models. Users encountered elevated error rates when using these models.

The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.

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

Investigating: We are experiencing degraded availability for the Grok 4.6 and Grok 4.7 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.

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