GitHub Outage History

GitHub is up right now

GitHub had 99 outages in the last 2 years totaling 130h 43m of downtime — averaging 4.1 incidents per month.

There were 99 GitHub outages since February 27, 2026 totaling 130h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.githubstatus.com · Aggregated across GitHub products

Minor May 23, 2026

Intermittent errors with app installation token authentication

Detected by Pingoru
May 23, 2026, 07:32 PM UTC
Resolved
May 23, 2026, 07:32 PM UTC
Duration
Timeline · 8 updates
  1. investigating May 23, 2026, 04:00 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating May 23, 2026, 04:01 PM UTC

    We are seeing an increased rate of authentication failures for app installation tokens, affecting approximately 1% of tokens. We are continuing to investigate.

  3. investigating May 23, 2026, 04:35 PM UTC

    We are continuing to investigate an elevated error rate of authentication failures for app installation tokens. Next update in one hour.

  4. investigating May 23, 2026, 05:41 PM UTC

    We are seeing signs of mitigation and are continuing to monitor for complete mitigation. Next update in one hour.

  5. investigating May 23, 2026, 06:42 PM UTC

    We see significant signs of mitigation and are monitoring for full mitigation.

  6. investigating May 23, 2026, 07:06 PM UTC

    We have identified and are applying additional mitigation and will continue to monitor for complete mitigation.

  7. investigating May 23, 2026, 07:32 PM UTC

    This is fully mitigated, we will continue to monitor to ensure it does not reoccur.

  8. resolved May 23, 2026, 07:32 PM UTC

    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.

Read the full incident report →

Critical May 15, 2026

Actions is experiencing degraded availability

Detected by Pingoru
May 15, 2026, 08:13 AM UTC
Resolved
May 15, 2026, 08:48 AM UTC
Duration
34m
Affected: ActionsPages
Timeline · 7 updates
  1. investigating May 15, 2026, 08:13 AM UTC

    We are investigating reports of degraded availability for Actions

  2. investigating May 15, 2026, 08:14 AM UTC

    Pages is experiencing degraded availability. We are continuing to investigate.

  3. investigating May 15, 2026, 08:26 AM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  4. investigating May 15, 2026, 08:27 AM UTC

    The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

  5. investigating May 15, 2026, 08:29 AM UTC

    We are monitoring an issue that was affecting GitHub Actions and causing downstream issues in GitHub Coding Agent and GitHub Code Review Agent. The issue has resolved now but we are closely monitoring our systems for full recovery.

  6. monitoring May 15, 2026, 08:41 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  7. resolved May 15, 2026, 08:48 AM UTC

    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.

Read the full incident report →

Notice May 15, 2026

[Retroactive] Incident with GitHub.com

Detected by Pingoru
May 15, 2026, 03:30 AM UTC
Resolved
May 15, 2026, 02:30 AM UTC
Duration
Timeline · 1 update
  1. resolved May 15, 2026, 03:57 AM UTC

    Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed. The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the source of the traffic and prevented further disruption.

Read the full incident report →

Minor May 13, 2026

Incident with CodeQL

Detected by Pingoru
May 13, 2026, 02:41 PM UTC
Resolved
May 13, 2026, 04:03 PM UTC
Duration
1h 22m
Timeline · 6 updates
  1. investigating May 13, 2026, 02:41 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating May 13, 2026, 02:43 PM UTC

    We are investigating delays affecting CodeQL, the code analysis engine used by Code Scanning. Some users may experience delayed or incomplete code scanning results. Our engineering team is investigating. We will provide another update by 15:15 UTC.

  3. investigating May 13, 2026, 02:58 PM UTC

    We have applied a mitigation to increase processing capacity. We are continuing to monitor to confirm full recovery. We will provide another update by 15:30 UTC.

  4. monitoring May 13, 2026, 03:26 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  5. monitoring May 13, 2026, 03:30 PM UTC

    CodeQL impact has been mitigated. We are continuing to monitor for durable recovery.

  6. resolved May 13, 2026, 04:03 PM UTC

    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.

Read the full incident report →

Minor May 11, 2026

Incident with high errors on Git Operations

Detected by Pingoru
May 11, 2026, 02:25 PM UTC
Resolved
May 11, 2026, 02:33 PM UTC
Duration
8m
Affected: Git Operations
Timeline · 2 updates
  1. investigating May 11, 2026, 02:25 PM UTC

    We are investigating reports of degraded performance for Git Operations

  2. resolved May 11, 2026, 02:33 PM UTC

    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.

Read the full incident report →

Critical May 7, 2026

CCR and CCA failing to start for PR comments

Detected by Pingoru
May 07, 2026, 05:02 AM UTC
Resolved
May 07, 2026, 06:56 AM UTC
Duration
1h 54m
Timeline · 4 updates
  1. investigating May 07, 2026, 05:02 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. monitoring May 07, 2026, 06:13 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  3. monitoring May 07, 2026, 06:14 AM UTC

    Copilot code review and cloud agents are starting again for pull requests, we are monitoring for full recovery.

  4. resolved May 07, 2026, 06:56 AM UTC

    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.

Read the full incident report →

Major May 6, 2026

Incident with Actions, we are investigating reports of degraded availability

Detected by Pingoru
May 06, 2026, 07:19 AM UTC
Resolved
May 06, 2026, 09:44 AM UTC
Duration
2h 25m
Affected: Actions
Timeline · 6 updates
  1. investigating May 06, 2026, 07:19 AM UTC

    We are investigating reports of degraded availability for Actions

  2. investigating May 06, 2026, 08:00 AM UTC

    Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue

  3. investigating May 06, 2026, 09:08 AM UTC

    We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery.

  4. monitoring May 06, 2026, 09:19 AM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  5. monitoring May 06, 2026, 09:44 AM UTC

    Actions wait times have fully recovered.

  6. resolved May 06, 2026, 09:44 AM UTC

    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.

Read the full incident report →

Minor May 5, 2026

Increased Latency and Failures for SSH Git Operations

Detected by Pingoru
May 05, 2026, 04:49 PM UTC
Resolved
May 05, 2026, 06:35 PM UTC
Duration
1h 46m
Affected: Git Operations
Timeline · 7 updates
  1. investigating May 05, 2026, 04:49 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. monitoring May 05, 2026, 04:54 PM UTC

    Between approximately 14:00 and 16:10 UTC, customers using SSH-based Git operations may have experienced elevated latency and failures. HTTP-based operations were not impacted. We've identified a suspected root cause and are working to implement a mitigation to prevent further impact.

  3. investigating May 05, 2026, 05:23 PM UTC

    Git Operations is experiencing degraded performance. We are continuing to investigate.

  4. investigating May 05, 2026, 05:26 PM UTC

    We're continuing to work on preventing further impact from the earlier issue. No SSH-based impact is expected at this time. We'll post new updates if impact recurs or once our mitigation is in place.

  5. monitoring May 05, 2026, 06:25 PM UTC

    The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability.

  6. monitoring May 05, 2026, 06:35 PM UTC

    We've completed our mitigation to prevent further impact. At this time the incident is considered resolved.

  7. resolved May 05, 2026, 06:35 PM UTC

    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.

Read the full incident report →

Minor April 24, 2026

Delays with Actions Jobs for Larger Runners using VNet Injection in the East US region

Detected by Pingoru
Apr 24, 2026, 07:02 PM UTC
Resolved
Apr 25, 2026, 12:36 AM UTC
Duration
5h 33m
Timeline · 4 updates
  1. investigating Apr 24, 2026, 07:02 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 24, 2026, 07:09 PM UTC

    We are investigating reports of degraded performance for Larger Runners with vnet injection in East US and we are working with our service provider on mitigation.

  3. investigating Apr 24, 2026, 07:14 PM UTC

    This is related to the public impact, "Multiservice impact for Azure Workloads in East US" shared at https://azure.status.microsoft/

  4. resolved Apr 25, 2026, 12:36 AM UTC

    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.

Read the full incident report →

Minor April 23, 2026

Disruption with users unable to start Claude and Codex agent task from the web

Detected by Pingoru
Apr 23, 2026, 07:28 PM UTC
Resolved
Apr 23, 2026, 07:42 PM UTC
Duration
13m
Timeline · 3 updates
  1. investigating Apr 23, 2026, 07:28 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 23, 2026, 07:33 PM UTC

    We have identified the root cause of the issue and are working on mitigation.

  3. resolved Apr 23, 2026, 07:42 PM UTC

    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.

Read the full incident report →

Critical April 23, 2026

Incident with multiple GitHub services

Detected by Pingoru
Apr 23, 2026, 04:12 PM UTC
Resolved
Apr 23, 2026, 05:30 PM UTC
Duration
1h 18m
Affected: WebhooksActionsCopilot
Timeline · 8 updates
  1. investigating Apr 23, 2026, 04:12 PM UTC

    We are investigating reports of degraded availability for Copilot and Webhooks

  2. investigating Apr 23, 2026, 04:19 PM UTC

    We are investigating multiple unavailable services.

  3. investigating Apr 23, 2026, 04:34 PM UTC

    Actions is experiencing degraded performance. We are continuing to investigate.

  4. investigating Apr 23, 2026, 04:52 PM UTC

    We have identified the root problem and are working on mitigation.

  5. investigating Apr 23, 2026, 05:03 PM UTC

    The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.

  6. investigating Apr 23, 2026, 05:04 PM UTC

    Many services are mitigated and are validating the remaining services.

  7. investigating Apr 23, 2026, 05:10 PM UTC

    Webhooks is operating normally.

  8. resolved Apr 23, 2026, 05:30 PM UTC

    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.

Read the full incident report →

Minor April 23, 2026

Investigating errors on GitHub

Detected by Pingoru
Apr 23, 2026, 02:40 PM UTC
Resolved
Apr 23, 2026, 03:18 PM UTC
Duration
38m
Affected: ActionsPackagesCodespacesCopilot
Timeline · 8 updates
  1. investigating Apr 23, 2026, 02:40 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating Apr 23, 2026, 02:41 PM UTC

    Packages is experiencing degraded performance. We are continuing to investigate.

  3. investigating Apr 23, 2026, 02:42 PM UTC

    Codespaces is experiencing degraded performance. We are continuing to investigate.

  4. investigating Apr 23, 2026, 02:44 PM UTC

    Copilot is experiencing degraded performance. We are continuing to investigate.

  5. investigating Apr 23, 2026, 02:51 PM UTC

    Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.

  6. investigating Apr 23, 2026, 03:02 PM UTC

    A mitigation was applied and services have recovered. Actions is working through queued work before fully recovering.

  7. monitoring Apr 23, 2026, 03:02 PM UTC

    The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.

  8. resolved Apr 23, 2026, 03:18 PM UTC

    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.

Read the full incident report →

Critical April 22, 2026

Disruption with Copilot chat and Copilot Coding Agent

Detected by Pingoru
Apr 22, 2026, 03:35 PM UTC
Resolved
Apr 22, 2026, 07:18 PM UTC
Duration
3h 42m
Timeline · 8 updates
  1. investigating Apr 22, 2026, 03:35 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 22, 2026, 03:43 PM UTC

    We are aware of users seeing errors interacting with Copilot chat on github.com and Copilot cloud agent. We have identified the cause and are investigating remediations.

  3. investigating Apr 22, 2026, 04:24 PM UTC

    We continue to work on mitigation for Copilot chat and cloud agent.

  4. investigating Apr 22, 2026, 04:58 PM UTC

    Mitigation is progressing for Copilot chat and cloud agent.

  5. investigating Apr 22, 2026, 05:40 PM UTC

    Mitigation is progressing for Copilot chat and cloud agent recovery.

  6. investigating Apr 22, 2026, 05:49 PM UTC

    We are now seeing recovery for Copilot cloud agent.

  7. investigating Apr 22, 2026, 06:05 PM UTC

    Copilot cloud agent and chat are mitigated for github.com.

  8. resolved Apr 22, 2026, 07:18 PM UTC

    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.

Read the full incident report →

Major April 16, 2026

Incident with Codespaces

Detected by Pingoru
Apr 16, 2026, 03:06 PM UTC
Resolved
Apr 16, 2026, 06:28 PM UTC
Duration
3h 21m
Affected: Codespaces
Timeline · 7 updates
  1. investigating Apr 16, 2026, 03:06 PM UTC

    We are investigating reports of degraded performance for Codespaces

  2. investigating Apr 16, 2026, 03:08 PM UTC

    We are experiencing degraded performance in Codespaces related to creating a new Codespace or starting an existing Codespace from the VS Code editor. SSH connections to Codespaces are not impacted. We are working toward mitigation and will continue to keep you updated on progress.

  3. investigating Apr 16, 2026, 03:41 PM UTC

    Codespaces is experiencing degraded availability. We are continuing to investigate.

  4. investigating Apr 16, 2026, 03:49 PM UTC

    We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.

  5. investigating Apr 16, 2026, 04:37 PM UTC

    Our provider is implementing a mitigation and we are seeing signs of recovery.

  6. monitoring Apr 16, 2026, 06:22 PM UTC

    The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.

  7. resolved Apr 16, 2026, 06:28 PM UTC

    On April 16, 2026 between 09:30 UTC and 17:15 UTC, users experienced failures when attempting to connect to GitHub Codespaces via the VS Code editor. During this time, approximately 40% of codespace start operations failed. Users connecting via SSH were not impacted. The issue was caused by a failure in an upstream download service that prevented the VS Code Server from being retrieved during codespace startup. The impact was mitigated by implementing a workaround to use an alternative download path when the primary endpoint is degraded. We are working with the upstream dependency to address the root cause of the download service failure, and we are improving our fallback mechanisms to reduce the impact of similar upstream failures in the future.

Read the full incident report →

Minor April 9, 2026

Disruption with GitHub notifications

Detected by Pingoru
Apr 09, 2026, 04:42 AM UTC
Resolved
Apr 09, 2026, 04:57 AM UTC
Duration
15m
Timeline · 3 updates
  1. investigating Apr 09, 2026, 04:42 AM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. monitoring Apr 09, 2026, 04:57 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  3. resolved Apr 09, 2026, 04:57 AM UTC

    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.

Read the full incident report →

Minor April 2, 2026

Copilot Coding Agent failing to start some jobs

Detected by Pingoru
Apr 02, 2026, 04:18 PM UTC
Resolved
Apr 02, 2026, 04:30 PM UTC
Duration
12m
Timeline · 3 updates
  1. investigating Apr 02, 2026, 04:18 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 02, 2026, 04:28 PM UTC

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

  3. resolved Apr 02, 2026, 04:30 PM UTC

    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

Read the full incident report →

Major April 1, 2026

Disruption with GitHub's code search

Detected by Pingoru
Apr 01, 2026, 03:02 PM UTC
Resolved
Apr 01, 2026, 11:45 PM UTC
Duration
8h 42m
Timeline · 7 updates
  1. investigating Apr 01, 2026, 03:02 PM UTC

    We are investigating reports of impacted performance for some GitHub services.

  2. investigating Apr 01, 2026, 04:00 PM UTC

    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.

  3. investigating Apr 01, 2026, 05:48 PM UTC

    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.

  4. investigating Apr 01, 2026, 07:37 PM UTC

    We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.

  5. investigating Apr 01, 2026, 10:00 PM UTC

    We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.

  6. investigating Apr 01, 2026, 11:45 PM UTC

    Code search has recovered and is serving production traffic.

  7. resolved Apr 01, 2026, 11:45 PM UTC

    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.

Read the full incident report →