GitHub
Apps and SaaS. Source: GitHub status page.
History starts 2026-08-05 11:38 UTC, the oldest incident this status page still shows. Figures for the last 90 days cover only the part since then.
- Incidents, last 90 days
- 51+
- Median duration
- 1h 18m
- p95 duration
- 10h 42m
- Naming an upstream provider
- 7%
- With a postmortem on the status page
- 0%
What failed, last 90 days
| Exhausted memory, disk, CPU, queues, connection pools or quotas | 13 |
| A provider or third-party service this vendor depends on failed | 10 |
| A configuration change caused the failure | 7 |
| The text does not say enough to tell | 4 |
| A code release introduced the failure | 3 |
| Login, tokens, certificates or credentials failed | 3 |
| Data delayed, stale, lost or corrupted, or needing replay after recovery | 2 |
| Network, DNS, routing or connectivity failure | 2 |
| Traffic surge or denial-of-service attack | 2 |
| A zone, region or data center became unavailable | 1 |
| Hardware, power, cooling or another physical failure | 1 |
| Orchestration, control plane, service discovery or load balancing failed | 1 |
| A schema or data migration caused the failure | 1 |
Tagged by claude-haiku-5-5 from each incident's updates. See the methodology.
Incidents per month
Hatched months are before the recorded history starts.
All recorded incidents
Delays for Pull Requests and Webhook deliveries
Affected: Webhooks, Pull Requests, Actions
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.
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 claude-haiku-5-5 with low confidence (taxonomy v0.2).
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 claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 claude-haiku-5-5 with low confidence (taxonomy v0.2).
-
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: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: Hardware or facility. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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: A zone, region or data center became unavailable. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
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: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
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: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
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: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 claude-haiku-5-5 with low confidence (taxonomy v0.2).
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
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
- 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: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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 claude-haiku-5-5 with medium confidence (taxonomy v0.2).
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
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 claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).
-
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 configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).
-
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.