GitHub Status - Incident History

Disruption with some GitHub services

2026-04-14T04:40:12Z

Apr 14, 04:40 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, 03:47 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, 02:40 UTC
Update - The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.

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

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

Incident with Pages

2026-04-13T20:35:37Z

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

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

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

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

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

Disruption with some GitHub services

2026-04-13T17:40:09Z

Apr 13, 17:40 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.

Apr 13, 16:59 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:41 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

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

2026-04-10T13:28:23Z

Apr 10, 13:28 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.

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

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

Disruption with some GitHub services

2026-04-09T20:36:52Z

Apr 9, 20:36 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.

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

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

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

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

Apr 9, 16:20 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.

Disruption with some GitHub services

2026-04-09T10:15:37Z

Apr 9, 10:15 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.

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

Apr 9, 09:57 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:50 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with GitHub notifications

2026-04-09T04:57:17Z

Apr 9, 04: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.

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

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

Disruption with some GitHub services

2026-04-02T21:48:43Z

Apr 2, 21:48 UTC
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, 20:35 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, 19:28 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, 18:25 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, 17:59 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:49 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Copilot Coding Agent failing to start some jobs

2026-04-02T16:30:05Z

Apr 2, 16:30 UTC
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:28 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:18 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with GitHub's code search

2026-04-01T23:45:45Z

Apr 1, 23:45 UTC
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, 22:00 UTC
Update - We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.

Apr 1, 19:37 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, 17:48 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, 16:00 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, 15:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

GitHub audit logs are unavailable

2026-04-01T16:10:17Z

Apr 1, 16:10 UTC
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:07 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:06 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Incident with Copilot

2026-04-01T12:41:38Z

Apr 1, 12:41 UTC
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:10 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:02 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.

Apr 1, 11:37 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:24 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.

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

Apr 1, 10:31 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:00 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, 09:58 UTC
Investigating - We are investigating reports of degraded performance for Copilot

Incident with Pull Requests: High percentage of 500s

2026-03-31T21:23:43Z

Mar 31, 21:23 UTC
Resolved - On Monday March 31st, 2026, between 13:53 UTC and 21:23 UTC the Pull Requests service experienced elevated latency and failures. On average, the error rate was 0.15% and peaked at 0.28% of requests to the service. This was due to a change in garbage collection (GC) settings for a Go-based internal service that provides access to Git repository data. The changes caused more frequent GC activity and elevated CPU consumption on a subset of storage nodes, increasing latency and failure rates for some internal API operations.

We mitigated the incident by reverting the GC changes. To prevent future incidents and improve time to detection and mitigation, we are instrumenting additional metrics and alerting for GC-related behavior, improving our visibility into other signals that could cause degraded impact of this type, and updating our best practices and standards for garbage collection in Go-based services.

Mar 31, 21:16 UTC
Monitoring - The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.

Mar 31, 21:12 UTC
Update - We continue to see a small subset of repositories experiencing timeouts and elevated latency in Pull Requests, affecting under 1% of requests.

Mar 31, 19:28 UTC
Update - Error rates remain elevated across multiple pull request endpoints. We are pursuing multiple potential mitigations.

Mar 31, 18:42 UTC
Update - We continue to experience elevated error rates affecting Pull Requests. An earlier fix resolved one component of the issue, but some users may still encounter intermittent timeouts when viewing or interacting with pull requests. Our teams are actively investigating the remaining causes.

Mar 31, 17:16 UTC
Update - We identified an issue causing increased errors when accessing Pull Requests. The mitigation is being applied across our infrastructure and we will continue to provide updates as the mitigation rolls out.

Mar 31, 16:35 UTC
Update - We are seeing recovery in latency and timeouts of requests related to pull requests, even though 500s are still elevated. While we are continuing to investigate, we are applying a mitigation and expect further recovery after it is applied.

Mar 31, 16:15 UTC
Update - We are continuing to investigate increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

Mar 31, 15:39 UTC
Update - We are investigating increased 500 errors affecting GitHub services. You may experience intermittent failures when using Pull Requests and other features. We are actively working to identify and resolve the underlying cause.

Mar 31, 15:06 UTC
Update - We are seeing a higher than average number of 500s due to timeouts across GitHub services. We have a potential mitigation in flight and are continuing to investigate.

Mar 31, 15:05 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests

Issues with metered billing report generation

2026-03-31T15:10:22Z

Mar 31, 15:10 UTC
Resolved - On March 31, 2026, between 06:15 UTC and 15:30 UTC, the GitHub billing usage reports feature was degraded due to reduced server capacity. Customers requesting billing usage reports and loading the top usage by organization and repository on the billing overview and usage pages were impacted. The average error rate for usage report requests was 15%, peaking at 98% over an eight-minute window. For the billing pages, an average of 56% of requests failed to load the top usage cards. The root cause was an increase in billing usage report requests with large datasets, which exhausted the capacity of the nodes responsible for reporting data. There was no impact on billing charges.

We mitigated the incident by adjusting our auto-scaling thresholds to better meet our capacity needs. We are working to improve our metrics to reduce time to detection and mitigation for similar issues in the future.

Mar 31, 15:01 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.

Mar 31, 14:59 UTC
Update - We have applied mitigations to a data store related to billing reports, and are seeing partial recovery to billing report generation. We continue to monitor for full recovery.

Mar 31, 14:56 UTC
Update - We are seeing a high number of 500s due to timeouts across GitHub services. We are redeploying some of our core services and we expect that this allow us to recover.

Mar 31, 14:39 UTC
Update - We're continuing to see high failure rates on billing report generation, and are working on mitigations for a data store related to billing reports.

Mar 31, 13:56 UTC
Update - We're seeing issues related to metered billing reports, intermittently affecting metered usage graphs and reports on the billing page. We have identified an issue with a data store, and are working on mitigations.

Mar 31, 13:47 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Elevated delays in Actions workflow runs and Pull Request status updates

2026-03-30T13:25:38Z

Mar 30, 13:25 UTC
Resolved - On March 30, 2026, between 10:11 UTC and 13:25 UTC, GitHub Actions experienced degraded performance. During this time, approximately 2.65% of workflow jobs triggered by pull request events experienced start delays exceeding 5 minutes. The issue was caused by replication lag on an internal database cluster used by Actions, which triggered write throttling in our database protection layer and slowed job queue processing.

The replication lag originated from planned maintenance to scale the internal database. Newly added database hosts triggered guardrails in the throttling layer, restricting write throughput. The incident was mitigated by excluding the new hosts from replication delay calculations.

To prevent recurrence, we have updated our maintenance procedures to ensure new hosts are excluded from throttling assessments during scaling operations. Additionally, we are investing in automation to streamline this type of maintenance activity.

Mar 30, 13:25 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.

Mar 30, 13:20 UTC
Monitoring - The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.

Mar 30, 13:02 UTC
Investigating - We are investigating reports of degraded performance for Actions and Pull Requests

Incident with Copilot

2026-03-27T05:00:00Z

Mar 27, 05:00 UTC
Resolved - On March 27, 2026, from 02:30 to 04:56 UTC, a misconfiguration in our rate limiting system caused users on Copilot Free, Student, Pro, and Pro+ plans to experience unexpected rate limit errors. The configuration that was incorrectly applied was intended solely for internal staff testing of rate-limiting experiences. Copilot Business and Copilot Enterprise accounts were not affected.

During this period, affected users received error messages instructing them to retry after a certain time. Approximately 32% of active Free users, 35% of active Student users, 46% of active Pro users, and 66% of active Pro+ users were affected.

After identifying the root cause, we reverted the change and restored the expected rate limits. We are reviewing our deployment and validation processes to help ensure configurations used for internal testing cannot be inadvertently applied to production environments.

Disruption with some GitHub services

2026-03-24T20:56:05Z

Mar 24, 20:56 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.

Mar 24, 20:38 UTC
Update - We are investigating elevated error rates affecting multiple GitHub services including Actions, Issues, Pull Requests, Webhooks, Codespaces, and login functionality. Some users may have experienced errors when accessing these features. Most services are now showing signs of recovery. We'll post another update by 21:00 UTC.

Mar 24, 20:23 UTC
Update - Issues is experiencing degraded performance. We are continuing to investigate.

Mar 24, 20:23 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.

Mar 24, 20:20 UTC
Update - Webhooks is experiencing degraded performance. We are continuing to investigate.

Mar 24, 20:18 UTC
Investigating - We are investigating reports of degraded performance for Actions

Teams Github Notifications App is down

2026-03-24T19:51:16Z

Mar 24, 19:51 UTC
Resolved - On March 24, 2026, between 15:57 UTC and 19:51 UTC, the Microsoft Teams Integration and Teams Copilot Integration services were degraded and unable to deliver GitHub event notifications to Microsoft Teams. On average, the error rate was 37.4% and peaked at 90.1% of requests to the service -- approximately 19% of all integration installs failed to receive GitHub-to-Teams notifications in this time period.

This was due to an outage at one of our upstream dependencies, which caused HTTP 500 errors and connection resets for our Teams integration.

We coordinated with the relevant service teams, and the issue was resolved at 19:51 UTC when the upstream incident was mitigated.

We are working to update observability and runbooks to reduce time to mitigation for issues like this in the future.

Mar 24, 18:50 UTC
Update - We are experiencing degraded availability from Azure Teams APIs, which is impacting notifications from GitHub to Microsoft Teams. We are awaiting resolution from Azure.

Mar 24, 17:43 UTC
Update - We are experiencing degraded availability from Azure APIs, which is impacting notifications from GitHub to Microsoft Teams. We are working with Azure to resolve the issue.

Mar 24, 17:09 UTC
Update - We found an issue impacting notifications from GitHub to Microsoft Teams. We are working on mitigation and will keep users updated on progress towards mitigation.

Mar 24, 16:59 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with some GitHub services

2026-03-22T10:02:05Z

Mar 22, 10:02 UTC
Resolved - On March 22, 2026, between 09:05 UTC and 10:02 UTC, users may have experienced intermittent errors and increased latency when performing Git http read operations. On average, the error rate was 3.84% and peaked at 15.55% of requests to the service. The issue was caused by elevated latency in an internal authentication service within one of our regional clusters. We mitigated the issue by redirecting traffic away from the affected cluster at 09:39 UTC, after which error rates returned to normal. The incident was fully resolved at 10:02 UTC.

We are working to scale the authentication service and reduce our time to detection and mitigation of issues like this one in the future.

Mar 22, 09:27 UTC
Update - We are investigating intermittently high latency and errors from Git operations.

Mar 22, 09:08 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with Copilot Coding Agent Sessions

2026-03-20T01:58:40Z

Mar 20, 01:58 UTC
Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and
peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its
backing datastore.

We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first.

We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.

Mar 20, 01:26 UTC
Update - We are rolling out our mitigation and are seeing recovery.

Mar 20, 01:00 UTC
Update - We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation.

Mar 20, 00:58 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Git operations for users in the west coast are experiencing an increase in latency

2026-03-20T00:05:15Z

Mar 20, 00:05 UTC
Resolved - On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues.

Mar 20, 00:05 UTC
Update - We have reached stability with git operations through our changes deployed today.

Mar 19, 23:52 UTC
Update - We are seeing early signs of improvement. We are working on one more small change to further improve traffic routing on the west coast.

Mar 19, 22:57 UTC
Update - We have completed the rollout of our new network path and are monitoring its impact.

Mar 19, 21:59 UTC
Update - We are beginning the rollout of our new network path. During this change, users will continue to see higher latency from the west coast. We will provide another update when the rollout is complete.

Mar 19, 18:27 UTC
Update - We are working to enable a new network path in the west coast to reduce load and will monitor the impact on latency for Git Operations

Mar 19, 17:49 UTC
Update - We are still seeing elevated latency for Git operations in the west coast and are continuing to investigate

Mar 19, 17:01 UTC
Update - We are redirecting traffic back to our Seattle region and customers should see a decrease in latency for Git operations

Mar 19, 16:25 UTC
Investigating - We are investigating reports of degraded performance for Git Operations

Issues with Copilot Coding Agent

2026-03-19T14:32:55Z

Mar 19, 14:32 UTC
Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and
peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its
backing datastore.

We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first.

We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.

Mar 19, 14:06 UTC
Update - Copilot is operating normally.

Mar 19, 14:02 UTC
Update - We are investigating reports that Copilot Coding Agent session logs are not available in the UI.

Mar 19, 13:45 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.

Mar 19, 13:44 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with Copilot Coding Agent sessions

2026-03-19T02:52:44Z

Mar 19, 02:52 UTC
Resolved - On March 19, 2026, between 01:05 UTC and 02:52 UTC, and again on March 20, 2026, between 00:42 UTC and 01:58 UTC, the Copilot Coding Agent service was degraded and users were unable to start new Copilot Agent sessions or view existing ones. During the first incident, the average error rate was ~53% and
peaked at ~93% of requests to the service. During the second incident, the average error rate was ~99%% and peaked at ~100%% of requests with significant retry amplification. Both incidents were caused by the same underlying system authentication issue that prevented the service from connecting to its
backing datastore.

We mitigated each incident by rotating the affected credentials, which restored connectivity and returned error rates to normal. The mitigation time was 01:24. The second occurrence was due to an incomplete remediation of the first.

We are implementing automated monitoring for credential lifecycle events and improving operational processes to reduce our time to detection and mitigation of issues like this one in the future.

Mar 19, 02:46 UTC
Update - We have rolled out our mitigation and are seeing recovery for Copilot Coding Agent sessions

Mar 19, 02:25 UTC
Update - We are seeing widespread issues starting and viewing Copilot Agent sessions. We have a hypothesis for the cause and are working on remediation.

Mar 19, 02:05 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Disruption with some GitHub services

2026-03-19T01:44:01Z

Mar 19, 01:44 UTC
Resolved - On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues.

This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

Mar 19, 01:43 UTC
Update - We are seeing recovery in git operations for customers on the West Coast of the US.

Mar 19, 00:56 UTC
Update - We continue to investigate the slow performance of Git Operations affecting the US West Coast.

Mar 19, 00:10 UTC
Update - We continue to investigate degraded performance for git operations from the US West Coast.

Mar 18, 23:33 UTC
Update - We are continuing to investigate degraded performance for git operations from the US West Coast.

Mar 18, 22:48 UTC
Update - We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.

Mar 18, 22:36 UTC
Update - Git Operations is experiencing degraded performance. We are continuing to investigate.

Mar 18, 22:36 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.

Webhook delivery is delayed

2026-03-18T19:46:38Z

Mar 18, 19:46 UTC
Resolved - On March 18, 2026, between 18:18 UTC and 19:46 UTC all webhook deliveries experienced elevated latency. During this time, average delivery latency increased from a baseline of approximately 5 seconds to a peak of approximately 160 seconds. This was due to resource constraints in the webhook delivery pipeline, which caused queue backlog growth and increased delivery latency. We mitigated the incident by shifting traffic and adding capacity, after which webhook delivery latency returned to normal. We are working to improve capacity management and detection in the webhook delivery pipeline to help prevent similar issues in the future.

Mar 18, 19:25 UTC
Update - We are seeing recovery and are continuing to monitor the latency for webhook deliveries

Mar 18, 18:51 UTC
Investigating - We are investigating reports of degraded performance for Webhooks