Abstract representation of network connectivity and data flow with GitHub logo.
Visualizing GitHub's complex infrastructure and data services.· Github Blog

GitHub Availability Dips in June 2026

GitHub reports six availability incidents in June 2026, detailing progress and setbacks in migrating services from its monolith.

7 min read

GitHub's June 2026 availability report reveals a mixed bag of progress and setbacks, detailing six incidents that degraded service performance. The company is doubling down on transparency, as noted in the monthly report, responding to customer demand for more insight into infrastructure investments.

Visual TL;DR. June 2026 Incidents leads to Monolith Migration Challenges. Monolith Migration Challenges leads to Stability Incident Impact. Stability Incident Impact leads to Git Traffic Plateau. Git Traffic Plateau leads to User Latency Avoidance. Monolith Migration Challenges leads to New Pull Request Service. June 2026 Incidents leads to Increased Transparency. GitHub Architecture leads to Monolith Migration Challenges.

  1. June 2026 Incidents: six availability incidents degraded service performance
  2. Monolith Migration Challenges: monolith traffic in Azure Central US peaked at 45%
  3. Stability Incident Impact: May 21 stability incident paused ramp-up for nearly a month
  4. Git Traffic Plateau: Git in Azure reached 43% traffic, missing 50% target
  5. User Latency Avoidance: decisions made to avoid user latency, awaiting vPoP traffic
  6. New Pull Request Service: extracted pull requests service, pullsd, handles 100% anonymous PRs
  7. Increased Transparency: doubling down on transparency responding to customer demand
  8. GitHub Architecture: migrating services from its monolith
Visual TL;DR
Visual TL;DR, startuphub.ai June 2026 Incidents leads to Monolith Migration Challenges. Monolith Migration Challenges leads to New Pull Request Service. June 2026 Incidents leads to Increased Transparency June 2026 Incidents Monolith Migration Challenges Git Traffic Plateau New Pull Request Service Increased Transparency From startuphub.ai · The publishers behind this format
Visual TL;DR, startuphub.ai June 2026 Incidents leads to Monolith Migration Challenges. Monolith Migration Challenges leads to New Pull Request Service. June 2026 Incidents leads to Increased Transparency June 2026Incidents MonolithMigration… Git TrafficPlateau New Pull RequestService IncreasedTransparency From startuphub.ai · The publishers behind this format
Visual TL;DR, startuphub.ai June 2026 Incidents leads to Monolith Migration Challenges. Monolith Migration Challenges leads to New Pull Request Service. June 2026 Incidents leads to Increased Transparency June 2026 Incidents six availability incidents degradedservice performance Monolith Migration Challenges monolith traffic in Azure Central USpeaked at 45% Git Traffic Plateau Git in Azure reached 43% traffic, missing50% target New Pull Request Service extracted pull requests service, pullsd,handles 100% anonymous PRs Increased Transparency doubling down on transparency respondingto customer demand From startuphub.ai · The publishers behind this format
Visual TL;DR, startuphub.ai June 2026 Incidents leads to Monolith Migration Challenges. Monolith Migration Challenges leads to New Pull Request Service. June 2026 Incidents leads to Increased Transparency June 2026Incidents six availabilityincidents degradedservice performance MonolithMigration… monolith traffic inAzure Central USpeaked at 45% Git TrafficPlateau Git in Azurereached 43%traffic, missing… New Pull RequestService extracted pullrequests service,pullsd, handles… IncreasedTransparency doubling down ontransparencyresponding to… From startuphub.ai · The publishers behind this format
Visual TL;DR, startuphub.ai June 2026 Incidents leads to Monolith Migration Challenges. Monolith Migration Challenges leads to Stability Incident Impact. Stability Incident Impact leads to Git Traffic Plateau. Git Traffic Plateau leads to User Latency Avoidance. Monolith Migration Challenges leads to New Pull Request Service. June 2026 Incidents leads to Increased Transparency. GitHub Architecture leads to Monolith Migration Challenges June 2026 Incidents six availability incidents degradedservice performance Monolith Migration Challenges monolith traffic in Azure Central USpeaked at 45% Stability Incident Impact May 21 stability incident paused ramp-upfor nearly a month Git Traffic Plateau Git in Azure reached 43% traffic, missing50% target User Latency Avoidance decisions made to avoid user latency,awaiting vPoP traffic New Pull Request Service extracted pull requests service, pullsd,handles 100% anonymous PRs Increased Transparency doubling down on transparency respondingto customer demand GitHub Architecture migrating services from its monolith From startuphub.ai · The publishers behind this format
Visual TL;DR, startuphub.ai June 2026 Incidents leads to Monolith Migration Challenges. Monolith Migration Challenges leads to Stability Incident Impact. Stability Incident Impact leads to Git Traffic Plateau. Git Traffic Plateau leads to User Latency Avoidance. Monolith Migration Challenges leads to New Pull Request Service. June 2026 Incidents leads to Increased Transparency. GitHub Architecture leads to Monolith Migration Challenges June 2026Incidents six availabilityincidents degradedservice performance MonolithMigration… monolith traffic inAzure Central USpeaked at 45% StabilityIncident Impact May 21 stabilityincident pausedramp-up for nearly… Git TrafficPlateau Git in Azurereached 43%traffic, missing… User LatencyAvoidance decisions made toavoid user latency,awaiting vPoP… New Pull RequestService extracted pullrequests service,pullsd, handles… IncreasedTransparency doubling down ontransparencyresponding to… GitHubArchitecture migrating servicesfrom its monolith From startuphub.ai · The publishers behind this format
!-- /sh-diagram -->

The push to migrate traffic from the monolithic architecture saw Monolith traffic in Azure Central US peak at 45%, falling short of projections due to a stability incident on May 21. The ramp-up was paused for nearly a month and restarted with stricter stability gates.

Git in Azure reached a peak of 43% traffic, missing the 50% target. This plateau is attributed to decisions aimed at avoiding user latency, specifically awaiting additional vPoP traffic and currently routing only HTTP traffic for Git.

Architectural Milestones Amidst Challenges

Despite missed targets, significant progress was made. The new extracted pull requests service, pullsd, now handles 100% of anonymous pull request reads. Reposd, an extracted repository service, became the first to serve production REST traffic from Azure, reaching 50% before being scaled back due to a Redis capacity constraint.

A new users service is offloading approximately 500,000 queries per second from the primary database. API rate limiting is now largely handled at the Gateway, reducing contention within the monolith.

Client-side database load shedding is live against 5% of production traffic, providing crucial data for managing stress. Furthermore, two-person confirmation is now mandated for interactive production access and ChatOps changes, enhancing security with a unified audit trail.

June Incidents

The report details two primary incidents from June 2026:

  • On June 4, Copilot code review experienced elevated failures, with an average of 81.6% of requests failing due to an incompatible dependency release. Mitigation involved removing the problematic version and redeploying the service. Future prevention includes dependency pinning and improved compatibility checks. This incident underscores the importance of robust error handling, even for advanced tools like GitHub Copilot.
  • On June 8, signed-out users faced sustained HTTP 504 errors on various GitHub pages due to a surge in abusive, automated anonymous traffic. The issue impacted unauthenticated requests, causing gateway timeouts. Mitigation involved targeted blocking of anomalous traffic patterns.

GitHub continues to prioritize availability, capacity, and then features.

© 2026 StartupHub.ai. All rights reserved. Do not enter, scrape, copy, reproduce, or republish this article in whole or in part. Use as input to AI training, fine-tuning, retrieval-augmented generation, or any machine-learning system is prohibited without written license. Substantially-similar derivative works will be pursued to the fullest extent of applicable copyright, database, and computer-misuse laws. See our terms.