GitHub Outage History

GitHub is up right now

GitHub had 131 outages in the last 2 years totaling 116h 40m of downtime — averaging 5.4 incidents per month.

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

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

Notice May 28, 2026

Elevated error rates across multiple services

Detected by Pingoru
May 28, 2026, 07:07 PM UTC
Resolved
May 28, 2026, 07:07 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 28, 2026, 11:10 PM UTC

    On May 28, 2026, between 19:07 UTC and 19:16 UTC, multiple GitHub services experienced elevated error rates. This was due to a change that was partially deployed to an authentication service, causing errors for dependent services including the web experience, REST API, Git operations, and GitHub Actions. At peak impact, 10% of GitHub Actions runs failed to queue or encountered errors while downloading actions. We mitigated the incident by rolling back the change. We are expanding test coverage and improving our deployment validation process to prevent recurrence of this issue in the future.

Read the full incident report →

Critical May 28, 2026

Disruption with OpenAI Models

Detected by Pingoru
May 28, 2026, 07:01 PM UTC
Resolved
May 28, 2026, 08:41 PM UTC
Duration
1h 40m
Affected: Copilot
Timeline · 5 updates
  1. investigating May 28, 2026, 07:01 PM UTC

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

  2. investigating May 28, 2026, 07:20 PM UTC

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

  3. investigating May 28, 2026, 07:40 PM UTC

    We are investigating errors with Copilot requests using OpenAI models

  4. investigating May 28, 2026, 08:06 PM UTC

    Open AI models are currently unavailable. We are shifting requests to other models to reduce impact.

  5. resolved May 28, 2026, 08:41 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 28, 2026

Webhook APIs and UI Degraded

Detected by Pingoru
May 28, 2026, 01:13 AM UTC
Resolved
May 28, 2026, 01:32 AM UTC
Duration
18m
Affected: Webhooks
Timeline · 3 updates
  1. investigating May 28, 2026, 01:13 AM UTC

    We are investigating reports of degraded performance for Webhooks

  2. monitoring May 28, 2026, 01:27 AM UTC

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

  3. resolved May 28, 2026, 01:32 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 27, 2026

Incident with Pull Requests, Issues, Git Operations and API Requests

Detected by Pingoru
May 27, 2026, 12:10 PM UTC
Resolved
May 27, 2026, 01:16 PM UTC
Duration
1h 6m
Affected: Git OperationsAPI RequestsIssuesPull Requests
Timeline · 3 updates
  1. investigating May 27, 2026, 12:10 PM UTC

    We are investigating reports of degraded performance for API Requests, Git Operations, Issues and Pull Requests

  2. investigating May 27, 2026, 12:54 PM UTC

    We're continuing to investigate degraded performance of Git operations, Issues and Pull requests.

  3. resolved May 27, 2026, 01:16 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 26, 2026

Incident with Actions and Pages

Detected by Pingoru
May 26, 2026, 10:57 AM UTC
Resolved
May 26, 2026, 01:18 PM UTC
Duration
2h 21m
Affected: ActionsPages
Timeline · 8 updates
  1. investigating May 26, 2026, 10:57 AM UTC

    We are investigating reports of degraded performance for Actions and Pages

  2. investigating May 26, 2026, 11:19 AM UTC

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

  3. investigating May 26, 2026, 11:53 AM UTC

    We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.

  4. investigating May 26, 2026, 12:17 PM UTC

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

  5. investigating May 26, 2026, 12:37 PM UTC

    We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation

  6. monitoring May 26, 2026, 01:00 PM UTC

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

  7. monitoring May 26, 2026, 01:01 PM UTC

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

  8. resolved May 26, 2026, 01: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 May 25, 2026

Elevated rate of Git push errors

Detected by Pingoru
May 25, 2026, 09:02 AM UTC
Resolved
May 25, 2026, 09:02 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 08, 2026, 01:56 PM UTC

    On May 25, 2026, between 09:02 UTC and 09:11 UTC, Git push operations over HTTPS and SSH experienced elevated failures. During this window, an average of 31% and a peak of 43% of push requests failed. The incident was caused by a recently enabled code path that issued an unexpectedly expensive database query against a primary database. The resulting load exhausted the database's connection pool, which caused the push failures above. The acute impact resolved automatically as in-flight work completed. We mitigated the incident by disabling the feature flag controlling the new code path. We are working to route the affected read to a replica to reduce the likelihood of issues like this in the future.

Read the full incident report →

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, 02: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 →