Dev tools / Git hosting and CI / GitHub

GitHub

OPERATIONAL

Since Aug 2026 · 50 incidents · www.githubstatus.com · checked 2m ago

CompareStatus page
GradeFLast 73 days
DPRODFSHIP

Overview

30d90d1y
Admitted uptimeTime not covered by a widespread Sev 1 the provider posted itself. A best case.
100.000%Grade F
IncidentsEverything posted on the status page except scheduled maintenance.
171 Sev 1
Sev 1 downtimeTotal minutes of Sev 1 incidents, as posted.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
1h 45m
LongestLongest single incident, start to resolved.
18h 44m
Since lastTime since the last counted incident was resolved.
2h 27m

By area

AProduction
3INCIDENTS
4h 51mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 30d
SEV 2Oct 6, 2026 · 3h 43mSeveral services are degraded
SEV 2Oct 19, 2026 · 1h 08m · some customersDegraded availability for GitHub Actions, GitHub Pages and Webhooks
SEV 1Oct 7, 2026 · 0mIncident with Git Operations, Pull Requests and Actions
Most hit
Webhooks3
Actions2
Pull Requests2
Pages1
Worse. 13 in the last 6 months, 0 in the 6 before.
FShipping
15INCIDENTS
2d 13hAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 30d
SEV 2Oct 22, 2026 · 11h 02mProject updates delayed
SEV 2Oct 12, 2026 · 7h 54mIncident with Actions, Pull Requests and Issues
SEV 2Sep 23, 2026 · 18h 44m · regionalIncident across several services
Most hit
Actions9
Pull Requests6
Issues4
Webhooks4
Worse. 35 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Worse. 49 in the last 6 months, 0 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss1
Sev 2 · BleedingProd degraded or partly down8
Sev 3 · Can't shipCan't deploy, build or manage it6
Sev 4 · PapercutDocs, status page, slow dashboard2

When it breaks

Start times, last 12 months, UTC.

What breaks

Actions14 incidents
Pull Requests13 incidents
Issues8 incidents
Copilot AI Model Providers8 incidents
Webhooks6 incidents
API Requests5 incidents

Communication

Updates eachStatus page updates per incident, on average.
6.9Last 12 months
Update gapMedian time between status page updates during an incident.
12mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 23Sev 1–2

Incident history

Show all 50
Oct 22, 202611h 02mSEV 2
Project updates delayedIntermittent errors loading Issues, Pull Requests, search and Packages on github.com, plus degraded Actions and API requests, starting 2026-10-22. Capacity was added and the other services recovered by 18:26 UTC. GitHub Projects updates stayed delayed until mitigation at 00:55 UTC and resolution at 02:30 UTC on 2026-10-23. A root cause analysis is promised.AI-graded · API Requests +4
Why this grade
  1. RULES · SEV 3
    Sev 3 because API Requests had degraded performance
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Issues, pull requests, search and Actions had intermittent errors for hours; Projects updates stayed delayed until about 10 hours in.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
18 updates
  1. 15:28 UTC · investigating
    We are investigating reports of degraded performance for Actions, Issues and Pull Requests
  2. 15:33 UTC · investigating
    Some users may experience intermittent errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're investigating and working to restore normal service.
  3. 16:08 UTC · investigating
    Some users continue to experience intermittent errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're investigating and evaluating mitigation options to restore normal service.
  4. 16:26 UTC · investigating
    API Requests is experiencing degraded performance. We are continuing to investigate.
  5. 16:28 UTC · investigating
    Packages is experiencing degraded performance. We are continuing to investigate.
  6. 16:35 UTC · investigating
    API Requests is operating normally.
  7. 16:41 UTC · investigating
    Some users continue to experience errors loading Issues, Pull Requests, package listings and search results on github.com. <br /><br />We're working through multiple mitigation efforts and continuing to investigate.
  8. 17:16 UTC · investigating
    We're seeing recovery after adding capacity, with errors decreasing. Some users may still experience errors loading Issues, Pull Requests and search results on github.com. <br /><br />We're continuing to work towards full recovery and monitoring for stability.
  9. 17:41 UTC · investigating
    Actions, Issues, Packages and Pull Requests are operating normally.
  10. 17:43 UTC · investigating
    We're seeing recovery across the affected services. GitHub Projects is still recovering as queued updates are processed, and we're continuing to monitor for stability.
  11. 18:26 UTC · investigating
    The other affected services have recovered. <br /><br />We're continuing to investigate GitHub Projects and verify that normal operation has been restored.
  12. 19:04 UTC · investigating
    Some updates in GitHub Projects are still delayed. We're continuing mitigation work and monitoring.
  13. 19:56 UTC · investigating
    Some GitHub Projects updates related to issue changes and merged pull requests are still delayed. We're investigating the remaining delays and working to restore normal processing.
  14. 20:46 UTC · investigating
    Some GitHub Projects updates, including newly added items and changes to issues and pull requests, remain delayed.<br /><br />We've identified interruptions in update processing and are evaluating mitigations to restore normal operation.
  15. 22:07 UTC · investigating
    Some GitHub Projects updates, including newly added items and changes to issues and pull requests, are still delayed.<br /><br />We have seen some recovery, and are working to add more capacity to accelerate the recovery.
  16. 23:48 UTC · investigating
    GitHub Projects update processing has improved, but newly added items may still take longer than expected to appear. <br /><br />We're continuing to work on the remaining delays and monitor recovery.
  17. 00:55 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  18. 02:30 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.
Source
Oct 22, 20261h 01mSEV 3
Incident with Actions ResultsGitHub Actions workflow and step results were delayed for about an hour, along with some repository updates. Processing recovered after GitHub scaled processing capacity; no data loss was reported.AI-graded · Actions
Why this grade
  1. RULES · SEV 3
    Sev 3 because Actions had degraded performance
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    Delays in processing Actions workflow and step results and some repository updates for about an hour; runs still completed, just reported late.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
7 updates
  1. 14:18 UTC · investigating
    We are investigating reports of degraded performance for Actions
  2. 14:19 UTC · investigating
    We’re investigating delays in processing GitHub Actions workflow and step results, along with some repository updates.
  3. 14:35 UTC · investigating
    Repository update processing has recovered. We’re continuing to work on delays affecting GitHub Actions workflow and step results. We’ll share another update as we make progress.
  4. 15:06 UTC · investigating
    We’re seeing recovery, and repository update processing has returned to normal. Delays affecting GitHub Actions workflow and step results are continuing to clear as we scale processing capacity; the remaining backlog is expected to take about 20 minutes to drain.
  5. 15:17 UTC · monitoring
    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
  6. 15:18 UTC · monitoring
    GitHub Actions workflow and step result processing has recovered. Repository update processing has also returned to normal.
  7. 15:18 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.
Source
Oct 21, 20264h 30mSEV 2
Delays for Pull Requests and Webhook deliveriesGitHub experienced delays to pull request updates, webhook deliveries, and Actions workflow status on October 21, caused by load on its event streaming platform. Pull requests and Actions recovered by about 17:00 UTC, and webhooks recovered soon after. Audit log events stayed delayed by up to 110 minutes before recovering by about 19:20 UTC. A root cause analysis is promised.AI-graded · Webhooks +2
Why this grade
  1. RULES · SEV 2
    Sev 2 because Webhooks had a major outage
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Pull request updates, webhook deliveries and Actions status were delayed for about one to two hours; audit log delays lasted longer, with no data loss.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
15 updates
  1. 14:52 UTC · investigating
    We are investigating reports of degraded performance for Actions, Pull Requests and Webhooks
  2. 15:15 UTC · investigating
    Actions is experiencing degraded performance. We are continuing to investigate.
  3. 15:36 UTC · investigating
    We are investigating delays affecting pull request updates and webhook deliveries. Increased load on our event streaming platform is contributing to hotspots. We are shifting traffic away from affected areas and adding processing capacity; impact is ongoing while these mitigations take effect.
  4. 15:58 UTC · investigating
    We continue to see delays affecting pull request updates, webhook deliveries, and audit log events. The event streaming platform is showing signs of recovery, and we are monitoring as the impact continues.
  5. 16:17 UTC · investigating
    Audit log events and Actions workflow status updates continue to be delayed. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring the recovery and will share further updates as we learn more.
  6. 16:25 UTC · investigating
    Audit log events are delayed by up to 100 minutes, and Actions workflow status updates continue to experience extended delays. Pull request updates and webhook deliveries are recovering as we restore event processing and work through backlogs. We’re monitoring recovery and will share further updates as we learn more.
  7. 16:33 UTC · investigating
    Pull Requests is operating normally.
  8. 16:34 UTC · investigating
    Audit log events continue to be delayed by up to 110 minutes. Pull request updates have recovered. Actions is recovering, and users should no longer experience impact in Actions. Webhook deliveries continue to recover as we work through backlogs. We are monitoring recovery and will share further updates as we learn more.
  9. 16:57 UTC · investigating
    Actions and Webhooks are operating normally.
  10. 16:59 UTC · investigating
    Actions and webhook deliveries have recovered. Audit log events are still delayed by about 100 minutes. We are working through the backlog, and full recovery will take some time. We will share more updates as recovery continues.
  11. 17:09 UTC · investigating
    Pull request updates, Actions, and webhook deliveries have recovered. Audit log events are recovering and delays are decreasing, but we expect the remaining backlog to take approximately two to three hours to clear. We’re monitoring recovery and will share further updates.
  12. 18:18 UTC · investigating
    Audit log events are recovering, with delays now below 90 minutes as the remaining backlog is processed. We’ve reduced load on the event-streaming platform and are monitoring recovery. Further updates will follow.
  13. 18:52 UTC · investigating
    Audit log events continue to recover, with delays now below 70 minutes. We’ve applied mitigations to speed recovery and expect audit logs to fully recover in about 40 minutes. Pull request updates, Actions, and webhook deliveries remain recovered. We are monitoring progress and will share further updates.
  14. 19:22 UTC · investigating
    Pull request updates, Actions, and webhook deliveries have recovered. Audit log delays are now below 40 minutes, within the healthy threshold, and continue to decrease as the remaining backlog is processed.
  15. 19:22 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.
Source
Oct 19, 20261h 08mSEV 2
Degraded availability for GitHub Actions, GitHub Pages and WebhooksGitHub Actions, Pages and Actions-generated webhooks were degraded from about 15:24 to 16:52 UTC on October 19, 2026. About 5% of GitHub-hosted runner jobs started late and 0.02% of runs failed, while 8.5% of Actions jobs API requests errored in the first 30 minutes. No data was lost. Cause was an internal Actions service overloading a shared network link after simultaneous reconnect retries; a connection limit is now enforced.AI-graded · some customers · Webhooks +2
Why this grade
  1. RULES · SEV 1
    Sev 1 because the provider reported data loss or exposure
  2. CLAUDE · SEV 2 · SUBSET · HIGH CONFIDENCE
    Actions job starts were delayed for about 5% of runners and 0.02% of runs failed; Pages deploys and Actions webhooks were delayed for about 90 minutes.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
6 updates
  1. 15:49 UTC · investigating
    We are investigating reports of degraded performance for Actions and Pages
  2. 15:50 UTC · investigating
    Webhooks is experiencing degraded performance. We are continuing to investigate.
  3. 15:56 UTC · investigating
    We’re are currently investigating degraded availability affecting GitHub Actions, GitHub Pages and Webhooks. <br /><br />Customers may experience delays in workflow processing, site builds and webhook delivery.<br />
  4. 16:30 UTC · investigating
    We’re seeing recovery following mitigation and are continuing to monitor. <br /><br />Customers may still experience delays in GitHub Actions workflow status updates, GitHub Pages deployments, and check and workflow webhook events generated by Actions runs.
  5. 16:56 UTC · monitoring
    Actions, Pages and Webhooks are operating normally.
  6. 16:56 UTC · resolved
    On October 19, 2026, between 15:24 and 16:52 UTC, GitHub Actions, GitHub Pages, and webhooks generated by Actions were degraded. Live updates on GitHub.com and code search were also degraded for part of this time. No data was lost. <br /><br />Impact <br /><br /> - Workflow status updates, logs, and checks were delayed. <br /> - 5.13% of jobs on GitHub-hosted runners were delayed in starting, and 0.02% of workflow runs failed. <br /> - During the first 30 minutes, 8.47% of requests to the Actions jobs REST API returned errors. <br /><br />Pages deployments and webhooks generated by Actions runs were delayed. <br /><br />An internal Actions service that stores logs and run status lost connections to some of its cache servers in one cloud region and immediately retried them from every server at once. The resulting surge of new connections overloaded a shared network link between our data center and that region, which also disrupted other services that use the same link. We mitigated the incident by moving the Actions service off the affected cache servers and reducing connections from other services on the link. We then processed the delayed Actions work. We are continuing to investigate the cause of the initial connection timeouts. <br /><br />We were already in the process of rolling out a limit on how quickly this service can open new connections, but it was still in shadow mode (logging only, not enforcing) at the time of the incident. We have since fully enforced it and capped the service's concurrent connection attempts. We are extending these limits to other Actions services, adding backoff to retries, limiting how much shared network capacity a single service can use, and improving alerting so we can find the source of connection surges faster.
Source
Oct 15, 202624mNOT COUNTED
CCA Automations are delayed when starting an AutomationGitHub first reported delays when users started CCA Automations and mitigated a degradation. It later resolved the incident, stating investigation found no delay or impact to CCA Automations.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 0 · UNCLEAR · MEDIUM CONFIDENCE
    Initially reported as delays starting CCA Automations, but GitHub later found no delay or impact and resolved it as a false alarm.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
4 updates
  1. 18:31 UTC · investigating
    We are investigating reports of impacted performance for some GitHub services.
  2. 18:34 UTC · investigating
    CCA Automations are experiencing delays when users start an Automation
  3. 18:53 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  4. 18:56 UTC · resolved
    We suspected that CCA Automations were experiencing delays when users start an Automation, but further investigation found that there was no delay or impact to CCA Automations.<br />
Source
Oct 14, 20260mSEV 3
[Retroactive] Actions workflow run logs delayedSev 3 from the incident title (no components listed)
1 update
  1. 20:30 UTC · resolved
    On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.
Source
Oct 12, 20267h 54mSEV 2
Incident with Actions, Pull Requests and IssuesElevated 500 errors hit GitHub Actions, Pull Requests, Issues and Projects from about 11:51 to 12:41 UTC, with runs queuing and PR reviews failing. A notifications pipeline issued an expensive query that exhausted shared database replica capacity. Web and email notifications stayed delayed until 20:16 UTC. The query path was fixed.AI-graded · Issues +2
Why this grade
  1. RULES · SEV 3
    Sev 3 because Pull Requests had degraded performance
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Elevated 500s hit Actions runs, Pull Requests and Issues for about 40 minutes; notifications were delayed for hours.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
13 updates
  1. 12:21 UTC · investigating
    We are investigating reports of degraded performance for Actions, Issues and Pull Requests
  2. 12:33 UTC · investigating
    Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs.
  3. 12:57 UTC · investigating
    We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
  4. 13:02 UTC · investigating
    Pull Requests is operating normally.
  5. 13:38 UTC · investigating
    Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.
  6. 14:35 UTC · investigating
    The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
  7. 14:36 UTC · investigating
    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
  8. 14:37 UTC · investigating
    We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
  9. 15:19 UTC · investigating
    We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
  10. 15:50 UTC · investigating
    Notifications have resumed but will continue to be delayed as we work through a backlog.
  11. 17:34 UTC · investigating
    Web and email notifications continue to be delayed as we work through a backlog of notifications.
  12. 19:28 UTC · investigating
    Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
  13. 20:16 UTC · resolved
    On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. <br /><br />The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC. <br /><br />The incident was triggered through a latent condition in our notifications delivery pipeline that put a high volume of an expensive query on our sharded database replicas. This reduced available database capacity to serve requests for Issues, Pull Requests, Projects, and Actions.<br /><br />We have fixed the notifications pipeline’s code path that issued the expensive query. We are also improving resilience of the database layer to reduce the likelihood and impact of similar incidents.
Source
Oct 7, 202648mSEV 2
Incident with Git Operations, Issues, Actions and Pull RequestsGitHub had widespread degradation of Git operations, Actions, pull requests and issues from 16:52 to 17:01 UTC, a recurrence of an earlier outage. Mitigations were applied and all systems recovered. The shared root cause is described in the linked combined summary of both incidents.AI-graded · Git Operations +3
Why this grade
  1. RULES · SEV 2
    Sev 2 because Git Operations had a major outage
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Git operations, Actions, pull requests and issues degraded across GitHub for about nine minutes during a write-operation outage.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
5 updates
  1. 17:17 UTC · investigating
    We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests
  2. 17:25 UTC · investigating
    We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes.
  3. 17:27 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  4. 18:00 UTC · monitoring
    All systems have recovered. We have applied mitigations and do not anticipate another recurrence.
  5. 18:04 UTC · resolved
    On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7
Source
Oct 7, 20260mSEV 1
Incident with Git Operations, Pull Requests and ActionsSev 1 because the provider reported data loss or exposureGit Operations +4
20 updates
  1. 15:14 UTC · investigating
    We are investigating reports of degraded availability for Actions, Git Operations and Pull Requests
  2. 15:14 UTC · investigating
    Webhooks is experiencing degraded performance. We are continuing to investigate.
  3. 15:15 UTC · investigating
    Issues is experiencing degraded performance. We are continuing to investigate.
  4. 15:16 UTC · investigating
    Webhooks is experiencing degraded availability. We are continuing to investigate.
  5. 15:21 UTC · investigating
    Git Operations is experiencing degraded performance. We are continuing to investigate.
  6. 15:24 UTC · investigating
    We observed widespread impact across GitHub services between 15:06 UTC and 15:16 UTC, and are investigating the root cause. We are seeing all systems recover, and will provide another update shortly.
  7. 15:25 UTC · investigating
    Pull Requests is experiencing degraded performance. We are continuing to investigate.
  8. 15:27 UTC · investigating
    Git Operations is operating normally.
  9. 15:27 UTC · investigating
    Webhooks is experiencing degraded performance. We are continuing to investigate.
  10. 15:31 UTC · investigating
    The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
  11. 15:32 UTC · investigating
    Actions is operating normally.
  12. 15:35 UTC · investigating
    Git Operations is experiencing degraded performance. We are continuing to investigate.
  13. 15:41 UTC · investigating
    We are observing partial recovery across all systems. We are continuing to monitor and investigate the root cause of the disruption.
  14. 15:47 UTC · investigating
    The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
  15. 15:49 UTC · investigating
    The degradation affecting Git Operations and Webhooks has been mitigated. We are monitoring to ensure stability.
  16. 15:49 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  17. 15:56 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  18. 15:58 UTC · monitoring
    We are seeing full recovery across all systems including Git Operations, Pull Requests and Actions. We are continuing to investigate the root cause of the disruption between 15:06 UTC and 15:16 UTC, and will share another update shortly.
  19. 16:23 UTC · monitoring
    Git Operations, Pull Requests and Actions are fully recovered and stable. The root cause has been identified and mitigations are being applied to prevent a reoccurrence.
  20. 16:25 UTC · resolved
    On October 7, 2026, GitHub had two outages of write operations with the same cause, totaling about 19 minutes. The first ran from 15:06 to 15:16 UTC (about 10 minutes) and the second from 16:52 to 17:01 UTC (about 9 minutes). In both windows, actions that save or change data failed across Git operations, pull requests, issues, GitHub Actions, the API, webhooks, sign-in and authentication, GitHub Apps and OAuth, code scanning, Codespaces, and Copilot. Reading data was largely unaffected. In the first outage, 5.6% of all web and API requests failed, peaking at 8.9%, and more than 12,000 organizations saw failed requests. Up to 26% of Git authentication requests failed, and 17% of Actions workflow runs failed with infrastructure errors. In the second outage, 6.2% of web and API requests failed, peaking at 9.3%, and more than 11,000 organizations were affected. Up to 25% of Git authentication requests failed, and 19% of Actions workflow runs failed. No databases experienced data loss, and operations retried after recovery succeeded. GitHub relies on an internal service that keeps track of which database servers should receive new and updated data. While replacing machines that run this service as part of regular maintenance, one of the new machines started with an outdated copy of its records, which still listed database servers we had already retired. When this node came online, it incorrectly modified routing configuration with the outdated records, routing write requests to non-existent database servers. Each outage ended when one of our established machines with correct configuration became the leader of the quorum and sent the correct configuration. After the first outage, we identified the new machine as the source and paused automated maintenance to stop it from being leader again. At 16:52 UTC, an automated maintenance task that did not honor the pause put it back in charge, and the outage happened again. We shut that machine down at 17:02 UTC and have since removed it, and the automation now honors the pause, which was a new regression due to an update of our puppet infrastructure. To prevent recurrence, we are clearing retired database servers from the service's records before any new machine is added, and we are keeping new machines from being elected leader until their records have been checked. We are also changing our systems to reject configuration that point to servers that don't exist and to keep using the last known-good settings instead. Finally, we are giving responders a faster way to take a misbehaving machine out of service, and adding alerts so changes like this are spotted within seconds. We will share a more detailed write-up of these incidents in our monthly availability report, along with the status of the repairs we are making to prevent issues like these in the future.
Source
Oct 6, 20263h 43mSEV 2
Several services are degradedA database connection pool saturated by long GitHub Enterprise Importer queries caused elevated error rates, about 1.30% of requests, across 12 services from 19:44 to 19:50 UTC. Recovery came when the migration calls stopped. Enterprise migrations stayed paused until a code fix merged and they resumed at 23:32 UTC.AI-graded · Webhooks +1
Why this grade
  1. RULES · SEV 2
    Sev 2 because Webhooks had a major outage
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    Pull requests, webhooks, OAuth, Git over SSH and other services saw elevated errors for about six minutes; GEI migrations stayed paused until 23:32 UTC.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
9 updates
  1. 19:57 UTC · investigating
    We are investigating reports of degraded performance for Pull Requests and Webhooks
  2. 20:04 UTC · investigating
    Webhooks is operating normally.
  3. 20:12 UTC · investigating
    Pull Requests is operating normally.
  4. 20:22 UTC · investigating
    A number of services including issues, pull requests, and webhooks, were briefly degraded, but have now recovered. Enterprise migrations are paused while we validate causes and mitigations.
  5. 20:26 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  6. 20:57 UTC · investigating
    All services are functioning normally except for enterprise migrations, which are still paused. They will resume soon.
  7. 21:29 UTC · investigating
    We are working towards a mitigation that will allow us to resume processing enterprise migrations.
  8. 22:40 UTC · investigating
    We are deploying a mitigation and plan to resume migrations shortly thereafter
  9. 23:40 UTC · resolved
    On October 6, 2026, from 19:44 to 19:50 UTC, GitHub experienced a service outage with elevated error rates peaking at 1.30% of all requests, totaling approximately 1.16 million failed requests. This impacted 12 services across GitHub, including Pull Requests, Webhooks, Repos, OAuth, Git over SSH, Codespaces, and Gists. The incident was triggered by GitHub Enterprise Importer (GEI) making multiple, long duration queries which saturated a database connection pool. Recovery was seen at approximately 19:50 UTC once the migration's calls stopped; GEI migrations were reenabled at 23:32 UTC after a code fix was merged.<br /><br />We have completed a detailed root-cause review and are implementing improved database-health safeguards. We will continue to review and add additional safeguards to prevent future recurrence.
Source
Oct 5, 20261h 45mSEV 3
Disruption with some GitHub servicesA networking failure between one on-premises datacenter region and some cloud-hosted regional database services caused slow pages, timeouts and errors on organization and enterprise billing, licensing and settings pages from 23:05 to 00:11 UTC. Average error rate was 1.9%, peaking at 13.8%. Traffic was shifted to a healthy region to mitigate it.AI-graded · some customers
Why this grade
  1. RULES · SEV 3
    Sev 3 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · HIGH CONFIDENCE
    Organization and enterprise billing, licensing and settings pages showed slow loads and errors for about an hour; average error rate 1.9%.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
3 updates
  1. 23:47 UTC · investigating
    We are investigating reports of impacted performance for some GitHub services.
  2. 00:05 UTC · investigating
    Users may experience issues accessing organization and enterprise billing and licensing pages. We are deploying a mitigation and monitoring for recovery.
  3. 01:32 UTC · resolved
    On October 5, 2026, between 23:05 UTC and 00:11 UTC on October 6, some users experienced slow page loads, timeouts, and errors when accessing organization and enterprise billing, licensing, and settings pages. On average, the error rate was 1.9% and peaked at 13.8% of requests to the service that powers these pages.<br /><br />This was caused by a networking failure, which disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database services. We mitigated the incident by shifting the database traffic to a healthy region.<br /><br />We are working to make regional database failover faster and more complete, reduce timeouts so these pages fail fast instead of hanging, and add latency-based alerting to reduce our time to detection and mitigation of issues like this one in the future. We continue to partner with our cloud provider to understand the underlying network failure.
Source
Oct 5, 20263h 38mSEV 2
Incident with ActionsGitHub-hosted Actions runners failed or delayed jobs from about 18:48 to 22:49 UTC on October 5, 2026. At peak 47% of runs failed. A network failure between an on-premises region and cloud database and storage services caused it. Traffic was shifted and capacity added. Some repository list, billing and licensing pages also had intermittent errors. Self-hosted runners were not affected.AI-graded · some customers · Actions +1
Why this grade
  1. RULES · SEV 1
    Sev 1 because Pages had a major outage
  2. CLAUDE · SEV 2 · SUBSET · HIGH CONFIDENCE
    GitHub-hosted Actions runs failed or stalled for about four hours; self-hosted runners and existing Pages sites were unaffected.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
12 updates
  1. 19:11 UTC · investigating
    We are investigating reports of degraded performance for Actions
  2. 19:15 UTC · investigating
    We’re investigating an issue causing delays when assigning GitHub-hosted runners to Actions jobs. Some workflows may take longer to start across runner configurations. Our teams are working to mitigate the issue, and we’ll provide an update as we learn more.
  3. 19:50 UTC · investigating
    We’re still investigating delays in assigning GitHub-hosted runners, affecting workflow start times across multiple runner configurations. Our teams are working to mitigate the impact; we’ll share another update as we learn more.
  4. 20:39 UTC · investigating
    We’re continuing to investigate job failures and delays affecting GitHub-hosted runner assignment and workflow start times. Our teams are actively working to mitigate the impact and will provide another update as we learn more.
  5. 20:47 UTC · investigating
    Actions is experiencing degraded availability. We are continuing to investigate.
  6. 21:09 UTC · investigating
    In addition to ongoing issues with Actions and Hosted Runners, some customers are also unable to access repository list, licensing and billing pages within their GitHub accounts. We continue to investigate and are working on mitigation.
  7. 21:22 UTC · investigating
    Pages is experiencing degraded performance. We are continuing to investigate.
  8. 21:31 UTC · investigating
    Actions is experiencing degraded performance. We are continuing to investigate.
  9. 21:32 UTC · investigating
    We have applied mitigations to address GitHub Actions failures. Queued jobs are clearing, new jobs are not delayed, and we expect full runner recovery shortly. We continue to monitor for full recovery and are working to mitigate ongoing issues affecting other services, including access to repository lists, licensing, and billing pages.
  10. 21:54 UTC · investigating
    Actions is operating normally.
  11. 22:40 UTC · investigating
    Pages is operating normally.
  12. 22:49 UTC · resolved
    On October 5, 2026, between 18:48 and 22:49 UTC, GitHub Actions and Hosted Runners experienced degraded performance. Over the full incident, 14.3% of workflow runs using GitHub-hosted runners and 26.5% of individual GitHub-hosted jobs did not start within five minutes. <br /><br /> <br />During the roughly 90-minute period of highest impact, 47.0% of workflow runs using GitHub-hosted runners failed and 71.9% of GitHub-hosted jobs did not start within five minutes, while existing Pages sites continued to serve normally. A portion of customers also encountered intermittent errors in repository lists, licensing and billing pages, and some Copilot features. Self-hosted runners were not affected. <br /><br /><br />The incident was caused by a partial networking failure that disrupted connectivity between one of our on-premises datacenter regions and a subset of cloud-hosted regional database and storage services. <br /><br /><br />We mitigated the incident by shifting database and storage traffic to healthy regions and endpoints and increasing capacity for affected compute services. GitHub Actions and Hosted Runners recovered by 21:54 UTC, and all affected services recovered by 22:49 UTC. <br /><br /> <br />We are partnering with our cloud provider to understand the network failure and identify improvements to network-path resilience, detection, and recovery for similar incidents.
Source
Oct 1, 20263h 09mSEV 3
Actions Job DelaysGitHub-hosted Actions runners had delayed or failed job starts on Oct 1, 2026, from about 14:15 to 17:56 UTC. About 0.68% of runs were delayed and 0.196% of jobs failed to start. A cloud provider routing change caused rate-limit errors, and retry behavior added load. Runner subscriptions were excluded from the inventory service and capacity was scaled, and the provider raised rate limits.AI-graded · some customers · Actions
Why this grade
  1. RULES · SEV 2
    Sev 3 because Actions had degraded performance, raised to Sev 2 for security
  2. CLAUDE · SEV 3 · SUBSET · HIGH CONFIDENCE
    Job starts on GitHub-hosted runners were delayed or failed for about 0.2% of jobs and 0.68% of runs over several hours; most of Actions worked.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
10 updates
  1. 14:47 UTC · investigating
    We are investigating reports of degraded performance for Actions
  2. 14:54 UTC · investigating
    We have identified the cause of increased Actions run start delays on Ubuntu runners and are actively deploying a fix. Customers may continue to experience intermittent delays while the mitigation rolls out and service metrics return to normal.
  3. 15:02 UTC · investigating
    Run-start delays on Ubuntu runners have been resolved. We are investigating run-start delays on Windows runners and will share more information as it becomes available.
  4. 15:10 UTC · monitoring
    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
  5. 15:20 UTC · investigating
    Actions is experiencing degraded performance. We are continuing to investigate.
  6. 15:29 UTC · investigating
    We are seeing a reoccurrence in run-start delays, and are continuing to investigate to issue. Customers will potentially experience delays of up to ten minutes.
  7. 16:10 UTC · investigating
    We have identified an issue with our upstream provider which is causing Actions requests to 429 which is creating the delays. We have escalated to the owning team and are investigating how to mitigate the 429s.
  8. 16:48 UTC · investigating
    We are currently applying a mitigation and anticipate recovery within thirty minutes.
  9. 17:50 UTC · investigating
    GitHub Actions experienced degraded performance for some hosted runners due to throttling within an upstream Azure dependency. Service capacity has recovered, and we are continuing to monitor while working with Azure on the underlying condition.
  10. 17:56 UTC · resolved
    On October 1, 2026, GitHub Actions experienced two periods of delayed and failed job starts on GitHub-hosted runners, beginning at approximately 14:15 UTC. Across the 14:15–17:56 UTC incident-response window, approximately 0.68% of workflow runs experienced start delays, and 0.196% of jobs failed to start. <br /><br />A routing change at our cloud provider concentrated API traffic on a single backend, causing an increase in rate-limit errors. Incorrect retry behavior in the provider’s inventory service added load to the affected APIs, compounding the rate limiting. This disrupted runner provisioning and reduced available capacity in affected regions. The resulting increase in demand in unaffected regions exposed a concurrency limit in our job-assignment system, delaying jobs even where runners were available. <br /><br />During the response, we increased job-assignment concurrency, scaled runner capacity, and worked with our cloud provider to reduce API load by excluding our runner subscriptions from its inventory service. By approximately 16:15 UTC, jobs were starting and executing as expected. We continued mitigation and monitoring until the incident was resolved at 17:56 UTC. <br /><br />Our cloud provider has since increased resource-management API rate limits for our workloads. To reduce the likelihood and impact of similar incidents, we are also adding more granular rate-limiting alerts and updating our job-assignment system to handle increased demand across fewer available regions.
Source
Oct 1, 202620mSEV 4
Elevated request latencyGitHub.com experienced two periods of slow page loads and intermittent request failures from 13:04 to 13:34 UTC on October 1, 2026. The error rate averaged 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic delayed requests before they reached application servers. Performance recovered as traffic subsided, and additional traffic filtering was applied.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · GLOBAL · MEDIUM CONFIDENCE
    GitHub.com web requests were slow and intermittently failed for about 30 minutes, averaging a 0.52% error rate and peaking at 6.13%.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
4 updates
  1. 13:37 UTC · investigating
    We are investigating reports of impacted performance for some GitHub services.
  2. 13:39 UTC · investigating
    We are investigating recurrent periods of elevated latency affecting web requests. We’ll share updates as more information becomes available.
  3. 13:51 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  4. 13:57 UTC · resolved
    On October 1, 2026, between 13:04 UTC and 13:34 UTC, users experienced two periods of slow page loads and intermittent request failures on GitHub.com. On average, the error rate was 0.52% and peaked at 6.13%. An unusually high volume of incoming traffic placed additional load on our traffic-handling infrastructure, delaying requests before they reached our application servers. Performance returned to normal as the traffic subsided, and we have since applied additional traffic filtering to protect against similar traffic. We are improving alerting for delays in our traffic-handling infrastructure and strengthening our automated traffic protections to reduce our time to detection and mitigation.
Source
Oct 1, 20260mSEV 3
[Retroactive] Actions workflow run failures after deployment gate approvalsSev 3 from the incident title (no components listed)
1 update
  1. 02:00 UTC · resolved
    On October 1, around 02:00 UTC, an isolated infrastructure failure caused GitHub Actions to lose execution state for a small number of existing workflow runs. Affected runs may remain stuck, fail deployment approvals, or return errors when cancelled. Service connectivity has recovered, but the lost state cannot be restored by retrying an approval. If you're affected, you can trigger a new run or contact GitHub Support with links to your stuck runs so we can unblock them. Once cleared, select "Re-run all jobs." This preserves the workflow run ID but starts a new attempt, rebuilds artifacts, and requires fresh deployment approvals. Before rerunning, check whether any deployment steps already completed to avoid repeating changes.
Source
Sep 28, 202652mSEV 4
Copilot Code Review is unable to complete reviewsSev 4 from the incident title (no components listed)
4 updates
  1. 21:16 UTC · investigating
    We are investigating reports of impacted performance for some GitHub services.
  2. 21:23 UTC · investigating
    Revert of the impacted change is in flight, expect full recovery once the deployment is done.
  3. 22:08 UTC · investigating
    Copilot Code review has recovered, for reviews that were previously not successful you can re-request review from your PR.
  4. 22:08 UTC · resolved
    On September 28, 2026, between 19:23 UTC and 22:08 UTC the Copilot Code Review service was degraded and pull request reviews did not complete in all environments. On average, approximately 70% of requested reviews did not complete. Reviews requested during this window were not automatically retried, and users needed to re-request a review from their pull request. This was due to a change in a dependent service that stopped delivering data Copilot Code Review needs to complete a review. Review completion is an inherently delayed signal, because each review job takes time to start and finish, so it took longer to detect the impact.<br /><br />We mitigated the incident by reverting the change.<br /><br />We are working to add a faster signal for reviews that fail to complete, add deployment validation that confirms a Copilot Code Review completes end to end, improve how we track internal dependencies between services, and make our deployment pipeline more reliable to reduce our time to detection and mitigation of issues like this one in the future.
Source
Sep 24, 20263h 50mSEV 3
Disruption with billing information updatesUsers could not reliably add or update billing address information because requests to the address validation service stalled or timed out. About 1,700 users were affected from September 22 to September 24, 2026. An OS upgrade exposed an HTTP client adapter incompatibility; the fix was switching the HTTP client used for address validation, and alerting was added.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 3 from the incident title (no components listed), raised to Sev 2 for security
  2. CLAUDE · SEV 3 · SUBSET · HIGH CONFIDENCE
    Billing address updates failed for about 1,700 users, at up to 100% of requests in the flow, for roughly two days.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
7 updates
  1. 16:51 UTC · investigating
    We are investigating reports of impacted performance for some GitHub services.
  2. 16:51 UTC · investigating
    We are investigating failures on billing information updates. Customers may be unable to create or update their billing information in the meantime.
  3. 17:40 UTC · investigating
    We have identified the problem and are actively working on mitigation.
  4. 18:22 UTC · investigating
    We are continuing to work on mitigation. We will post another update in approximately one hour.
  5. 20:10 UTC · investigating
    We have applied the mitigation and are seeing signs of recovery. We are continuing to monitor the system closely.
  6. 20:24 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  7. 20:41 UTC · resolved
    Beginning on September 22, 2026 at 11:51 UTC, approximately 1,700 users experienced delays and errors when adding or updating billing address information because requests to the address validation service timed out or failed. Within the affected address validation flow, requests failed at an average rate of 69.3%, reaching 100% at peak. <br /><br />An operating system upgrade exposed a compatibility issue in an adapter used by our HTTP client library, causing requests to stall. A subsequent change to shorten request timeouts caused stalled requests to return connection errors and increased the failure rate. <br /><br />We mitigated the incident on September 24, 2026 at 20:24 UTC by changing the HTTP client used for address validation. We have added alerting to detect similar issues sooner and are extending the fix to other integrations.
Source
Sep 23, 202618h 44mSEV 2
Incident across several servicesA failed planned database maintenance triggered a failover that left replicas in Azure Central US unable to resume replication. GitHub API requests, org creation, GitHub App installs and membership changes failed or degraded from 07:57 UTC on September 23 until errors were mitigated at 10:58 UTC. Projects label updates and search stayed delayed until full service returned at 04:55 UTC on September 24.AI-graded · regional · API Requests
Why this grade
  1. RULES · SEV 3
    Sev 3 because API Requests had degraded performance
  2. CLAUDE · SEV 2 · REGIONAL · HIGH CONFIDENCE
    Elevated 500 and 404 errors hit the API and blocked org creation, GitHub App installs and membership changes in Azure Central US for about three hours; Projects label updates lagged until the next day.
  3. Claude Haiku 5.5 · prompt v7 · Oct 23, 2026 · Raw record
16 updates
  1. 10:11 UTC · investigating
    We are investigating reports of degraded performance for API Requests
  2. 10:20 UTC · investigating
    Database replicas have detached. We're working to restore the database replicas. Users may experience issues beyond creating organizations and a degraded experience with the GitHub API and Projects.
  3. 10:57 UTC · investigating
    Database replicas have been restored. Org creation and the GitHub API are no longer degraded.
  4. 10:58 UTC · investigating
    The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability.
  5. 11:38 UTC · investigating
    We are seeing recovery for Projects. Users may experience stale search results for Projects while indexing catches up.
  6. 13:35 UTC · investigating
    Users may experience stale Project search results. We are working to increase indexing speed. All other services are available.
  7. 17:01 UTC · investigating
    Updates to issue labels may be delayed in being reflected in Projects by about ~10 minutes. We have added some capacity to work through the backlog more quickly, but it'll likely be a few hours to complete processing the full backlog of messages. All other services are available.
  8. 17:30 UTC · investigating
    We will post another update in approximately one hour to share our progress.
  9. 18:42 UTC · investigating
    Continuing to investigate the lag that may be experienced in issue labels being accurately reflected in Projects. We are working on alternate solutions to process the backlog of label updates.
  10. 20:26 UTC · investigating
    We are preparing to deploy a change that will mitigate the impact.
  11. 21:39 UTC · investigating
    Updates to issue labels may be delayed in being reflected in Projects. We are continuing to deploy a change that will accelerate processing of the backlog of label updates. All other services are available. We will provide another update within the next hour.
  12. 00:16 UTC · investigating
    We've deployed a change intended to accelerate processing of the backlog of issue label updates in Projects. A sizable backlog still remains and we continue working through it. All other services are operating normally. We will provide another update within the next hour.
  13. 02:00 UTC · investigating
    We are continuing to process the backlog of issue label updates for Projects. Users may still see delays before label changes are reflected in Projects. All other services are operating normally.
  14. 03:14 UTC · investigating
    We are continuing to process the backlog of issue label updates for Projects. Label changes may still be delayed. All other services are operating normally.
  15. 04:55 UTC · monitoring
    The degradation has been mitigated. We are monitoring to ensure stability.
  16. 04:55 UTC · resolved
    Starting at 07:57 UTC on September 23, GitHub experienced elevated 500 and 404 responses across several application pages. This caused failures when installing GitHub Apps, creating organizations, and making some organization membership changes. Customers also experienced delayed label updates and stale search results in Projects. <br /><br />The infrastructure failure was isolated to our Azure Central US region. The API errors were mitigated by 10:58 UTC on September 23. Projects' processing continued to recover while an accumulated backlog was drained, and full service was restored at 04:55 UTC on September 24. <br /><br />The incident was caused by a failed planned maintenance operation on a primary database. Automated recovery initiated an emergency database failover, after which several replicas in the affected region were unable to resume replication correctly. This reduced available database capacity and caused the API errors and downstream Projects processing delays. <br /><br />We have mitigated the immediate failure mode. We are also improving maintenance safety checks, database failover handling, post-failover replica validation, and downstream processing resilience to reduce the likelihood and impact of similar incidents.
Source
Sep 20, 20261h 09mSEV 3
Incident with Pull RequestsSev 3 because Pull Requests had degraded performancePull Requests
4 updates
  1. 22:13 UTC · investigating
    We are investigating reports of degraded performance for Pull Requests
  2. 22:27 UTC · monitoring
    The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
  3. 22:32 UTC · monitoring
    A git fileserver issue caused a brief delay in creating some merge commits - we've isolated the underlying server and already observed recovery.
  4. 23:22 UTC · resolved
    On September 20, 2026, between 21:46 and 22:24 UTC the Pull Requests service was degraded and pull request merge and test-merge commits were created late, with delays reaching approximately four minutes at peak. Merge commits were delayed rather than lost. Because some Actions workflow runs start only after a pull request's merge commit is created, a subset of workflow runs for pull request events were also delayed. <br /><br />This was due to a routine repository maintenance job for an unusually large repository consuming nearly all of the memory on a single Git storage server, which left that server unable to serve the Git operations used to create merge commits. <br /><br />We mitigated the incident by removing the affected server from service at 22:18 UTC, after which the queued merge commits were created within six minutes. <br /><br />We have capped the memory a single repository maintenance job may consume so that one repository cannot exhaust a server, and we have improved monitoring and alerting on storage server health to reduce our time to detection and mitigation of issues like this one in the future.
Source
Sep 17, 202650mSEV 4
Elevated rate of errors for OpenAI models provided by CopilotSev 4 because Copilot AI Model Providers had degraded performanceCopilot AI Model Providers
3 updates
  1. 20:59 UTC · investigating
    We are investigating reports of degraded performance for Copilot AI Model Providers
  2. 21:39 UTC · monitoring
    We are experiencing degraded availability for GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-6 Astra, GPT-5.3-Codex in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. The provider is working to mitigate the problem and we are monitoring recovery. We recommend choosing another model or selecting 'Auto' to continue using Copilot.
  3. 21:49 UTC · resolved
    Between 20:26 and 21:17 UTC on September 17, 2026, GitHub Copilot experienced degradation affecting several GPT models, including GPT-5.6 Luna, GPT-5.6 Terra, GPT-5.6 Sol, GPT-5.3-Codex, and GPT-6 Astra. Users encountered elevated error rates when using these models.<br /><br />The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring and coordinated with the provider. Our automated model-warning system activated in-product warnings for affected models during the incident. Service returned to normal after the provider implemented a mitigation.
Source

Peers, 90 days

Compare
Docker HubGrade A+100.00% up4 incidentsMTTR 11mnpmGrade D100.00% up9 incidentsMTTR 2h 15mGitHubGrade F99.87% up49 incidentsMTTR 1h 18m

README badge

GitHub's live grade, for your README.

GitHub grade badge
[![github on downagain.dev](https://downagain.dev/badge/github.svg)](https://downagain.dev/p/github)