---
type: "post"
id: "as-traffic-grew-exponentially-we-moved-99-99999-9d909d"
slug: "as-traffic-grew-exponentially-we-moved-99-99999-9d909d"
title: "As traffic grew exponentially, we moved 99.99999% of GitHub's Git repos to Azure."
description: "GitHub says it has moved 99.99999% of its Git repositories to Azure Blob Storage as repository traffic grew."
retrieval_nugget: "GitHub says it has moved 99.99999% of its Git repositories to Azure Blob Storage as repository traffic grew."
published_at: "2026-10-21"
updated_at: "2026-10-21"
record_date: "2026-10-21"
date_kind: "published_at"
topics: ["github"]
entities: ["GitHub","Azure Blob Storage","Git","Microsoft Azure"]
related_patterns: []
novelty_label: "same_event"
what_changed: "Same event as Building Git infrastructure for agent-scale development"
prior_refs: ["memory:f6848346-1211-8b76-a02c-8f0f3aa01e65"]
source_url: "https://github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure/"
source_urls: ["https://github.blog/engineering/architecture-optimization/the-bridge-to-agent-scale-git-infrastructure/"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:as-traffic-grew-exponentially-we-moved-99-99999-9d909d"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/as-traffic-grew-exponentially-we-moved-99-99999-9d909d/","markdown":"https://newruntime.com/posts/as-traffic-grew-exponentially-we-moved-99-99999-9d909d.md","json":"https://newruntime.com/posts/as-traffic-grew-exponentially-we-moved-99-99999-9d909d.json"}
---

# As traffic grew exponentially, we moved 99.99999% of GitHub's Git repos to Azure.

## Retrieval answer

GitHub says it has moved 99.99999% of its Git repositories to Azure Blob Storage as repository traffic grew.

GitHub says it has moved 99.99999% of its Git repositories to Azure Blob Storage as repository traffic grew. The company presents the work as part of its effort to build Git infrastructure for “agent-scale” demand.

The remaining fraction consists of its busiest repositories. GitHub says it introduced a new write path for those repositories so that cross-region round trips do not cap throughput. It also says the architecture enables stateless replicas backed by Azure Blob Storage.

This is an internal infrastructure change, not a new GitHub product, Git protocol revision, or separately described customer setting. The source does not state an absolute repository count, traffic volume, migration cost, or before-and-after latency and throughput measurements. It also does not give a completion date or establish the effect of the migration on an individual repository, developer, or GitHub customer.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Github](https://newruntime.com/topics/github.md): Explore the github topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)