Nov 9, 07:03 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, 06:51 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 9, 06:30 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, 05:59 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Status: Resolved All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience. Affected components Image Generation (Operational)
Nov 8, 12:32 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Nov 8, 12:29 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 8, 11:56 UTC Update - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability. Nov 8, 11:50 UTC Update - We've identified a problematic component and are working to redeploy it. Nov 8, 11:20 UTC Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 8, 11:16 UTC Update - We are continuing to investigate degraded performance primarily for unauthenticated users. Nov 8, 10:36 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Nov 7, 15:05 UTC Resolved - This incident has been resolved. Nov 7, 14:37 UTC Monitoring - A fix has been implemented and we are monitoring the results. Nov 7, 14:28 UTC Investigating - We are currently investigating this issue.
Nov 7, 02:51 UTC Monitoring - We are continuing to monitor for any further issues. Nov 7, 00:59 UTC Investigating - Cloudflare is investigating issues with Spectrum in Phoenix. This may be impacting the availability of existing Spectrum applications. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
Nov 6, 17:59 UTC Identified - We are continuing to work on a fix for the issue. Nov 6, 17:47 UTC Investigating - Cloudflare has identified a bug with our purge pipeline impacting fedramp customers. Stale content may be served until expired. Non-fedramp customers are not impacted.
Start: 2026-10-15T10:00:00+00:00 We are currently carrying out urgent maintenance on all of our core routers. The routers are being serviced one after another. During this work, network redundancy is reduced globally. We do not expect any service interruptions, but you may experience increased latency. This maintenance ensures the long-term security and stability of our infrastructure. We appreciate your understanding and thank you for your patience. We are still in the process of performing this maintenance. Thank you for your patience. In_progress2026-11-06T15:36:38+00:00
Start: 2026-11-09T06:00:00+00:00 Estimated end: 2026-11-11T15:00:00+00:00 During this time, technicians will be upgrading various power supply components, including the UPS system in NBG1-DC2 . The work should not negatively affect our server systems. You can see which data center your server is located in by doing a trace route (for example, by using https://dnstools.ws/).
Status: Resolved All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience. Affected components ChatGPT Work (Operational) dots (Operational) Codex Web (Operational)
Nov 6, 00:20 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Nov 6, 00:19 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:06 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 5, 23:58 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Nov 5, 23:36 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
Status: Complete (Thu, 05 Nov 2026 16:00:00 GMT - Thu, 05 Nov 2026 19:55:46 GMT) The planned maintenance is complete. Some users may need to sign in to Docker Desktop or Docker Sandboxes again. Affected components Docker Authentication (Operational)
Nov 5, 17:42 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Nov 5, 17:04 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 5, 16:52 UTC Update - Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation. Nov 5, 16:50 UTC Investigating - We are investigating reports of degraded performance for Actions
Nov 5, 16:24 UTC Resolved - This incident is now resolved Nov 5, 16:03 UTC Monitoring - We have resolved the API degradation issue, and are monitoring the services. Nov 5, 15:23 UTC Investigating - We are currently investigating an issue with degraded API response times on our platform. Dashboard services may have delayed response times, as well as some of our API endpoint responses. Active platform services are not affected by degradation.
Incident began at 2026-10-19 23:00 and ended at 2026-10-20 05:08 (all times are US/Pacific ). Incident Report Summary On Monday, 19 Oct 2026 at 22:53 US/Pacific (Tuesday, 20 Oct 2026, 06:53 BST), a data center facility that hosts europe-west2-b, a zone within the europe-west2 cloud region, experienced an external electrical power disruption. This resulted in service unavailability for workloads located in this zone. The subsequent failover of these workloads to unaffected zones and alternate regions caused transient latency and elevated error rates across the broader europe-west2 region. The resolution of the main impact was completed within 6 hours and 8 minutes. Root Cause Facility architecture and background: The data center facility in the UK region hosts Cloud clusters serving the europe-west2-b zone, which form part of the multi-zonal europe-west2 Cloud region. The site relies on a 2N utility power architecture—where the facility has complete duplicate power paths for every critical load—backed by a central high-voltage generator bank managed by a dual-redundant Programmable Logic Controller (PLC). Primary utility power is supplied to the facility via two independent feeders (A and B), supplemented by a standby utility connection configured for manual campus-wide transfer during maintenance operations or emergency events. The two high-voltage primary feeders (A and B) terminate at separate primary intake switchboards capable of closed-loop operation if either board is taken offline. Switching between the primary and standby utility providers utilizes open transitions and key interlocks to prevent parallel connections across sources. Uninterruptible Power Supply (UPS) battery systems provide approximately five minutes of autonomous runtime. This bridge power ensures uninterrupted operation while the PLC detects utility undervoltage events, initiates diesel generator startup, synchronizes the generators, and transfers the site load. Prior to the utility disrupti
Status: Resolved All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience. Affected components Conversations (Operational)
Nov 4, 18:16 UTC Resolved - Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/xr3myzj7ms51 Nov 4, 18:07 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 4, 17:53 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:40 UTC Investigating - We are investigating reports of degraded availability for Actions
Nov 4, 17:01 UTC 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, 16:49 UTC Update - The degradation has been mitigated. We are monitoring to ensure stability. Nov 4, 16:48 UTC Monitoring - The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability. Nov 4, 16:45 UTC Update - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability. Nov 4, 16:34 UTC Update - We have identified an issue with events that might trigger Actio
Nov 4, 13:38 UTC Update - We can confirm that the revocation of all affected certificates is now complete. Let's Encrypt has published every revocation in its Certificate Revocation Lists (CRLs). Every Let's Encrypt certificate that was on the affected server has been revoked with the reason "key compromise". Browsers and clients that check revocation will now reject the old certificates. The replacement certificates now in use are not affected, and customers don't need to do anything. Our provider's investigation is still ongoing. We will continue to follow up and will share the final outcome once it is complete. Oct 31, 12:50 UTC Update - We've completed the reissuance of managed TLS certificates for custom domains. All managed certificates have been reissued with new private keys, and the previous certificates have been revoked. No action is required from customers using managed certificates. If you manage your own TLS certificates and haven't done so yet, we continue to recommend revoking and reissuing them with new private keys as a precaution. - What we're doing to prevent this in the future We have stopped using the affected provider while their investigation continues. We recognise that we can't rely on any single layer of security, so we're taking additional steps to reduce the potential impact of similar incidents that could occur in the future. We're reducing what each server holds: we're changing how configurations are distributed so that each PoP only receives the configuration and TLS certificates for the sites it is actively serving, limiting the data stored on any single server. Neither our investigation nor the provider's has found any evidence of unauthorized access to our server. Should anything change, we will provide an update via email and on our status page. Thank you for your patience while we completed this work. At bunny.net, we understand the trust you place in us to keep your content secure, and we take that responsibility seriously. If y
Nov 4, 11:50 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Nov 4, 11:43 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 4, 11:30 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:17 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:11 UTC Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 4, 10:38 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, 09:53 UTC Update - Pull Requests is experiencing degraded availability. We are continuing to investigate. Nov 4, 09:50 UTC Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 4, 09:49 UTC Investigating - We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests
Nov 4, 10:01 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Nov 4, 10:01 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 4, 09:50 UTC Update - We're continuing to see recovery as rollout continues Nov 4, 09:11 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, 08:47 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:45 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Nov 3, 22:41 UTC 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:37 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:05 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, 21:37 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, 20:57 UTC Investigating - We are investigating reports of degraded performance for Git Operations
Nov 3, 13:56 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Nov 3, 13:54 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Nov 3, 13:52 UTC Investigating - API Requests is operating normally. Nov 3, 13:51 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Nov 3, 13:43 UTC Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability. Nov 3, 13:42 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Nov 3, 13:25 UTC Investigating - We are investigating reports of degraded performance for Copilot
Start: 2026-10-28T17:08:08+00:00 A critical security vulnerability has recently been identified in the EDK II UEFI firmware component (CVE-2026-97631, CVSS 9.5). Further details can be found in the advisory: https://github.com/tianocore/edk2/security/advisories/GHSA-99cj-7hg9-mp4m What is affected? The vulnerability affects systems that boot over the network using PXE. During the boot process, an attacker may be able to execute malicious code through specially crafted network packets, even before the operating system and its security mechanisms (e.g., Secure Boot) are active. Systems that are already running are not directly at risk; the vulnerability can only be exploited during a PXE boot. An official patch is not yet available. What do we recommend? As an immediate precautionary measure, we recommend avoiding reboots of your hosts until further notice if they use PXE boot. What happens next? We are currently analyzing the impact on our environment and developing further recommendations and additional protective measures. We will inform you promptly as soon as new findings or updates become available. Network filters have already been in place for cloud servers for some time. These protective measures are now fully implemented across our Cloud infrastructure, resolving the issue for Cloud. For dedicated (bare-metal) servers, we are continuing to explore ways to further expand these protective measures within our data center networks. The network filters described in our last update are now active at our network edge and between our locations. We are completing the rollout of the filters on cloud servers today. For dedicated (BareMetal) servers, we are currently evaluating how to extend these protective measures further within our DC networks. Until then, our previous recommendations still apply, especially for dedicated servers: Please avoid reboots where possible, and if a reboot is necessary, temporarily block incoming ICMP packets using the Hetzner Firewall. We
Status: Resolved All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience. Affected components File uploads (Operational)
Nov 2, 18:24 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Nov 2, 18:10 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Nov 2, 17:58 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:46 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
Oct 31, 14:43 PDT Resolved - This incident has been resolved. Oct 31, 12:40 PDT Monitoring - A fix has been implemented and we are monitoring the results. Oct 31, 08:26 PDT Investigating - We are currently investigating this issue.
Oct 30, 23:29 UTC 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, 22:32 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, 21:44 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:00 UTC Update - We are investigating elevated errors when viewing some Dependabot alerts. Oct 30, 20:59 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Status: Resolved All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience. Affected components ChatGPT Work (Operational) dots (Operational)
Oct 30, 19:23 UTC 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, 18:32 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:06 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:00 UTC Update - Pages is experiencing degraded performance. We are continui
Status: Resolved All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience. Affected components Images (Operational)
Oct 30, 09:18 PDT Resolved - This incident has been resolved. Oct 30, 08:43 PDT Monitoring - A fix has been implemented and we are monitoring the results. Oct 30, 08:43 PDT Identified - The issue has been identified and a fix is being implemented. Oct 30, 08:23 PDT Investigating - We are currently investigating this issue.
Oct 30, 15:02 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 30, 14:49 UTC Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability. Oct 30, 14:48 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:45 UTC Update - Issues is operating normally. Oct 30, 14:39 UTC Update - Pages is experiencing degraded performance. We are continuing to investigate. Oct 30, 14:36 UTC Update - Issues is experiencing degraded performance. We are continuing to investigate. Oct 30, 14:35 UTC Update - We are investigating degraded performance across multiple services. We will continue to keep users updated on progress towards mitigation. Oct 30, 14:31 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Status: Resolved The issue affecting image and video generation, Flows, and MCP in ElevenCreative has been resolved. Generations are completing normally. Affected components All features (Operational)
Oct 29, 12:49 UTC 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:33 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. 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. We are actively applying mitigations and monitoring for recovery. Oct 29, 11:01 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, 10:22 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:19 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.
Oct 28, 15:28 UTC 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:26 UTC Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. Oct 28, 15:24 UTC Update - Copilot is experiencing degraded performance. We are continuing to investigate. Oct 28, 15:15 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, 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. 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:33 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
Oct 28, 02:40 PDT Resolved - This incident has been resolved. Oct 28, 02:27 PDT Monitoring - A fix has been implemented and we are monitoring the results. Oct 28, 01:54 PDT Identified - The issue has been identified and a fix is being implemented. Oct 28, 01:36 PDT Investigating - We are currently investigating this issue.
Status: Resolved All affected services are operating normally again. We’re sorry for the disruption, and we appreciate your patience. Affected components Batch (Operational) Chat Completions (Operational) Responses (Operational)
Oct 26, 18:57 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 26, 18:54 UTC Update - 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. Oct 26, 18:50 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 26, 18:48 UTC Investigating - We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests
Oct 26, 06:30 UTC Resolved - This incident has been resolved. Oct 26, 06:21 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 26, 06:11 UTC Identified - The issue has been identified and a fix is being implemented. Oct 26, 05:54 UTC Investigating - We are currently investigating this issue.
Oct 24, 20:43 UTC Resolved - This incident has been resolved, we're not observing performance issues anymore. Oct 24, 19:35 UTC Monitoring - We've found and resolved the issue and are actively monitoring performance. Oct 24, 18:45 UTC Investigating - We are currently investigating this issue affecting the CDN performance in DE.
Oct 24, 00:23 UTC 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. Oct 24, 00:23 UTC Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability. Oct 23, 23:42 UTC Update - 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. Oct 23, 23:41 UTC Investigating - We are investigating reports of degraded performance for Copilot AI Model Providers
Oct 23, 18:51 UTC Resolved - We identified that an advisory-publication driven fan-out was overwhelming Dependabot alert processing on repositories by saturating the queue with its own events, delaying processing of events related to repository pushes. We have now isolated this fan-out and applied a throttle so it runs at a fixed rate and cannot delay other events. This remediation has successfully prevented a new fan-out process impacting users. Oct 23, 18:36 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 23, 17:27 UTC Update - Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability. We're continuing to investigate and work to restore normal processing. Oct 23, 16:43 UTC Update - We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring progress and will share another update as we learn more. Oct 23, 16:11 UTC Update - We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring the rollout and will share another update as we learn more. Oct 23, 15:39 UTC Update - We’re scaling alert processing capacity to reduce the backlog causing delays in some Dependabot alerts closing after affected repositories have been updated. We’re continuing to monitor and will share another update as more information becomes available. Oct 23, 15:00 UTC Update - We’re investigating delays in some Dependabot alerts closing after affected repositories have been updated to address a vulnerability. Alert processing is backed up. We’ll share more information as it becomes available. Oct 23, 14:58 UTC Investigating - We are investi
Oct 23, 08:05 UTC Resolved - On October 23, 2026, between 07:06 UTC and 07:27 UTC, GitHub Actions workflow run results were delayed. Job status, check run updates, and logs in the GitHub UI and API updated with an average delay of about 2 minutes, and some updates were delayed by up to about 7 minutes. During this window, a storage dependency that Actions uses to process workflow logs and artifacts throttled our requests. This slowed result processing, causing updates to queue up. The queue was fully processed by 07:27 UTC, shortly after the throttling stopped. To reduce the risk of recurrence, we have added several storage accounts to increase capacity, and we are working on additional steps to continue to scale. We are also working with our storage provider to understand why the throttling occurred, and improving how result processing handles storage throttling and how quickly we detect it. Oct 23, 07:56 UTC Update - As of 07:27 UTC, Actions results are delivering within normal SLOs again. Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future. Oct 23, 07:53 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Oct 23, 07:31 UTC Update - We are seeing delays in results from Actions workflows being reported within GitHub starting from 07:07 UTC. Recovery is already being seen but our team is continuing to investigate and monitor performance. Oct 23, 07:29 UTC Investigating - We are investigating reports of degraded performance for Actions
Oct 23, 02:30 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 23, 00:55 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 22, 23:48 UTC Update - GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. We're continuing to work on the remaining delays and monitor recovery. Oct 22, 22:07 UTC Update - Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed. We have seen some recovery, and are working to add more capacity to accelerate the recovery. Oct 22, 20:46 UTC Update - Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed. We've identified interruptions in update processing and are evaluating mitigations to restore normal operation. Oct 22, 19:56 UTC Update - Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing. Oct 22, 19:04 UTC Update - Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring. Oct 22, 18:26 UTC Update - The other affected services have recovered. We're continuing to investigate GitHub Projects and verify that normal operation has been restored. Oct 22, 17:43 UTC Update - We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability. Oct 22, 17:41 UTC Update - Actions, Issues, Packages and Pull Requests are operating normally. Oct 22, 17:16 UTC Update - We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search resul
Oct 22, 15:18 UTC Resolved - On October 22, 2026, from 13:05 to 15:20 UTC, our event streaming platform was degraded resulting in elevated job processing latency spikes of 19-35 seconds and elevated job processing times of 4m – this resulted in delayed Actions workflow and step results (up to 13m), notifications (20m) and repository push events (12m). Recovery for repositories began at 14:32, with Actions recovery beginning at 14:59. The issue reoccurred at 16:26 again impacting Actions runs, repo push events, and notifications. Recovery began at 17:16 and completed at 2:07. The incident was caused by a significant increase in load coupled with client connection storms during a deployment overloading our Kafka event streaming brokers. To prevent future recurrence, we have expanded the affected cluster, shifted traffic to less loaded clusters, and implemented tunable client reconnect backoff. Oct 22, 15:18 UTC Update - GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal. Oct 22, 15:17 UTC Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Oct 22, 15:06 UTC Update - We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain. Oct 22, 14:35 UTC Update - Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress. Oct 22, 14:19 UTC Update - We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates. Oct 22, 14:18 UTC Investigating - We are investigating reports of degraded performance for Actions
Oct 22, 11:59 UTC Resolved - This incident has been resolved. Oct 22, 09:00 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 22, 06:43 UTC Investigating - We are currently investigating this issue.
Oct 22, 04:24 UTC Resolved - This incident has been resolved. Oct 22, 04:10 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 22, 03:07 UTC Identified - The issue has been identified and a fix is being implemented. Oct 22, 02:37 UTC Update - We are continuing to investigate this issue. Oct 22, 02:33 UTC Investigating - We are currently investigating this issue.
Oct 21, 19:22 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Oct 21, 19:22 UTC Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed. Oct 21, 18:52 UTC Update - Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates. Oct 21, 18:18 UTC Update - Audit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow. Oct 21, 17:09 UTC Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates. Oct 21, 16:59 UTC Update - Actions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues. Oct 21, 16:57 UTC Update - Actions and Webhooks are operating normally. Oct 21, 16:34 UTC Update - Audit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more. Oc
Status: Resolved The incident has been resolved. Docker Hub is operating normally, and we have confirmed that response times and availability have returned to expected levels for all services. Affected components Docker Authentication (Operational) Docker Hardened Images (Operational) Docker Hub Automated Builds (Operational) Docker Hub Registry (Operational) Docker Hub Web Services (Operational) Docker Package Repositories (Operational)
Status: Resolved On October 20, from 9:35 to 10:35 a.m. PDT, some users near Illinois experienced authentication errors with the API, ChatGPT, and Codex. We rolled back a configuration change, and service was restored. Affected components Login (Operational)
Oct 19, 16:56 UTC Resolved - On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. Impact - Workflow status updates, logs, and checks were delayed. - 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed. - During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors. Pages deployments and webhooks generated by Actions runs were delayed. An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to investigate the cause of the initial connection timeouts. We were already in the process of rolling out a limit on how quickly this service can open new connections, but it was still in shadow mode (logging only, not enforcing) at the time of the incident. We have since fully enforced it and capped the service's concurrent connection attempts. We are extending these limits to other Actions services, adding backoff to retries, limiting how much shared network capacity a single service can use, and improving alerting so we can find the source of connection surges faster. Oct 19, 16:56 UTC Monitoring - Actions, Pages and Webhooks are operating normally. Oct 19, 16:30 UTC Update - We’re seeing recovery following mitigation and are continuing to monitor. Customers may still experience delays in GitHub Actions workflow status updates,
Oct 16, 10:19 UTC Resolved - This issue has now been resolved. Oct 15, 21:20 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 15, 21:09 UTC Investigating - We're currently investigating intermittent issues when listing/uploading to Storage zones in DE and failed uploads in Stream.
Oct 15, 13:15 UTC Resolved - Root Cause behind this incident was a core network outage on one of our major Frankfurt providers that made a large number of Bunny servers in Frankfurt unreachable between 02:36 and 02:44 UTC. We haven't observed any further issues since 02:44 UTC, nor expect any further issues due to this and will be resolving this incident at this time. Oct 15, 07:24 UTC Update - All affected services have been stable, we are continuing to monitor Oct 15, 02:44 UTC Monitoring - We are investigating a network issue that lasted approximately 10 minutes and affected the availability of the Frankfurt Storage, Magic Containers, Bunny Database and CDN regions
Oct 14, 11:44 UTC Resolved - This incident has been resolved. Oct 14, 11:33 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 14, 11:20 UTC Identified - The issue has been identified and a fix is being implemented. Oct 14, 11:06 UTC Update - We are continuing to investigate the issue. We also observe increased errors in accessing package settings. Oct 14, 09:29 UTC Investigating - We observed increased errors and latency in login and viewing packages. We are investigating the issue.
Status: Resolved We have resolved the issue causing degraded performance with GPT-6.1 Sol in Codex and ChatGPT Work. Affected components Codex Web (Operational) CLI (Operational) VS Code extension (Operational) Codex API (Operational) ChatGPT Work (Operational)
Status: Resolved The incident is resolved. Error rates are back to normal, and stable service has been confirmed. We will publish a Root cause analysis once our review of the incident is complete. Affected components Conversations (Operational) Telephony (Operational) RAG (Operational) Quality (Operational) Other Agents APIs (Operational) UI (Operational) Integrations (Operational)
Status: Resolved After several hours of monitoring, our metrics show that error rate has remained at its stable baseline since 17:55 UTC; the increase in Dubbing platform latency and failure rate is now resolved. Affected components Other APIs (Operational) All features (Operational)
Status: Resolved We have monitored error metrics and have confirmed that as of 15:15 UTC, we do not see continuing Agent SIP conversation failures. We will conduct an internal investigation and post a full Root Cause Analysis upon conclusion. Affected components Telephony (Operational)
Status: Resolved Music had reduced availability after a latent infrastructure configuration issue was triggered by routine automated maintenance. This stopped new instances from starting and prevented automated recovery, and service was restored by manual intervention. The service is now fully operational again. Affected components Other APIs (Operational)
Status: Resolved All impacted services have now fully recovered. Affected components Conversations (Operational) GPTs (Operational) ChatGPT Work (Operational)
Oct 7, 22:36 UTC Resolved - This incident has now been resolved. Oct 7, 11:13 UTC Monitoring - Our Engineering team has identified a process load issue which has now been resolved. The team are now monitoring the situation Oct 7, 10:13 UTC Investigating - We are currently investigating Database performance degradation in some regions, our Engineering team are currently investigating root cause.
Status: Resolved We have released an updated app version with the fix for Linux, macOS and Windows. Affected users should update to the latest version. Affected components Codex in ChatGPT Desktop (Operational)
Oct 6, 08:58 UTC Resolved - This incident has been resolved Oct 6, 00:07 UTC Monitoring - A suboptimal log query had put a lot of load to an infrastructure component affecting performance of the whole system. The query has been isolated. We're observing better throughput, but will be monitoring the situation for the next few hours. Oct 5, 23:02 UTC Investigating - We're investigating performance degradation within our CDN Logging infrastructure, impacting our CDN Logging offering.
Status: Resolved All impacted services have now fully recovered. Affected components Conversations (Operational) Image Generation (Operational) ChatGPT Work (Operational) Space (Operational) dots (Operational)
Status: Resolved All impacted services have now fully recovered. Affected components Login (Operational) Ads Manager (Operational) Ads API (Operational)
Sep 30, 02:58 PDT Resolved - This incident has been resolved. Sep 30, 02:48 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 30, 02:38 PDT Identified - The issue has been identified and a fix is being implemented. Sep 30, 02:16 PDT Investigating - We are currently investigating this issue.
Status: Resolved The issue affecting support chat has been resolved. You can now contact our support team through the Help Center as usual. Thank you for your patience while we worked to restore service.
Status: Resolved We have not seen any further errors after the fix was applied. All services are fully operational and stable. We will post an RCA on our status page after further investigation. Affected components Speech to Text (Operational) Other APIs (Operational) Conversations (Operational) All features (Operational)
Sep 27, 06:47 UTC Resolved - This incident has been resolved. Sep 27, 01:30 UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep 27, 00:50 UTC Investigating - We are currently investigating this issue.
Status: Resolved All impacted services have now fully recovered. Affected components Codex Web (Operational) CLI (Operational) VS Code extension (Operational) Codex API (Operational)
Sep 25, 17:15 UTC Resolved - A subset of optimizer workers exhibited disk performance issues, impacting Optimizer software's throughput. A fix has been deployed to all servers sharing this same hardware model and performance is back at normal levels again. Sep 25, 14:49 UTC Investigating - We are currently investigating degraded optimizer processing, causing increased latency in serving assets on CDN. This issue sits under image transformation and asset compression only.
Incident began at 2026-09-25 15:47 and ended at 2026-09-25 16:40 (times are in Coordinated Universal Time (UTC) ). Summary: Mitigated elevated error rate with Google Workspace Studio web. Description: The issue with Google Workspace Studio has been resolved for all affected users as of Friday, 2026-09-25 09:40 PDT. From preliminary analysis, the root cause of the issue is a recent rollout. Our engineering team has rolled back which mitigated the issue. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have experienced an endless loading screen when attempting to access Google Workspace Studio on the web. Workaround: The issue is now mitigated. Affected products: Google Workspace Studio
Sep 23, 20:32 PDT Resolved - This incident has been resolved. https://x.com/discord/status/2102964092189475028?s=20 Sep 23, 20:05 PDT Monitoring - A fix has been implemented and we are monitoring results. Please close and refresh your app to get the fix for adult status. Sep 23, 19:10 PDT Identified - We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but "adult" on web/desktop. We’re aware of the issue and actively working on a fix. Sep 23, 19:08 PDT Investigating - We’re aware of an issue where users are seeing mismatched age group statuses across devices. For example, appearing as “unconfirmed” on an older mobile app version, but "adult" on web/desktop. We’re aware of the issue and actively working on a fix.
Sep 22, 14:07 UTC Resolved - Network performance issues caused by an upstream provider have been mitigated via traffic rerouting. All services and connection timeouts have returned to normal. Sep 22, 13:37 UTC Investigating - We are currently investigating intermittent timeouts with Bunny dashboard access (Login) and API responses within Poland
Sep 21, 22:53 UTC Resolved - This incident has been resolved. Sep 21, 21:42 UTC Monitoring - The synchronization delays have been resolved, and normal operations have been restored. We will continue monitoring the service to ensure everything remains stable. Sep 21, 19:34 UTC Investigating - We are currently investigating an issue causing synchronization delays across our CDN. Our team is actively working to identify the cause and restore normal operations. We will provide further updates as more information becomes available. We apologize for any inconvenience this may cause.
Sep 21, 09:17 UTC Resolved - Video encoding delays have now been fully resolved. Sep 19, 12:00 UTC Monitoring - We have noted improvement in transcoding process delays, and are monitoring the situation. Sep 17, 20:31 UTC Identified - We have been made aware of increased processing time in video encoding queues. We're working on alleviating the underlying issue.
Sep 17, 13:39 PDT Resolved - This incident has been resolved. Sep 17, 13:17 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 17, 13:00 PDT Identified - The issue has been identified and a fix is being implemented. Sep 17, 11:18 PDT Investigating - We are currently investigating this issue.
Sep 16, 15:35 PDT Resolved - This incident has been resolved. Sep 16, 15:15 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 16, 14:45 PDT Identified - The issue has been identified and a fix is being implemented. Sep 16, 14:32 PDT Investigating - We are currently investigating this issue.
Sep 16, 12:28 PDT Resolved - This incident has been resolved. Sep 16, 12:20 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 16, 12:03 PDT Investigating - We are currently investigating this issue.
Sep 16, 09:43 PDT Resolved - This incident has been resolved. Sep 16, 09:15 PDT Identified - We're currently experiencing an issue that prevents users from completing purchases (including Nitro subscriptions and Shop items) through the Android app. This is caused by an ongoing outage with Google Play. Purchases on other platforms (iOS, web, and desktop) are unaffected, and existing subscriptions remain active. We're monitoring Google's status and will post an update as soon as service is restored. No action is needed on your part — please try again later. https://pay.google.com/status/incidents/gQJsjf662F7KwPyiNqav
Sep 15, 18:19 UTC Resolved - This incident has been resolved. Sep 15, 18:18 UTC Update - Stable Sep 15, 17:20 UTC Identified - The issue has been identified and a fix is being implemented. Sep 15, 17:20 UTC Investigating - We are currently investigating this issue.
Sep 15, 16:35 UTC Resolved - This incident has been resolved. Sep 15, 16:13 UTC Investigating - We are investigating delays affecting npm package publishing. Some newly published package versions may take longer than expected to become available.
Sep 15, 08:16 PDT Resolved - This incident has been resolved. Sep 15, 07:58 PDT Monitoring - A fix has been implemented and we are currently monitoring recovery of services. Sep 15, 07:42 PDT Identified - The issue has been identified and we are working to restore service. Sep 15, 07:26 PDT Investigating - We are currently investigating this issue.
We are providing an update on the disruption affecting the Middle East (UAE) (me-central-1) Region. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in the mec1-az2 Availability Zone. We continue to work on recovering regional resources, as well as zonal resources hosted in the other affected Availability Zones (mec1-az1 and mec1-az3). Since the disruption began in March, most customers have been able to re-establish their operations in other Regions by restoring backups or copying data that remained accessible. AWS Support remains available to help customers who need assistance moving their applications to alternate Regions. We remain committed to supporting our customers in the UAE. We are working on replacing the affected infrastructure and will provide an update on the restoration of our services in the coming months. We have notified the relevant authorities and continue to work with them toward that goal.
We are providing an update on the disruption affecting the Middle East (Bahrain) (me-south-1) Region. The damage to our infrastructure spanned multiple Availability Zones and exceeded what our regional and multi-AZ services are designed to withstand. After a thorough assessment, we have determined that we are unable to restore access to the resources and data hosted exclusively in this Region. When the first Availability Zone was damaged in March, we began recommending that customers migrate their workloads to other Regions, and most did so before the Region became unavailable following the disruption of a second Availability Zone in April. Since then, we have supported the remaining customers in re-establishing their operations in alternate Regions, using backups where available or implementing alternative solutions to mitigate the impact of inaccessible data. In parallel, we assessed all affected infrastructure and exhausted every option for restoring data and resources that had not been migrated before the Region became unavailable. We remain committed to supporting our customers in Bahrain in the long term and will share a further update in early 2027. We have notified the relevant authorities and continue to work with them toward that goal.
Status: Resolved Newly pushed images and tags are now processing and appearing normally. We have resolved the issue and confirmed that pushed tags were stored correctly and were not lost. Affected components Docker Hub Registry (Operational) Docker Hub Web Services (Operational)
Sep 14, 03:13 PDT Resolved - This incident has been resolved. Sep 14, 02:55 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 14, 02:15 PDT Investigating - We are currently investigating this issue.
Sep 11, 10:46 PDT Resolved - This incident has been resolved. Sep 11, 10:39 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 11, 09:27 PDT Identified - The issue has been identified and a fix is being implemented. Sep 11, 09:24 PDT Investigating - We are currently investigating an issue involving high error-rates for image downloads.
Start: 2026-06-26T06:00:00+00:00 Due to the continuing high demand and the limited availability of required hardware components, the provisioning of cloud servers at our locations is currently only possible to a limited extent. Given this situation, we are currently required to restrict the creation of new cloud servers for both new customers and some of our existing customers. The selection of affected existing customers is made at random. Unfortunately, it is not possible to individually influence or prioritize specific requests. We are continuously monitoring the situation and working intensively to expand capacity. More details can be found in this article: https://docs.hetzner.com/cloud/general/faq#why-can-cloud-instances-occasionally-not-be-ordered Thank you very much for your understanding.
Sep 10, 23:42 PDT Resolved - This incident has been resolved. Sep 10, 23:20 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 10, 21:21 PDT Investigating - We are currently investigating this issue.
Sep 8, 18:24 UTC Resolved - The issue affecting payment attempts on the billing dashboard has been resolved. Our monitoring has confirmed that the service is operating normally. Sep 8, 17:07 UTC Monitoring - A fix has been deployed for the issue affecting payment attempts on the billing dashboard. The service has been restored, and we are currently monitoring the situation to ensure everything continues to operate as expected. Sep 8, 15:47 UTC Identified - We are currently aware of an issue of failed payment attempts on our billing dashboard on user accounts. Our team are working to restore its functionality.
Status: Resolved After completing the monitoring stage, we have confirmed that STT latency has returned to baseline stability. Affected components Other APIs (Operational) Speech to Text (Operational)
Sep 4, 07:33 PDT Resolved - This incident has been resolved. Sep 4, 07:21 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 4, 07:16 PDT Investigating - We are currently investigating this issue.
Sep 4, 13:48 UTC Resolved - This incident has been resolved. Sep 4, 13:27 UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep 4, 11:29 UTC Investigating - We are currently investigating this issue.
Sep 4, 05:54 PDT Resolved - Microsoft has resolved the underlying issue, we are seeing deliveries to M365 process normally. Sep 4, 05:22 PDT Update - We are continuing to monitor for any further issues. Sep 4, 05:20 PDT Monitoring - Starting around 08:00 UTC, Microsoft began experiencing an incident causing an increased volume of deferred emails across all M365 regions. The affected responses are returning "451 4.7.500 Server busy". Our teams are actively monitoring the situation. Sending to other email providers is not affected.
Sep 3, 23:21 UTC Resolved - This incident has been resolved. Sep 3, 22:41 UTC Monitoring - A fix has been implemented and we are monitoring the results. Sep 3, 22:17 UTC Update - We are continuing to investigate this issue. Sep 3, 21:42 UTC Investigating - We are currently investigating this issue.
Sep 3, 15:27 PDT Resolved - This incident has been resolved. Sep 3, 15:06 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 3, 14:31 PDT Identified - We've identified an issue causing some servers to appear unavailable in the client
Status: Resolved The issue causing elevated errors across ChatGPT and Codex has been resolved. Some Codex remote control users may need to pair their mobile device again following this incident. Affected components Voice mode (Operational) Search (Operational) Codex Web (Operational) Connectors/Apps (Operational) CLI (Operational) Login (Operational) File uploads (Operational) Conversations (Operational) Compliance API (Operational) Image Generation (Operational) Agent (Operational) VS Code extension (Operational) ChatGPT Work (Operational) GPTs (Operational) Codex in ChatGPT Desktop (Operational) Codex API (Operational) Sites (Operational) Deep Research (Operational)
Sep 3, 15:38 UTC Resolved - This issue is now fully resolved. Our Engineering team have identified additional guardrails to prevent this specific issue from happening in future. Sep 3, 14:25 UTC Update - We have confirmed that all services have fully resumed. Our Engineering team are currently monitoring the situation. Playback has now fully resumed without issue. New uploads during the outage have failed and thus would need re-uploading. Existing transcoding videos were not lost, however the status reported on some of these videos may be inaccurate as a result. Sep 3, 14:01 UTC Update - We are observing some isolated issues on the back of the fix. We are working to fully restore the process on our platform. Sep 3, 14:00 UTC Monitoring - We have identified a backend database issue which had caused a timeout across our video servers (to include our player and uploading process). The problem was rectified and we are now monitoring the situation. Sep 3, 13:47 UTC Investigating - Our Engineering team are currently investigating an issue on our Stream platform of playback failures on our embedded players, as well as upload failures to our platform.
Sep 3, 08:37 PDT Resolved - This incident has been resolved. Sep 3, 08:01 PDT Monitoring - A fix has been implemented and we are monitoring the results. Sep 3, 07:56 PDT Identified - The issue has been identified and a fix is being implemented. Sep 3, 07:35 PDT Investigating - Some servers may appear unavailable in the client. We are investigating
Sep 3, 13:11 UTC Resolved - This incident has been resolved. Sep 3, 08:53 UTC Identified - We are currently observing performance degradation with a Tier 1 transit provider in the Los Angeles area due to multiple fiber cuts on their network. This has impacted connectivity between the Bunny Optimizer LA cluster and a small number of US CDN PoPs. Traffic has been rerouted to minimize the impact.
Sep 2, 16:42 PDT Resolved - This incident has been resolved. Sep 2, 16:35 PDT Identified - We've identified an issue with our endpoint selection service and are applying a mitigation now. We are seeing recovery to endpoint selection now. Sep 2, 16:26 PDT Investigating - We are investigating problems with voice endpoint selection. Your calls may fail to start or may fail to get an endpoint.
Sep 2, 11:26 PDT Resolved - This incident has been resolved. Sep 2, 11:18 PDT Monitoring - We have recovered. We are still investigating the root cause and will post an update once we have more information Sep 2, 10:51 PDT Update - We are still investigating the issue, some servers are continuing to have a degraded experience Sep 2, 10:04 PDT Update - We are continuing to investigate this issue Sep 2, 09:12 PDT Investigating - We're investigating an issue where some servers are offline.
Sep 2, 15:51 UTC Resolved - A wider network incident in Los Angeles impacted Bunny Services hosted in the region. Affected network providers have mitigated the incident and all impacted services have remained stable since then. Sep 2, 14:38 UTC Investigating - We're investigating reports of widespread network issues in Los Angeles that seem to be impacting our services as well. We are working with our providers in the area to understand the issue at hand and mitigate.
Aug 31, 17:49 PDT Resolved - This incident has been resolved. Aug 31, 16:56 PDT Identified - We are taking steps to remediate the issue Aug 31, 16:38 PDT Update - We are taking steps to remediate the issue Aug 31, 16:26 PDT Update - some servers will appear unavailable for some users, and some other services may also be impacted (voice calls, activities) Aug 31, 15:54 PDT Investigating - Some users may not be able to connect to some of their servers
Aug 31, 15:01 PDT Resolved - Event queues have caught up and events are processing normally. Aug 31, 14:28 PDT Update - The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. We expect all delays to be resolved within the hour. Aug 31, 13:43 PDT Update - The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. Aug 31, 13:13 PDT Update - The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. We expect all delays to be resolved in the next 2 hours. Aug 31, 12:38 PDT Update - The event processing backlog is steadily decreasing, and we’re continuing to monitor the recovery. Aug 31, 11:59 PDT Update - The delays in event processing are reducing. We expect all delays to be resolved in the next 3 hours. Aug 31, 10:56 PDT Update - We are putting a fix in place for this issue. There is significant backlogs of event logs to process. We update the expected time of resolution when available. Aug 31, 10:05 PDT Update - We are continuing to work on a fix for this issue. Aug 31, 09:24 PDT Update - We are continuing to work on a fix for this issue. Aug 31, 08:29 PDT Update - We are continuing to work on a fix for this issue. Aug 31, 07:47 PDT Identified - We are currently experiencing delays in event log processing in our US region.
Status: Resolved We’ll mark this incident as resolved. Our ticketing system is operational again, though the outage materially affected its setup. We’re working with the team to restore full functionality, but capacity is sufficient to consider the incident resolved. Affected components All features (Operational)
Aug 27, 14:16 PDT Resolved - This incident has been resolved. Aug 27, 14:00 PDT Monitoring - A fix has been implemented and we are monitoring the results. Aug 27, 13:45 PDT Identified - We have identified the issue and working on restoring service. Aug 27, 13:38 PDT Investigating - We are currently investigating an outage in our EU datacenter
Status: Resolved The issue has been resolved. A root cause analysis will be shared shortly. Affected components Text to Speech (Operational) Speech to Text (Operational)
Aug 25, 22:31 UTC Resolved - After monitoring the affected services, we have confirmed that Database management and idle Database activation are operating normally. Aug 25, 16:06 UTC Monitoring - The issue has been resolved and the affected services have been restored. Our Engineering team will continue monitoring the platform to ensure everything remains stable. Aug 25, 16:01 UTC Update - Our Engineering team are continuing to work on the issue. Additionally, we are aware of some working Databases failing during this outage. This is related and our team are also working to address this. Aug 25, 14:06 UTC Identified - We have identified an issue with our Database controller, that our Engineering team are working to restore. Databases already online are not affected and will continue operating normally, but idle Databases or Database management is currently unavailable.
Status: Complete (Tue, 25 Aug 2026 20:20:00 GMT - Tue, 25 Aug 2026 20:30:00 GMT) What's changing? On 8/25, we will migrate our status page to incident.io: http://incident.io Status Pages. This migration is part of our ongoing efforts to improve incident response, on-call management, and reliability communication. With incident.io: http://incident.io, we're bringing incident response, on-call management, and post-incident reviews into a single platform, so you get faster and more consistent updates during incidents. What you need to know • Our status page URL remains the same: you can still access it at : https://dockerstatus.com/https://dockerstatus.com. • Email subscribers will be automatically migrated to the new status page. No action needed. • A new RSS subscription option will be available to subscribers. • Slack subscriptions will need to be re-added after the migration to keep receiving updates. • Webhook subscription options will no longer be available. What you need to do • If you're subscribed via Email: • You'll be automatically migrated. No action required. • If you're subscribed via Slack: • Confirm the migration is complete by checking for "Powered by incident.io: http://incident.io" at the bottom of : https://dockerstatus.com/https://dockerstatus.com. • Re-subscribe your Slack workspace to keep receiving updates. • If you're subscribed via Webhook: • Wait until after the maintenance window is complete. • Choose an alternative subscription option: Email, Slack, or RSS. If you have questions or issues, reach out to our Support team: https://hub.docker.com/support/contact Thanks for your patience as we make this change. Affected components Docker Authentication (Operational)
Status: Resolved Our engineers have traced media loading error rates as they have returned to baseline. Studio, Audiobooks, Image & Video, Music and Dubbing products should now functional normally. Affected components All features (Operational) Other APIs (Operational)
Status: Resolved The issue causing some ChatGPT web users to be unexpectedly logged out when refreshing the page has been resolved. Affected components Login (Operational)
Aug 20, 10:31 PDT Resolved - This incident has been resolved. Aug 20, 10:09 PDT Update - GCP has put a mitigation in place, we are monitoring the results. At this time we are experiencing no impacts. All delayed webhooks and logs have been processed. Aug 20, 09:30 PDT Update - Outbound delivery is operating normally. Currently there are delays for event logs and some webhooks. Aug 20, 09:19 PDT Monitoring - Mailgun is monitoring service impacts in GCP's us-west1 region. We are routing traffic away from impacted infrastructure. Currently we are seeing delays in log processing and a small number of message sends.
Status: Resolved All impacted services have now fully recovered. Affected components Conversations (Operational) Image Generation (Operational) ChatGPT Work (Operational)
