Github

Oct 26, 18:57 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Oct 26, 18:54 UTC
Update - We saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.

We mitigated the issue and all services have recovered.

Oct 26, 18:50 UTC
Monitoring - …

Oct 24, 00:23 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Oct 24, 00:23 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.

Oct 23, 23:42 UTC
Update - We are experiencing degraded availability for the Grok 4.6 and Grok 4.7 models in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. …

Oct 23, 18:51 UTC
Resolved - We identified that an advisory-publication driven fan-out was overwhelming Dependabot alert processing on repositories by saturating the queue with its own events, delaying processing of events related to repository pushes.

We have now isolated this fan-out and applied a throttle so it runs at a fixed rate and cannot delay other events. This remediation has successfully prevented a new fan-out process impacting users.

Oct 23, 18:36 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Oct 23, 17:27 UTC
Update - Some Dependabot alerts continue …

Oct 23, 08:05 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Oct 23, 07:56 UTC
Update - As of 07:27 UTC, Actions results are delivering within normal SLOs again.

Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future.

Oct 23, 07:53 UTC
Monitoring - The degradation affecting Actions …

Oct 23, 02:30 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Oct 23, 00:55 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Oct 22, 23:48 UTC
Update - GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear.

We're continuing to work on the remaining delays and monitor recovery.

Oct 22, 22:07 UTC
…

Oct 22, 15:18 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Oct 22, 15:18 UTC
Update - GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.

Oct 22, 15:17 UTC
Monitoring - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

Oct 22, 15:06 UTC
Update - We’re seeing recovery, and repository update processing has …

Oct 21, 19:22 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Oct 21, 19:22 UTC
Update - Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed.

Oct 21, 18:52 UTC
Update - Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations …

Oct 19, 16:56 UTC
Resolved - On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost.

Impact

- Workflow status updates, logs, and checks were delayed.
- 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed.
- During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors.

Pages deployments and webhooks generated by Actions …

Oct 15, 18:56 UTC
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.

Oct 15, 18:53 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Oct 15, 18:34 UTC
Update - CCA Automations are experiencing delays when users start an Automation

Oct 15, 18:31 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Oct 13, 20:30 UTC
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 ran normally and no run delays or check delays occurred.

Oct 12, 20:16 UTC
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 immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC.

The incident was triggered through a latent condition in our notifications delivery pipeline that …

Oct 7, 18:04 UTC
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: https://www.githubstatus.com/incidents/djlmxz2zd0j7

Oct 7, 18:00 UTC
Update - All systems have recovered. We have applied mitigations and do not anticipate another recurrence.

Oct 7, 17:27 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Oct 7, 17:25 UTC
Update - …

Oct 7, 16:25 UTC
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 failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected.

In the first outage, 5.6% of all web and API requests failed, peaking at 8.9%, …

Oct 6, 23:40 UTC
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, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool. Recovery was seen at approximately 19:50 UTC once the migration's calls stopped; GEI migrations were reenabled at 23:32 UTC after a code fix was merged.

We …

Oct 6, 01:32 UTC
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 to the service that powers these pages.

This was caused by a networking failure, which disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database services. We mitigated the incident by shifting the database traffic to a healthy region.

We are working to make …

Oct 5, 22:49 UTC
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 the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some …

Oct 1, 17:56 UTC
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 0.196% of jobs failed to start.

A routing change at our cloud provider concentrated API traffic on a single backend, causing an increase in rate-limit errors. Incorrect retry behavior in the provider’s inventory service added load to the affected APIs, compounding the rate limiting. This disrupted runner provisioning and reduced available capacity in affected regions. …

Oct 1, 13:57 UTC
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 our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returned to normal as the traffic subsided, and we have since applied additional traffic filtering to protect against similar traffic. We are improving alerting for delays in our traffic-handling infrastructure and strengthening our automated traffic …

Oct 1, 02:00 UTC
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 recovered, but the lost state cannot be restored by retrying an approval.


If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, …

Sep 28, 22:08 UTC
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 automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot Code Review needs to complete a review. Review completion is an inherently delayed signal, because each review job takes time to …