---
title: "GitHub’s incidents rose from 2 to 8 a month as it moved 140 of 151 services to Azure"
summary: "GitHub’s availability reports, March 2025 to October 2026, and its status page to 13 November: the incidents each month, the move to Azure behind several, and what to check after one."
url: https://www.thetechbag.com/blog/github-incidents-2-to-8-azure-migration
format: Trend
desk: "Cloud & DevOps"
region: Global
published: 2026-11-14
facts_checked: 2026-11-14
author: TechBag (The TechBag Journal)
tags: ["GitHub outage","GitHub down","GitHub Actions outage","GitHub availability report","GitHub Azure migration","GitHub status","GitHub incidents","Azure Central US","GitHub Actions","self-hosted runners","MySQL migration","East US 3","GitHub Copilot outage","pull requests","webhooks","status page","incident history","Microsoft Azure"]
cover: https://www.thetechbag.com/blog/covers/github-incidents-2-to-8-azure-migration.png
---

# GitHub’s incidents rose from 2 to 8 a month as it moved 140 of 151 services to Azure

*GitHub’s availability reports, March 2025 to October 2026, and its status page to 13 November: the incidents each month, the move to Azure behind several, and what to check after one.*

Trend · Cloud & DevOps · By TechBag · Published 2026-11-14 · Facts checked 2026-11-14 · Canonical: https://www.thetechbag.com/blog/github-incidents-2-to-8-azure-migration

The short version

1. GitHub’s monthly availability report counted 8 incidents in October, after 2 in September. Its status page logged 25 incidents in October against 14, and marked 8 of them critical, its highest level.[1][2][6]
2. The months are those of GitHub’s move into Microsoft Azure. By 9 November, 140 of its 151 production services and 32 of 50 MySQL primary databases ran in Azure Central US, from 120 of 160 and 13 of 51 on 7 October.[1][2]
3. The move caused one of three critical incidents on 9 to 11 November: traffic sent to a core Actions database in its new region exceeded the limits there, and 28% of workflow runs were affected on average, 65% at the peak.[7]

GitHub publishes two records of its own reliability: a status page that opens an incident within minutes, and a monthly availability report that explains the largest ones weeks later. Both moved up in October, while GitHub was shifting its services out of its own data centres and into Azure. What do the two records count, how much of October came from the move, and what should a team that ships through GitHub check?[1][6]

## Eight write-ups in October, after two

Until July, each report opened with one sentence: in that month, “we experienced N incidents that resulted in degraded performance across GitHub services”. From August the reports drop that sentence and write up each incident at length: what customers saw, what went wrong, and what GitHub is changing.[3][5] Over the twenty months to October the count ran from 1 to 10 a month: 29 in the ten months to December 2025, and 60 in the ten months of 2026, with the highest month in April.[5]

**Figure: GitHub reported 8 incidents in October, after 2 in September; 2026 has averaged 6 a month**

*Incidents in GitHub's monthly availability reports, March 2025 to October 2026*

|  | Incidents in the availability report |
| --- | --- |
| Mar ’25 | 1 |
| Apr ’25 | 3 |
| May ’25 | 3 |
| Jun ’25 | 3 |
| Jul ’25 | 1 |
| Aug ’25 | 3 |
| Sep ’25 | 3 |
| Oct ’25 | 4 |
| Nov ’25 | 3 |
| Dec ’25 | 5 |
| Jan ’26 | 2 |
| Feb ’26 | 6 |
| Mar ’26 | 4 |
| Apr ’26 | 10 |
| May ’26 | 9 |
| Jun ’26 | 6 |
| Jul ’26 | 8 |
| Aug ’26 | 5 |
| Sep ’26 | 2 |
| Oct ’26 | 8 |

Source: GitHub availability reports, March 2025 to October 2026; TechBag count for August to October 2026 · as of 14 November 2026 · 7 October counted as two incidents, as GitHub declared them

TechBag countWhat the report counts

Each of the fifteen incidents written up in the August, September and October reports matches an incident the status page marks critical, and every critical incident of those months has a write-up. The status page logs many more, most of them minor: 25 in October, and 21 already in the first thirteen days of November.

More incidents did not mean longer ones. On the status page, October’s eight ran for 16 hours 43 minutes in all; August’s five ran for 33 hours 9 minutes, led by an Actions outage of 10 hours 42 minutes on 6 August. Nor is the status page’s own total at a high: February logged 37.[3][6]

| Month | Availability report | Status page, all | Status page, critical |
| --- | --- | --- | --- |
| Oct 2025 | 4 | 22 | – |
| Nov 2025 | 3 | 17 | – |
| Dec 2025 | 5 | 15 | – |
| Jan 2026 | 2 | 25 | – |
| Feb 2026 | 6 | 37 | – |
| Mar 2026 | 4 | 32 | – |
| Apr 2026 | 10 | 26 | 3 |
| May 2026 | 9 | 23 | 8 |
| Jun 2026 | 6 | 23 | 4 |
| Jul 2026 | 8 | 26 | 6 |
| Aug 2026 | 5 | 27 | 5 |
| Sep 2026 | 2 | 14 | 2 |
| Oct 2026 | 8 | 25 | 8 |
| 1–13 Nov 2026 | not yet published | 21 | 3 |

## What the move to Azure is, and where it showed

GitHub explained the programme in its May report: its traffic is “growing rapidly, driven in large part by AI-assisted and agentic development workflows”, and keeping up means “moving to Azure for elastic capacity, breaking our monolith apart into isolated services, and eliminating the shared failure points that have driven past incidents”. In February 8% of the main application’s traffic was served from Azure; by 9 November Azure served 66% of its reads and 52% of Git reads. Traffic on the services already moved has risen 82% since March.[4][1]

Two of October’s eight incidents began in network connections to the cloud. On 5 October a partial network failure at the cloud provider disrupted connections to the cloud-hosted databases behind the service that assigns Actions jobs, and for about 90 minutes most jobs on GitHub-hosted runners did not start within five minutes; self-hosted runners were not affected. On 19 October an Actions service’s retries to its cache servers saturated the network link between GitHub’s data centre and a cloud region. GitHub also reports an Azure network disruption on 29 October across all three Central US availability zones, affecting at least 34,128 signed-in users, which is not among the eight.[1]

The rest had other causes: two write outages on 7 October, when a newly added machine routed database writes to retired servers (web and API failures peaked at 8.9% and 9.3%, at more than 12,000 and 11,000 organisations); an overloaded event-streaming platform on 21 October; a Copilot credential with an outside model provider that stopped working on 28 October; and a full database connection pool on 30 October, when 43% of merge attempts failed.[1]

**Figure: Three critical incidents in three days, the first from moving a core Actions database**

*GitHub status-page incidents, 9 to 13 November, opening time in UTC*

| Date | Event | Detail |
| --- | --- | --- |
| 9 Nov, 10:00 UTC | Webhooks and Actions delayed | A slowed Kafka broker stalled a job queue; 26% of webhook deliveries delayed on average |
| 9 Nov, 18:12 UTC | Actions after a database move | Traffic to the migrated core Actions database exceeded its new region's limits; 28% of runs hit, 65% at peak |
| 10 Nov, 16:10 UTC | Git and pull requests slow | Overload in shared Git infrastructure; Actions delayed for 1.8% of events, 7% at peak |
| 11 Nov, 20:48 UTC | Actions, Pages, Copilot degraded | 33 minutes; no root cause published yet |
| 13 Nov, 15:47 UTC | Pull request merges time out | 3% of merge requests at first, then about 1% |

Source: GitHub status page, incident records · as of 14 November 2026 · Critical incidents emphasised; the other two were marked major

GitHub’s account of 9 November is specific. After the database moved, “the volume of requests exceeded the capacity and rate limits configured there”; it shifted some traffic back, raised the limits and moved it again in steps. It says the migration of that cluster is complete, and that it will shift traffic in smaller steps in the moves still to come.[7] The next day, a recent change to how merges are computed overloaded the systems behind Git operations; GitHub turned that change off and briefly limited low-priority traffic, which restricted commit pages for users who were not signed in.[8] On 13 November merges timed out for about 3% of requests before GitHub took mitigating action.[12]

## What to check after an incident, and what to watch

The incident records name the work a team may have to redo. On 9 November, GitHub says, “Actions skips events older than 30 minutes, so some workflow runs did not start” when webhook deliveries ran late, and runs left stuck after the evening incident held concurrency until released; GitHub is preparing an API for customers to clear them. On 10 November 0.09% of pull-request events started no workflow and had to be triggered again.[9][7][8]

Our viewWhere Actions sits in the release path

After any Actions incident, look for workflows that never started, not only those that failed: a run that never began shows no failure. Self-hosted runners kept working through the hosted-runner outage of 5 October, though on 19 and 20 July an expired certificate stopped self-hosted and larger runners instead, so a second pool helps only for the failures it does not share.[1][5]

The status page now shows each service’s uptime over 90 days. A major outage counts in full, a partial outage at 30% of its duration, and degraded performance not at all, so a month of many degraded incidents can leave the uptime figure unchanged.[10]

**What to watch.**

- **A second Azure region.** GitHub says the East US 3 build is about a week behind plan, with its first traffic ramp in the first week of December.[1]
- **The last 11 services and 18 database primaries** still to move, after the lesson of 9 November about limits in the new region.[1][7]
- **The November report.** Each of the last six appeared between the 8th and the 14th of the next month. November already has three critical incidents in thirteen days, and 11 November’s cause is still to be published.[6][11]

Other providers’ failures the same week, read from their own status posts: [Microsoft 365’s outage of more than 21 hours](https://www.thetechbag.com/blog/microsoft-365-outage-21-hours-exchange-online-20-services) and [AWS’s 5 hours 45 minutes of failed launches in Tokyo](https://www.thetechbag.com/blog/aws-tokyo-zone-5-hours-failed-launches).

How we did this

Figures as of 14 November 2026, 7:30pm IST

The monthly series is from GitHub’s availability reports for March 2025 to October 2026. Through July 2026 each report states its count; the August, September and October reports do not, so we counted the incidents written up, taking the two write outages of 7 October as two (GitHub declared two incidents and the status page lists two) and 25 July’s two related periods as one, as GitHub did. Status-page counts are every incident in GitHub’s status history for each month, maintenance excluded, read on 14 November (page last updated 10:39 UTC); no incident before April 2026 carries the critical level. Durations are the status page’s open-to-resolved times, which match the times in the reports’ headings; each write-up also gives an impact duration that can differ (for 6 October, about 6 minutes of failed requests, then about 3 hours 30 minutes of paused migrations, against 3 hours 43 minutes on the status page). The same applies to 9 and 10 November, where the summaries give impact from 18:07 and from about 15:00 UTC against incidents opened at 18:12 and 16:10. The service totals are GitHub’s: 160 production services on 7 October and 151 on 9 November; the reports do not explain the change. Averages, sums and durations are our arithmetic.

Spotted an error? Write to us; corrections are published at the foot of the piece.

Sources

1. [GitHub, GitHub availability report: October 2026](https://github.blog/news-insights/company-news/github-availability-report-october-2026/) — 13 November 2026
2. [GitHub, GitHub availability report: September 2026](https://github.blog/news-insights/company-news/github-availability-report-september-2026/) — 14 October 2026
3. [GitHub, GitHub availability report: August 2026](https://github.blog/news-insights/company-news/github-availability-report-august-2026/) — 10 September 2026
4. [GitHub, GitHub availability report: May 2026](https://github.blog/news-insights/company-news/github-availability-report-may-2026/) — 11 June 2026
5. [GitHub, availability reports for March 2025 to July 2026](https://github.blog/tag/github-availability-report/) — 16 April 2025 to 12 August 2026 One report a month, each under this tag.
6. [GitHub status, incident history](https://www.githubstatus.com/history) — as of 14 November 2026, 10:39 UTC
7. [GitHub status, Incident with Actions and Checks API](https://www.githubstatus.com/incidents/tp8cghg7tlc4) — 9 November 2026
8. [GitHub status, Incident with Git Operations and Pull Requests](https://www.githubstatus.com/incidents/hnf21m9jkl3c) — 10 November 2026
9. [GitHub status, Incident with Webhooks and Actions](https://www.githubstatus.com/incidents/xxb3l2bm76dr) — 9 November 2026
10. [GitHub, Bringing more transparency to GitHub’s status page](https://github.blog/news-insights/company-news/bringing-more-transparency-to-githubs-status-page/) — 17 April 2026
11. [GitHub status, Impact across multiple GitHub products including Actions, Pages, and Copilot products](https://www.githubstatus.com/incidents/dvy0t3mvh1lg) — 11 November 2026
12. [GitHub status, Incident with Pull Requests](https://www.githubstatus.com/incidents/1xzmt89vv61l) — 13 November 2026

**Disclosure.** TechBag is a software reseller: it earns when companies buy through it, including from vendors named here. The analysis is TechBag’s own; no vendor paid for or saw this piece before publication. Facts are labelled reported, TechBag count or our view.

**Read this next:** [Microsoft 365’s outage ran past 21 hours as an Exchange Online fault hit 20 services](https://www.thetechbag.com/blog/microsoft-365-outage-21-hours-exchange-online-20-services) — Microsoft 365’s outage the same week ran past 21 hours, as an Exchange Online fault hit 20 services.

Go deeper on TechBag

- [AWS’s Tokyo fault ran 5 hours 45 minutes; some launches ‘succeeded’, then terminated](https://www.thetechbag.com/blog/aws-tokyo-zone-5-hours-failed-launches) — another provider’s outage the same week, read from its own status posts
- [GitHub Enterprise](https://www.thetechbag.com/github/github-enterprise) — Actions, hosted and self-hosted runners, and the plans
- [Observability and APM guide](https://www.thetechbag.com/browse/devops/observability-apm) — tools that watch pipelines and services from outside the provider