GitHub Outage History

GitHub is up right now

GitHub had 76 outages in the last 2 years totaling 40h 15m of downtime — averaging 3.1 incidents per month.

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

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

Minor June 17, 2026

Disruption with Copilot next edit suggestions

Detected by Pingoru
Jun 17, 2026, 05:57 PM UTC
Resolved
Jun 17, 2026, 07:28 PM UTC
Duration
1h 30m
Timeline · 5 updates
  1. investigating Jun 17, 2026, 05:57 PM UTC

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

  2. investigating Jun 17, 2026, 06:40 PM UTC

    We have identified a likely cause and are applying a mitigation

  3. investigating Jun 17, 2026, 07:09 PM UTC

    We have applied mitigation and are seeing recovery

  4. monitoring Jun 17, 2026, 07:14 PM UTC

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

  5. resolved Jun 17, 2026, 07:28 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 June 17, 2026

Incident with Copilot Availability

Detected by Pingoru
Jun 17, 2026, 03:50 AM UTC
Resolved
Jun 17, 2026, 04:44 AM UTC
Duration
53m
Affected: Copilot
Timeline · 5 updates
  1. investigating Jun 17, 2026, 03:50 AM UTC

    We are investigating reports of degraded availability for Copilot

  2. investigating Jun 17, 2026, 03:52 AM UTC

    We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.

  3. investigating Jun 17, 2026, 04:26 AM UTC

    We've applied a mitigation to unblock Copilot functionality. Users may start to see signs of recovery. Relaunching your client should accelerate signs of recovery. We will continue to monitor the situation.

  4. monitoring Jun 17, 2026, 04:44 AM UTC

    Copilot is operating normally.

  5. resolved Jun 17, 2026, 04: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 →

Major June 16, 2026

Disruption with some GitHub services

Detected by Pingoru
Jun 16, 2026, 05:45 PM UTC
Resolved
Jun 16, 2026, 06:15 PM UTC
Duration
29m
Affected: Copilot AI Model Providers
Timeline · 5 updates
  1. investigating Jun 16, 2026, 05:45 PM UTC

    We are investigating reports of degraded availability for Copilot AI Model Providers

  2. investigating Jun 16, 2026, 05:47 PM UTC

    We are experiencing degraded availability for the Opus 4.8 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

  3. monitoring Jun 16, 2026, 06:00 PM UTC

    The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.

  4. monitoring Jun 16, 2026, 06:14 PM UTC

    The issues with our upstream model provider have been resolved, and Opus 4.8 is once again available in Copilot products and IDE surfaces. We will continue monitoring to ensure stability, but mitigation is complete.

  5. resolved Jun 16, 2026, 06:15 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 June 15, 2026

Multiple services have elevated errors and endpoint failures when checking feature flags

Detected by Pingoru
Jun 15, 2026, 06:32 PM UTC
Resolved
Jun 15, 2026, 07:10 PM UTC
Duration
38m
Timeline · 4 updates
  1. investigating Jun 15, 2026, 06:32 PM UTC

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

  2. monitoring Jun 15, 2026, 07:02 PM UTC

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

  3. monitoring Jun 15, 2026, 07:10 PM UTC

    We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services. Customers may have experienced failed requests or degraded functionality. A fix has been deployed and error rates are steadily decreasing. All affected services are now mitigated and we are monitoring recovery.

  4. resolved Jun 15, 2026, 07:10 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 June 15, 2026

Increased latency with webhooks

Detected by Pingoru
Jun 15, 2026, 03:37 PM UTC
Resolved
Jun 15, 2026, 05:37 PM UTC
Duration
2h
Affected: Webhooks
Timeline · 4 updates
  1. investigating Jun 15, 2026, 03:37 PM UTC

    We are investigating reports of degraded performance for Webhooks

  2. investigating Jun 15, 2026, 04:39 PM UTC

    Webhooks delivery latency has returned to normal levels. The backlog that built up during the incident has been cleared at approximately 4:29 UTC. We consider this incident resolved.

  3. monitoring Jun 15, 2026, 04:39 PM UTC

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

  4. resolved Jun 15, 2026, 05:37 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 June 11, 2026

Incident with Webhooks

Detected by Pingoru
Jun 11, 2026, 07:42 PM UTC
Resolved
Jun 11, 2026, 10:19 PM UTC
Duration
2h 37m
Affected: Webhooks
Timeline · 5 updates
  1. investigating Jun 11, 2026, 07:42 PM UTC

    We are investigating reports of degraded performance for Webhooks

  2. investigating Jun 11, 2026, 07:42 PM UTC

    We are currently experiencing delays in Web Hook delivery and are actively investigating the root cause.

  3. investigating Jun 11, 2026, 07:58 PM UTC

    We have applied a mitigation and are monitoring for recovery.

  4. monitoring Jun 11, 2026, 08:00 PM UTC

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

  5. resolved Jun 11, 2026, 10:19 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 →

Notice June 9, 2026

Degraded availability for GitHub.com, GraphQL API, and Webhooks UI/API

Detected by Pingoru
Jun 09, 2026, 03:48 PM UTC
Resolved
Jun 08, 2026, 03:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Jun 09, 2026, 03:48 PM UTC

    On June 8, 2026, between 14:49 and 14:54 UTC, a subset of requests to GitHub.com, the REST API, GraphQL API, and Webhooks UI/API experienced elevated error rates due to a transient infrastructure capacity issue that self-resolved within approximately 5 minutes. Users experienced HTTP 500 errors and timeouts when accessing GitHub.com, the REST API, GraphQL API, and Webhooks UI/API for approximately 5 minutes, with the REST API taking up to 12 minutes to fully recover.

Read the full incident report →

Minor June 8, 2026

Disruption with Claude Opus 4.7

Detected by Pingoru
Jun 08, 2026, 09:05 AM UTC
Resolved
Jun 08, 2026, 10:03 AM UTC
Duration
57m
Affected: Copilot AI Model Providers
Timeline · 4 updates
  1. investigating Jun 08, 2026, 09:05 AM UTC

    We are investigating reports of degraded performance for Copilot AI Model Providers

  2. investigating Jun 08, 2026, 09:08 AM UTC

    We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.

  3. investigating Jun 08, 2026, 09:49 AM UTC

    We are experiencing degraded availability for the Claude Opus 4.7 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue, and starting to see recovery.

  4. resolved Jun 08, 2026, 10:03 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 →

Critical June 8, 2026

Pull Requests and Issues unavailable for signed-out users

Detected by Pingoru
Jun 08, 2026, 07:11 AM UTC
Resolved
Jun 08, 2026, 08:36 AM UTC
Duration
1h 24m
Affected: IssuesPull RequestsActions
Timeline · 8 updates
  1. investigating Jun 08, 2026, 07:11 AM UTC

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

  2. investigating Jun 08, 2026, 07:14 AM UTC

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

  3. investigating Jun 08, 2026, 07:31 AM UTC

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

  4. investigating Jun 08, 2026, 07:32 AM UTC

    Pull Requests is experiencing degraded performance. We are continuing to investigate.

  5. investigating Jun 08, 2026, 08:13 AM UTC

    Following investigation, we are seeing that impact is limited to unauthenticated users when accessing Pull Requests or Issues. Our team continues to work towards mitigation with more updates to follow as we have them.

  6. investigating Jun 08, 2026, 08:27 AM UTC

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

  7. monitoring Jun 08, 2026, 08:35 AM UTC

    The degradation affecting Actions, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

  8. resolved Jun 08, 2026, 08: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 June 6, 2026

Disruption with some GitHub services in the EU region

Detected by Pingoru
Jun 06, 2026, 04:53 PM UTC
Resolved
Jun 06, 2026, 05:07 PM UTC
Duration
14m
Affected: Packages
Timeline · 3 updates
  1. investigating Jun 06, 2026, 04:53 PM UTC

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

  2. investigating Jun 06, 2026, 04:56 PM UTC

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

  3. resolved Jun 06, 2026, 05:07 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 June 6, 2026

EU Network Maintenance

Detected by Pingoru
Jun 06, 2026, 03:31 PM UTC
Resolved
Jun 06, 2026, 06:49 PM UTC
Duration
3h 17m
Timeline · 5 updates
  1. investigating Jun 06, 2026, 03:31 PM UTC

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

  2. investigating Jun 06, 2026, 03:31 PM UTC

    We are conducting routine maintenance on our network infrastructure in the EU. This will not impact production traffic, but may result in slightly increased latency for the remainder of our work. We expect this to last until 15:00 UTC.

  3. monitoring Jun 06, 2026, 03:36 PM UTC

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

  4. monitoring Jun 06, 2026, 06:48 PM UTC

    All work has been completed and we are hands off.

  5. resolved Jun 06, 2026, 06:49 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 June 5, 2026

Auth issue resulting in API impacts, including some Slack and Teams channel subscriptions

Detected by Pingoru
Jun 05, 2026, 05:20 PM UTC
Resolved
Jun 05, 2026, 10:21 PM UTC
Duration
5h
Timeline · 8 updates
  1. investigating Jun 05, 2026, 05:20 PM UTC

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

  2. investigating Jun 05, 2026, 05:25 PM UTC

    Customers may see unexpected repo unsubscription events in their Slack or Teams channels.

  3. investigating Jun 05, 2026, 06:04 PM UTC

    During 14:49 UTC to 16:45 UTC, customers may have experienced authorization failures for legitimate requests. This was caused by a recently enabled feature flag, which has now been turned off as a mitigation. Customers should now see normal authorization behavior. This is also the cause of the chat integration issue, and we are exploring options to restore it. In the meantime, customers can manually re-subscribe their repo.

  4. monitoring Jun 05, 2026, 06:05 PM UTC

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

  5. monitoring Jun 05, 2026, 06:43 PM UTC

    We are still exploring options to restore the deleted subscriptions, and we will provide another update soon. In the meantime, customers can manually re-subscribe their Slack and Teams channels to repositories.

  6. monitoring Jun 05, 2026, 08:34 PM UTC

    Additional detail on the scope of impact during the 14:49 UTC to 16:45 UTC window: a small but elevated percentage of authenticated requests to GitHub.com received incorrect authorization failures. We saw a 1 to 2% increase in 4xx responses for a small number of endpoints (/repos/{owner}/{repo}/pulls/{pull_number}, /repos/{owner}/{repo}, /repos/{owner}/{repo}/contents/{path}). The vast majority of requests completed normally; customers who saw errors during the window can retry now and should see them succeed.

  7. monitoring Jun 05, 2026, 10:21 PM UTC

    Affected Slack and Teams subscriptions have been restored. Please contact support if you encounter any additional issues.

  8. resolved Jun 05, 2026, 10:21 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 June 4, 2026

Live updates degraded

Detected by Pingoru
Jun 04, 2026, 08:20 PM UTC
Resolved
Jun 04, 2026, 08:32 PM UTC
Duration
11m
Timeline · 2 updates
  1. investigating Jun 04, 2026, 08:20 PM UTC

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

  2. resolved Jun 04, 2026, 08:32 PM UTC

    Everything is operating normally.

Read the full incident report →

Notice May 28, 2026

Elevated error rates across multiple services

Detected by Pingoru
May 28, 2026, 11:10 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 →

Minor May 20, 2026

Incident with Actions

Detected by Pingoru
May 20, 2026, 04:58 PM UTC
Resolved
May 20, 2026, 08:14 PM UTC
Duration
3h 15m
Affected: Actions
Timeline · 6 updates
  1. investigating May 20, 2026, 04:58 PM UTC

    We are investigating reports of degraded performance for Actions

  2. investigating May 20, 2026, 05:46 PM UTC

    A subset of runners are taking longer than expected to connect, which may delay some jobs from beginning execution. We are actively working to mitigate the issue.

  3. monitoring May 20, 2026, 05:52 PM UTC

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

  4. monitoring May 20, 2026, 06:17 PM 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.

  5. monitoring May 20, 2026, 07:41 PM UTC

    Customer impact has fully subsided. We are maintaining yellow status while we deploy a permanent fix to prevent recurrence.

  6. resolved May 20, 2026, 08:14 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 →