GitHub
Apps and SaaS. Source: GitHub status page.
- Incidents, last 90 days
- 64
- Median to mitigation
- 47m
- Median to resolution
- 1h 10m
- p95 to resolution
- 10h 28m
- Naming an upstream provider
- 6%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 17 |
| A provider or third-party service this vendor depends on failed | 16 |
| The text does not say enough to tell | 7 |
| Orchestration, control plane, service discovery or load balancing failed | 5 |
| Network, DNS, routing or connectivity failure | 5 |
| Login, tokens, certificates or credentials failed | 4 |
| Traffic surge or denial-of-service attack | 2 |
| A schema or data migration caused the failure | 2 |
| A code release introduced the failure | 2 |
| A configuration change caused the failure | 1 |
| Hardware, power, cooling or another physical failure | 1 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 1 |
| CDN or edge layer failed or served bad content | 1 |
Tagged by deepseek/deepseek-v4.1-flash from each incident's updates. See the methodology.
Incidents per month
All recorded incidents
Delays for Pull Requests and Webhook deliveries
Affected: Webhooks, Pull Requests, Actions
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
-
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these...
-
investigating
We continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.
-
investigating
Audit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.
-
investigating
Audit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will...
-
investigating
Pull Requests is operating normally.
-
investigating
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...
-
investigating
Actions and Webhooks are operating normally.
-
investigating
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.
-
investigating
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.
-
investigating
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.
-
investigating
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...
-
investigating
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.
-
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.
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded availability for GitHub Actions, GitHub Pages and Webhooks
Affected: Webhooks, Actions, Pages
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Actions and Pages
-
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
investigating
We’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks. Customers may experience delays in workflow processing, site builds and webhook delivery.
-
investigating
We’re seeing recovery following mitigation and are continuing to monitor. Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.
-
monitoring
Actions, Pages and Webhooks are operating normally.
-
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.
Excerpts are shortened. Read the full incident on GitHub's status page.
CCA Automations are delayed when starting an Automation
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
CCA Automations are experiencing delays when users start an Automation
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
resolved
We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Actions workflow run logs delayed
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
resolved
On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions, Pull Requests and Issues
Affected: Issues, Pull Requests, Actions
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
-
investigating
Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.
-
investigating
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
-
investigating
Pull Requests is operating normally.
-
investigating
Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.
-
investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
-
investigating
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
investigating
We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
-
investigating
We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
-
investigating
Notifications have resumed but will continue to be delayed as we work through a backlog.
-
investigating
Web and email notifications continue to be delayed as we work through a backlog of notifications.
-
investigating
Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
-
resolved
On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. The...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Git Operations, Issues, Actions and Pull Requests
Affected: Git Operations, Issues, Pull Requests, Actions
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
-
investigating
We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7....
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
monitoring
All systems have recovered. We have applied mitigations and do not anticipate another recurrence.
-
resolved
On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures:...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Git Operations, Pull Requests and Actions
Affected: Git Operations, Webhooks, Issues, Pull Requests, Actions
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
-
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
-
investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
-
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
-
investigating
We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
-
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
-
investigating
Git Operations is operating normally.
-
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
investigating
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
-
investigating
Actions is operating normally.
-
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
-
investigating
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
-
investigating
The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
monitoring
We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
-
monitoring
Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
-
resolved
On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data...
Excerpts are shortened. Read the full incident on GitHub's status page.
Several services are degraded
Affected: Webhooks, Pull Requests
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Pull Requests and Webhooks
-
investigating
Webhooks is operating normally.
-
investigating
Pull Requests is operating normally.
-
investigating
A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
investigating
All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
-
investigating
We are working towards a mitigation that will allow us to resume processing enterprise migrations.
-
investigating
We are deploying a mitigation and plan to resume migrations shortly thereafter
-
resolved
On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
-
resolved
On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
Affected: Actions, Pages
Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Actions
-
investigating
We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
-
investigating
We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
-
investigating
We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
-
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
-
investigating
In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
-
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
-
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
-
investigating
We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including...
-
investigating
Actions is operating normally.
-
investigating
Pages is operating normally.
-
resolved
On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. During...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions Job Delays
Affected: Actions
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Names an upstream provider: Azure.
-
investigating
We are investigating reports of degraded performance for Actions
-
investigating
We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.
-
investigating
Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.
-
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.
-
investigating
We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.
-
investigating
We are currently applying a mitigation and anticipate recovery within thirty minutes.
-
investigating
GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.
-
resolved
On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated request latency
Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
resolved
On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Actions workflow run failures after deployment gate approvals
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
resolved
On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot Code Review is unable to complete reviews
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
Revert of the impacted change is in flight, expect full recovery once the deployment is done.
-
investigating
Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.
-
resolved
On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with billing information updates
Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.
-
investigating
We have identified the problem and are actively working on mitigation.
-
investigating
We are continuing to work on mitigation. We will post another update in approximately one hour.
-
investigating
We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
resolved
Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident across several services
Affected: API Requests
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Names an upstream provider: Azure.
-
investigating
We are investigating reports of degraded performance for API Requests
-
investigating
Database replicas have detached. We're working to restore the database replicas. Users may experience issues beyond creating organizations and a degraded experience with the GitHub API and Projects.
-
investigating
Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
-
investigating
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
-
investigating
We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
-
investigating
Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.
-
investigating
Updates to issue labels may be delayed in being reflected in Projects by about ~10 minutes. We have added some capacity to work through the backlog more quickly, but it'll likely be a few hours to complete processing the full backlog of messages. All other services are available.
-
investigating
We will post another update in approximately one hour to share our progress.
-
investigating
Continuing to investigate the lag that may be experienced in issue labels being accurately reflected in Projects. We are working on alternate solutions to process the backlog of label updates.
-
investigating
We are preparing to deploy a change that will mitigate the impact.
-
investigating
Updates to issue labels may be delayed in being reflected in Projects. We are continuing to deploy a change that will accelerate processing of the backlog of label updates. All other services are available. We will provide another update within the next hour.
-
investigating
We've deployed a change intended to accelerate processing of the backlog of issue label updates in Projects. A sizable backlog still remains and we continue working through it. All other services are operating normally. We will provide another update within the next hour.
-
investigating
We are continuing to process the backlog of issue label updates for Projects. Users may still see delays before label changes are reflected in Projects. All other services are operating normally.
-
investigating
We are continuing to process the backlog of issue label updates for Projects. Label changes may still be delayed. All other services are operating normally.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
resolved
Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
Affected: Pull Requests
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Pull Requests
-
monitoring
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
-
monitoring
A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
-
resolved
On September 20, 2026, between 21:46 and 22:24 UTC the Pull Requests service was degraded and pull request merge and test-merge commits were created late, with delays reaching approximately four minutes at peak. Merge commits were delayed rather than lost. Because some Actions...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated rate of errors for OpenAI models provided by Copilot
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Names an upstream provider: OpenAI.
-
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
-
monitoring
We are experiencing degraded availability for GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-6 Astra, GPT-5.3-Codex in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. The provider is working to mitigate the problem and we are monitoring...
-
resolved
Between 20:26 and 21:17 UTC on September 17, 2026, GitHub Copilot experienced degradation affecting several GPT models, including GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-5.3-Codex, and GPT-6 Astra. Users encountered elevated error rates when using these models. The...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degradation with Gemini 3.8 Flash
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded availability for Copilot AI Model Providers
-
investigating
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
-
investigating
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
-
monitoring
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
-
resolved
On September 16, 2026, between 04:40 and 11:45 UTC, the Gemini 3.8 Flash model in GitHub Copilot experienced degraded availability. Requests to this model failed at an average rate of 6.4%, and the impact was highest during peak traffic hours. Other Copilot models were not...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
resolved
On September 15, 2026 between 15:30 and 20:00 UTC, some Copilot code reviews on pull requests failed to complete. The cause was increased latency in an internal caching service that GitHub Copilot Code Review relies on to coordinate its review jobs. This caused a timeout in lock...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
monitoring
We are investigating degraded availability for Claude Fable 5.1, affecting some Copilot products and integrated development environments. The issue is caused by a problem with our upstream model provider. Customers can use another model or select Auto while we investigate.
-
investigating
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
-
investigating
We continue to investigate intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customers can use another model or select Auto while we monitor the situation.
-
investigating
We continue to monitor intermittent errors affecting Claude Fable 5.1 in some Copilot products and integrated development environments. Customer-facing metrics have recovered, and we are awaiting confirmation from our upstream provider that the issue will not recur. Customers...
-
investigating
The issues with our upstream model provider have been resolved, and Claude Fable 5.1 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.
-
resolved
On September 15, 2026, between 05:45 and 09:50 UTC, the Claude Fable 5.1 model in GitHub Copilot experienced intermittently degraded availability, with an average error rate of 2.8%. During brief recurring 15 minute periods that recurred every ~45 minutes, availability for...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions Larger Runner Jobs for some customers may be slow to start
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
resolved
On September 14, 2026, between 16:10 and 19:01 UTC, some customers using GitHub Actions larger runners experienced longer-than-normal wait times for jobs to start. During this period, 5.7% of larger-runner jobs were affected. A routine expansion of our compute capacity exposed a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with several GitHub Services
Affected: API Requests, Issues, Pull Requests, Actions, Pages
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded availability for API Requests, Issues, Pages and Pull Requests
-
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
-
investigating
We're seeing increased database replication delays on collab which is causing increased error rates in authorization endpoints and follow-on increased error rates across the system - we are investigating
-
investigating
We have reduced load on this cluster with internal load-shedding and are seeing signs of recovery but continue to monitor
-
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
-
resolved
On September 13, 2026, between 08:43 and 10:44 UTC, GitHub experienced degraded availability across approximately 28 services, including Issues, Pull Requests, Actions, Codespaces, Pages, Notifications, Code Scanning, Git LFS, and new account signup. At peak, 8.8% of requests to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degradation in repos contents API
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
resolved
On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC. The cause was a capacity change that spread one of our clusters across additional...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Copilot Code Review
Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
Some users may be experiencing failures when using Copilot code review. We have identified the root cause and are working on a mitigation.
-
investigating
We are applying the mitigation and expect recovery within approximately 30 minutes.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
resolved
On September 4, 2026, between 20:04 and 22:26 UTC, GitHub Copilot code review experienced an increased failure rate. Affected pull request reviews failed to complete or post review comments. The incident was caused by a change to the service’s authentication permissions that...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Grok Copilot AI Model Provider
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
-
investigating
We are experiencing degraded availability for the Grok 4.6 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.
-
investigating
The Grok 4.5 model has degraded availability as well. We are working with the upstream provider to resolve the issue.
-
investigating
The issues with our upstream model provider have been resolved, and Grok models are once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.
-
resolved
Between 13:22 and 17:11 UTC on September 03, 2026, GitHub Copilot experienced degradation affecting several Grok models, including Grok 4.5 and Grok 4.6. Users encountered elevated error rates, but other models were not affected. The degradation was caused by an issue with an...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delays in commit processing
Affected: Pull Requests
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Pull Requests
-
investigating
Diffs in the PR view may be stale for several minutes. We are investigating and scaling up resources.
-
investigating
Time to update pull request diffs have improved to normal thresholds.
-
resolved
On September 1, 2026, between approximately 14:01 and 16:01 UTC, updates in response to pushes were delayed, temporarily showing stale diffs. The median time to refresh a diff after a push rose from the normal level of about 3 seconds to over 2 minutes at the peak, and more than...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated rate of errors for OpenAI models provided by Copilot
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Names an upstream provider: OpenAI.
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
-
investigating
Copilot is experiencing a higher rate of errors for OpenAI models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4, and the gpt-5.6 family of models. Other models are not impacted.
-
investigating
One of our model providers has confirmed an incident on their end. We have provided them details to help identify the issue. We are starting to see recovery.
-
monitoring
The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
-
monitoring
The issues with our upstream model provider have been resolved, and gpt-5.3-codex, gpt-5.4-mini, gpt-5.4-nano, gpt-5.5, and the gpt-5.6 family of models are once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation...
-
resolved
Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot AI Model Providers
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded availability for Copilot AI Model Providers
-
investigating
We are experiencing degraded availability for the Kimi K3 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 'Auto' to continue using...
-
investigating
Copilot AI Model Providers is experiencing degraded performance. We are continuing to investigate.
-
investigating
The issues with our upstream model provider have been mitigated, and Kimi K3 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability.
-
resolved
On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. The issue was...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with GitHub Billing
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
We are currently investigating increased errors with billing services. Customers may observe failed billing budget page loads, and users of the Copilot CLI may observe failures starting or continuing sessions.
-
investigating
We've applied a mitigation to unblock Copilot usage and have observed recovery for this particular impact. We're continuing to investigate and apply mitigations for the billing page disruption while monitoring to ensure Copilot remains recovered.
-
investigating
We are continuing to monitor the mitigation that we have applied for the billing page disruption.
-
investigating
Our mitigation is still holding as we continue to investigate to find the root cause.
-
investigating
Our mitigation continues to hold, and service conditions remain stable. We are continuing to investigate the concentrated workload responsible for the issue and are preparing additional preventative improvements. We have not identified a material change in customer impact since...
-
investigating
No material change since the previous update. Service conditions remain stable following the mitigation, and we have not observed any further customer impact. We are actively monitoring the service while implementing targeted fixes to address the underlying root cause.
-
resolved
On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions and Pull Requests
Affected: Pull Requests, Actions
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Actions and Pull Requests
-
investigating
We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide...
-
investigating
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
-
investigating
We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.
-
monitoring
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
-
resolved
On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
Affected: Actions, Pages
Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded availability for Actions
-
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
-
investigating
We've identified an issue with a database primary and are failing over to a replica immediately
-
investigating
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
-
investigating
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.
-
investigating
Pages is operating normally.
-
investigating
We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.
-
investigating
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.
-
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
monitoring
All inbound queues have recovered and Actions is operating as expected. 3.7% of jobs assigned to larger runners during the early stage of this incident are stuck waiting for runner assignment. Those will be canceled within the hour. Other runners are successfully processing all...
-
resolved
On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
resolved
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/y1t7p9fzrlj2
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions delays in starting runs
Affected: Actions
Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Actions
-
investigating
Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.
-
monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
-
resolved
On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright. The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated errors on Fable 5 due to upstream provider
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded availability for Copilot AI Model Providers
-
investigating
We are experiencing degraded availability for the Fable model in Copilot products and IDE surfaces. This is due to an issue with the upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using...
-
resolved
On August 24th, 2026, between approximately 06:35 and 07:25 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates when using Claude Fable 5, with requests sometimes...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded Git Operations over SSH
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On August 21, 2026, between 14:00 and 14:07 UTC, dotcom Git operations over SSH were degraded. Successful Git operations over SSH fell by more than 95% for during the peak impact window, making clone, fetch, or push over SSH effectively unavailable to most users for...
Excerpts are shortened. Read the full incident on GitHub's status page.
Intermittent failures creating agent tasks
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
Users may experience delays when starting tasks using Copilot Cloud Agent. We are actively investigating the issue and will provide updates as we learn more.
-
investigating
We have identified the problematic component and are working to fail over to a healthy instance. Further updates will be provided as we perform mitigations.
-
investigating
We are experiencing issues with Copilot Cloud Agent tasks, resulting in newly started tasks not properly displaying on-going progress. These Copilot Cloud Agent tasks are still being completed correctly but lack proper visibility. We are actively investigating the issue and will...
-
investigating
Users are experiencing delays when starting tasks using Copilot Cloud Agent and are not be able to see the status of these tasks. Copilot Cloud Agent tasks are still being completed. We have identified the cause of the issue and are putting mitigations in place to return service...
-
investigating
We are seeing signs of recovery for Copilot Cloud Agent task status visibility, but this recovery is slower than anticipated. We are pursuing additional mitigating measures to accelerate recovery.
-
investigating
We are observing gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact.
-
investigating
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and are continuing to monitor the impact.
-
investigating
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility, with session output delayed by approximately 1 hour. We have taken additional steps to accelerate the recovery and expect this to take effect within the next hour.
-
investigating
We are continuing to observe gradual recovery for Copilot Cloud Agent task status visibility. Session output continues to be delayed by approximately 1 hour as our remediation steps take effect.
-
investigating
We are seeing gradual recovery in Copilot Cloud Agent task status visibility as we deploy a fix for the root cause. Session output remains delayed by approximately one hour while remediation continues.
-
resolved
Between 13:57 UTC on August 20 and 00:37 UTC on August 21, 2026, some users of the Copilot Cloud Agent experienced delays of up to 60 to 90 minutes in seeing the status and results of their agent tasks. The agent tasks themselves continued to run and complete during this time;...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
resolved
On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to run jobs on Actions Larger Runners and were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. These issues were caused by failures in backend requests resolving...
Excerpts are shortened. Read the full incident on GitHub's status page.
Intermittent failures in runner group and runner-related permissions pages
Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
monitoring
We are investigating reports of failure to load runner groups and runner-related permissions for customers using larger runners.
-
monitoring
We have identified the source of a communication issue between Actions services and are working toward mitigation. Customers may experience failure to load runner groups and runner-related permissions issues when using Larger Runners.
-
monitoring
We have applied a mitigation and are seeing recovery signals. We will continue monitoring recovery and providing updates.
-
resolved
On August 18, 2026, between 05:02 UTC and 11:30 UTC, customers were unable to view or manage Actions Runners and Runner Groups through the GitHub UI and API. The issue was caused by failures in backend requests reading runner and runner group data. The failures were caused by an...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with GitHub.com
Affected: Git Operations, Webhooks, API Requests, Issues, Pull Requests, Actions, Pages, Copilot
Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
- GitBook: GitHub outage affecting Git Sync
- CircleCI: GitHub Incidents impacting CircleCI functionality
- Pulumi: GitHub services failing
- v0: Github service degraded
- Cursor: GitHub degradation affecting some Cursor services — Automations, Cloud Agents, Codebase
- Snyk: GitHub Integration Degradation
- Ona (Gitpod): GitHub incident is causing elevated error rate for environments
- dbt Cloud: Git Failures in dbt Platform
- Graphite: GitHub is experiencing an outage. Some actions may be impacted.
- ClickHouse Cloud: Provisioning of new CDC pipes for Postgres might be delayed or failing
- HeyGen: Degraded Service
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
API Requests is experiencing degraded performance. We are continuing to investigate.
-
investigating
Actions is experiencing degraded performance. We are continuing to investigate.
-
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are seeing an approximate 20% error rate across numerous experiences including Pull Requests, Issues, and others. Investigations are currently under way and we will be posting updates as they become available
-
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
-
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. Investigations are on-going into the root cause, and updates will continue to be provided...
-
investigating
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. Investigations are...
-
investigating
Copilot is experiencing degraded availability. We are continuing to investigate.
-
investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
-
investigating
Issues is experiencing degraded availability. We are continuing to investigate.
-
investigating
Pull Requests is experiencing degraded availability. We are continuing to investigate.
-
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
-
investigating
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently...
-
investigating
Webhooks is experiencing degraded availability. We are continuing to investigate.
-
investigating
API Requests is experiencing degraded availability. We are continuing to investigate.
-
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
-
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
-
investigating
Webhooks is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are currently...
-
investigating
We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. SAML and OIDC authentication, SCIM, and Team Sync are also impacted. We are still working...
-
investigating
We identified the problematic component and have taken corrective actions. There are strong signs of recovery but we are still working to completely restore service, with error rates still remaining slightly elevated. We will post further updates as recovery continues.
-
investigating
The degradation affecting API Requests, Actions, Git Operations, Issues, Pages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
-
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
-
investigating
We identified the problematic component and have taken corrective actions, but we are seeing residual impact across numerous services. We are continuing to apply additional mitigations and investigate the remaining impact.
-
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
-
investigating
We identified the problematic component and have taken corrective actions, but we are seeing residual impact in the form of sporadic authentication failures. We are continuing to apply additional mitigations and investigate the remaining impact.
-
investigating
The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.
-
investigating
API Requests is experiencing degraded availability. We are continuing to investigate.
-
investigating
API Requests is operating normally.
-
investigating
We are continuing to investigate sporadic authentication failures. We have partially disabled authentication token retries and have seen improvement, and we are monitoring impact before fully applying this mitigation.
-
investigating
We are continuing to investigate sporadic failures affecting Copilot authentication in some applications. Copilot usage via the GitHub CLI and GitHub App are unaffected.
-
investigating
Issues is operating normally.
-
investigating
We are continuing to apply mitigations to address sporadic Copilot authentication failures in some applications. We expect full recovery within the next 30 minutes. Copilot usage via the GitHub CLI and GitHub App are unaffected.
-
resolved
On August 17, 2026, from 13:28–21:15 UTC (7h 47m), GitHub.com experienced elevated errors and latency across Issues, Pull Requests, APIs, Actions, and Copilot. At peak, web/API error rates were approximately 20%, while archive and raw-content downloads reached approximately 50%....
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with GHEC Team Sync
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
GHEC Team Sync is currently degraded for enterprises with personal accounts, causing delays when syncing teams to IdP groups. We have identified the cause of the delays and are working on a mitigation. We will provide an update on our progress at 20:00 UTC.
-
investigating
We have deployed a mitigation. At this time GHEC Team Sync has recovered for enterprises with personal accounts. Teams syncing to IdP groups have returned to their normal cadence.
-
resolved
On August 13, 2026, from 15:31:21 UTC to 18:27:55 UTC, GitHub Enterprise Cloud team synchronization was degraded for enterprises using personal accounts. Organization teams experienced delays of up to 3 to 13 hours (median 8 hours) when syncing with IdP groups, resulting in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
Affected: Git Operations, Webhooks, Issues, Pull Requests, Packages
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Webhooks
-
investigating
Pull Requests is experiencing degraded performance. We are continuing to investigate.
-
investigating
Issues is experiencing degraded performance. We are continuing to investigate.
-
investigating
Git Operations is experiencing degraded performance. We are continuing to investigate.
-
investigating
Packages is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are currently investigating a brief degradation of service for Git operations (specifically pushes), issues, pull requests, package registry, and webhooks between 14:32 and 14:46 UTC. We have identified the source of the degradation and are investigating mitigation strategies...
-
monitoring
The degradation affecting Git Operations, Issues, Packages, Pull Requests and Webhooks has been mitigated. We are monitoring to ensure stability.
-
monitoring
We have temporarily disabled a background job which caused the impact. At this time the impact is fully mitigated.
-
resolved
Between 14:24 and 14:53 UTC on 13 August 2026, a routine background job to delete an organization overwhelmed a key shared database, causing multiple GitHub services to briefly return elevated errors and slower responses. Most affected was the webhook management API, with...
Excerpts are shortened. Read the full incident on GitHub's status page.
Errors with the Fable 5 Model in Copilot
Affected: Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Copilot AI Model Providers
-
investigating
We are experiencing degraded availability for the Fable 5 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 'Auto' to continue using...
-
investigating
We are seeing modest recovery, but are still experiencing degraded availability for the Fable 5 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...
-
investigating
The issues with our upstream model provider have been resolved, and Fable 5 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.
-
resolved
On August 13th, 2026, between approximately 14:06 and 15:47 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider. Users encountered elevated error rates, peaking at 43% and averaging 12%. Users who selected...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Login and Release Asset downloads
Failure mode: Traffic surge or denial-of-service attack. Root cause: An external attack. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
- HashiCorp: Issues When Downloading Terraform Providers
- Socket: GitHub Service Disruption Impacting Socket Firewall Downloads
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
We are investigating issues with Login and when downloading Release Assets. We will continue to keep users updated on progress towards mitigation.
-
investigating
We have identified the root cause and are working on mitigation. Errors on the login page and downloading release assets have decreased, but we are not fully mitigated. We will continue to provide updates.
-
resolved
On August 12 and 13, 2026, some anonymous (logged-out) requests to github.com experienced HTTP 5xx errors when loading pages like the sign-in page, and when downloading release assets, due to an unusual traffic pattern that repeatedly overloaded a part of our infrastructure that...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests and Issues
Affected: Issues, Pull Requests
Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
investigating
We are investigating reports of degraded performance for Issues and Pull Requests
-
investigating
We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database...
-
monitoring
The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
-
monitoring
We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the...
-
resolved
Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with GraphQL API Requests
Affected: API Requests
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for API Requests
-
investigating
We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information
-
investigating
We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident.
-
monitoring
The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
-
monitoring
We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident.
-
resolved
On August 11, 2026, between 14:00 UTC and 16:00 UTC the GraphQL API service was degraded and customers in saw higher than normal timeouts. On average, the timeout rate was 0.06% and peaked at 0.14% of requests routing to the service. This was due to increased utilization at one...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Copilot for access to some models
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
monitoring
We are currently investigating reports of some Copilot users experiencing issues accessing certain models. Affected users may see errors or degraded functionality when attempting to use specific models. We are actively working on a fix and will provide updates as we have more...
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
monitoring
The issue has been mitigated across all affected environments. We are currently deploying on a fix to prevent reoccurrence. We will provide another update once the fix has been deployed.
-
monitoring
We have deployed and validated the fix to prevent immediate reoccurrence. We will be performing additional work to limit these kinds of failures in the future.
-
resolved
On August 10, 2026, between 19:48 UTC and 20:49 UTC, GitHub Copilot users saw an incomplete list of available models. During this window, the service could return as few as one model instead of the full catalog. Requests that tried to use a model missing from that shortened list...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with creation of fine grained personal access tokens
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
investigating
We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
monitoring
We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery.
-
resolved
On August 10, 2026, between 17:16 and 18:21 UTC, users were unable to create new fine-grained personal access tokens (FG PAT) through the GitHub website. When a user submitted the FG PAT creation form, they were returned to the FG PAT list without an error message and no FG PAT...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
Affected: Actions, Pages
Failure mode: A code release introduced the failure. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Actions
-
investigating
Actions is experiencing degraded availability. We are continuing to investigate.
-
investigating
We are investigating errors affecting GitHub Actions. Some workflow runs are failing to start or failing partway through, and some requests to the Actions REST API are returning errors. Some customers may also see unexpected rate limiting in their workflows. Engineers have...
-
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
-
investigating
Pages is operating normally.
-
investigating
Pages is experiencing degraded performance. We are continuing to investigate.
-
investigating
We are continuing to work on the issue affecting GitHub Actions. Some workflow runs are still delayed or failing to complete, and some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may also see failures. Engineers...
-
investigating
Actions and Pages are experiencing degraded availability. We are continuing to investigate.
-
investigating
We are continuing to work on the issue affecting GitHub Actions. Workflow runs are still failing or delayed in starting, and some queued jobs may time out. Some requests to the Actions API are returning errors. Customers running migrations with GitHub Enterprise Importer may see...
-
investigating
We are continuing to work on an issue affecting multiple GitHub services. Workflow runs are failing or delayed in starting, and some queued jobs may time out. Copilot code review, Copilot coding agent, hosted runners, and migrations using GitHub Enterprise Importer might also...
-
investigating
We are continuing to work on an issue affecting multiple GitHub services. Workflow runs are still failing or delayed in starting, and some queued jobs may time out. Customers using self-hosted runners may see errors or rate limiting when runners register. Copilot code review,...
-
investigating
We are continuing to work on an issue affecting multiple GitHub services. Workflow runs are still failing, and jobs may remain queued for an extended period before starting or may time out. Jobs using GitHub-hosted runners are particularly affected while capacity is constrained....
-
investigating
We are continuing to work on an issue affecting GitHub Actions. Capacity remains constrained and jobs may still be delayed or fail while it recovers gradually. Customers using self-hosted runners may see errors or rate limiting when runners register. Copilot code review, Copilot...
-
investigating
We are continuing to work on an issue affecting GitHub Actions. Webhook triggers are currently throttled to help with recovery and and we are processing approximately 15% of webhooks, so many events such as pushes and pull requests are not triggering workflow runs. Of jobs...
-
investigating
We are continuing to work on an issue affecting GitHub Actions. Webhook triggers remain throttled to aid recovery, so many push and pull request events are not triggering new workflow runs. We identified runners being assigned jobs that are no longer valid and are deploying a...
-
investigating
We continue to make progress on the issue affecting GitHub Actions. We have deployed a fix that addresses runners being assigned jobs that are no longer valid, and are seeing improvement in job completion rates. For workflow runs that are starting, success rates have increased...
-
investigating
We have deployed fixes that address runners being assigned invalid jobs and are taking additional steps to clear the backlog of affected jobs. Job completion rates for running workflows have improved significantly, with success rates now at 99%. Global queues for hosted runner...
-
investigating
System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out. Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and...
-
investigating
System-wide queues have been drained, and new jobs are being processed as expected. The fix for self-hosted runners not picking up jobs has been fully rolled out. Webhook-triggered Actions workflows have been restored to full throughput. GitHub Pages, Copilot code review, and...
-
investigating
The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
monitoring
We’re investigating reports that some Actions Runner Controller runners are taking longer than expected to recover. We’ll provide an update as our investigation progresses.
-
monitoring
During the incident, some Actions Runner Controller (ARC) runner pods became stuck in an idle state. Affected users can delete those pods using kubectl or redeploy their Actions Runner Controller application. ARC will automatically create replacement runners. The next releases...
-
resolved
On August 6, 2026, between 15:05 UTC and 00:14 UTC on August 7, GitHub Actions experienced degraded availability. During the incident, workflow runs failed or remained queued for an extended period of time. Customers using both GitHub-hosted and self-hosted runners were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pages - Deployment Lag
Affected: Pages
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
investigating
We are investigating reports of degraded performance for Pages
-
monitoring
The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
-
resolved
On August 6, 2026, at 07:00 UTC, a configuration change inadvertently reduced the capacity of the service that processes GitHub Pages deployments. As traffic increased over the following hours, latency in the deployment pipeline progressively increased. At 12:09 UTC, latency...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some Copilot Cloud Agent jobs not starting
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
investigating
We are investigating reports of impacted performance for some GitHub services.
-
monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
-
monitoring
Copilot cloud agent jobs have recovered and the backlog of delayed jobs is being processed.
-
resolved
On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
Failure mode: Login, tokens, certificates or credentials failed. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On 2026-08-03, between 06:52 and 11:25 UTC, some GitHub Copilot users experienced errors when using chat and agent features. Requests to list the available models failed, and because every chat or agent interaction begins by retrieving the list of models, affected users saw...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On August 1, 2026, between 17:47 UTC and 18:20 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.007%, while failures for Fable 5 peaked at 5.6%. Other models remained...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded availability GPT 5.6 Luna
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On August 1st, 2026, the GPT-5.6 Luna model in GitHub Copilot experienced degraded availability in intermittent time intervals between ~08:05 UTC and ~16:30 UTC. Specifically the timeframes observed were 10:00-10:20 UTC, 10:45-11:50 UTC, 13:00-14:25 UTC, and 16:00-16:30 UTC....
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot model Claude Fable 5 experiencing elevated errors
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 30, 2026, the Claude Fable 5 model in GitHub Copilot experienced degraded availability for approximately 73 minutes, from 08:33 to 09:46 UTC. During this time, requests to Claude Fable 5 in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot AI Model Providers
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 29, 2026, between 19:45 UTC and 21:51 UTC, users of the Fable 5 model in GitHub Copilot experienced increased request failures and latency. The average failure rate across all Copilot requests was 0.006%, while failures for Fable 5 peaked at 21%. Other models remained...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 29, 2026, from 14:51 UTC to 15:28 UTC, GitHub Actions experienced elevated REST API request timeouts and errors, failures registering runners, and delayed workflow run starts for customers whose traffic was served by a single infrastructure site. This was caused by an...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with GraphQL API Requests
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 26, 2026 at 21:34 UTC we began seeing intermittent errors on the GitHub GraphQL API. A subset of GraphQL API requests returned HTTP 502 errors in short bursts. During the impact window an average of 0.09% of GraphQL API requests in the affected region failed, with a peak...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions run failures and delays
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).
-
resolved
Please refer to the combined summary in this related incident: https://www.githubstatus.com/incidents/s65j9gslmfm8
Excerpts are shortened. Read the full incident on GitHub's status page.
Several GPT models degraded
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 25, 2026, between 09:07 and 10:04 UTC, the GPT-5.2, GPT-5.3-Codex, GPT-5.4, GPT-5.4 Mini, GPT-5.6 Sol, GPT-5.6 Terra and GPT-5.6 Luna models experienced degraded availability in GitHub Copilot products and IDE surfaces. Requests to these models had an average failure...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 25, 2026, GitHub Actions experienced two related periods of degradation that caused some workflow runs to be delayed by more than 5 minutes or end with infrastructure failures. First period (08:45 – 09:13 UTC): During planned maintenance on a critical-path Redis cluster...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
Failure mode: A schema or data migration caused the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
Between July 24, 19:17 UTC and July 24, 20:02 UTC, users were unable to create pull requests due to a database schema change. In total, 113,930 pull request creation attempts were impacted across 50,904 users, with an average error rate of 1.75% and a maximum error rate of 2.25%...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: Network, DNS, routing or connectivity failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On July 24th at 16:04 UTC, a loss of connectivity occurred in network paths in one of our three physical data center availability zones (AZs). This resulted in packet loss due to the remaining active paths becoming saturated. Our data centers use a leaf-spine switch fabric in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With Blocked GitHub.com Traffic
Failure mode: CDN or edge layer failed or served bad content. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
Between July 23, 2026 at 18:45 UTC and July 24, 2026 at 11:19 UTC, an abuse mitigation update caused some legitimate customers whose traffic was routed through our Central Europe and South America edge locations to be incorrectly blocked from GitHub.com. We estimate that...
Excerpts are shortened. Read the full incident on GitHub's status page.
Latency issues across a number of services
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
resolved
On July 23, 2026, between 07:08 and 09:39 UTC, several services experienced delays: 8% of actions workflow runs experienced an average run start delay of 10 minutes, 5% of webhook deliveries exceeded SLO, and code scanning, repos, notifications, issues and pull requests...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with actions hosted runners
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
resolved
On July 22, 2026, between 19:36 UTC and 22:04 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some SSH connections using deploy keys are failing
Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
- HashiCorp: Terraform Runs Failing to Fetch GitHub Sources Over SSH
- Acquia: GitHub Incident Impacting Acquia Pipelines
-
resolved
On July 21, 2026, between 07:41 UTC and 11:57 UTC, the SSH Authentication service was degraded and some SSH connections failed to authenticate. On average, 12.2% of SSH authentication requests failed, peaking at 15.7%. Both user RSA keys and deploy keys were impacted. This was...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with GPT 5.3 Codex
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
Between 06:39 and 18:11 UTC on July 20, 2026, the Copilot service experienced a degradation of the GPT 5.3 model due to an issue with our upstream provider. The upstream model provider returned intermittent errors for GPT 5.3 Codex requests, which caused some responses to fail....
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
- v0: Github service degraded
- CircleCI: Errors with GitHub APIs delaying workflows
- Render: Degraded builds/deploys (all regions)
- Socket: Upstream GitHub API errors impacting Socket GitHub App
- Devin (Cognition): Github outage
-
resolved
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with GitHub Actions
Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
- v0: Github service degraded
- CircleCI: Errors with GitHub APIs delaying workflows
- Render: Degraded builds/deploys (all regions)
- Socket: Upstream GitHub API errors impacting Socket GitHub App
- Devin (Cognition): Github outage
-
resolved
Between July 19, 2026, at 23:05 UTC and July 20, 2026, at 03:55 UTC, Actions self-hosted and larger runners were unable to connect to GitHub. During this period, Actions jobs were delayed or failed when trying to acquire a runner. Jobs using standard and Mac hosted runners were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded REST API Availability
Failure mode: A zone, region or data center became unavailable. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
- Render: GitHub outage affecting new service creation and service deploys
- CodeRabbit: Incident: CodeRabbit not able to authenticate to GitHub
- Socket: Github App reports are failing
- CircleCI: Errors accessing CircleCI and delays starting pipelines and scheduled workflows
- Bitrise: Elevated error rates on Bitrise Website
- Vercel: GitHub-linked deployments and authentication affected
- v0: GitHub integration degraded
- Devin (Cognition): GitHub outage
-
resolved
From 22:21 UTC - 23:50 UTC on July 16, 2026, the REST API experienced significant degradation. During this period, about 39% of REST API requests failed with HTTP 500 level responses, with the errors peaking at 44.3%. We identified the issue as an infrastructure change that...
Excerpts are shortened. Read the full incident on GitHub's status page.
Claude Fable 5 experiencing degraded performance
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On July 16, 2026, GitHub Copilot users experienced elevated errors when using Claude Fable 5 from 17:33 UTC until mitigation at 22:04 UTC. The average error rate was 1.4%, with a maximum error rate of 30.85%. The issue was caused by degradation at an upstream model provider;...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 16, 2026, between 08:50 UTC and 09:50 UTC, the GitHub MCP Server’s web_search tool experienced elevated failures. The average error rate was 42% and peaked at 82% of requests to the tool. Other GitHub MCP Server tools were unaffected. This was caused by degradation at a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 14, 2026, between 15:17 and 15:37 UTC, a rollout to GitHub's internal webhook delivery pipeline caused a subset of webhook delivery records to not be written to our webhook deliveries store after being processed and delivered successfully. Affected deliveries would be...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: An external attack. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 14, 2026, the GitHub Codespaces service was degraded during two periods — between 06:00 UTC and 09:56 UTC, and again between 10:54 UTC and 12:53 UTC — and some users experienced intermittent failures or delays when creating new codespaces. Impact was concentrated in a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions runs are experiencing failures to start
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 13, 2026, between 13:11 and 13:53 UTC, some customers experienced failures starting and running GitHub Actions workflows, which also affected Copilot cloud agent sessions and GitHub Pages builds since they depend on Actions. During the peak of the incident, 30% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delays starting Actions runs
Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).
-
resolved
On July 9, 2026, between 03:29 UTC and 13:39 UTC, GitHub Actions experienced delayed and failed job starts on GitHub-hosted runners. The incident was caused by an unhealthy state in a backend data service responsible for provisioning hosted runners, preventing runner acquisition...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions and Codespaces APIs experiencing partial failures
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pages
Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 2nd, 2026, between approximately 15:00 and 18:30 UTC, the GitHub Pages service experienced degraded deployment performance due to a surge in demand that exceeded available processing capacity. During this period, users publishing to GitHub Pages may have seen their...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delays in copilot budget limits resets for some users
Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On July 1, 2026, between approximately 00:00 UTC and 13:04 UTC, some GitHub Copilot customers whose budget was exhausted before the monthly reset remained incorrectly blocked from paid Copilot usage after the new billing month began, even though their budgets had reset. Some...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services - Signup Flow
Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
Between 15:19 UTC and 15:49 UTC on June 30, 2026, users were unable to complete the signup flow for GitHub.com/signup. Approximately 62% of new user signups failed for about 30 minutes during this window. This was caused by a configuration change to the signup flow that...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
From June 26, 2026 at 23:40 UTC through June 28, 2026 at 20:55 UTC, Copilot Cloud Agent was degraded. The agent could fail when reporting progress, replying to pull request comments, or opening pull requests. For affected built-in tool calls, the average error rate was...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
This incident was used to notify for a maintenance event. There is no specific root cause analysis. Work progressed as planned without any issues to report.
Excerpts are shortened. Read the full incident on GitHub's status page.
Degradation with Webhooks, Pull Requests and Actions
Failure mode: Hardware, power, cooling or another physical failure. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).
-
resolved
On June 25, 2026, between 17:33 UTC and 17:55 UTC, our background job service experienced degradation which increased delays to pull requests, repository pushes, Actions workflows, and Webhooks, with delays peaking at 7m. The issue was caused by underlying hypervisor issues and...
Excerpts are shortened. Read the full incident on GitHub's status page.
We are seeing elevated errors with Next Edit Suggestions and Completions
-
resolved
On June 23, 2026, between 22:45 and 23:29 UTC, GitHub Copilot Completions and Next Edit Suggestions were degraded for users in all regions. During this window, affected users may have seen failed or missing code completions and Next Edit Suggestions. On average about 25% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With Webhooks
-
resolved
On June 17, 2026, between 11:35 UTC and 19:20 UTC, the Webhooks service was degraded and delivered webhook payloads with missing installation information. On average, 11.3% of webhook deliveries were impacted. Customers relying on the installation field for authentication or...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Copilot next edit suggestions
-
resolved
On June 17, 2026, between 16:57 UTC and 19:14 UTC, Copilot code completions were degraded and users were unable to receive Next Edit Suggestions. Standard ghost text code completions were not affected. This was due to a configuration change that caused the service's routing...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot Availability
-
resolved
On June 17, 2026, between approximately 03:35 UTC and 04:44 UTC, GitHub Copilot was degraded and most of its frontier chat models were temporarily unavailable across all regions. During this window, affected models either disappeared from the model picker in the web, editor, and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On June 16, 2026, between 17:20 UTC and 18:15 UTC, the Opus 4.8 model experienced degraded availability in GitHub Copilot. During this window, some requests to Opus 4.8 failed or errored. Other Copilot models were not affected and remained available as alternatives. This was...
Excerpts are shortened. Read the full incident on GitHub's status page.
Multiple services have elevated errors and endpoint failures when checking feature flags
-
resolved
Between 17:38 UTC and 18:22 UTC on June 15, 2026, approximately 83% of requests to the analytics endpoint serving the /chronicle feature failed. The cause was an internal feature-flag service that encountered a transient error and failed to recover, causing feature flag checks...
Excerpts are shortened. Read the full incident on GitHub's status page.
Increased latency with webhooks
-
resolved
On June 15, 2026, between 15:27 UTC and 16:23 UTC, GitHub webhook deliveries were delayed. During this window, webhook events were delivered later than normal, with average end-to-end delivery latency peaking at approximately 8.8 minutes. No webhook deliveries were lost —...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On June 11, 2026, between 19:28 UTC and 21:06 UTC, GitHub webhook deliveries were delayed. Average delivery latency peaked at approximately 3.4 minutes, with some deliveries delayed by as much as 62 minutes at the 99th percentile. No events were lost — delayed events were queued...
Excerpts are shortened. Read the full incident on GitHub's status page.
Authentication issues related to API requests
Knock-on incidents at other vendors that started during this one and name GitHub:
- Graphite: GitHub is experiencing an outage. Some actions may be impacted.
- Expo: GitHub's incident causes certain actions to fail
- CircleCI: Incident with GitHub APIs
-
resolved
Between 15:05 UTC and 16:25 UTC, GitHub API services experienced degraded availability due to sporadic authentication failures affecting approximately 9% of requests. Customers experienced intermittent "logged out" behavior as erroneous 401 responses triggered repeated...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded availability for GitHub.com, GraphQL API, and Webhooks UI/API
-
resolved
On June 8, 2026, between 14:49 and 14:54 UTC, a subset of requests to GitHub.com, the REST API, GraphQL API, and Webhooks UI/API experienced elevated error rates due to a transient infrastructure capacity issue that self-resolved within approximately 5 minutes. Users experienced...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Claude Opus 4.7
-
resolved
On June 8, 2026, between 08:40 UTC and 09:30 UTC, the Claude Opus 4.7 model experienced degraded availability with error rates peaking at 8.4% and averaging 1.9%. This was due to an upstream provider issue that caused temporary unavailability and rate limiting on secondary...
Excerpts are shortened. Read the full incident on GitHub's status page.
Pull Requests and Issues unavailable for signed-out users
-
resolved
On June 8, 2026, between approximately 06:30 UTC and 08:36 UTC, signed-out users experienced sustained elevated HTTP 504 errors when accessing Pull Requests, Issues, releases, patch diffs, and other related GitHub.com pages. During the incident, approximately 17% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services in the EU region
-
resolved
On June 6, 2026 between 16:18 UTC and 17:01 UTC, users experienced elevated error rates when performing Git operations (cloning, fetching, downloading archives) and accessing package registries. The issue affected users whose traffic was routed through our European...
Excerpts are shortened. Read the full incident on GitHub's status page.
EU Network Maintenance
-
resolved
This incident was used to notify for a maintenance event. There is no specific root cause analysis. Maintenance did run longer than expected (we were complete at 18:48 UTC) but the work proceeded as planned.
Excerpts are shortened. Read the full incident on GitHub's status page.
Auth issue resulting in API impacts, including some Slack and Teams channel subscriptions
-
resolved
On June 5, 2026, between 15:35 UTC and 16:45 UTC, 0.11% of authenticated REST API requests incorrectly returned “not found” responses. Impact was concentrated among - and significantly higher for - users authenticating with user-to-server tokens to access organization-owned...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot Code Review Failing
-
resolved
On June 4, 2026, from 17:30 UTC to 18:55 UTC, Copilot Code Review experienced elevated failures for review requests on GitHub.com. Affected users saw “Copilot ran into an error” on pull requests when requesting a code review. During the incident window, an average of 81.6% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between June 1, 2026, 23:00 UTC and June 4, 2026 04:11 UTC, customers experienced delays in Dependabot scheduled version updates. Pull request creation for version updates was delayed, with delays increasing over time and reaching up to two days. Approximately 1.5 million...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On June 2, 2026, between 21:54 UTC and June 3, 2026 06:45 UTC, the Spark service was degraded and users were unable to store or retrieve data for their Spark apps in one of our hosting regions. Users could still make changes to their app configuration during this time. The error...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delays with Code Scanning and Billing
-
resolved
Starting from 13:00 UTC June 1, 2026, to 00:17 UTC June 2, 2026, multiple services experienced delayed job processing due to increased latency in our background job queue service. The root cause was insufficient queue processing capacity to handle a large week-over-week increase...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated error rates across multiple services
-
resolved
On May 28, 2026, between 19:07 UTC and 19:16 UTC, multiple GitHub services experienced elevated error rates. This was due to a change that was partially deployed to an authentication service, causing errors for dependent services including the web experience, REST API, Git...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with OpenAI Models
Names an upstream provider: OpenAI.
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On May 28th, 2026, between approximately 18:27 and 20:41 UTC, the GitHub Copilot service was degraded due to an issue with the Responses API of an upstream provider affecting the GPT-5.2, GPT-5.3-Codex, GPT-5.4, and GPT-5.5 models. Requests routed to these models via the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Webhook APIs and UI Degraded
-
resolved
On May 28, 2026, between 00:54 UTC and 01:19 UTC, some users experienced errors when interacting with the Webhooks API, including webhook delivery history and configuration endpoints. On average, the error rate was 0.28% and peaked at 0.45%. This was due to a bug that caused a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests, Issues, Git Operations and API Requests
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On May 27, 2026, between 12:07 UTC and 13:16 UTC, users experienced degraded performance for Git operations, Pull Requests, Issues, GraphQL API, and related services on github.com. During this time, operations that depended on Git file servers experienced elevated error rates...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On May 26, 2026, between 15:10 UTC and 16:35 UTC the Copilot service was degraded and many models were no longer available for use. On average, the error rate was ~5% and peaked at 11% of requests to the service. This was due to a change that introduced a configuration mismatch...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions and Pages
-
resolved
On May 26, 2026, between 10:40 UTC and 12:56 UTC, GitHub Actions jobs were degraded. From 10:40 to 12:16 UTC, all newly queued Actions runs failed to start. From 12:16 to 12:56 UTC, Actions runs that required downloading actions for their workflows continued to fail. GitHub...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated rate of Git push errors
-
resolved
On May 25, 2026, between 09:02 UTC and 09:11 UTC, Git push operations over HTTPS and SSH experienced elevated failures. During this window, an average of 31% and a peak of 43% of push requests failed. The incident was caused by a recently enabled code path that issued an...
Excerpts are shortened. Read the full incident on GitHub's status page.
Intermittent errors with app installation token authentication
-
resolved
On May 23, 2026 between 06:00 UTC and 19:12 UTC, GitHub experienced intermittent errors authenticating GitHub app installation tokens . During this time, between 1-5% of app installation token authentication requests failed, with an average of 2.3% and the error rate peaking at...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On May 20, 2026, between 16:00 UTC and 17:45 UTC, GitHub Actions customers experienced run start delays exceeding 5 minutes. Approximately 4.5% of all runs were delayed during the impact window, with scale set jobs disproportionately affected. 30% of scale set jobs were delayed...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On May 19, 2026, between 05:30 UTC and 14:50 UTC, some Copilot users experienced failures when using code completions, chat sessions, and cloud agent sessions. At peak impact, approximately 13% of Copilot API requests failed, and approximately 24% of remote sessions failed to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions is experiencing degraded availability
-
resolved
On May 15, 2026, from approximately 07:43 UTC to 08:48 UTC, GitHub Actions experienced a degradation that caused workflow runs to fail or experience delayed starts for a subset of customers. The incident was triggered by a planned failover of supporting infrastructure used by...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Incident with GitHub.com
-
resolved
Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed. The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with CodeQL
-
resolved
On May 13, 2026, between 14:31 and 16:03 UTC, the Code Scanning service experienced processing delays and 12% of check runs took over 15 minutes to complete. The delays were caused by replication lag due to an internal database migration, resulting in insufficient worker...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with CodeQL, Webhooks, Notifications, and Slack Integration
-
resolved
On May 12, 2026, between 13:41 and 17:43 UTC, some services experienced delays in processing. For the Code Scanning service, 53% of check runs took over 15 minutes to complete. Additionally, notifications took an average of 22 minutes to be delivered and Slack integration...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with high errors on Git Operations
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On May 11th, 2026, between 14:00 UTC and 14:33 UTC, HTTP-based Git read operations were degraded. On average, the error rate was 2.8% and peaked at 7.5% of requests to the service. This was due to resource exhaustion in a networking gateway between GitHub.com’s frontend service...
Excerpts are shortened. Read the full incident on GitHub's status page.
CCR and CCA failing to start for PR comments
-
resolved
On May 7, 2026, between 04:12 UTC and 06:13 UTC, Copilot Cloud Agent and Copilot Code Review Agent sessions for pull requests were delayed or failed to start. The issue was caused by follow-up recovery work from a separate Pull Requests incident...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
Knock-on incidents at other vendors that started during this one and name GitHub:
- Graphite: GitHub is experiencing an outage. Some actions may be impacted.
- CircleCI: GitHub incident with Pull Requests
-
resolved
On May 6, 2026 between 15:12 and 19:02 UTC creation of new pull request review threads on GitHub.com failed. This included new line comments and file comments on pull requests. Existing PRs and previously created comments were unaffected. This incident was caused by a 32-bit...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On May 6, 2026 between 11:02 UTC and 11:13 UTC, users were unable to start or view Copilot Cloud Agent or remote sessions. During this time, requests to the session API returned errors, preventing users from creating new sessions or viewing existing ones. The issue was caused by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions, we are investigating reports of degraded availability
-
resolved
On May 6, 2026, from approximately 06:45 UTC to 09:15 UTC, GitHub Actions Standard Ubuntu hosted runners were degraded. 17.1% of jobs requesting a standard runner failed. This was caused by an unexpected data shape in the allocation configuration data for standard runners. That...
Excerpts are shortened. Read the full incident on GitHub's status page.
Increased Latency and Failures for SSH Git Operations
-
resolved
Between approximately 14:00 and 16:10 UTC on May 5, 2026, SSH-based Git operations experienced elevated latency and intermittent failures. On average, the error rate was 0.46% and peaked at 0.6% of SSH write requests. HTTP-based Git operations, including web UI and HTTPS clones,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On May 5, 2026, from approximately 13:22 UTC to 17:05 UTC, GitHub Actions hosted runners in the East US region were degraded. 13.5% of jobs requesting a standard runner failed and ~16% of requested Larger Runners with private networking pinned to East US failed or were delayed...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues and Webhooks
-
resolved
On 2026-05-04 at 3:37:17 PM UTC we detected increased latency on issues resulting in timeouts, and elevated 500 errors on webhooks. A scheduled workload drove high utilization on the primary host of a critical datastore, saturating the connection pool. We paused the job to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incomplete pull request results in repositories
-
resolved
On April 28, 2026, at approximately 14:07 UTC, GitHub received reports that pull requests were missing from search results across global and repository /pulls pages. The issue was caused by a manually invoked repair job intended for a single repository, which was executed...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 28, 2026, from approximately 12:41 UTC to 17:09 UTC, GitHub Actions jobs using Standard Ubuntu 22 and Ubuntu 24 hosted runners experienced run start delays. Approximately 8% of hosted runner jobs using Ubuntu 22 and Ubuntu 24 experienced delays greater than 5 minutes or...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
- Graphite: GitHub is experiencing an outage. Some actions in Graphite are affected.
- Vanta: Missing GitHub data
-
resolved
On April 22, 2026 from 18:49 to 19:32 UTC , the Copilot Cloud Agent service began failing during session execution for users running the Agent HQ Codex agent. Codex agent sessions failed to start for all entry points (issue assignment, @copilot comment mentions). 0.5% of total...
Excerpts are shortened. Read the full incident on GitHub's status page.
GitHub search is degraded
Knock-on incidents at other vendors that started during this one and name GitHub:
- Graphite: GitHub is experiencing an outage. Some actions in Graphite are affected.
- Vanta: Missing GitHub data
-
resolved
On April 27, 2026 between 16:15 UTC and 22:46 UTC, GitHub search services experienced degraded connectivity due to saturation of the load balancing tier deployed in front of our search infrastructure. This resulted in intermittent failures for services relying on our search data...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delays with Actions Jobs for Larger Runners using VNet Injection in the East US region
-
resolved
On April 24, 2026, from approximately 11:39 UTC to April 25, 2026 at 00:15 UTC, GitHub Actions experienced delays and timeouts for Larger Hosted Runner jobs using VNet injection in the East US region without a failover region configured. Standard and Self-hosted runners were not...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
-
resolved
On April 23, 2026, between 16:05 UTC and 20:43 UTC, the Pull Requests service experienced a regression affecting merge queue operations. PRs merged via merge queue using the squash merge method produced incorrect merge commits when the merge group contained more than one PR. In...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with users unable to start Claude and Codex agent task from the web
-
resolved
Between 18:45 and 19:42 UTC on April 23, users were unable to start new agent tasks using either Claude or Codex agent on github.com. This was caused by a code change to how Copilot mission control routes task creation requests. Ongoing agent tasks and other Copilot agent...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with multiple GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
- Semgrep: Failures running diff-aware scans for GitHub.com customers
- Netlify: Elevated Rate of Build Failures
- Snyk: GitHub integration service degraded
-
resolved
On April 23, 2026, between 16:03 UTC and 17:27 UTC, multiple GitHub services experienced elevated error rates and degraded performance due to DNS resolution failures originating from our DNS infrastructure in our VA3 datacenter. Approximately 5–7% of overall traffic was affected...
Excerpts are shortened. Read the full incident on GitHub's status page.
Investigating errors on GitHub
-
resolved
On April 23, 2026 between 14:30 UTC and 15:18 UTC multiple services were degraded on github.com. During this time approximately 1.5% of all web requests resulted in a 5xx status and unicorn pages for github.com users. We also saw elevated error rates across Actions workflow...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 22, 2026, between 09:00 UTC and 22:05 UTC, the Copilot coding agent and pull request comment event processing were degraded. During this period, approximately 0.5% of total pull request and issue comments mentioned @copilot (~23,000 invocations), explicitly requested...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Copilot chat and Copilot Coding Agent
-
resolved
On April 22, 2026, between 15:16 UTC and 19:18 UTC, users experienced errors when interacting with Copilot Chat on github.com and Copilot Cloud Agent. During this time, users were unable to use Copilot Chat or Copilot Cloud Agent. Copilot Memory (in preview) was not available to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with projects service
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On April 21, 2026, between 13:35 UTC and 01:24 UTC the following day the projects service was degraded. During this time period, projects may have been out of sync and users may have experienced delays in changes to projects and their items. Delays in reflected changes peaked at...
Excerpts are shortened. Read the full incident on GitHub's status page.
Partial degradation for code scanning default setup and for code quality
-
resolved
On April 20, 2026 between 10:28 UTC and 15:04 UTC GitHub experienced degraded service for code scanning default setup, code quality, and project boards. Repair of affected project boards additionally lasted until April 21, 05:04 UTC During this time, code scanning default setup...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 17, 2026, between 14:46 UTC and 15:12 UTC, users experienced a degraded web experience on GitHub.com. During this time, approximately 1.5% of web requests resulted in errors, with some users encountering slow page loads or failed requests. The issue was caused by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
On April 16, 2026 between 09:30 UTC and 17:15 UTC, users experienced failures when attempting to connect to GitHub Codespaces via the VS Code editor. During this time, approximately 40% of codespace start operations failed. Users connecting via SSH were not impacted. The issue...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 14, between 00:58 UTC and 06:08 UTC, GitHub Enterprise Cloud customers experienced 500 errors when attempting to access Copilot Insights pages which was caused by an authentication failure in our metrics pipeline. We fully mitigated the issue and validated the fix in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pages
-
resolved
On Sunday April 13th, 2026, between 18:53 UTC and 20:30 UTC, the GitHub Pages service experienced elevated error rates. On average, the error rate was 10.58% and peaked at 12.77% of requests to the service, resulting in approximately 17.5 million failed requests returning HTTP...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 13, 2026, between 14:41 UTC and 17:29 UTC, the Copilot service experienced degraded performance. All Copilot users were impacted by increased latency, and approximately 20% experienced request failures when interacting with Copilot Cloud Agent (CCA). On average, request...
Excerpts are shortened. Read the full incident on GitHub's status page.
Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard
-
resolved
On April 9, 2026, between 22:59 UTC and April 10, 2026, 13:24 UTC, the Copilot Mission Control service was degraded and did not display Claude and Codex Cloud Agent sessions in the agents tab dashboard. Customers were unable to see, list, or manage their third party agent...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 9, 2026, between 16:05 UTC and 20:36 UTC, the Copilot cloud agent service was degraded, causing new agent sessions to be delayed or fail to start. Users who attempted to start Copilot cloud agent sessions during this period experienced jobs getting stuck in the queue,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 9, 2026, between 09:05 UTC and 19:05 UTC, the Copilot coding agent service was degraded and users experienced significant delays starting new agent sessions. Approximately 84% of new agent session requests were delayed across four separate outage waves, with queue wait...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with GitHub notifications
-
resolved
On April 9, 2026, between 03:22 UTC and 04:49 UTC, GitHub Notifications experienced degraded availability. During this time, approximately 45% of requests to the notifications service returned errors, with a peak error rate of approximately 54%, preventing affected users from...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot Coding Agent failing to start some jobs
-
resolved
Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load...
Excerpts are shortened. Read the full incident on GitHub's status page.
GitHub audit logs are unavailable
-
resolved
On April 1, 2026, between 15:34 UTC and 16:02 UTC, our audit log service lost connectivity to its backing data store due to a failed credential rotation. During this 28-minute window, audit log history was unavailable via both the API and web UI. This resulted in 5xx errors for...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with GitHub's code search
-
resolved
On April 1st, 2026 between 14:40 and 17:00 UTC the GitHub code search service had an outage which resulted in users being unable to perform searches. The issue was initially caused by an upgrade to the code search Kafka cluster ZooKeeper instances which caused a loss of quorum....
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On April 1, 2026, between 07:29 and 12:41 UTC, some customers experienced elevated 5xx errors and increased latency when using GitHub Copilot features that rely on `/agents/sessions` endpoints (including creating or viewing agent sessions). The issue was caused by resource...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests: High percentage of 500s
-
resolved
On Monday March 31st, 2026, between 13:53 UTC and 21:23 UTC the Pull Requests service experienced elevated latency and failures. On average, the error rate was 0.15% and peaked at 0.28% of requests to the service. This was due to a change in garbage collection (GC) settings for...
Excerpts are shortened. Read the full incident on GitHub's status page.
Issues with metered billing report generation
-
resolved
On March 31, 2026, between 06:15 UTC and 15:30 UTC, the GitHub billing usage reports feature was degraded due to reduced server capacity. Customers requesting billing usage reports and loading the top usage by organization and repository on the billing overview and usage pages...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated delays in Actions workflow runs and Pull Request status updates
-
resolved
On March 30, 2026, between 10:11 UTC and 13:25 UTC, GitHub Actions experienced degraded performance. During this time, approximately 2.65% of workflow jobs triggered by pull request events experienced start delays exceeding 5 minutes. The issue was caused by replication lag on...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On March 27, 2026, from 02:30 to 04:56 UTC, a misconfiguration in our rate limiting system caused users on Copilot Free, Student, Pro, and Pro+ plans to experience unexpected rate limit errors. The configuration that was incorrectly applied was intended solely for internal staff...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
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.
Excerpts are shortened. Read the full incident on GitHub's status page.
Teams Github Notifications App is down
-
resolved
On March 24, 2026, between 15:57 UTC and 19:51 UTC, the Microsoft Teams Integration and Teams Copilot Integration services were degraded and unable to deliver GitHub event notifications to Microsoft Teams. On average, the error rate was 37.4% and peaked at 90.1% of requests to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On March 22, 2026, between 09:05 UTC and 10:02 UTC, users may have experienced intermittent errors and increased latency when performing Git http read operations. On average, the error rate was 3.84% and peaked at 15.55% of requests to the service. The issue was caused by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Copilot Coding Agent Sessions
-
resolved
On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average...
Excerpts are shortened. Read the full incident on GitHub's status page.
Git operations for users in the west coast are experiencing an increase in latency
-
resolved
On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root...
Excerpts are shortened. Read the full incident on GitHub's status page.
Issues with Copilot Coding Agent
-
resolved
On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Copilot Coding Agent sessions
-
resolved
On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root...
Excerpts are shortened. Read the full incident on GitHub's status page.
Webhook delivery is delayed
-
resolved
On March 18, 2026, between 18:18 UTC and 19:46 UTC all webhook deliveries experienced elevated latency. During this time, average delivery latency increased from a baseline of approximately 5 seconds to a peak of approximately 160 seconds. This was due to resource constraints in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Errors starting and connecting to Codespaces
-
resolved
On 16 March 2026, between 14:16 UTC and 15:18 UTC, Codespaces users encountered a download failure error message when starting newly created or resumed codespaces. At peak, 96% of the created or resumed codespaces were impacted. Active codespaces with a running VSCode...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded performance for various services
-
resolved
On March 13, 2026, between 13:35 UTC and 16:02 UTC, a configuration change to an internal authorization service reduced its processing capacity below what was needed during peak traffic. This caused intermittent timeouts when other GitHub services checked user permissions,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded Codespaces experience
-
resolved
On March 12, 2026, between 01:00 UTC and 18:53 UTC, users saw failures downloading extensions within created or resumed codespaces. Users would see an error when attempting to use an extension within VS Code. Active codespaces with extensions already downloaded were not...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions failures to download (401 Unauthorized)
-
resolved
On March 12, 2026 between 02:30 and 06:02 UTC some GitHub Apps were unable to mint server to server tokens, resulting in 401 Unauthorized errors. During the outage window, ~1.3% of requests resulted in 401 errors incorrectly. This manifested in GitHub Actions jobs failing to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
Between 01:36 and 08:11 UTC on Thursday March 12, GitHub.com experienced elevated error rates across Git operations, web requests, and related services. During a planned infrastructure upgrade, a configuration issue caused newly provisioned Kubernetes nodes to run an...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with API Requests
-
resolved
On March 11, 2026, between 14:25 UTC and 14:34 UTC, the REST API platform was degraded, resulting in increased error rates and request timeouts. REST API 5xx error rates peaked at ~5% during the incident window with two distinct spikes: the first impacting REST services broadly,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded experience with Copilot Code Review
-
resolved
On March 11, 2026, between 13:00 UTC and 15:23 UTC the Copilot Code Review service was degraded and experienced longer than average review times. On average, Copilot Code Review requests took 4 minutes and peaked at just under 8 minutes. This was due to hitting worker capacity...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With Webhooks
-
resolved
On March 10, 2026, between 23:00 UTC and 23:40 UTC, the Webhooks service was degraded and ~6% of users experienced intermittent errors when accessing webhook delivery history, retrying webhook deliveries, and listing webhooks via the UI and API. Approximately 0.37% of requests...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
-
resolved
On March 9, 2026, between 15:03 and 20:52 UTC, the Webhooks API experienced was degraded, resulted in higher average latency on requests and in certain cases error responses. Approximately 0.6% of total requests exceeded the normal latency threshold of 3s, while 0.4% of requests...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
On March 9, 2026, between 01:23 UTC and 03:25 UTC, users attempting to create or resume codespaces in the Australia East region experienced elevated failures, peaking at a 100% failure rate for this region. Codespaces in other regions were not affected. The create and resume...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
-
resolved
On March 6, 2026, between 16:16 UTC and 23:28 UTC the Webhooks service was degraded and some users experienced intermittent errors when accessing webhook delivery histories, retrying webhook deliveries, and listing webhooks via the UI and API. On average, the error rate was...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions is experiencing degraded availability
-
resolved
On March 5, between 22:39 and 23:55 UTC, Actions was degraded due to a repeat of an incident a few hours prior. In this case, a Redis cluster topology change made as a follow-up to the earlier incident caused a repeat of the earlier degradation of Actions jobs. Details of both...
Excerpts are shortened. Read the full incident on GitHub's status page.
Multiple services are affected, service degradation
-
resolved
On Mar 5, 2026, between 16:24 UTC and 19:30 UTC, Actions was degraded. During this time, 95% of workflow runs failed to start within 5 minutes with an average delay of 30 minutes and 10% workflow runs failed with an infrastructure error. This was due to Redis infrastructure...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On March 5, 2026, between 12:53 UTC and 13:35 UTC, the Copilot mission control service was degraded. This resulted in empty responses returned for users' agent session lists across GitHub web surfaces. Impacted users were unable to see their lists of current and previous agent...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some OpenAI models degraded in Copilot
Names an upstream provider: OpenAI.
-
resolved
On March 5th, 2026, between approximately 00:26 and 00:44 UTC, the Copilot service experienced a degradation of the GPT 3.5 Codex model due to an issue with our upstream provider. Users encountered elevated error rates when using GPT 3.5 Codex, impacting approximately 30% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Claude Opus 4.6 Fast not appearing for some Copilot users
-
resolved
On March 3, 2026, between 19:44 UTC and 21:05 UTC, some GitHub Copilot users reported that the Claude Opus 4.6 Fast model was no longer available in their IDE model selection. After investigation, we confirmed that this was caused by enterprise administrators adjusting their...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with all GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On March 3, 2026, between 18:46 UTC and 20:09 UTC, GitHub experienced a period of degraded availability impacting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other dependent services. At the peak of the incident, GitHub.com request failures...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delayed visibility of newly added issues on project boards
-
resolved
Between March 2, 21:42 UTC and March 3, 05:54 UTC project board updates, including adding new issues, PRs, and draft items to boards, were delayed from 30 minutes to over 2 hours, as a large backlog of messages accumulated in the Projects data denormalization pipeline. The...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests /pulls
-
resolved
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages. This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot agent sessions
-
resolved
On February 27, 2026, between 22:53 UTC and 23:46 UTC, the Copilot coding agent service experienced elevated errors and degraded functionality for agent sessions. Approximately 87% of attempts to start or interact with agent sessions encountered errors during this period. This...
Excerpts are shortened. Read the full incident on GitHub's status page.
Code view fails to load when content contains some non-ASCII characters
-
resolved
Starting February 26, 2026 at 22:10 UTC through February 27, 05:50 UTC, the repository browsing UI was degraded and users were unable to load pages for files and directories with non-ASCII characters (including Japanese, Chinese, and other non-Latin scripts). On average, the...
Excerpts are shortened. Read the full incident on GitHub's status page.
High latency on webhook API requests
-
resolved
Between February 26, 2026 UTC and February 27, 2026 UTC, customers hitting the webhooks delivery API may have experienced higher latency or failed requests. During the impact window, 0.82% of requests took longer than 3s and 0.004% resulted in a 500 error response. Our monitors...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On February 26, 2026, between 09:27 UTC and 10:36 UTC, the GitHub Copilot service was degraded and users experienced errors when using Copilot features including Copilot Chat, Copilot Coding Agent and Copilot Code Review. During this time, 5-15% of affected requests to the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot Agent Sessions impacting CCA/CCR
-
resolved
On February 25, 2026, between 15:05 UTC and 16:34 UTC, the Copilot coding agent service was degraded, resulting in errors for 5% of all requests and impacting users starting or interacting with agent sessions. This was due to an internal service dependency running out of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues and Pull Requests Search
-
resolved
On February 23, 2026, between 21:01 UTC and 21:30 UTC the Search service experienced degraded performance, resulting in an average of 3.5% of search requests for Issues and Pull Requests being rejected. During this period, updates to Issues and Pull Requests may not have been...
Excerpts are shortened. Read the full incident on GitHub's status page.
Code search experiencing degraded performance
-
resolved
Between 2026-02-23 19:10 and 2026-02-24 00:46 UTC, all lexical code search queries in GitHub.com and the code search API were significantly slowed, and during this incident, between 5 and 10% of search queries timed out. This was caused by a single customer who had created a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On February 23, 2026, between 15:00 UTC and 17:00 UTC, GitHub Actions experienced degraded performance. During the time, 1.8% of Actions workflow runs experienced delayed starts with an average delay of 15 minutes. The issue was caused by a connection rebalancing event in our...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On February 23, 2026, between 14:45 UTC and 16:19 UTC, the Copilot service was degraded for Claude Haiku 4.5 model. On average, 6% of the requests to this model failed due to an issue with an upstream provider. During this period, automated model degradation notifications...
Excerpts are shortened. Read the full incident on GitHub's status page.
Extended job start delays for larger hosted runners
-
resolved
On February 20, 2026, between 17:45 UTC and 20:41 UTC, 4.2% of workflows running on GitHub Larger Hosted Runners were delayed by an average of 18 minutes. Standard, Mac, and Self-Hosted Runners were not impacted. The delays were caused by communication failures between backend...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot GPT-5.1-Codex
-
resolved
On February 20, 2026, between 07:30 UTC and 11:21 UTC, the Copilot service experienced a degradation of the GPT 5.1 Codex model. During this time period, users encountered a 4.5% error rate when using this model. No other models were impacted. The issue was resolved by a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded performance in merge queue
-
resolved
On February 17, 2026, between 17:07 UTC and 19:06 UTC, some customers experienced intermittent authentication failures affecting GitHub Actions, parts of Git operations, and other authentication-dependent requests. On average, the Actions error rate was approximately 0.6% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Intermittent authentication failures on GitHub
-
resolved
On February 17, 2026, between 17:07 UTC and 19:06 UTC, some customers experienced intermittent authentication failures affecting GitHub Actions, parts of Git operations, and other authentication-dependent requests. On average, the Actions error rate was approximately 0.6% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services regarding file upload
-
resolved
On February 13, 2026, between 21:46 UTC and 22:58 UTC (72 minutes), the GitHub file upload service was degraded and users uploading from a web browser on GitHub.com were unable to upload files to repositories, create release assets, or upload manifest files. During the incident,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between February 11th 21:30 UTC and February 12th 15:40 UTC, users in Western Europe experienced degraded quality for all Next Edit Suggestions requests. Additionally, on February 12th, between 18:40 UTC and 20:30 UTC, users in Australia and South America experienced degraded...
Excerpts are shortened. Read the full incident on GitHub's status page.
Intermittent disruption with Copilot completions and inline suggestions
-
resolved
Between February 11th 21:30 UTC and February 12th 15:40 UTC, users in Western Europe experienced degraded quality for all Next Edit Suggestions requests. Additionally, on February 12th, between 18:40 UTC and 20:30 UTC, users in Australia and South America experienced degraded...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
From Feb 12, 2026 09:16:00 UTC to Feb 12, 2026 11:01 UTC, users attempting to download repository archives (tar.gz/zip) that include Git LFS objects received errors. Standard repository archives without LFS objects were not affected. On average, the archive download error rate...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
On February 12, 2026, between 00:51 UTC and 09:35 UTC, users attempting to create or resume Codespaces experienced elevated failure rates across Europe, Asia and Australia, peaking at a 90% failure rate. The disconnects were triggered by a bad configuration rollout in a core...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On February 11 between 16:37 UTC and 00:59 UTC the following day, 4.7% of workflows running on GitHub Larger Hosted Runners were delayed by an average of 37 minutes. Standard Hosted and self-hosted runners were not impacted. This incident was caused by capacity degradation in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with API Requests
-
resolved
On February 11, 2026, between 13:51 UTC and 17:03 UTC, the GraphQL API experienced degraded performance due to elevated resource utilization. This resulted in incoming client requests waiting longer than normal, timing out in certain cases. During the impact window,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On February 11, 2025, between 14:30 UTC and 15:30 UTC, the Copilot service experienced degraded availability for requests to Claude Haiku 4.5. During this time, on average 10% of requests failed with 23% of sessions impacted. The issue was caused by an upstream problem from...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On February 10th, 2026, between 14:35 UTC and 15:58 UTC web experiences on GitHub.com were degraded including Pull Requests and Authentication, resulting in intermittent 5xx errors and timeouts. The error rate on web traffic peaked at approximately 2%. This was due to increased...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues, Actions and Git Operations
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On February 9, 2026, GitHub experienced two related periods of degraded availability affecting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other services. The first period occurred between 16:12 UTC and 17:39 UTC, and the second between 18:53...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot Policy Propagation Delays
Knock-on incidents at other vendors that started during this one and name GitHub:
- v0: GitHub operations are degraded on v0
- Snyk: GitHub Integration Degradation
- CircleCI: We are investigating issues with delays in pages loading
-
resolved
GitHub experienced degraded Copilot policy propagation from enterprise to organizations between February 3 at 21:00 UTC through February 10 at 16:00 UTC. During this period, policy changes could take up to 24 hours to apply. We mitigated the issue on February 10 at 16:00 UTC...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On February 9, 2026, GitHub experienced two related periods of degraded availability affecting GitHub.com, the GitHub API, GitHub Actions, Git operations, GitHub Copilot, and other services. The first period occurred between 16:12 UTC and 17:39 UTC, and the second between 18:53...
Excerpts are shortened. Read the full incident on GitHub's status page.
Notifications are delayed
Knock-on incidents at other vendors that started during this one and name GitHub:
- v0: GitHub operations are degraded on v0
- Snyk: GitHub Integration Degradation
- CircleCI: We are investigating issues with delays in pages loading
-
resolved
On February 9th notifications service started showing degradation around 13:50 UTC, resulting in an increase in notification delivery delays. Our team started investigating. Around 14:30 UTC the service started to recover as the team continued investigating the incident. Around...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On February 9th, 2026, between 09:16 UTC and 15:12 UTC GitHub Actions customers experienced run start delays. Approximately 0.6% of runs across 1.8% of repos were affected, with an average delay of 19 minutes for those delayed runs. The incident occurred when increased load...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded performance for Copilot Coding Agent
-
resolved
On February 9, 2026, between ~06:00 UTC and ~12:12 UTC, Copilot Coding Agent and related Copilot API endpoints experienced degraded availability. The primary impact was to agent-based workflows (requests to /agents/swe/*, including custom agent configuration checks), where 154k...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded Performance in Webhooks API and UI, Pull Requests
-
resolved
On February 9, 2026, between 07:05 UTC and 11:26 UTC, GitHub experienced intermittent degradation across Issues, Pull Requests, Webhooks, Actions, and Git operations. Approximately every 30 minutes, users encountered brief periods of elevated errors and timeouts lasting roughly...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
-
resolved
On February 6, 2026, between 17:49 UTC and 18:36 UTC, the GitHub Mobile service was degraded, and some users were unable to create pull request review comments on deleted lines (and in some cases, comments on deleted files). This impacted users on the newer comment-positioning...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On February 10, 2026, between 10:28 and 11:54 UTC, Visual Studio Code users experienced a degraded experience on GitHub Copilot when using the Claude Opus 4.6 model. During this time, approximately 50% of users encountered agent turn failures due to the model being unable to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delays in UI updates for Actions Runs
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On February 3, 2026, between 14:00 UTC and 17:40 UTC, customers experienced delays in Webhook delivery for push events and delayed GitHub Actions workflow runs. During this window, Webhook deliveries for push events were delayed by up to 40 minutes, with an average delay of 10...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On February 3, 2026, between 09:35 UTC and 10:15 UTC, GitHub Copilot experienced elevated error rates, with an average of 4% of requests failing. This was caused by a capacity imbalance that led to resource exhaustion on backend services. The incident was resolved by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
On February 2, 2026, GitHub Codespaces were unavailable between 18:55 and 22:20 UTC and degraded until the service fully recovered at February 3, 2026 00:15 UTC. During this time, Codespaces creation and resume operations failed in all regions. This outage was caused by a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On February 2, 2026, between 18:35 UTC and 22:15 UTC, GitHub Actions hosted runners were unavailable, with service degraded until full recovery at 23:10 UTC for standard runners and at February 3, 2026 00:30 UTC for larger runners. During this time, Actions jobs queued and timed...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
From Jan 31, 2026 00:30 UTC to Feb 2, 2026 18:00 UTC Dependabot service was degraded and failed to create 10% of Automated Pull Requests. This was due to a cluster failover that connected to a read-only database. We mitigated the incident by pausing Dependabot queues until...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
From Feb 2, 2026 17:13 UTC to Feb 2, 2026 17:36 UTC we experienced failures on ~0.02% of Git operations. While deploying an internal service, a misconfiguration caused a small subset of traffic to route to a service that was not ready. During the incident we observed the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded Experience - Failing to finalize some CCA Jobs
-
resolved
Between 2026-01-30 19:06 UTC and 2026-01-30 20:04 UTC, Copilot Coding Agent experienced sessions getting stuck, with a mismatch between the UI-reported session status and the underlying Actions and job execution state. Impacted users could observe Actions finish successfully but...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions Workflows Run Start Delays
-
resolved
On Jan 28, 2026, between 14:56 UTC and 15:44 UTC, GitHub Actions experienced degraded performance. During this time, workflows experienced an average delay of 49 seconds, and 4.7% of workflow runs failed to start within 5 minutes. The root cause was an atypical load pattern that...
Excerpts are shortened. Read the full incident on GitHub's status page.
Regression in windows runners for public repositories
-
resolved
On Jan 26, 2026, from approximately 14:03 UTC to 23:42 UTC, GitHub Actions experienced job failures on some Windows standard hosted runners. This was caused by a configuration difference in a new Windows runner type that caused the expected D: drive to be missing. About 2.5% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with repo creation
-
resolved
Between January 24, 2026,19:56 UTC and January 25, 2026, 2:50 UTC repository creation and clone were degraded. On average, the error rate was 25% and peaked at 55% of requests for repository creation. This was due to increased latency on the repositories database impacting a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On January 22, 2026, our authentication service experienced an issue between 14:00 UTC and 14:50 UTC, resulting in downstream disruptions for users. From 14:00 UTC to 14:23 UTC, authenticated API requests experienced higher-than-normal error rates, with an average of 16.9% and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Policy pages for Copilot are timing out
-
resolved
On January 21, between 17:50 and 20:53 UTC, around 350 enterprises and organizations experienced slower load times or timeouts when viewing Copilot policy pages. The issue was traced to performance degradation under load due to an issue in upstream database caching capability...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot Chat - Grok Code Fast 1 Outage
-
resolved
On Jan 21st, 2025, between 11:15 UTC and 13:00 UTC the Copilot service was degraded for Grok Code Fast 1 model. On average, more than 90% of the requests to this model failed due to an issue with an upstream provider. No other models were impacted. The issue was resolved after...
Excerpts are shortened. Read the full incident on GitHub's status page.
Run start delays in Actions
-
resolved
On January 20, 2026, between 19:08 UTC and 20:18 UTC, manually dispatched GitHub Actions workflows saw delayed job starts. GitHub products built on Actions such as Dependabot, Pages builds, and Copilot coding agent experienced similar delays. All jobs successfully completed...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident affecting actions-runner-controller
-
resolved
On January 20, 2026, between 14:39 UTC and 16:03 UTC, actions-runner-controller users experienced a 1% failure rate for API requests managing GitHub Actions runner scale sets. This caused delays in runner creation, resulting in delayed job starts for workflows targeting those...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between 2026-01-16 16:17 and 2026-01-17 02:54 UTC, some Copilot Business users were unable to access and use certain Copilot features and models. This was due to a bug with how we determine if a user has access to a feature, inadvertently marking features and models as...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues and Pull Requests
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On January 15, 2026, between 16:40 UTC and 18:20 UTC, we observed increased latency and timeouts across Issues, Pull Requests, Notifications, Actions, Repositories, API, Account Login and Alive. An average 1.8% of combined web and API requests saw failure, peaking briefly at 10%...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions workflow run and job status updates are experiencing delays
-
resolved
On January 15th, between 14:18 UTC and 15:26 UTC, customers experienced delays in status updates for workflow runs and checks. Status updates were delayed by up to 20 minutes, with a median delay of 11 minutes. The issue stemmed from an infrastructure upgrade to our database...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
-
resolved
On January 14, 2026, between 19:34 UTC and 21:36 UTC, the Webhooks service experienced a degradation that delayed delivery of some webhooks. During this window, a subset of webhook deliveries that encountered proxy tunnel errors on their initial delivery attempt were delayed by...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Incident with GitHub Copilot (GPT-5 model)
-
resolved
From January 14, 2026, at 18:15 UTC until January 15, 2026, at 11:30 UTC, GitHub Copilot users were unable to select the GPT-5 model for chat features in VS Code, JetBrains IDEs, and other IDE integrations. Users running GPT-5 in Auto mode experienced errors. Other models were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Claude Opus 4.5 model experiencing degraded performance
-
resolved
On January 14th, 2026, between approximately 10:20 and 11:25 UTC, the Copilot service experienced a degradation of the Claude Opus 4.5 model due to an issue with our upstream provider. During this time period, users encountered a 4.5% error rate when using Claude Opus 4.5. No...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot's GPT-5.1 model has degraded performance
-
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.
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Names an upstream provider: Azure.
-
resolved
Between 2026-01-13 22:20 and 2026-01-14 00:18 UTC, GitHub Code Search experienced an increase in latency and request timeouts. This was caused by some network transit links between GitHub and Azure Express Route experiencing a small error rate that contributed to applications...
Excerpts are shortened. Read the full incident on GitHub's status page.
GitHub Copilot failures
-
resolved
On January 13th, 2026, between 09:25 UTC and 10:11 UTC, GitHub Copilot experienced unavailability. During this window, error rates averaged 18% and peaked at 100% of service requests, leading to an outage of chat features across Copilot Chat, VS Code, JetBrains IDEs, and other...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
From January 9 13:11 UTC to January 12 10:17 UTC, new Linux Custom Images generated for Larger Hosted Runners were broken and not able to run jobs. Customers who did not generate new Custom Images during this period were not impacted. This issue was caused by a change to improve...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
From January 5, 2026, 00:00 UTC to January 10, 2026, 02:30 UTC, customers using the AI Controls public preview feature experienced delays in viewing Copilot agent session data. Newly created sessions took progressively longer to appear, initially hours, then eventually exceeding...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On January 8th, 2025, between approximately 00:00 and 1:30 UTC, the Copilot service experienced a degradation of the Grok Code Fast 1 model due to an issue with our upstream provider. Users encountered elevated error rates when using Grok Code Fast 1. Approximately 4.5% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some models missing in Copilot
-
resolved
On January 7th, 2026, between 17:16 and 19:33 UTC Copilot Pro and Copilot Business users were unable to use certain premium models, including Claude Opus 4.5 and GPT-5.2. This was due to a misconfiguration with Copilot models, inadvertently marking these premium models as...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On January 6, 2026 between 12:55 UTC and 17:04 UTC, the ability to download Actions artifacts from GitHub’s web interface was degraded. During this time, all attempts to download artifacts from the web interface failed. Artifact downloads via the REST API and GitHub CLI were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On January 6th, 2026, between approximately 8:41 and 10:07 UTC, the Copilot service experienced a degradation of the GPT-5.1-Codex-Max model due to an issue with our upstream provider. During this time, up to 14.17% of requests to GPT-5.1-Codex-Max failed. No other models were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On December 31, 2025, between 04:00 UTC and 22:31 UTC, all users visiting https://github.com/features/copilot were unable to load the page and were instead redirected to an error page. The issue was caused by an unexpected content change that resulted in page rendering errors....
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues and Pull Requests
-
resolved
On December 23, 2025, between 09:15 UTC and 10:32 UTC the Issues and Pull Requests search indexing service was degraded and caused search results to contain stale data up to 3 minutes old for roughly 1.3 million issues and pull requests. This was due to search indexing queues...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On December 22, 2025, between 22:01 UTC and 22:32 UTC, unauthenticated requests to github.com were degraded, resulting in slow or timed out page loads and API requests. Unauthenticated requests from Actions jobs, such as release downloads, were also impacted. Authenticated...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On December 18, 2025, between 16:25 UTC and 19:09 UTC the service underlying Copilot policies was degraded and users, organizations, and enterprises were not able to update any policies related to Copilot. No other GitHub services, including other Copilot services were impacted....
Excerpts are shortened. Read the full incident on GitHub's status page.
Intermittent networking failures across GitHub-hosted Actions runners
-
resolved
On December 18th, 2025, from 08:15 UTC to 17:11 UTC, some GitHub Actions runners experienced intermittent timeouts for Github API calls, which led to failures during runner setup and workflow execution. This was caused by network packet loss between runners in the West US region...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With Copilot
-
resolved
From 11:50-12:25 UTC, Copilot Coding Agent was unable to process new agent requests. This affected all users creating new jobs during this timeframe, while existing jobs remained unaffected. The cause of this issue was a change to the actions configuration where Copilot Coding...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot Code Review is degraded, and not returning responses to users
-
resolved
On December 15, 2025, between 15:15 UTC and 18:22 UTC, Copilot Code Review experienced a service degradation that caused 46.97% of pull request review requests to fail, requiring users to re-request a review. Impacted users saw the error message: “Copilot encountered an error...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot Grok Code Fast 1
-
resolved
On Dec 15th, 2025, between 14:00 UTC and 15:45 UTC the Copilot service was degraded for Grok Code Fast 1 model. On average, 4% of the requests to this model failed due to an issue with our upstream provider. No other models were impacted. The issue was resolved after the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruptions in Login and Signup Flows
-
resolved
Between 13:25 UTC and 18:35 UTC on Dec 11th, GitHub experienced an increase in scraper activity on public parts of our website. This scraper activity caused a low priority web request pool to increase and eventually exceed total capacity resulting in users experiencing 500...
Excerpts are shortened. Read the full incident on GitHub's status page.
We are investigating a rise in request failures on several services
-
resolved
Between 13:25 UTC and 18:35 UTC on December 11th, GitHub experienced elevated traffic to portions of GitHub.com that exceeded previously provisioned capacity for specific request types. As a result, users encountered intermittent 500 errors. Impact was most pronounced on Login,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some macOS Actions jobs routing to Ubuntu instead
-
resolved
Between December 9th, 2025 21:07 UTC and December 10th, 2025 14:52 UTC, 177 macos-14-large jobs were run on an Ubuntu larger runner VM instead of MacOS runner VMs. The impacted jobs were routed to a larger runner with incorrect metadata. We mitigated this by deleting the runner....
Excerpts are shortened. Read the full incident on GitHub's status page.
Some Actions customers experiencing run start delays
-
resolved
On December 10, 2025 between 08:50 UTC and 11:00 UTC, some GitHub Actions workflow runs experienced longer-than-normal wait times for jobs starting or completing. All jobs successfully completed despite the delays. At peak impact, approximately 8% of workflow runs were affected....
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On December 8, 2025, between 21:15 and 22:24 UTC, Copilot code completions experienced a significant service degradation. During this period, up to 65% of code completion requests failed. The root cause was an internal feature flag that caused the primary model supporting...
Excerpts are shortened. Read the full incident on GitHub's status page.
Potential disruption with our Agent Control Plane UI Settings
-
resolved
On November 26th, 2025, between approximately 02:24 UTC and December 8th, 2025 at 20:26 UTC, enterprise administrators experienced a disruption when viewing agent session activities in the Enterprise AI Controls page. During this period, users were unable to list agent session...
Excerpts are shortened. Read the full incident on GitHub's status page.
Team synchronization is experiencing delays for non enterprise managed users
-
resolved
On December 5th, 2025, between 12:00 pm UTC and 9:00 pm UTC, our Team Synchronization service experienced a significant degradation, preventing over 209,000 organization teams from syncing their identity provider (IdP) groups. The incident was triggered by a buildup of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Webhooks delivery degradation
-
resolved
On December 3, 2025, between 22:21 UTC and 23:44 UTC, the Webhooks service experienced a degradation that delayed writes of webhook delivery records to our database. During this period, many webhook deliveries were not visible in the webhook delivery UI or API for more than an...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On November 28th, 2025, between approximately 05:51 and 08:04 UTC, Copilot experienced an outage affecting the Claude Sonnet 4.5 model. Users attempting to use this model received an HTTP 400 error, resulting in 4.6% of total chat requests during this timeframe failing. Other...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On November 24, 2025, between 12:15 and 15:04 UTC, Codespaces users encountered connection issues when attempting to create a codespace after choosing the recently released VS Code Codespaces extension, version 1.18.1. Users were able to downgrade to the 1.18.0 version of the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between November 20, 2025 17:16 UTC to November, 2025 19:08 UTC some users experienced delayed or failed Git Operations for raw file downloads. On average, the error rate was less than 0.2%. This was due to a sustained increase in unauthenticated repository traffic. We mitigated...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On November 19, between 17:36 UTC and 18:04 UTC, GitHub Actions service experienced degraded performance that caused excessive latency in queueing and updating workflow runs and job statuses. Operations related to artifacts, cache, job steps and logs also had significantly...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between November 19th, 16:13UTC and November 21st, 12:22UTC, the GitHub Enterprise Importer (GEI) service was in a degraded state, during which time, customers of the service experienced a delay when reclaiming mannequins post-migration. We have taken steps to prevent similar...
Excerpts are shortened. Read the full incident on GitHub's status page.
Git operation failures
Knock-on incidents at other vendors that started during this one and name GitHub:
- Render: GitHub-backed services failing to build in all regions
- Harness: [Notification] Harness Pipeline executions may be failing due to an ongoing GitHub outage
- Augment Code: Remote agent and code review service disruption
- Retool: Source Control Temporarily Impacted (GitHub Users)
-
resolved
From Nov 18, 2025 20:30 UTC to Nov 18, 2025 21:34 UTC we experienced failures on all Git operations, including both SSH and HTTP Git client interactions, as well as raw file access. These failures also impacted products that rely on Git operations. The root cause was an expired...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between November 17, 2025 21:24 UTC and November 18, 2025 00:04 UTC the gists service was degraded and users were unable to create gists via the web UI. 100% of gist creation requests failed with a 404 response. This was due to a change in the web middleware that inadvertently...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
From Nov 17, 2025 00:00 UTC to Nov 17, 2025 15:00 UTC Dependabot was hitting a rate limit in GitHub Container Registry (GHCR) and was unable to complete about 57% of jobs. To mitigate the issue we lowered the rate at which Dependabot started jobs and increased the GHCR rate...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some users may experience failing git push and pull operations.
-
resolved
From Nov 13, 2025 14:50 UTC to Nov 13, 2025 15:01 UTC we experienced failures on all Git Push and SSH operations. An internal service became unhealthy due to a scaling configuration change. We reverted the change and are evaluating our health monitoring and processes to prevent...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On November 12, 2025, between 22:10 UTC and 23:04 UTC, Codespaces used internally at GitHub were impacted. There was no impact to external customers. The scope of impact was not clear in the initial steps of incident response, so it was considered public until confirmed...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delay in notification deliveries
-
resolved
On November 12th, 2025, from 13:10 - 17:40 UTC, notifications service was degraded, showing an increase in web notifications latency and increasing delays in notification deliveries. A change to the notifications settings access path introduced additional load to the settings...
Excerpts are shortened. Read the full incident on GitHub's status page.
Larger hosted runners experiencing delays
-
resolved
On November 11, 2025, between 16:28 UTC and 20:54 UTC, GitHub Actions larger hosted runners experienced degraded performance, with 0.4% of overall workflow runs and 8.8% of larger hosted runner jobs failing to start within 5 minutes. The majority of impact was mitigated by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
Between November 5, 2025 23:27 UTC and November 6, 2025 00:06 UTC, ghost text requests experienced errors from upstream model providers. This was a continuation of the service disruption for which we statused Copilot earlier that day, although more limited in scope. During the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Copilot Code Completions partially unavailable
-
resolved
On November 5, 2025, between 21:46 and 23:36 UTC, ghost text requests experienced errors from upstream model providers that resulted in 0.9% of users seeing elevated error rates. During the service disruption, users were automatically re-routed to healthy model hosts but may...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With GitHub Enterprise Importer
-
resolved
On November 4, 2025, GitHub Enterprise Importer experienced a period of degraded migration performance and elevated error rates between 18:04 UTC and 23:36 UTC. During this interval customers queueing and running migrations experienced prolonged queue times and slower...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Packages
-
resolved
On November 3, 2025, between 14:10 UTC and 19:20 UTC, GitHub Packages experienced degraded performance, resulting in failures for 0.5% of Nuget package download requests. The incident resulted from an unexpected change in usage patterns affecting rate limiting infrastructure in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with using workflow_dispatch for Actions
-
resolved
On November 1, 2025, between 2:30 UTC and 6:14 UTC, Actions workflows could not be triggered manually from the UI. This impacted all customers queueing workflows from the UI for most of the impact window. The issue was caused by a faulty code change in the UI, which was promptly...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On October 30th we shipped a change that broke 3 links in the "Solutions" dropdown of the marketing navigation seen on https://github.com/home. We noticed internally the broken links and declared an incident so our users would know no other functionality was impacted. We were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Copilot Bing search tool
-
resolved
A cloud resource used by the Copilot bing-search tool was deleted as part of a resource cleanup operation. Once this was discovered, the resource was recreated. Going forward, more effective monitoring will be put in place to catch this issue earlier.
Excerpts are shortened. Read the full incident on GitHub's status page.
Experiencing connection issues across Actions, Codespaces, and possibly other services
-
resolved
On October 29th, 2025 between 14:07 UTC and 23:15 UTC, multiple GitHub services were degraded due to a broad outage in one of our service providers: - Users of Codespaces experienced failures connecting to new and existing Codespaces through VSCode Desktop or Web. On average the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Inconsistent results when using the Haiku 4.5 model
-
resolved
From October 28th at 16:03 UTC until 17:11 UTC, the Copilot service experienced degradation due to an infrastructure issue which impacted the Claude Haiku 4.5 model, leading to a spike in errors affecting 1% of users. No other models were impacted. The incident was caused due to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with viewing some repository pages from large organizations
-
resolved
Between October 23, 2025 19:27:29 UTC and October 27, 2025 17:42:42 UTC, users experienced timeouts when viewing repository landing pages. We observed the timeouts for approximately 5,000 users across less than 1,000 repositories including forked repositories. The impact was...
Excerpts are shortened. Read the full incident on GitHub's status page.
githubstatus.com was unavailable UTC 2025 Oct 24 02:55 to 03:13
-
resolved
On UTC Oct 24 2:55 - 3:15 AM, githubstatus.com was unreachable due to service interruption with our status page provider. During this time, GitHub systems were not experiencing any outages or disruptions. We are working our vendor to understand how to improve availability of...
Excerpts are shortened. Read the full incident on GitHub's status page.
git operations over ssh seeing increased latency on github.com
-
resolved
From Oct 22, 2025 15:00 UTC to Oct 24, 2025 14:30 UTC git operations via SSH saw periods of increased latency and failed requests, with failure rates ranging from 1.5% to a single spike of 15%. Git operations over http were not affected. This was due to resource exhaustion on...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions - Larger hosted runners
-
resolved
On October 23, 2025, between 15:54 UTC and 19:20 UTC, GitHub Actions larger hosted runners experienced degraded performance, with 1.4% of overall workflow runs and 29% of larger hosted runner jobs failing to start or timing out within 5 minutes. The full set of contributing...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with API Requests
-
resolved
On October 22, 2025, between 14:06 UTC and 15:17 UTC, less than 0.5% of web users experienced intermittent slow page loads on GitHub.com. During this time, API requests showed increased latency, with up to 2% timing out. The issue was caused by elevated loads on one of our...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On October 21, 2025, between 13:30 and 17:30 UTC, GitHub Enterprise Cloud Organization SAML Single Sign-On experienced degraded performance. Customers may have been unable to successfully authenticate into their GitHub Organizations during this period. Organization SAML recorded...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On October 21, 2025, between 07:55 UTC and 12:20 UTC, GitHub Actions experienced degraded performance. During this time, 2.11% workflow runs failed to start within 5 minutes, with an average delay of 8.2 minutes. The root cause was increased latency on a node in one of our Redis...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Grok Code Fast 1 in Copilot
-
resolved
From October 20th at 14:10 UTC until 16:40 UTC, the Copilot service experienced degradation due to an infrastructure issue which impacted the Grok Code Fast 1 model, leading to a spike in errors affecting 30% of users. No other models were impacted. The incident was caused due...
Excerpts are shortened. Read the full incident on GitHub's status page.
Codespaces creation failling
-
resolved
On October 20, 2025, between 08:05 UTC and 10:50 UTC the Codespaces service was degraded, with users experiencing failures creating new codespaces and resuming existing ones. On average, the error rate for codespace creation was 39.5% and peaked at 71% of requests to the service...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with push notifications
-
resolved
On October 17th, 2025, between 12:51 UTC and 14:01 UTC, mobile push notifications failed to be delivered for a total duration of 70 minutes. This affected github.com and GitHub Enterprise Cloud in all regions. The disruption was related to an erroneous configuration change to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On October 14th, 2025, between 18:26 UTC and 18:57 UTC a subset of unauthenticated requests to the commit endpoint for certain repositories received 503 errors. During the event, the average error rate was 3%, peaking at 3.5% of total requests. This event was triggered by a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with GPT-5-mini in Copilot
-
resolved
On Oct 14th, 2025, between 13:34 UTC and 16:00 UTC the Copilot service was degraded for GPT-5 mini model. On average, 18% of the requests to GPT-5 mini failed due to an issue with our upstream provider. We notified the upstream provider of the problem as soon as it was detected...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On October 9th, 2025, between 14:35 UTC and 15:21 UTC, a network device in maintenance mode that was undergoing repairs was brought back into production before repairs were completed. Network traffic traversing this device experienced significant packet loss. Authenticated users...
Excerpts are shortened. Read the full incident on GitHub's status page.
Multiple GitHub API endpoints are experiencing errors
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
Between 13:39 UTC and 13:42 UTC on Oct 9, 2025, around 2.3% of REST API calls and 0.4% Web traffic were impacted due to the partial rollout of a new feature that had more impact on one of our primary databases than anticipated. When the feature was partially rolled out it...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On October 7, 2025, between 7:48 PM UTC and October 8, 12:05 AM UTC (approximately 4 hours and 17 minutes), the audit log service was degraded, creating a backlog and delaying availability of new audit log events. The issue originated in a third-party dependency. We mitigated...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On October 3rd, between approximately 10:00 PM and 11:30 Eastern, the Copilot service experienced degradation due to an issue with our upstream provider. Users encountered elevated error rates when using the following Claude models: Claude Sonnet 3.7, Claude Opus 4, Claude Opus...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded Gemini 2.5 Pro experience in Copilot
-
resolved
Between October 1st, 2025 at 1 AM UTC and October 2nd, 2025 at 10:33 PM UTC, the Copilot service experienced a degradation of the Gemini 2.5 Pro model due to an issue with our upstream provider. Before 15:53 UTC on October 1st, users experienced higher error rates with large...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded Performance for GitHub Actions MacOS Runners
-
resolved
On October 1, 2025 between 07:00 UTC and 17:20 UTC, Mac hosted runner capacity for Actions was degraded, leading to timed out jobs and long queue times. On average, the error rate was 46% and peaked at 96% of requests to the service. XL and Intel runners recovered by 10:10 UTC,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Gemini 2.5 Pro and Gemini 2.0 Flash in Copilot
-
resolved
On September 29, 2025, between 17:53 and 18:42 UTC, the Copilot service experienced a degradation of the Gemini 2.5 model due to an issue with our upstream provider. Approximately 24% of requests failed, affecting 56% of users during this period. No other models were impacted....
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On September 29, 2025 between 16:26 UTC and 17:33 UTC the Copilot API experienced a partial degradation causing intermittent erroneous 404 responses for an average of 0.2% of GitHub MCP server requests, peaking at times around 2% of requests. The issue stemmed from an upgrade of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On September 26, 2025 between 16:22 UTC and 18:32 UTC raw file access was degraded for a small set of four repositories. On average, raw file access error rate was 0.01% and peaked at 0.16% of requests. This was due to a caching bug exposed by excessive traffic to a handful of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On September 23, 2025, between 15:29 UTC and 17:38 UTC and also on September 24, 2025 between 15:02 UTC and 15:12, email deliveries were delayed up to 50 minutes which resulted in significant delays for most types of email notifications. This occurred due to an unusually high...
Excerpts are shortened. Read the full incident on GitHub's status page.
Claude Opus 4 is experiencing degraded performance
-
resolved
On September 24th, 2025, between 08:02 UTC and 09:11 UTC the Copilot service was degraded for Claude Opus 4 and Claude Opus 4.1 requests. On average, 22% of requests failed for Claude Opus 4 and 80% of requests for Claude Opus 4.1. This was due to an upstream provider returning...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
Between 20:06 UTC September 23 and 04:58 UTC September 24, 2025, the Copilot service experienced degraded availability for Claude Sonnet 4 and 3.7 model requests. During this period, 0.46% of Claude 4 requests and 7.83% of Claude 3.7 requests failed. The reduced availability...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pages and Actions
-
resolved
On September 23, between 17:11 and 17:40 UTC, customers experienced failures and delays when running workflows on GitHub Actions and building or deploying GitHub Pages. The issue was caused by a faulty configuration change that disrupted service to service communication in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On September 23, 2025, between 15:29 UTC and 17:38 UTC and also on September 24, 2025 between 14:02 UTC and 15:12 UTC, email deliveries were delayed up to 50 minutes which resulted in significant delays for most types of email notifications. This occurred due to an unusually...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
On September 17, 2025 between 13:23 and 16:51 UTC some users in West Europe experienced issues with Codespaces that had shut down due to network disconnections and subsequently failed to restart. Codespace creations and resumes were failed over to another region at 15:01 UTC....
Excerpts are shortened. Read the full incident on GitHub's status page.
Unauthenticated LFS requests for public repos are returning unexpected 401 errors
-
resolved
Between 16:26 UTC on September 15th and 18:30 UTC on September 16th, anonymous REST API calls to approximately 20 endpoints were incorrectly rejected because they were not authenticated. While this caused unauthenticated requests to be rejected by these endpoints, all...
Excerpts are shortened. Read the full incident on GitHub's status page.
Creating GitHub apps using the REST API will fail with a 401 error
-
resolved
Between 16:26 UTC on September 15th and 18:30 UTC on September 16th, anonymous REST API calls to approximately 20 endpoints were incorrectly rejected because they were not authenticated. While this caused unauthenticated requests to be rejected by these endpoints, all...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On September 15th between 17:55 and 18:20 UTC, Copilot experienced degraded availability for all features. This was due a partial deployment of a feature flag to a global rate limiter. The flag triggered behavior that unintentionally rate limited all requests, resulting in 100%...
Excerpts are shortened. Read the full incident on GitHub's status page.
Repository search is degraded
-
resolved
At around 18:45 UTC on Friday, September 12, 2025, a change was deployed that unintentionally affected search index management. As a result, approximately 25% of repositories were temporarily missing from search results. By 12:45 UTC on Saturday, September 14, most missing...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On September 10, 2025 between 13:00 and 14:15 UTC, Actions users experienced failed jobs and run start delays for Ubuntu 24 and Ubuntu 22 jobs on standard runners in private repositories. Additionally, larger runner customers experienced run start delays for runner groups with...
Excerpts are shortened. Read the full incident on GitHub's status page.
Degraded REST API success rates for some customers
-
resolved
On September 4, 2025 between 15:30 UTC and 20:00 UTC the REST API endpoints git/refs, git/refs/*, and git/matching-refs/* were degraded and returned elevated errors for repositories with reference counts over 22k. On average, the request error rate to these specific endpoints...
Excerpts are shortened. Read the full incident on GitHub's status page.
Loading avatars might fail for a 0.5% of total users and 100% users around the Arabian Peninsula. We are investigating.
-
resolved
Between August 21, 2025 at 15:00 UTC, and September 2, 2025 at 15:22 UTC the avatars.githubusercontent.com image service was degraded and failed to display user avatars for users in the Middle East. During this time, avatar images appeared broken on github.com for affected...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On August 27, 2025 between 20:35 and 21:17 UTC, Copilot, Web and REST API traffic experienced degraded performance. Copilot saw an average of 36% of requests fail with a peak failure rate of 77%. Approximately 2% of all non-Copilot Web and REST API traffic requests failed. This...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On August 21, 2025, from approximately 15:37 UTC to 18:10 UTC, customers experienced increased delays and failures when starting jobs on GitHub Actions using standard hosted runners. This was caused by connectivity issues in our East US region, which prevented runners from...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues and Git Operations
-
resolved
On August 21st, 2025, between 6:15am UTC and 6:25am UTC Git and Web operations were degraded and saw intermittent errors. On average, the error rate was 1% for API and Web requests. This was due to database infrastructure automated maintenance reducing capacity below our...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between 15:49 and 16:37 UTC on 20 Aug 2025, creating a new GitHub account via the web signup page consistently returned server errors, and users were unable to complete signup during this 48-minute window. We detected the issue at 16:04 UTC and restored normal signup...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On August 19, 2025, between 13:35 UTC and 14:33 UTC, GitHub search was in a degraded state. When searching for pull requests, issues, and workflow runs, users would have seen some slow, empty or incomplete results. In some cases, pull requests failed to load. The incident was...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Packages
-
resolved
On August 14, 2025, between 17:50 UTC and 18:08 UTC, the Packages NPM Registry service was degraded. During this period, NPM package uploads were unavailable and approximately 50% of download requests failed. We identified the root cause as a sudden spike in Packages publishing...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On August 14, 2025, between 02:30 UTC and 06:14 UTC, GitHub Actions was degraded. On average, 3% of workflow runs were delayed by at least 5 minutes. The incident was caused by an outage in a downstream dependency that led to failures in backend service connectivity in one...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with search on GitHub we are seeing increased failure rates
-
resolved
On August 12, 2025, between 13:30 UTC and 17:14 UTC, GitHub search was in a degraded state. Users experienced inaccurate or incomplete results, failures to load certain pages (like Issues, Pull Requests, Projects, and Deployments), and broken components like Actions workflow and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On August 11, 2025, from 18:41 to 18:57 UTC, GitHub customers experienced errors and increased latency when loading GitHub’s web interface. During this time, a configuration change to improve our UI deployment system caused a surge in requests to a backend datastore. This change...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
-
resolved
At 15:33 UTC on August 5, 2025, we initiated a production database migration to drop a column from a table backing pull request functionality. While the column was no longer in direct use, our ORM continued to reference the dropped column in a subset of pull request queries. As...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with pull requests
Knock-on incidents at other vendors that started during this one and name GitHub:
- Cursor: BugBot and Background Agent Service Degradation due to GitHub Outage
- Cypress Cloud: GitHub Incident affecting Cypress Integrations
-
resolved
At 15:33 UTC on August 5, 2025, we initiated a production database migration to drop a column from a table backing pull request functionality. While the column was no longer in direct use, our ORM continued to reference the dropped column in a subset of pull request queries. As...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between 06:04 UTC to 10:55 UTC on August 1, 2025, 100% of users attempting to sign up with an email and password experienced errors. Social signup was not affected. Once the problem became clear, the offending code was identified and a change was deployed to resolve the issue....
Excerpts are shortened. Read the full incident on GitHub's status page.
Increase in 429s for Git Operations
-
resolved
Public Summary Draft Between July 28, 2025 16:31 UTC to July 29, 2025 12:05 UTC users saw degraded Git Operations for raw file downloads. On average, the error rate was .005%, with a peak error rate of 3.89%. This was due to a sustained increase in unauthenticated repository...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues, API Requests and Pull Requests
-
resolved
Between July 28, 2025, 22:23:00 UTC and July 29, 2025 02:06:00 UTC, GitHub experienced degraded performance across multiple services including API, Issues, GraphQL and Pull Requests. During this time, approximately 4% of Web and API requests resulted in 500 errors. This incident...
Excerpts are shortened. Read the full incident on GitHub's status page.
GitHub Enterprise Importer migrations are stalled
Names an upstream provider: Azure.
-
resolved
Between approximately 21:41 UTC July 28th and 03:15 UTC July 29th, GitHub Enterprise Importer (GEI) operated in a degraded state where migrations could not be processed. Our investigation found that a component of the GEI infrastructure had been improperly taken out of service...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between July 28, 2025 16:31 UTC to July 29, 2025 12:05 UTC users saw degraded Git Operations for raw file downloads. On average, the error rate was .005%, with a peak error rate of 3.89%. This was due to a sustained increase in unauthenticated repository traffic. We mitigated...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions Hosted Runners
-
resolved
On July 23rd, 2025, from approximately 14:30 to 16:30 UTC, GitHub Actions experienced delayed job starts for workflows in private repos using Ubuntu-24 standard hosted runners. This was due to resource provisioning failures in one of our datacenter regions. During this period,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot and Claude Sonnet 4
-
resolved
On July 22nd, 2025, between 17:58 and 18:35 UTC, the Copilot service experienced degraded availability for Claude Sonnet 4 requests. 4.7% of Claude 4 requests failed during this time. No other models were impacted. The issue was caused by an upstream problem affecting our...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some Copilot Models Experiencing Degraded Performance
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On July 21, 2025, between 07:20 UTC and 08:00 UTC, the Copilot service experienced degraded availability for Claude 4 requests. 2% of Claude 4 requests failed during this time. The issue was caused by an upstream problem affecting our ability to serve requests. We mitigated by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On July 21st, 2025, between 07:00 UTC and 09:45 UTC the API, Codespaces, Copilot, Issues, Package Registry, Pull Requests and Webhook services were degraded and experienced dropped requests and increased latency. At the peak of this incident (a 2 minute period around 07:00 UTC)...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On July 16, 2025, between 05:20 UTC and 08:30 UTC, the Copilot service experienced degraded availability for Claude 3.7 requests. Around 10% of Claude 3.7 requests failed during this time. The issue was caused by an upstream problem affecting our ability to serve requests. We...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Disruption with some GitHub Services
-
resolved
On 15 July, between 19:55 and 19:58 UTC, requests to GitHub had a high failure rate while successful requests suffered up to 10x expected latency. Browser-based requests saw a failure rate of up to 20%, GraphQL had up to a 9% failure rate and 2% of REST API requests failed. Any...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On July 8, 2025, between 14:20 UTC and 16:30 UTC, GitHub Actions service experienced degraded performance leading to delays in updates to Actions workflow runs including missing logs and delayed run status. During this period, 1.07% of Actions workflow runs experienced delayed...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On July 7, 2025, between 21:14 UTC and 22:34 UTC, Copilot coding Agent was degraded and non-responsive to issue assignment. Impact was limited to internal GitHub staff because the feature flag gating a newly released feature was enabled on internal development setups and not in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On July 7th, 2025, between 18:20 UTC and 22:10 UTC the Actions service was degraded for GitHub Larger Hosted and scale set runners. During this time window, 9% of GitHub Larger Hosted Runners and scale set jobs saw a delay of at least 5 minutes before being assigned to a runner....
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On 7/3/2025, between 3:22 AM and 7:12 AM UTC, customers were prevented from SSO authorizing Personal Access Tokens and SSH keys via the GitHub UI. Approximately 1300 users were impacted. A code change modified the content type of the response returned by the server, causing a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On July 2, 2025, between 1:35 AM UTC and 16:23 UTC, the GitHub Enterprise Importer (GEI) migration service experienced degraded performance and slower-than-normal migration queue processing times. This incident was triggered due to a migration including an abnormally large...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On July 2nd, 2025, between approximately 08:40 and 10:16 UTC, the Copilot service experienced degradation due to an infrastructure issue which impacted the Claude Sonnet 4 model, leading to a spike in errors. No other models were impacted. The issue was mitigated by rebalancing...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Claude 3.7 Sonnet in Copilot Chat
-
resolved
On June 30th, 2025, between approximately 18:20 and 19:55 UTC, the Copilot service experienced a degradation of the Claude Sonnet 3.7 model due to an issue with our upstream provider. Users encountered elevated error rates when using Claude Sonnet 3.7. No other models were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With Actions
-
resolved
Due to a degradation of one instance of our internal message delivery service, a percentage of jobs started between 06/30/2025 19:18 UTC and 06/30/2025 19:50 UTC failed, and are no longer retry-able. Runners assigned to these jobs will automatically recover within 24 hours, but...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On June 26, 2025, between 17:10 UTC and 23:30 UTC, around 40% of attempts to create a repository from a template repository failed. The failures were an unexpected result of a gap in testing and observability. We mitigated the incident by rolling back the deployment. We are...
Excerpts are shortened. Read the full incident on GitHub's status page.
GitHub Enterprise Importer delays
-
resolved
On June 26th, between 14:42UTC and 18:05UTC, the GitHub Enterprise Importer (GEI) service was in a degraded state, during which time, customers of the service experienced extended repository migration durations. Our investigation found that the combined effect of several...
Excerpts are shortened. Read the full incident on GitHub's status page.
Repository Navigation Bar Missing in GitHub Enterprise Cloud
-
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.
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with the GitHub mobile android application
-
resolved
Between June 19th, 2025 11:35 UTC and June 20th, 2025 11:20 UTC the GitHub Mobile Android application was unable to login new users. The iOS app was unaffected. This was due to a new GitHub App feature being tested internally, which was inadvertently enforced for all...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On June 18, 2025 between 22:20 UTC and 23:00 UTC the Claude Sonnet 3.7 and Claude Sonnet 4 models for GitHub Copilot Chat experienced degraded performance. During the impact, some users would receive an immediate error when making a request to a Claude model. This was due to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Partial Actions Cache degradation
-
resolved
On June 18, 2025, between 08:21 UTC and 18:47 UTC, some Actions jobs experienced intermittent failures downloading from the Actions Cache service. During the incident, 17% of workflow runs experienced cache download failures, resulting in a warning message in the logs and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Partial Degradation in Issues Experience
-
resolved
On June 18, 2025, between 15:15 UTC and 19:29 UTC, the Issues service was degraded, and certain GraphQL queries accessing the `ReactionGroup.reactors` field returned errors. Our query routing infrastructure was impacted by exceptions from a particular database migration,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with multiple GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
- Socket: High GitHub App Error Rate
- Expo: Elevated GitHub errors
- Render: GitHub-based deploys erroring
-
resolved
On June 17, 2025, between 19:32 UTC and 20:03 UTC, an internal routing policy deployment to a subset of network devices caused reachability issues for certain network address blocks within our datacenters. Authenticated users of the github.com UI experienced 3-4% error rates for...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
Multiple services critical to GitHub's attestation infrastructure experienced an outage which prevented Fulcio from issuing signing certificates. During the outage, GitHub customers who use the "actions/attest-build-provenance" action from public repositories were not able to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some Copilot chat models are failing requests
-
resolved
On June 12, 2025, between 17:55 UTC and 21:07 UTC the GitHub Copilot service was degraded and experienced unavailability for Gemini models and reduced availability for Claude models. Users experienced significantly elevated error rates for code completions, slow response times,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between 2025-06-10 12:25 UTC and 2025-06-11 01:51 UTC, GitHub Enterprise Cloud (GHEC) customers with approximately 10,000 or more users, saw performance degradation and 5xx errors when loading the Enterprise Settings’ People management page. Less than 2% of page requests...
Excerpts are shortened. Read the full incident on GitHub's status page.
Codespaces billing is delayed
-
resolved
On June 10, 2025, between 12:15 UTC and 19:04 UTC, Codespaces billing data processing experienced delays due to capacity issues in our worker pool. Approximately 57% of codespaces were affected during this incident, during which some customers may have observed incomplete or...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
-
resolved
On June 10, 2025, between 14:28 UTC and 14:45 UTC the pull request service experienced a period of degraded performance, resulting in merge error rates exceeding 1%. The root cause was an overloaded host in our Git infrastructure. We mitigated the incident by removing this host...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With Copilot
-
resolved
On June 6, 2025, an update to mitigate a previous incident led to automated scaling of database infrastructure used by Copilot Coding Agent. The clients of the service were not implemented to automatically handle an extra partition. Hence it was unable to retrieve data across...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On June 6, 2025, between 00:21 UTC to 12:40 UTC the Copilot service was degraded and a subset of Copilot Free users were unable to sign up for or use the Copilot Free service on github.com. This was due to a change in licensing code that resulted in some users losing access...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On June 5th, 2025, between 17:47 UTC and 19:20 UTC the Actions service was degraded, leading to run start delays and intermittent job failures. During this period, 47.2% of runs had delayed starts, and 21.0% of runs failed. The impact extended beyond Actions itself - 60% of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On June 4, 2025, between 14:35 UTC and 15:50 UTC , the Actions service experienced degradation, leading to run start delays. During the incident, about 15.4% of all workflow runs were delayed by an average of 16 minutes. An unexpected load pattern revealed a scaling issue in our...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On May 30, 2025, between 08:10 UTC and 16:00 UTC, the Microsoft Teams GitHub integration service experienced a complete service outage. During this period, the service was unable to deliver notifications or process user requests, resulting in a 100% error rate for all...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On May 28, 2025, from approximately 09:45 UTC to 14:45 UTC, GitHub Actions experienced delayed job starts for workflows in public repos using Ubuntu-24 standard hosted runners. This was caused by a misconfiguration in backend caching behavior after a failover, which led to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On May 27, 2025, between 09:31 UTC and 13:31 UTC, some Actions jobs experienced failures uploading to and downloading from the Actions Cache service. During the incident, 6% of all workflow runs couldn’t upload or download cache entries from the service, resulting in a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Incident with Git Operations
-
resolved
Between 10:00 and 20:00 UTC on May 27, a change to our git proxy service resulted in some git client implementations not being able to consistently push to GitHub. Reverting the change resulted in an immediate resolution of the problem for all customers. The inflated time to...
Excerpts are shortened. Read the full incident on GitHub's status page.
We're experiencing errors
Knock-on incidents at other vendors that started during this one and name GitHub:
- Vercel: GitHub Deployment and API Errors
- Snyk: GitHub API is degraded
- CircleCI: Dropped webhooks for GitHub pipelines
- Cypress Cloud: GitHub Authentication Degradation
-
resolved
On May 26, 2025, between 06:20 UTC and 09:45 UTC GitHub experienced broad failures across a variety of services (API, Issues, Git, etc). These were degraded at times, but peaked at 100% failure rates for some operations during this time. On May 23, a new feature was added to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On May 23, 2025, between 17:40 UTC and 18:30 UTC public API and UI requests to read and write Git repository content were degraded and triggered user-facing 500 responses. On average, the error rate was 61% and peaked at 88% of requests to the service. This was due to the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delayed GitHub Actions Jobs
-
resolved
On May 22, 2025, between 07:06 UTC and 09:10 UTC, the Actions service experienced degradation, leading to run start delays. During the incident, about 11% of all workflow runs were delayed by an average of 44 minutes. A recently deployed change contained a defect that caused...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
-
resolved
A change to the webhooks UI removed the ability to add webhooks. The timeframe of this impact was between May 20th, 2025 20:40 UTC and May 21st, 2025 12:55 UTC. Existing webhooks, as well as adding webhooks via the API were unaffected. The issue has been fixed.
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Copilot
-
resolved
On May 20, 2025, between 18:18 UTC and 19:53 UTC, Copilot Code Completions were degraded in the Americas. On average the error rate was 50% of requests to the service in the affected region. This was due to a misconfiguration in load distribution parameters after a scale down...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated error rates for Claude Sonnet 3.7
-
resolved
On May 20, 2025, between 12:09 PM UTC and 4:07 PM UTC, the GitHub Copilot service experienced degraded availability, specifically for the Claude Sonnet 3.7 model. During this period, the success rate for Claude Sonnet 3.7 requests was highly variable, down to approximately 94%...
Excerpts are shortened. Read the full incident on GitHub's status page.
GitHub Enterprise Importer (GEI) is experiencing degraded throughput
-
resolved
Between May 16, 2025, 1:21 PM UTC and May 17, 2025, 2:26 AM UTC, the GitHub Enterprise Importer service was degraded and experienced slow processing of customer migrations. Customers may have seen extended wait times for migrations to start or complete. This incident was...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On May 16th, 2025, between 08:42:00 UTC and 12:26:00 UTC, the data store powering the Audit Log API service experienced elevated latency resulting in higher error rates due to timeouts. About 3.8% of Audit Log API queries for Git events experienced timeouts. The data store team...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Gemini 2.5 Pro
-
resolved
Between May 15, 2025 10:10 UTC and May 15, 2025 22:58 UTC the Copilot service was degraded and returned a high volume of internal server errors for requests targeting Gemini 2.5 Pro, a public preview model. This was due to a high volume of rate limiting by the upstream model...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On May 15, 2025, between 00:08 AM UTC and 10:21 AM UTC, customers were unable to create fine-grained Personal Access Tokens (PATs) on github.com. This incident was triggered by a recent code change to our front end that unintentionally affected the way certain pages loaded and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Gemini 2.5 Pro model
-
resolved
Between May 14, 2025 14:16 UTC and May 15, 2025 01:02 UTC the Copilot service was degraded and returned a high volume of internal server errors for requests targeting Gemini 2.5 Pro, a public preview model. On average, the error rate for Gemini 2.5 Pro was 19.6% and peaked at...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Git Operations
-
resolved
On May 8, 2025, between 14:40 UTC and 16:27 UTC the Git Operations service was degraded causing some pushes and merges to fail. On average, the error rate was 1.4% with a peak error rate of 2.24%. This was due to a configuration change which unexpectedly led a critical service...
Excerpts are shortened. Read the full incident on GitHub's status page.
Issue Attachments Failing to Upload
-
resolved
On May 1, 2025 from 22:09 UTC to 23:13 UTC, the Issues service was degraded and users weren't able to upload attachments. The root cause was identified to be a new feature which added a custom header to all client-side HTTP requests, causing a CORS errors when uploading...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Pull Request Ref Updates
-
resolved
On April 30, 2025, between 8:02 UTC and 9:05 UTC, the Pull Requests service was degraded and failed to update refs for repositories with higher traffic. This was due to a repository migration creating a larger than usual number of enqueued jobs. This resulted in an increase in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Delays for web and email notification delivery
-
resolved
On April 29th, 2025, between 8:40am UTC and 12:50pm UTC the notifications service was degraded and stopped delivering most web and email notifications as well as some mobile push notifications. This was due to a large and faulty schema migration that rendered a set of database...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Git Operations, API Requests and Issues
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On April 28th, 2025, between 4AM and 11AM UTC, ~0.5% of customers experienced HTTP 500 or 429 responses for raw file access (via the GitHub website and APIs). Additionally, ~0.5% of customers may have seen slow pull request page loads and increased timeouts in the GraphQL API....
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Starting at 19:13:50 UTC, the service responsible for importing Git repositories began experiencing errors that impacted both GitHub Enterprise Importer migrations and the GitHub Importer which were restored at 22:11:00 UTC. At the time, 837 migrations across 57 organizations...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues, API Requests and Pages
-
resolved
On April 23, 2025, between 07:00 UTC and 07:20 UTC, multiple GitHub services experienced degradation caused by resource contention on database hosts. The resulting error rates, which ranged from 2–5% of total requests, led to intermittent service disruption for users. The issue...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
-
resolved
On April 16, 2025 between 3:22:36 PM UTC and 5:26:55 PM UTC the Pull Request service was degraded. On average, 0.7% of page views were affected. This primarily affected logged-out users, but some logged-in users were affected as well. This was due to an error in how certain Pull...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 15th during regular testing we found a bug in our Copilot Metrics Pipeline infrastructure causing some data used to aggregate Copilot usage for the Copilot Metrics API to not be ingested. As a result of the bug, customer metrics in the Copilot Metrics API would have...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services for Safari Users
-
resolved
On April 15, 2025 from 12:45 UTC to 13:56 UTC, access to GitHub.com was restricted for logged out users using WebKit-based browsers, such as Safari and various mobile browsers. During the impacting time, roughly 6.6M requests were unsuccessful. This issue was caused by a...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Access from China temporarily blocked for users that were not logged in
-
resolved
Due to a configuration change with unintended impact, some users that were not logged in who tried to visit GitHub.com from China were temporarily unable to access the site. For users already logged in, they could continue to access the site successfully. Impact started...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
On April 11 from 3:05am UTC to 3:44am UTC, approximately 75% of Codespaces users faced create and start failures. These were caused by manual configuration changes to an internal dependency. We reverted the changes and immediately restored service health. We are working on safer...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some Pull Requests stuck in processing state
-
resolved
On April 9, 2025, between 11:27 UTC and 12:39 UTC, the Pull Requests service was degraded and experienced delays in processing updates. At peak, approximately 1–1.5% of users were affected by delays in synchronizing pull requests. During this period, users may have seen a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests
-
resolved
On April 9, 2025, between 7:01 UTC and 9:31 UTC, the Pull Requests service was degraded and failed to update refs for repositories with higher traffic. This was due to a repository migration creating a larger than usual number of enqueued jobs. This resulted in an increase in...
Excerpts are shortened. Read the full incident on GitHub's status page.
Vision requests are unavailable for certain models on Copilot Chat on github.com
-
resolved
On 2025-04-08, between 00:42 and 18:05 UTC, as we rolled out an updated version of our GPT 4o model, we observed that vision capabilities for GPT-4o for Copilot Chat in GitHub were intermittently unavailable. During this period, customers may have been unable to upload image...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 7, 2025 between 2:15:37 AM UTC and 2:31:14 AM UTC, multiple GitHub services were degraded. Requests to these services returned 5xx errors at a high rate due to an internal database being exhausted by our Codespaces service. The incident mitigated on its own. We have...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On 2025-04-03, between 6:13:27 PM UTC and 7:12:00 PM UTC the docs.github.com service was degraded and errored. On average, the error rate was 8% and peaked at 20% of requests to the service. This was due to a misconfiguration and elevated requests. We mitigated the incident by...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between 2025-03-27 12:00 UTC and 2025-04-03 16:00 UTC, the GitHub Enterprise Cloud Dormant Users report was degraded and falsely indicated that dormant users were active within their business. This was due to increased load on a database from a non-performant query. We mitigated...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On April 1st, 2025, between 08:17:00 UTC and 09:29:00 UTC the data store powering the Audit Log service experienced elevated errors resulting in an approximate 45 minute delay of Audit Log Events. Our systems maintained data continuity and we experienced no data loss. The delay...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between March 29 7:00 UTC and March 31 17:00 UTC users were unable to unsubscribe from GitHub marketing email subscriptions due to a service outage. Additionally, on March 31, 2025 from 7:00 UTC to 16:40 UTC users were unable to submit eBook and event registration forms on...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Disruption with Pull Request Ref Updates
-
resolved
Beginning at 21:24 UTC on March 28 and lasting until 21:50 UTC, some customers of github.com had issues with PR tracking refs not being updated due to processing delays and increased failure rates. We did not status before we completed the rollback, and the incident is currently...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
This incident was opened by mistake. Public services are currently functional.
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with Pull Request Ref Updates
-
resolved
Between March 27, 2025, 23:45 UTC and March 28, 2025, 01:40 UTC the Pull Requests service was degraded and failed to update refs for repositories with higher traffic activity. This was due to a large repository migration that resulted in a larger than usual number of enqueued...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Incident with Migrations Submitted Via GitHub UI
-
resolved
Between 2024-03-23 18:10 UTC and 2024-03-24 16:10 UTC, migration jobs submitted through the GitHub UI experienced processing delays and increased failure rates. This issue only affected migrations initiated via the web interface. Migrations started through the API or the command...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On March 21st, 2025, between 11:45 UTC and 13:20 UTC, users were unable to interact with GitHub Copilot Chat in GitHub. The issue was caused by a recently deployed Ruby change that unintentionally overwrote a global value. This led to GitHub Copilot Chat in GitHub being...
Excerpts are shortened. Read the full incident on GitHub's status page.
Intermittent GitHub Actions workflow failures
-
resolved
On March 21st, 2025, between 05:43 UTC and 08:49 UTC, the Actions service experienced degradation, leading to workflow run failures. During the incident, approximately 2.45% of workflow runs failed due to an infrastructure failure. This incident was caused by intermittent...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
On March 21, 2025 between 01:00 UTC and 02:45 UTC, the Codespaces service was degraded and users in various regions experienced intermittent connection failures. The peak error error was 30% of connection attempts across 38% of Codespaces. This was due to a service deployment....
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pages
-
resolved
On March 20, 2025, between 19:24 UTC and 20:42 UTC the GitHub Pages experience was degraded and returned 503s for some customers. We saw an error rate of roughly 2% for Pages views, and new page builds were unable to complete successfully before timing out. This was due to...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions: Queue Run Failures
-
resolved
On March 18th, 2025, between 23:20 UTC and March 19th, 2025 00:15 UTC, the Actions service experienced degradation, leading to run start delays. During the incident, about 0.3% of all workflow runs queued during the time failed to start, about 0.67% of all workflow runs were...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On March 18th, 2025, between 13:35 UTC and 17:45 UTC, some users of GitHub Copilot Chat in GitHub experienced intermittent failures when reading or writing messages in a thread, resulting in a degraded experience. The error rate peaked at 3% of requests to the service. This was...
Excerpts are shortened. Read the full incident on GitHub's status page.
macos-15-arm64 hosted runner queue delays
-
resolved
On March 18, between 13:04 and 16:55 UTC, Actions workflows relying on hosted runners using the beta MacOS 15 image experienced increased queue time waiting for available runners. An image update was pushed the previous day that included a performance reduction. The slower...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues
-
resolved
Between March 17, 2025, 18:05 UTC and March 18, 2025, 09:50 UTC, GitHub.com experienced intermittent failures in web and API requests. These issues affected a small percentage of users (mostly related to pull requests and issues), with a peak error rate of 0.165% across all...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some Actions users are seeing their workflow jobs failing to start
-
resolved
On March 12, 2025, between 13:28 UTC and 14:07 UTC, the Actions service experienced degradation leading to run start delays. During the incident, about 0.6% of workflow runs failed to start, 0.8% of workflow runs were delayed by an average of one hour, and 0.1% of runs...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions and Pages
-
resolved
On March 8, 2025, between 17:16 UTC and 18:02 UTC, GitHub Actions and Pages services experienced degraded performance leading to delays in workflow runs and Pages deployments. During this time, 34% of Actions workflow runs experienced delays, and a small percentage of runs using...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On March 7, 2025, from 09:30 UTC to 11:07 UTC, we experienced a networking event that disrupted connectivity to our search infrastructure, impacting about 25% of search queries and indexing attempts. Searches for PRs, Issues, Actions workflow runs, Packages, Releases, and other...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues, Git Operations and API Requests
-
resolved
On March 3rd 2025 between 04:07 UTC and 09:36 UTC various GitHub services were degraded with an average error rate of 0.03% and peak error rate of 9%. This issue impacted web requests, API requests, and git operations. This incident was triggered because a network node in one of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Elevated Request Latency for Write operations on github.com and api.github.com
-
resolved
On February 28th, 2025, between 05:49 UTC and 06:55 UTC, a newly deployed background job caused increased load on GitHub’s primary database hosts, resulting in connection pool exhaustion. This led to degraded performance, manifesting as increased latency for write operations and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On February 27, 2025, between 11:30 UTC and 12:22 UTC, Actions experienced degraded performance, leading to delays in workflow runs. On average, 5% of Actions workflow runs were delayed by 31 minutes. The delays were caused by updates in a dependent service that led to failures...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions and Packages
-
resolved
On February 26, 2025, between 14:51 UTC and 17:19 UTC, GitHub Packages experienced a service degradation, leading to billing-related failures when uploading and downloading Packages. During this period, the billing usage and budget pages were also inaccessible. Initially, we...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On February 25th, 2025, between 14:25 UTC and 16:44 UTC email and web notifications experienced delivery delays. At the peak of the incident the delay resulted in ~10% of all notifications taking over 10 minutes to be delivered, with the remaining ~90% being delivered within...
Excerpts are shortened. Read the full incident on GitHub's status page.
Claude 3.7 Sonnet Partially Unavailable
-
resolved
On February 25, 2025 between 13:40 UTC and 15:45 UTC the Claude 3.7 Sonnet model for GitHub Copilot Chat experienced degraded performance. During the impact, occasional requests to Claude would result in an immediate error to the user. This was due to upstream errors with one of...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Packages
-
resolved
On February 25, 2025, between 00:17 UTC and 01:08 UTC, GitHub Packages experienced a service degradation, leading to failures uploading and downloading packages, along with increased latency for all requests to GitHub Packages registry. At peak impact, about 14% of uploads and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Claude 3.5 Sonnet model is unavailable in Copilot
-
resolved
On February 24, 2025 between 21:42 UTC and 22:14 UTC the Claude 3.5 Sonnet model for GitHub Copilot Chat experienced degraded performance. During the impact, all requests to Claude 3.5 Sonnet would result in an immediate error to the user. This was due to misconfiguration within...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Issues
-
resolved
On February 24, 2025, between 15:17 UTC and 17:08 UTC the GitHub Issues & Pull Requests services were degraded by showing stale results on search powered pages such as /issues and /pulls, meaning the displayed results may not have included the most recent updates. Additional...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On February 21 2025 12:00 UTC - 2/24/2025, 18:31 UTC, the Copilot Metrics API failed to ingest daily metrics aggregations for all customers resulting in failure to populate new metrics from 2025-02-21 to 2025-02-24. This failure was triggered by the metrics ingestion process...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On February 16th, 2025 from 11:30 UTC to 12:44 UTC, API requests to GitHub.com experienced increased latency and failures. Around 1% of API requests failed at the peak of this incident. This outage was caused by an experimental feature that malfunctioned and generated excessive...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On February 15, 2025, between 6:35 pm UTC and 4:15 am UTC the Codespaces service was degraded and users in various regions experienced intermittent connection failures. On average, the error rate was 50% and peaked at 65% of requests to the service. This was due to a service...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Incident with Migrations service
-
resolved
Between Thursday 13th, 2025 19:30 UTC and Friday 14th, 2025 08:02 UTC the Migrations service was experiencing intermittent migration failures for some customers. This was caused by a code change that contained an edge case that erroneously failed some migrations. We mitigated...
Excerpts are shortened. Read the full incident on GitHub's status page.
Claude Sonnet unavailable in GitHub Copilot
-
resolved
On February 12th, 2025, between 21:30 UTC and 23:10 UTC the Copilot service was degraded and all requests to Claude 3.5 Sonnet were failing. No other models were impacted. This was due to an issue with our upstream provider which was detected within 12 minutes, at which point we...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with GIT LFS and Other Requests
-
resolved
On February 6, 2025, between 8:40AM UTC and 11:13AM UTC the GitHub REST API was degraded following the rollout of a new feature. The feature resulted in an increase in requests that saturated a cache and led to cascading failures in unrelated services. The error rate peaked at...
Excerpts are shortened. Read the full incident on GitHub's status page.
Actions Larger Runners Provisioning Delays
-
resolved
Between Feb 5, 2025 00:34 UTC and 11:16 UTC, up to 7% of organizations using GitHub-hosted larger runners with public IP addresses had those jobs fail to start during the impact window. The issue was caused by a backend migration in the public IP management system, which caused...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Incident with some GitHub services
-
resolved
A component that imports external git repositories into GitHub had an incident that was caused by the improper internal configuration of a gem. We have since rolled back to a stable version, and all migrations are able to resume.
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests and Issues
Knock-on incidents at other vendors that started during this one and name GitHub:
-
resolved
On January 30th, 2025 from 14:22 UTC to 14:48 UTC, web requests to GitHub.com experienced failures (at peak the error rate was 44%), with the average successful request taking over 3 seconds to complete. This outage was caused by a hardware failure in the caching layer that...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On 29 January 2025 between 14:00 UTC and 16:28 UTC Copilot chat in github.com was degraded, where chat messages which included chat skills failed to save to our datastore due to a change in client side generated identifiers. We mitigated the incident by rolling back the client...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On January 27th, 2025, between 23:32:00 UTC and 23:41:00 UTC the Audit Log Streaming service experienced an approximate 9 minute delay of Audit Log Events. Our systems maintained data continuity and we experienced no data loss. There was no impact to the Audit Log API or the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident With Migration Service
-
resolved
Between Sunday 20:50 UTC and Monday 15:20 UTC the Migrations service was unable to process migrations. This was due to a invalid infrastructure credential. We mitigated the issue by updating the credential internally. Mechanisms and automation will be implemented to detect and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On January 23, 2025, between 9:49 and 17:00 UTC, the available capacity of large hosted runners was degraded. On average, 26% of jobs requiring large runners had a >5min delay getting a runner assigned. This was caused by the rollback of a configuration change and a latent bug...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Request Rebase Merges
-
resolved
On January 16, 2025, between 00:45 UTC and 09:40 UTC the Pull Requests service was degraded and failed to generate rebase merge commits. This was due to a configuration change that introduced disagreements between replicas. These disagreements caused a secondary job to run,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption connecting to Codespaces
-
resolved
On January 14, 2025, between 19:13 UTC and 21:210 UTC the Codespaces service was degraded and led to connection failures with running codespaces, with a 7.6% failure rate for connections during the degradation. Users with bad connections could not use impacted codespaces until...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Git Operations
Knock-on incidents at other vendors that started during this one and name GitHub:
- Render: Services relying on GitHub may fail to build
- Semgrep: GitHub Outage Impacting Semgrep Managed Scanning
-
resolved
On January 13, 2025, between 23:35 UTC and 00:24 UTC all Git operations were unavailable due to a configuration change causing our internal load balancer to drop requests between services that Git relies upon. We mitigated the incident by rolling back the configuration change....
Excerpts are shortened. Read the full incident on GitHub's status page.
Issues with VNet Injected Larger Hosted Runners in East US 2
Names an upstream provider: Azure.
Started during Azure: Networking issues impacting Azure Services in East US 2.
-
resolved
On January 9, 2025, larger hosted runners configured with Azure private networking in East US 2 were degraded, causing delayed job starts for ~2,300 jobs between 16:00 and 20:00 UTC. There was also an earlier period of impact from 2025-01-08 22:00 UTC to 2025-01-09 4:10 UTC with...
Excerpts are shortened. Read the full incident on GitHub's status page.
Some GitHub Actions may not run
-
resolved
On January 9, 2025, between 06:26 and 07:49 UTC, Actions experienced degraded performance, leading to failures in about 1% of workflow runs across ~10k repositories. The failures occurred due to an outage in a dependent service, which disrupted Redis connectivity in the East US...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Webhooks
-
resolved
On January 9, 2025, between 01:26 UTC and 01:56 UTC GitHub experienced widespread disruption to many services, with users receiving 500 responses when trying to access various functionality. This was due to a deployment which introduced a query that saturated a primary database...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions resulting in degraded performance
-
resolved
On January 7th, 2025 between 11:54:00 and 16:39 UTC, degraded performance was observed in Actions, Webhooks, and Issues, caused by an internal Certificate Authority configuration change that disrupted our event infrastructure. The configuration issue was promptly identified and...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Actions
-
resolved
On January 2, 2025 between 16:00:00 and 22:27:30 UTC, a bug in feature-flagged code that cleans up Pull Requests after they are closed or merged incorrectly cleared the merge commit SHA for ~139,000 pull requests. During the incident, Actions workflows triggered by the on:...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On December 20th, 2024, between 15:57 UTC and 16:39 UTC some of our marketing pages became inaccessible and users attempting to access the pages would have received 500 errors. There was no impact to any operational product or service area. This issue was due to a partial outage...
Excerpts are shortened. Read the full incident on GitHub's status page.
Live updates on pages not loading reliably
-
resolved
On December 17th, 2024, between 14:33 UTC and 14:50 UTC, many users experienced intermittent errors and timeouts when accessing github.com. The error rate was 8.5% on average and peaked at 44.3% of requests. The increased error rate caused a broad impact across our services,...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Upon further investigation, the degradation in migrations in the EU was caused by an internal configuration issue, which was promptly identified and resolved. No customer migrations were impacted during this time and the issue only affected GitHub Enterprise Cloud - EU and had...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On December 4th, 2024 between 18:52 UTC and 19:11 UTC, several GitHub services were degraded with an average error rate of 8%. The incident was caused by a change to a centralized authorization service that contained an unoptimized database query. This led to an increase in...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Incident with Pull Requests
-
resolved
On December 3rd, between 23:29 and 23:43 UTC, Pull Requests experienced a brief outage and teams have confirmed the issue to be resolved. Due to brevity of incident it was not publicly statused at the time however an RCA will be conducted and shared in due course.
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Pull Requests and API Requests
-
resolved
On December 3, 2024, between 19:35 UTC and 20:05 UTC API requests, Actions, Pull Requests and Issues were degraded. Web and API requests for Pull Requests experienced a 3.5% error rate and Issues had a 1.2% error rate. The highest impact was for users who experienced errors...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between Dec 3 03:35 UTC and 04:35 UTC, availability of large hosted runners for Actions was degraded due to failures in background VM provisioning jobs. This was a shorter recurrence of the issue that occurred the previous day. Users would see workflows queued waiting for a...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
Between Dec 1 12:20 UTC and Dec 2 1:05 UTC, availability of large hosted runners for Actions was degraded due to failures in background VM provisioning jobs. Users would see workflows queued waiting for a runner. On average, 8% of all workflows requiring large runners over the...
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Codespaces
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on GitHub's status page.
Incident with Sporadic Timeouts in Codespaces
-
resolved
This incident has been resolved.
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with GitHub Search
-
resolved
Between 13:30 and 15:00 UTC, repository searches were timing out for most users. The ongoing efforts from the similar incident last week helped uncover the main contributing factors. We have deployed short-term mitigations and identified longer term work to proactively identify...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On November 25th, 2024 between 10:38 UTC and 12:00 UTC the Claude model for GitHub Copilot Chat experienced degraded performance. During the impact, all requests to Claude would result in an immediate error to the user. This was due to upstream errors with one of our...
Excerpts are shortened. Read the full incident on GitHub's status page.
Repository searches not working for some users
-
resolved
On November 21, 2024, between 14:30 UTC and 15:53 UTC search services at GitHub were degraded and CPU load on some nodes hit 100%. On average, the error rate was 22 requests/second and peaked at 83 requests/second. During this incident Enterprise Profile pages were slow to load...
Excerpts are shortened. Read the full incident on GitHub's status page.
Disruption with some GitHub services
-
resolved
On November 19, 2024, between 10:56:00 UTC and 12:03:00 UTC the notifications service was degraded and stopped sending notifications. On average, notifications delivery was delayed about 1 hour. This was due to a database host coming out of a regular maintenance process in read...
Excerpts are shortened. Read the full incident on GitHub's status page.
[Retroactive] Merge Queues not processing queued Pull Requests in some repositories
-
resolved
Between 2024-11-06 11:14 UTC and 2024-11-08 at 18:15 UTC, pull requests added to merge queues in some repositories were not processed. This was caused by a bug in a new version of the merge queue code, and was mitigated by rolling back a feature flag. Around 1% of enqueued PRs...
Excerpts are shortened. Read the full incident on GitHub's status page.