GitHub Status

Apr 15, 2026

No incidents reported today.

Apr 14, 2026

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.
Apr 14, 06:08 UTC

Update - This incident has been resolved. We will continue to monitor to ensure stability. Thank you for your patience and understanding as we addressed this issue.
Apr 14, 06:07 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 14, 06:07 UTC

Update - We identified an issue that impacts the Copilot Dashboard on the Insights tab and are working on mitigation. We will continue to keep you updated on progress.
Apr 14, 04:40 UTC

Update - The team continues to investigate issues accessing with Copilot Dashboard on the Insights tab. We will continue providing updates on the progress towards mitigation.
Apr 14, 03:47 UTC

Update - The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.
Apr 14, 02:40 UTC

Update - Degradation of Service - Insights Page
Apr 14, 02:37 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 14, 01:57 UTC

Apr 13, 2026

Incident with Pages

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.
Apr 13, 20:35 UTC

Update - We have mitigated the issue with Pages.
Apr 13, 20:32 UTC

Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
Apr 13, 20:30 UTC

Update - We are investigating reports of issues with Pages. We will continue to keep users updated on progress towards mitigation.
Apr 13, 19:57 UTC

Investigating - We are investigating reports of degraded availability for Pages
Apr 13, 19:56 UTC

Disruption with some GitHub services

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

Update - We have identified the root cause and are rolling out a fix for Copilot. The services should now be in recovery, with expected full recovery in 5 to 10 minutes.
Apr 13, 16:59 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 13, 16:41 UTC

Apr 12, 2026

No incidents reported.

Apr 11, 2026

No incidents reported.

Apr 10, 2026

Problems with third-party Claude and Codex Agent sessions not being listed in the agents tab dashboard

Resolved - On April 9, 2026, between 22:59 UTC and April 10, 2026, 13:24 UTC, the Copilot Mission Control service was degraded and did not display Claude and Codex Cloud Agent sessions in the agents tab dashboard. Customers were unable to see, list, or manage their third party agent sessions during this period. The underlying agent sessions continued to function normally. This was a visibility and management issue only, and no HTTP errors were generated. The API returned successful responses with incomplete results, with an average error rate of 0% and a maximum error rate of 0%. This was due to a code change that introduced a filter which inadvertently excluded third party agent sessions.

We mitigated the incident by reverting the problematic code change and deploying the fix to production.

We are working to add automated monitoring for dashboard content visibility and improve integration test coverage for third party agent session listing to reduce our time to detection and mitigation of issues like this one in the future.
Apr 10, 13:28 UTC

Update - We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.
Apr 10, 13:08 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 10, 13:07 UTC

Apr 9, 2026

Disruption with some GitHub services

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

Update - We continue to investigate periodic delays in Copilot Cloud Agent job processing
Apr 9, 19:52 UTC

Update - We are continuing to investigate Copilot Cloud Agent job delays
Apr 9, 18:57 UTC

Update - Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Apr 9, 17:48 UTC

Update - We are investigating delays processing Copilot Cloud Agent jobs
Apr 9, 16:57 UTC

Update - We are experiencing issues where jobs are being delayed to start for copilot coding agent
Apr 9, 16:20 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 9, 16:20 UTC

Disruption with some GitHub services

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

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 9, 10:15 UTC

Update - We are investigating an issue affecting GitHub Copilot coding agent. Users may experience significant delays when starting new agent sessions, with jobs remaining queued longer than expected. Our team has identified increased load as a contributing factor and is actively working to restore normal performance.
Apr 9, 09:57 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 9, 09:50 UTC

Disruption with GitHub notifications

Resolved - On April 9, 2026, between 03:22 UTC and 04:49 UTC, GitHub Notifications experienced degraded availability. During this time, approximately 45% of requests to the notifications service returned errors, with a peak error rate of approximately 54%, preventing affected users from successfully viewing or interacting with their notifications service. The issue was identified and resolved, restoring the service to full availability.

We are working to improve our metrics to reduce time to detection and mitigation for similar issues in the future.
Apr 9, 04:57 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 9, 04:57 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 9, 04:42 UTC

Apr 8, 2026

No incidents reported.

Apr 7, 2026

No incidents reported.

Apr 6, 2026

No incidents reported.

Apr 5, 2026

No incidents reported.

Apr 4, 2026

No incidents reported.

Apr 3, 2026

No incidents reported.

Apr 2, 2026

Disruption with some GitHub services

Resolved - Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour. During this hour, some new jobs would time out, while others would resume once rate limiting ended. Roughly 40% of jobs in this period were affected.

Once the cause of this rate limiting was identified, we were able to disable the new CCR feature via a feature flag. Once the jobs that were already in the queue were able to clear, we didn't see additional instances of rate limiting afterwards.
Apr 2, 21:48 UTC

Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 2, 21:48 UTC

Update - Although we are observing recovery once again, we expect continued periods of degradation.

Work that is queued during times of degradation does eventually get processed.

We continue to investigate and find a mitigation, and will update again within 2 hours.
Apr 2, 20:35 UTC

Update - This issue has recurred. Customers will once again experience false job starts when assigning tasks to Copilot Cloud Agent.

We are still investigating and trying to understand the pattern of degradation.
Apr 2, 19:28 UTC

Update - We are once again seeing recovery with Copilot Cloud Agent job starts.

We are keeping this open while we verify this won't recur.
Apr 2, 18:25 UTC

Update - When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running.

We are investigating.
Apr 2, 17:59 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 2, 17:49 UTC

Copilot Coding Agent failing to start some jobs

Resolved - Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour. During this hour, some new jobs would time out, while others would resume once rate limiting ended. Roughly 40% of jobs in this period were affected.

Once the cause of this rate limiting was identified, we were able to disable the new CCR feature via a feature flag. Once the jobs that were already in the queue were able to clear, we didn't see additional instances of rate limiting afterwards.

This was the same incident declared in https://www.githubstatus.com/incidents/d96l71t3h63k
Apr 2, 16:30 UTC

Update - When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running.

We are investigating.
Apr 2, 16:28 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 2, 16:18 UTC

Apr 1, 2026

Disruption with GitHub's code search

Resolved - On April 1st, 2026 between 14:40 and 17:00 UTC the GitHub code search service had an outage which resulted in users being unable to perform searches.

The issue was initially caused by an upgrade to the code search Kafka cluster ZooKeeper instances which caused a loss of quorum. This resulted in application-level data inconsistencies which required the index to be reset to a point in time before the loss of quorum occurred. Meanwhile, an accidental deploy resulted in query services losing their shard-to-host mappings, which are typically propagated by Kafka.

We remediated the problem by performing rolling restarts in the Kafka cluster, allowing quorum to be reestablished. From there we were able to reset our index to a point in time before the inconsistencies occurred.

The team is working on ways to improve our time to respond and mitigate issues relating to Kafka in the future.
Apr 1, 23:45 UTC

Update - Code search has recovered and is serving production traffic.
Apr 1, 23:45 UTC

Update - We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.
Apr 1, 22:00 UTC

Update - We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.
Apr 1, 19:37 UTC

Update - We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April 2026). We are still working on recovering our ingestion pipeline, and synchronizing the indexed data.

We will update again within 2 hours.
Apr 1, 17:48 UTC

Update - We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic configuration which is causing most requests for Code Search results to fail. We are working to restore the service and to re-ingest the misaligned data.
Apr 1, 16:00 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 1, 15:02 UTC

GitHub audit logs are unavailable

Resolved - On April 1, 2026, between 15:34 UTC and 16:02 UTC, our audit log service lost connectivity to its backing data store due to a failed credential rotation. During this 28-minute window, audit log history was unavailable via both the API and web UI. This resulted in 5xx errors for 4,297 API actors and 127 github.com users. Additionally, events created during this window were delayed by up to 29 minutes in github.com and event streaming. No audit log events were lost; all audit log events were ultimately written and streamed successfully. Customers using GitHub Enterprise Cloud with data residency were not impacted by this incident.

We were alerted to the infrastructure failure at 15:40 UTC — six minutes after onset — and resolved the issue by recycling the affected environment, restoring full service by 16:02 UTC. We are conducting a thorough review of our credential rotation process to strengthen its resiliency and prevent recurrence. In parallel, we are strengthening our monitoring capabilities to ensure faster detection and earlier visibility into similar issues going forward.
Apr 1, 16:10 UTC

Update - A routine credential rotation has failed for our our audit logs service; we have re-deployed our service and are waiting for recovery.
Apr 1, 16:07 UTC

Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 1, 16:06 UTC

Incident with Copilot

Resolved - On April 1, 2026, between 07:29 and 12:41 UTC, some customers experienced elevated 5xx errors and increased latency when using GitHub Copilot features that rely on `/agents/sessions` endpoints (including creating or viewing agent sessions). The issue was caused by resource exhaustion in one of the Copilot backend services handling these requests, in turn, causing timeouts and failed requests. We mitigated the incident by increasing the service’s available compute resources and tuning its runtime concurrency settings. Service health returned to normal and the incident was fully resolved by 12:41 UTC.
Apr 1, 12:41 UTC

Update - The success rate and latency for creating and viewing agent sessions has stabilized at baseline levels, we are continuing to monitor recovery
Apr 1, 12:10 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 1, 12:02 UTC

Update - The success rate for creating and viewing agent sessions has stabilized, and we're continuing to monitor latency, which is trending toward baseline levels.
Apr 1, 11:37 UTC

Update - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 1, 11:24 UTC

Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
Apr 1, 10:56 UTC

Update - Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate.
Apr 1, 10:31 UTC

Update - We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation.
Apr 1, 10:00 UTC

Investigating - We are investigating reports of degraded performance for Copilot
Apr 1, 09:58 UTC

All Systems Operational

About This Site

Past Incidents

All Systems Operational

About This Site

Related

Past Incidents