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