Snapshot 256776
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Subscribe to UpdatesSubscribe 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 Webhooks Operational Visit www.githubstatus.com for more information Operational API Requests Operational Issues Operational Pull Requests Operational Actions Operational Packages Operational Pages Operational Copilot Operational Codespaces Operational Copilot AI Model Providers Operational 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 Nov 11, 2026 No incidents reported today. Nov 10, 2026 Incident with Git Operations 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. Nov 10, 17:55 UTC Update - We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service. Nov 10, 17:46 UTC Update - Actions is operating normally. Nov 10, 17:28 UTC Update - Pull Requests is experiencing degraded performance. We are continuing to investigate. Nov 10, 17:12 UTC Update - We continue to investigate elevated response times for Git operations and pull requests. Some pull-request processing and Actions workflows are improving, but delays and failures persist. We're monitoring the impact and working to restore normal service. Nov 10, 17:07 UTC Update - Actions is experiencing degraded availability. We are continuing to investigate. Nov 10, 16:39 UTC Update - We're investigating elevated response times for Git operations and pull requests. GitHub Actions workflows that are triggered from Pull Requests are delayed. We're working to mitigate the impact and will share updates as we learn more. Nov 10, 16:31 UTC Update - Actions and Pull Requests are experiencing degraded availability. We are continuing to investigate. Nov 10, 16:26 UTC Investigating - We are investigating reports of degraded performance for Actions and Pull Requests Nov 10, 16:10 UTC Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot 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. Nov 10, 00:05 UTC Update - The issue affecting GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces has been mitigated. We are monitoring the service to ensure stability. Nov 9, 23:59 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Nov 9, 23:46 UTC Update - Copilot is operating normally. Nov 9, 23:22 UTC Update - Copilot AI Model Providers is experiencing degraded availability. We are continuing to investigate. Nov 9, 23:22 UTC Update - We are experiencing degraded availability for GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces due to an issue with an upstream model provider. We recommend choosing another model or selecting Auto to continue using Copilot until the issue is resolved. Nov 9, 23:16 UTC Investigating - We are investigating reports of degraded availability for Copilot Nov 9, 23:16 UTC Nov 9, 2026 Incident with Actions and Checks API 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. Nov 9, 18:59 UTC Monitoring - The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability. Nov 9, 18:43 UTC Update - Pages is experiencing degraded performance. We are continuing to investigate. Nov 9, 18:30 UTC Update - We're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more. Nov 9, 18:24 UTC Update - Webhooks is experiencing degraded performance. We are continuing to investigate. Nov 9, 18:23 UTC Update - Actions is experiencing degraded availability. We are continuing to investigate. Nov 9, 18:14 UTC Investigating - We are investigating reports of degraded availability for Actions Nov 9, 18:12 UTC Incident with Webhooks and Actions 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. Nov 9, 11:50 UTC Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. Nov 9, 11:45 UTC Update - Webhooks is experiencing degraded performance. We are continuing to investigate. Nov 9, 11:42 UTC Update - Webhooks is experiencing degraded availability. We are continuing to investigate. Nov 9, 11:17 UTC Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 9, 11:06 UTC Update - We've applied a mitigation and are monitoring for recovery. Nov 9, 10:47 UTC Update - We're investigating delays in Actions runs start times and webhook deliveries. Nov 9, 10:28 UTC Investigating - We are investigating reports of degraded performance for Actions and Webhooks Nov 9, 10:00 UTC Increased timeouts due to surge in anonymous users 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. Nov 9, 09:09 UTC Update - We are resolving this incident as error rates have remained low and we have prepared additional protections. Nov 9, 09:09 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 9, 09:05 UTC Update - Error rates have declined again, and we’re preparing targeted traffic controls while monitoring for a recurrence. Logged-in users and authenticated requests have not been affected. Nov 9, 08:47 UTC Update - We are continuing to observe high rates of 504 errors for anonymous requests. We are continuing to work on mitigation. Logged-in users and authenticated requests are unaffected. Nov 9, 08:16 UTC Investigating - We have observed a repeated increase in 504 errors for anonymous and unauthenticated traffic, including users who are not logged in and release downloads. We are continuing to investigate and apply mitigations. Nov 9, 07:43 UTC Update - The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution. Nov 9, 07:03 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 9, 06:51 UTC Update - We are debugging a spike in anonymous traffic. Some users who are not logged in may see errors on the site. CI jobs and release downloads may fail with a 504 Gateway Timeout status if they make anonymous calls. Nov 9, 06:30 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Nov 9, 05:59 UTC Nov 8, 2026 Increase in timeouts for some unauthenticated users 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. Nov 8, 12:32 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 8, 12:29 UTC Update - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability. Nov 8, 11:56 UTC Update - We've identified a problematic component and are working to redeploy it. Nov 8, 11:50 UTC Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 8, 11:20 UTC Update - We are continuing to investigate degraded performance primarily for unauthenticated users. Nov 8, 11:16 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Nov 8, 10:36 UTC Nov 7, 2026 No incidents reported. Nov 6, 2026 Degraded performance for multiple 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. Nov 6, 00:20 UTC Monitoring - This incident has been resolved. All affected services, including Git operations, Issues, Actions, and API access, have recovered and remained stable. Thank you for your patience. We'll share more details in our availability report. Nov 6, 00:19 UTC Investigating - Git Operations is operating normally. Nov 6, 00:19 UTC Update - We've applied a mitigation and are seeing recovery across affected services, including Git operations, Issues, Actions, and API access. We're monitoring to confirm stability and will post another update by 00:35 UTC. Nov 6, 00:06 UTC Monitoring - The degradation affecting Actions, Issues and Pages has been mitigated. We are monitoring to ensure stability. Nov 6, 00:06 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Nov 5, 23:58 UTC Update - We're investigating degraded performance and errors affecting several GitHub services, including Git operations, Issues, Actions, and API access. Some users may see failed requests or slow responses. We'll post another update by 00:05 UTC. Nov 5, 23:36 UTC Investigating - We are investigating reports of degraded performance for Actions and Pages Nov 5, 23:36 UTC Nov 5, 2026 Incident with Actions 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. Nov 5, 17:42 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 5, 17:04 UTC Update - Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation. Nov 5, 16:52 UTC Investigating - We are investigating reports of degraded performance for Actions Nov 5, 16:50 UTC Nov 4, 2026 Incident with Actions Resolved - Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/xr3myzj7ms51 Nov 4, 18:16 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 4, 18:07 UTC Update - We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs. Nov 4, 17:53 UTC Investigating - We are investigating reports of degraded availability for Actions Nov 4, 17:40 UTC Incident with Actions and Pages Resolved - On November 4, 2026, between 15:49 UTC and 16:48 UTC, and again between 17:20 UTC and 17:55 UTC, GitHub Actions, Pages, Webhooks, Code Scanning, and Copilot coding agent experienced delays. During this time, Actions workflow runs and job status updates were delayed by up to 25 minutes. Pages deployments dropped to about 4% of normal volume, webhook deliveries dropped to about 58% of normal volume, and Code Scanning analyses and Copilot coding agent sessions were delayed. Delayed events were processed after mitigation. This incident was caused by a configuration change to an internal event-routing service that unexpectedly paused delivery of several event streams. The change depended on feature flags that were not set up as intended, which the service did not handle gracefully. We mitigated the first period by rolling back the configuration change at 16:14 UTC. The code change itself was not reverted by the rollback, so a subsequent deployment reintroduced it. We mitigated the second period at 17:40 UTC by rolling back again, then processed queued events and cleared backlogs. We are taking several steps to prevent a repeat. The routing service will keep its existing behavior when a feature toggle is missing, so a misconfigured flag can no longer pause delivery. We are adding a pre-deploy check that each routing flag exists and is registered under the correct owning service, and we are making flag ownership less error-prone to set. We are also improving alerting so we detect paused event delivery sooner. Nov 4, 17:01 UTC Update - The degradation has been mitigated. We are monitoring to ensure stability. Nov 4, 16:49 UTC Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability. Nov 4, 16:48 UTC Update - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. Nov 4, 16:45 UTC Update - We have identified an issue with events that might trigger Actions. We have applied mitigations and are monitoring for recovery at this point. Customers may observe delayed status updates for their jobs. Nov 4, 16:34 UTC Update - Actions is experiencing degraded availability. We are continuing to investigate. Nov 4, 16:17 UTC Update - Webhooks is experiencing degraded performance. We are continuing to investigate. Nov 4, 16:12 UTC Update - We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation. Nov 4, 16:11 UTC Investigating - We are investigating reports of degraded performance for Actions and Pages Nov 4, 16:05 UTC Incident with Pull Requests, Git Operations and Issues 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. Nov 4, 11:50 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 4, 11:43 UTC Update - The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 4, 11:30 UTC Update - We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available. Nov 4, 11:17 UTC Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 4, 11:11 UTC Update - We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation. Nov 4, 10:38 UTC Update - Pull Requests is experiencing degraded availability. We are continuing to investigate. Nov 4, 09:53 UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 4, 09:50 UTC Investigating - We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests Nov 4, 09:49 UTC Increased task-related errors for Copilot Mission Control 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. Nov 4, 10:01 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 4, 10:01 UTC Update - We're continuing to see recovery as rollout continues Nov 4, 09:50 UTC Update - We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery. Nov 4, 09:11 UTC Update - Copilot Mission Control is experiencing increased error rates (approx 2.5%) in listing and creating tasks due to upstream database throttling. We are investigating two potential mitigations. Nov 4, 08:47 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Nov 4, 08:45 UTC Nov 3, 2026 Incident with Git Operations Resolved - On November 3, 2026, between 15:00 UTC and 22:37 UTC, Git operations over HTTPS on GitHub.com were degraded. Clones, fetches, and pushes over HTTPS were slow, and some failed. For about half of Git HTTPS traffic, median response time rose from under 100 milliseconds to as high as 5 seconds. On average, the error rate was 0.65% and peaked at 1.29% of requests to the service. Git operations over SSH were not affected. This was due to a buildup of excess connections on the hosts that serve Git HTTPS traffic, which saturated their network capacity and caused slow and failed responses for all clients served by those hosts. We mitigated the incident by blocking a client traffic pattern at our load balancers and reloading them, which released the excess connections. The block also prevented some users of one third-party integration from performing Git operations over HTTPS until we removed it on November 4 at 13:26 UTC. We are working to alert on sustained Git HTTPS latency sooner and make load balancer mitigations take effect on existing connections immediately. Nov 3, 22:41 UTC Monitoring - The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability. Nov 3, 22:37 UTC Update - We are seeing significant improvement, though some Git Operations may be slow for a small set of customers. We are marking this as mitigated and will continue to monitor. Nov 3, 22:37 UTC Update - Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status. Nov 3, 22:05 UTC Update - We have identified the issue impacting Git Operations and are beginning to roll out a mitigation. We will follow up with another update when we begin to see recovery. Nov 3, 21:37 UTC Investigating - We are investigating reports of degraded performance for Git Operations Nov 3, 20:57 UTC Incident with API, Git, and Copilot 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. Nov 3, 13:56 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 3, 13:54 UTC Investigating - API Requests is operating normally. Nov 3, 13:52 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Nov 3, 13:51 UTC Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability. Nov 3, 13:43 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Nov 3, 13:42 UTC Investigating - We are investigating reports of degraded performance for Copilot Nov 3, 13:25 UTC Nov 2, 2026 Elevated errors on GPT-5.4 Nano 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. Nov 2, 18:24 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Nov 2, 18:10 UTC Update - We are experiencing degraded availability for the GPT-5.4 Nano model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. Nov 2, 17:58 UTC Update - We are investigating reports of elevated errors on GPT-5.4 Nano Nov 2, 17:46 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers Nov 2, 17:46 UTC Nov 1, 2026 No incidents reported. Oct 31, 2026 No incidents reported. Oct 30, 2026 Incident with Dependabot Resolved - On October 30, 2026, between 20:15 and 21:56 UTC, an advisory-publication-driven fan-out caused an unexpected saturation of network connections to the Dependabot alerts datastore. During this period we observed a high rate of write failures on this datastore; users saw elevated failure rates when dismissing or resolving Dependabot alerts, as well as failures when linking Dependabot update pull requests to Dependabot security alerts. We also observed delays in creating and updating security alerts that extended through November 2, 2026. The unexpected fan-out was caused by a missing job queue throttle after the queues for the fan-out work were migrated as part of system maintenance. We have restored the fan-out throttle and further isolated and throttled these processes to guard against further disruptions. Oct 30, 23:29 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 30, 22:32 UTC Update - We have mitigated impact and are seeing recovery. We are monitoring for full recovery. Oct 30, 22:32 UTC Update - We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more. Oct 30, 21:44 UTC Update - We are investigating elevated errors when viewing some Dependabot alerts. Oct 30, 21:00 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Oct 30, 20:59 UTC Incident with Actions, Pages, and Webhooks Resolved - On October 30, 2026, from 17:50 to 18:32 UTC, Actions, Pages, and Webhooks experienced degraded performance. Actions workflow processing, Pages deployments, and webhook deliveries were delayed, and code search and live updates returned errors. Some Actions queues took additional time to drain after mitigation, and the incident was resolved at 19:23 UTC. The impact was triggered by maintenance on a cloud network gateway connecting an Actions service in the GitHub data center to Redis clusters in the Central US Azure region. The service's Redis client retried aggressively and redialed those connections. That produced a connection storm that saturated the gateway, with about 90% of connection attempts failing. Other services sharing the same network path were degraded as well. We mitigated the incident by removing the affected resources from rotation, which ended the connection storm and allowed the gateway to recover. We have already reduced the number of connection retries in the impacted service and are further improving retry behavior with jittered backoff, shorter connect timeouts, and retry budgets. We are also working with our infrastructure team to make GitHub more resilient to gateway maintenance. Oct 30, 19:23 UTC Monitoring - The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability. Oct 30, 18:32 UTC Update - All affected services have recovered following mitigation. We continue to investigate root cause. Oct 30, 18:32 UTC Update - 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. Oct 30, 18:06 UTC Update - Pages is experiencing degraded performance. We are continuing to investigate. Oct 30, 18:00 UTC Investigating - We are investigating reports of degraded performance for Actions and Webhooks Oct 30, 17:50 UTC Disruption with 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. Oct 30, 15:02 UTC Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability. Oct 30, 14:49 UTC Update - 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. Oct 30, 14:48 UTC Update - Issues is operating normally. Oct 30, 14:45 UTC Update - Pages is experiencing degraded performance. We are continuing to investigate. Oct 30, 14:39 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Oct 30, 14:36 UTC Update - We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation. Oct 30, 14:35 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Oct 30, 14:31 UTC Oct 29, 2026 Disruption with Copilot Cloud services Resolved - On October 29, 2026, between 05:50 UTC and 12:40 UTC, Copilot agent sessions on GitHub.com and in VS Code were degraded. Live session updates often failed to load, and on average 2.14% of requests to the agent sessions service failed, with a peak of 8.61%. For about 10 minutes around 09:20 UTC, up to 40% of requests to list or create agent sessions failed. Copilot Chat on GitHub.com showed degraded agent session features during this time. The issue occurred when a large increase in task-list requests from a client experiment overloaded the cache that supports the agent sessions service. We mitigated the impact by increasing cache capacity, reducing nonessential load on the cache, and disabling the client experiment. We are moving rate limiting to separate infrastructure, reducing client polling, and improving our alerting so we can detect and respond to this type of overload faster. Oct 29, 12:49 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 29, 12:33 UTC Update - We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. We are actively applying mitigations and monitoring for recovery. Oct 29, 11:37 UTC Update - We continue to experience failure rates of 1-2% and increased latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. Oct 29, 11:01 UTC Update - We are experiencing increased failures and latency on our agent sessions service, including creating and listing sessions. This can impact cloud based agent sessions on web, mobile, VS Code, CLI and the GitHub Copilot app. Oct 29, 10:22 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Oct 29, 10:19 UTC Oct 28, 2026 Disruption with some Copilot services Resolved - On October 28, 2026, between 13:52 and 15:24 UTC, Copilot users saw errors when using several GPT-family models and the MAI Code 1.1 Flash model. Affected experiences included Copilot Chat in IDEs and on GitHub.com, the Copilot CLI, Copilot Code Review, the Copilot Coding Agent, Code Scanning Autofix, and Code Quality. About 9.73% of requests to the affected models failed, with a peak of about 36.97% at the start of the incident. The errors happened because a credential that we use to authenticate with an upstream model provider became invalid. We mitigated the incident by replacing the credential and redeploying the service. We are strengthening how we manage credentials for upstream providers to prevent this type of failure, returning retryable errors when an upstream provider rejects a request, and improving our monitoring so that we detect and mitigate this type of problem faster in the future. Oct 28, 15:28 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Oct 28, 15:26 UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate. Oct 28, 15:24 UTC Update - We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon. Oct 28, 15:15 UTC Update - 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. Oct 28, 14:55 UTC Update - 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. Oct 28, 14:33 UTC Update - We are experiencing issues with upstream model providers resulting in a degraded experience across Copilot services. The team is actively investigating the issue. Oct 28, 14:15 UTC Investigating - We are investigating reports of impacted performance for some GitHub services. Oct 28, 14:12 UTC Incident History Powered by Atlassian Statuspage