GitHub's June 2026 availability report leads with a miss and explains it. Monolith traffic in Azure peaked at 45% in Central US, short of target, because GitHub paused the ramp for roughly a month after a May 21 stability incident. Git in Azure reached 43% combined HTTP and SSH, missing a 50% June target. GitHub has not set a new Git target. These are the headline numbers, and the report states them plainly.
Below those numbers, the structural work is more interesting. The new pullsd service now handles 100% of anonymous pull request reads outside the monolith. The new users service offloads roughly 500,000 queries per second at peak from the primary database. API rate limiting is 97% handled at the Gateway layer. Client-side database load shedding is running against 5% of live production traffic. Reposd, a new extracted repository service, became the first extracted service to serve production REST traffic from Azure before being deliberately dialed back for a Redis capacity constraint, with no incident and no forced rollback.
June produced six degraded-service incidents. The Copilot code review failure on June 4 hit an 81.6% average failure rate and 93.9% peak because a workflow auto-consumed an incompatible dependency release without validation. An abusive anonymous traffic spike on June 8 drove 504 errors on unauthenticated endpoints to a 34% peak for over two hours. A June 10 authentication failure caused sporadic 401 errors on roughly 9% of REST and GraphQL requests. The incident write-ups cover root causes, mitigation timelines, and specific remediation steps in progress. Read them for the operational detail the headline numbers do not carry.
[READ ORIGINAL →]