Live status · checked every 15 minutes
Is GitHub down right now?
GitHub hosts code, pull requests, issues, Actions, Pages, Codespaces and Copilot for developers.
Live reader reports
Is GitHub down for you?
Tap what's not working, or tell us it works. Reports are anonymous, one per visitor.
No reports in the last 24 hours. Be the first to tell other readers what you're seeing.
Every GitHub service
CheckedGitHub not working for you?
- Check your internet connection and any VPN or corporate proxy.
- Sign out and back in, or try a private browser window.
- Check the specific feature you use on the official status page: one part can be down while the rest works.
- Retry failed API calls and jobs with backoff.
GitHub outage history
Last 30 daysFixed Disruption with some GitHub services
-
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.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
Starting around 18:02 UTC on November 5, GitHub web sessions stopped being renewed based on recent activity, so users were signed out when their sessions expired due to inactivity. These sign-outs were caused by a bug in session renewal, not due to a security incident.We believe we fixed the bug at 05:23 UTC on November 19, and sessions created since then should renew as usual. We’re continuing to monitor the situation.If you had an inactive session from that period, you may still find that you’re signed out when you return to GitHub. If that happens, all you need to do is sign back in.
-
We are investigating reports of impacted performance for some GitHub services.
Fixed Degraded availability for GPT-6 Luna in Copilot
Affected: Copilot AI Model Providers
-
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.
-
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
-
We are experiencing degraded availability for the GPT-6 Luna model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Fusion' to continue using Copilot.
-
We are investigating reports of degraded performance for Copilot AI Model Providers
Fixed Degraded Availability for MAI Code 2 Flash in Copilot
Affected: Copilot AI Model Providers
-
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.
-
The issues with our upstream model provider have been resolved, and MAI Code 2 Flash is once again available in Copilot products and IDE surfaces.We will continue monitoring to ensure stability, but mitigation is complete.
-
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
-
We have been working with the upstream provider and applying mitigations, and are seeing widespread improvement in availability for MAI Code 2 Flash across Copilot products and IDE surfaces.We will continue monitoring.
-
We are experiencing degraded availability for the MAI Code 2 Flash model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting ‘Copilot Fusion’ to continue using Copilot.
-
We are investigating reports of degraded performance for Copilot AI Model Providers
Fixed Incident with Pull Requests
Affected: Pull Requests, Actions
-
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.
-
We’ve mitigated the issue affecting pull request merges and Actions workflow start times by reducing load on affected systems. Pull Requests and Actions have recovered, and we’re continuing to monitor their performance.
-
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
-
We’re seeing early signs of improvement in pull request merge times & workflow start times, but recovery is not yet confirmed. Users may still have difficulty merging pull requests. We’re reducing load on affected systems and monitoring the impact. We’ll share another update as we learn more.
-
We’re seeing early signs of improvement in pull request merge times, but recovery is not yet confirmed. The last confirmed timeout rate was 2.5%, compared with a baseline near 0.2%, so some users may still have difficulty merging pull requests. We’ll share another update as we learn more.
-
Actions is experiencing degraded performance. We are continuing to investigate.
-
We’re continuing to investigate elevated pull request merge timeouts. The latest reported rate is 4.75%, compared with a baseline near 0.2%, so some users may have difficulty merging pull requests. We’ll share another update as we learn more.
-
We’re continuing to investigate elevated pull request merge timeouts. Approximately 3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not materially improved performance, and our teams are working to reduce load and restore normal service. We’ll share another update as we learn more.
-
We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not restored normal performance, and our teams are continuing to investigate. We’ll share another update as we learn more.
-
We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. We’ll share another update as we learn more.
Fixed Copilot experiencing degraded model availability for some GPT models
Affected: Copilot AI Model Providers
-
Between 19:05 and 21:27 UTC on November 13, 2026, GitHub Copilot experienced degradation affecting GPT-6.1 Terra, GPT-5.6 Sol, and GPT-6 Luna 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.
-
The upstream provider has made mitigations and we are seeing the affected models begin to recover.
-
We are in contact with the upstream provider and monitoring as they work towards resolution. For customers who are impacted we recommend choosing another model or selecting ‘Auto’ to continue using Copilot.
-
We are experiencing degraded availability for gpt-5.6-sol-fast, gpt-5.6-sol, gpt-6.1-terra, and gpt-6-luna 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.
-
We are investigating reports of degraded performance for Copilot AI Model Providers
Fixed Incident with Pull Requests
Affected: Pull Requests
-
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.
-
We continue to monitor the stability of merge requests.
-
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
-
We’re continuing to investigate and monitor ~1% of merge requests timing out.
-
We’ve taken mitigating action to resolve the problem of merge requests timing out. This issue initially impacted 3% of requests and is now down to less than 1%. We continue to monitor recovery.
-
Pull Requests is experiencing degraded performance. We are continuing to investigate.
-
We’re investigating an issue with Pull Requests where some attempts to merge are timing out.
-
We are investigating reports of degraded availability for Pull Requests
Fixed Disruption with Email Delivery
-
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.
-
We’ve resolved the email-processing impact on our systems and are continuing to monitor. The upstream provider disruption may still cause delays for customers using that provider. Email delivery through other providers is operating normally.
-
We’re monitoring an email disruption related to an upstream provider degradation. Users whose email is hosted by the affected provider may experience delays in message delivery. Email service for users on other providers is currently operating normally. We’ll share updates as we learn more.
-
We are seeing recovery for sign-in, email address verification, and other forms of e-mail communication previously impacted. We will continue to monitor.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
Users may be unable to sign-in, verify e-mail addresses, reset passwords, or receive e-mail notifications due to degradation with an upstream e-mail provider. We will continue to monitor and provide updates.
-
We are seeing disruptions with email delivery for account sign-in and new account sign up. We are investigating.
-
We are investigating reports of impacted performance for some GitHub services.
Fixed Incident with Webhooks API
Affected: Webhooks
-
On November 12, 2026, between 17:59 UTC and 19:05 UTC, the GitHub Webhooks API experienced elevated latency and timeouts. During this time, about 1.23% of Webhooks API requests were slower than normal or timed out, peaking at about 3.63% of requests for a short period. 0.14% of webhook API requests failed during the incident. Webhook deliveries were unaffected. We traced the slow responses to elevated latency in an upstream database service that the Webhooks API depends on. Latency returned to normal at 19:05 UTC, and we continued to monitor until we resolved the incident at 19:33 UTC. We are working with our database provider to understand the cause and are improving our playbooks to detect degradations more quickly.
-
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
-
Webhooks API has traffic has recovered. We will continue to monitor for stability.
-
Webhooks API is experiencing timeouts and errors impacting about 1% of customer traffic. We are working through possible mitigation strategies.
-
We are investigating reports of degraded performance for Webhooks
Fixed Impact across multiple GitHub products including Actions, Pages, and Copilot products.
Affected: Webhooks, Actions, Pages, Copilot
-
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.
-
The backlog of Actions jobs has been fully processed. We’re observing full recovery across all impacted services.
-
We’re seeing recovery across all services and continuing to monitor. The backlog of Actions jobs are being processed. We’ll update when we see full recovery.
-
The degradation affecting Actions, Copilot, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
-
Copilot is experiencing degraded availability. We are continuing to investigate.
-
We’re investigating issues impacting multiple GitHub products including Actions, Pages, and Copilot products.
-
Pages is experiencing degraded availability. We are continuing to investigate.
-
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
Actions is experiencing degraded availability. We are continuing to investigate.
-
We are investigating reports of degraded availability for Pages
Fixed Incident with Webhooks
Affected: Webhooks
-
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.
-
Webhooks is operating normally.
-
We are investigating reports of degraded performance for Webhooks
Fixed Incident with Git Operations and Pull Requests
Affected: Pull Requests, Actions
-
On November 10, 2026, from approximately 15:00 UTC to 17:55 UTC, GitHub experienced degraded performance affecting repository pages, pull requests, and GitHub Actions. Customers may have seen slow or failed page loads and delays processing pull request updates and merges. Some pull requests continued to display an earlier source-branch commit after the broader service degradation ended. GitHub Actions workflows were delayed for approximately 1.8% of events, peaking at about 7% between 16:30 and 16:50 UTC. Delays were typically 1.5 to 3.5 minutes, up to 10 minutes. Approximately 0.09% of pull request events did not start their workflows and needed to be re-triggered. The degradation resulted from overload in the shared infrastructure that supports Git operations. Recent changes increased background processing and the work required to compute pull request merges, adding pressure to the same systems used by customer-facing requests. We mitigated the incident by disabling a recent merge-processing optimization, pausing background analysis, and temporarily limiting lower-priority traffic. The temporary limits also restricted access to commit pages for users who were not signed in. Background processing continued to catch up after service health recovered. We have reduced repeated repository-analysis work and are adding workload-level concurrency controls to better protect customer-facing requests. We are also improving our procedures for safely reducing background load and making pull request synchronization more resilient to temporary failures.
-
We continue to investigate elevated response times for Git operations and pull requests. Actions workflows are recovering. Pull request processing has shown some improvement, but users continue to experience delays and failures. We’re monitoring the impact and working to restore normal service.
-
Actions is operating normally.
-
Pull Requests is experiencing degraded performance. We are continuing to investigate.
-
We continue to investigate elevated response times for Git operations and pull requests. Some pull-request processing and Actions workflows are improving, but delays and failures persist. We're monitoring the impact and working to restore normal service.
-
Actions is experiencing degraded availability. We are continuing to investigate.
-
We're investigating elevated response times for Git operations and pull requests. GitHub Actions workflows that are triggered from Pull Requests are delayed. We're working to mitigate the impact and will share updates as we learn more.
-
Actions and Pull Requests are experiencing degraded availability. We are continuing to investigate.
-
We are investigating reports of degraded performance for Actions and Pull Requests
Fixed Degraded availability for GPT-5.3 Codex and GPT-5.6 models in Copilot
Affected: Copilot, Copilot AI Model Providers
-
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.
-
The issue affecting GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces has been mitigated. We are monitoring the service to ensure stability.
-
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
-
Copilot is operating normally.
-
Copilot AI Model Providers is experiencing degraded availability. We are continuing to investigate.
-
We are experiencing degraded availability for GPT-5.3 Codex, GPT-5.6 Luna, and GPT-5.6 Sol in Copilot products and IDE surfaces due to an issue with an upstream model provider. We recommend choosing another model or selecting Auto to continue using Copilot until the issue is resolved.
-
We are investigating reports of degraded availability for Copilot
Fixed Incident with Actions and Checks API
Affected: Webhooks, Actions, Pages
-
On November 9, 2026, between 18:07 and 18:59 UTC, GitHub Actions experienced degraded performance. During this time, some customers saw workflow runs fail to start, update or report status correctly. An average of 28% of workflow runs were affected, peaking at 65% during the worst period of the incident. Once Actions services recovered, some jobs were left in a state that limited available concurrency until the runs were released. The incident occurred during a planned migration of a core Actions database from GitHub’s datacenter to a new cloud region. After the migration completed, we shifted Actions service traffic to the new region. The volume of requests exceeded the capacity and rate limits configured there, so a portion of requests were rejected and workflow updates failed. Dependent services, including Webhooks, Pages and Copilot code review, saw secondary impact. We mitigated impact by shifting some of the traffic back to the original region, allowing service traffic to remain within the configured limits. We then increased capacity and rate limits in the new region before gradually shifting traffic back. While this was a one-time migration event for this cluster that is now complete, we are improving how we validate capacity and limits before shifting traffic during remaining migrations, including shifting traffic in smaller steps. To address the stuck runs left after the incident, we are improving our ability to detect and mitigate these runs for future cases as well as readying an API to enable customers to address this themselves.
-
The degradation affecting Actions, Pages and Webhooks has been mitigated. We are monitoring to ensure stability.
-
Pages is experiencing degraded performance. We are continuing to investigate.
-
We're investigating elevated errors affecting GitHub Actions and the Checks API. We'll share another update as we learn more.
-
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
Actions is experiencing degraded availability. We are continuing to investigate.
-
We are investigating reports of degraded availability for Actions
Fixed Incident with Webhooks and Actions
Affected: Webhooks, Actions
-
On November 9, 2026, from 09:23 to 11:40 UTC, one of our job queue clusters was degraded, delaying webhook deliveries, Actions workflow runs, and Dependabot and dependency graph updates. Until mitigation at 10:37 UTC, an average of 26% of webhook deliveries were delayed, peaking at 30%, and the backlog cleared by 11:40 UTC. Some deliveries were delayed by up to 3.5 hours, and delays for a small share began as early as 01:00 UTC. Actions skips events older than 30 minutes, so some workflow runs did not start. The incident was caused by a degraded host that had slowed one of the cluster's Kafka brokers since November 7. The broker stopped reporting the metrics our alerts rely on, so we did not identify it until it stalled the cluster on November 9. We mitigated the incident by removing the broker from service. We have since added an alert that pages us within 30 minutes when a host slows a broker this way, so we can remove the broker before it affects customers.
-
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
-
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
Webhooks is experiencing degraded availability. We are continuing to investigate.
-
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
We've applied a mitigation and are monitoring for recovery.
-
We're investigating delays in Actions runs start times and webhook deliveries.
-
We are investigating reports of degraded performance for Actions and Webhooks
Fixed Increased timeouts due to surge in anonymous users
-
On November 9, 2026, GitHub.com experienced intermittent timeouts between approximately 05:10 and 08:15 UTC. Across that full window, 6.5% of recorded requests to github.com timed out, with a five-minute peak of 13.9% between 07:40 and 07:45 UTC. Release downloads were more affected: 38.5% of recorded requests timed out, peaking at 76% during that same five-minute interval. The two main error waves lasted about two hours and ten minutes in total, with recovery between them. The errors affected repository browsing and disrupted some CI workflows and Copilot code review jobs. Contrary to our earlier updates, follow-up analysis confirmed at least 6,236 authenticated requests that timed out, affecting activity feeds, access to uploaded attachments and repository archive downloads. Errors occurred during elevated traffic to our web infrastructure that handles unauthenticated requests. Impact was mitigated when traffic causing pressure on this system was alleviated. Our follow-up work focuses on improving capacity monitoring, traffic prioritization improvements, and automated protection against traffic spikes.
-
We are resolving this incident as error rates have remained low and we have prepared additional protections.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
Error rates have declined again, and we’re preparing targeted traffic controls while monitoring for a recurrence. Logged-in users and authenticated requests have not been affected.
-
We are continuing to observe high rates of 504 errors for anonymous requests. We are continuing to work on mitigation. Logged-in users and authenticated requests are unaffected.
-
We have observed a repeated increase in 504 errors for anonymous and unauthenticated traffic, including users who are not logged in and release downloads. We are continuing to investigate and apply mitigations.
-
The problem with anonymous traffic receiving 504 status codes has been mitigated. We are continuing to observe for an abundance of caution.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
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.
-
We are investigating reports of impacted performance for some GitHub services.
Fixed Increase in timeouts for some unauthenticated users
Affected: API Requests
-
On November 8, 2026, between 08:43 and 12:29 UTC, unauthenticated requests to github.com and the GitHub REST API experienced elevated error rates. During this period, 11.3% of unauthenticated requests and 46.1% of release asset download requests failed. Authenticated requests were largely unaffected.Initial errors occurred in a backend service handling unauthenticated web traffic. A subsequent traffic spike caused high CPU utilization on servers in our caching layer. Some servers remained unhealthy after the spike ended, prolonging the disruption. We restored service by restarting caching software and rebooting affected servers.We are improving monitoring to detect these failures sooner, investigating why affected servers did not recover automatically, and reviewing caching behavior to better protect backend services during failures.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
-
We've identified a problematic component and are working to redeploy it.
-
API Requests is experiencing degraded performance. We are continuing to investigate.
-
We are continuing to investigate degraded performance primarily for unauthenticated users.
-
We are investigating reports of impacted performance for some GitHub services.
Fixed Degraded performance for multiple GitHub services
Affected: Git Operations, Issues, Actions, Pages
-
On November 5, 2026, between 23:21 and approximately 23:26 UTC, several GitHub services experienced elevated errors, including Git operations, Issues, Actions, authentication, and API requests. Customers may have encountered failed requests and Git pushes, and some Actions workflow runs were delayed. This incident was caused by a bug in our database failover automation during planned maintenance. The automation stopped before completing the switch to a replacement database primary, leaving the existing primary unable to accept writes. We mitigated the disruption by restoring writes on the original primary. We subsequently completed the maintenance and monitored services to confirm recovery. We are fixing the automation bug and strengthening our pre-maintenance checks and recovery procedures to prevent similar disruptions and restore service more quickly if a failure occurs.
-
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.
-
Git Operations is operating normally.
-
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.
-
The degradation affecting Actions, Issues and Pages has been mitigated. We are monitoring to ensure stability.
-
Issues is experiencing degraded performance. We are continuing to investigate.
-
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.
-
We are investigating reports of degraded performance for Actions and Pages
Fixed Incident with Actions
Affected: Actions
-
Between 16:39 and 16:57 UTC on November 5, 2026, some customers experienced failures starting workflow runs in GitHub Actions and Checks, and some in-progress runs failed. At peak, about 3% of workflow runs failed to queue, and roughly 0.21% of in-progress runs failed.The cause was resource exhaustion in a database service that stores Actions Checks data. Bursts of highly concurrent, large read requests put the service under memory pressure, which caused it to stall and reject requests.We mitigated the incident by failing over the affected database host. To prevent a recurrence, we have increased memory capacity across the affected database fleet. We will also be limiting concurrency of large queries to prevent heavy read traffic from causing a broad failure of critical workflows.
-
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
Some GitHub Actions workflow runs may experience delays or errors when starting. We’re investigating and preparing a mitigation.
-
We are investigating reports of degraded performance for Actions
Fixed Incident with Actions
Affected: Actions
-
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/xr3myzj7ms51
-
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
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.
-
We are investigating reports of degraded availability for Actions
Fixed Incident with Actions and Pages
Affected: Webhooks, Actions, Pages
-
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.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
-
The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
-
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.
-
Actions is experiencing degraded availability. We are continuing to investigate.
-
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
We are investigating reports of issues with Actions and Pages. We will continue to keep users updated on progress towards mitigation.
-
We are investigating reports of degraded performance for Actions and Pages
Fixed Incident with Pull Requests, Git Operations and Issues
Affected: Git Operations, API Requests, Issues, Pull Requests, Actions
-
n November 4, 2026, between 09:35 UTC and 11:43 UTC, customers experienced intermittent errors and timeouts across GitHub.com, primarily on actions that write data. At peak, about 20% of pull request write operations (such as merging, commenting, and reviewing) failed, along with about 10% of issue creates and edits and 10–15% of project item edits. Git pushes over SSH, REST and GraphQL API requests, code scanning uploads, releases, and package operations were also affected, and about 1% of Actions runs were delayed by more than five minutes or failed to start. Overall, nearly 4% of all requests to GitHub.com failed at the worst point. Reads were largely unaffected, and retrying a failed action a short time later usually succeeded.The incident was triggered by a burst of concurrent updates to the same database record, which tied up all available connections to one of our primary databases. Although that contention cleared, the backlog of waiting requests kept our database connection layer overloaded, and it did not recover on its own. We mitigated the incident by failing over to a new primary database host. Most services recovered by 11:31 UTC, and Actions recovered by 11:43 UTC.Since the incident, we have disabled the code path that triggered the contention, increased the processing capacity of our database connection layer by 50%, and added alerting to detect this type of overload earlier. We are also improving our procedures so we can fail over sooner in similar situations.
-
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
-
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.
-
API Requests is experiencing degraded performance. We are continuing to investigate.
-
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.
-
Pull Requests is experiencing degraded availability. We are continuing to investigate.
-
Actions is experiencing degraded performance. We are continuing to investigate.
-
We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests
Fixed Increased task-related errors for Copilot Mission Control
-
On November 4, 2026, between approximately 03:40 UTC and 10:01 UTC, some Copilot agent users experienced errors listing and creating agent tasks. On average, 1.22% of requests were failed, with a peak of 2.68% over a ten-minute interval.The issue occurred when increased task-list traffic and expensive queries exhausted shared database capacity. We mitigated the broader impact by disabling a client experiment and temporarily restricting task-list requests from the affected client. Task-list requests remained restricted after the wider service recovered; we removed the blanket restriction on November 6 and continued a gradual rollout.We’ve since improved task-list queries, moved rate limiting to separate infrastructure and added capacity monitoring. We’re continuing to reduce unnecessary client requests and validate capacity before expanding the rollout to reduce the chance of recurrence.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
We're continuing to see recovery as rollout continues
-
We've identified the issue with a specific client version and are deploying a mitigation. We are already seeing partial recovery.
-
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.
-
We are investigating reports of impacted performance for some GitHub services.
Fixed Incident with Git Operations
Affected: Git Operations
-
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.
-
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
-
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.
-
Our mitigation is rolled out and customers should start seeing improvements to Git Operations. We will continue to provide updates on mitigation status.
-
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.
-
We are investigating reports of degraded performance for Git Operations
Fixed Incident with API, Git, and Copilot requests
Affected: API Requests, Issues, Copilot
-
On November 3, 2026, between 12:34 and 13:51 UTC, some users experienced authentication failures and errors with the REST and GraphQL APIs, pull requests, Issues, and GitHub Copilot. On average, the error rate was 0.46% and peaked at 0.98% of API requests. Copilot API errors averaged 2.0% and peaked at 3.1%.This was caused by a bug in our process for replacing control-plane servers in one of our compute clusters. When a replacement server did not receive a timely response from the existing cluster, it incorrectly created a separate cluster. This stopped traffic from reaching much of the cluster's capacity and overloaded the authentication servers that were still handling requests.We mitigated the incident by removing the incorrectly configured server.We are also fixing the replacement logic and adding safeguards to prevent servers in this state from serving traffic.
-
The degradation has been mitigated. We are monitoring to ensure stability.
-
API Requests is operating normally.
-
The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
-
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
-
Issues is experiencing degraded performance. We are continuing to investigate.
-
We are investigating reports of degraded performance for Copilot
Fixed Elevated errors on GPT-5.4 Nano
Affected: Copilot AI Model Providers
-
On November 2, 2026, between 17:30 and 18:10 UTC, background tasks such as generating commit messages in GitHub Copilot were degraded. This was due to elevated errors with GPT-5.4 nano, a utility model. The elevated errors originated from an issue with an upstream model provider. No models that users could pick in the model picker were impacted. Service recovered when the upstream provider released a fix. We are working with the provider to understand the root cause and prevent similar issues from occurring going forward.
-
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
-
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.
-
We are investigating reports of elevated errors on GPT-5.4 Nano
-
We are investigating reports of degraded performance for Copilot AI Model Providers
Frequently asked questions
Is GitHub down right now?
No. As of 20:00 UTC on 19 November 2026, GitHub is working normally. If it is not working for you, try the checklist on this page.
When was the last GitHub outage?
The last incident was "Disruption with some GitHub services" on 19 November 2026, fixed after 1 hour 11 minutes.
Why is GitHub not working for me?
If this page shows no problem and few readers report one, the cause is usually local: your connection, a VPN or firewall, an outdated app or a sign-in problem. Work through the checklist above, then report it here so other readers can see it.
Unofficial status page. Teczpert is not affiliated with GitHub. Status data comes from the official status page and is checked every 15 minutes; reports come from readers. Official source: www.githubstatus.com.