<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb" -->

---
title: GitHub availability report: August 2026 | daily.dev
description: GitHub's August availability report details five incidents causing degraded service, including an Actions capacity cascade on August 6, an authentication-path...
canonical: https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: GitHub availability report: August 2026 | daily.dev
og:description: GitHub's August availability report details five incidents causing degraded service, including an Actions capacity cascade on August 6, an authentication-path...
og:url: https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb
og:image: https://api.daily.dev/og/posts/OqNgghwFB.png
og:image:alt: GitHub availability report: August 2026
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub availability report: August 2026

**[GitHub Blog](https://daily.dev/sources/ghblog)** · 15 min read · 0 upvotes · 0 comments

## Summary

GitHub's August availability report details five incidents causing degraded service, including an Actions capacity cascade on August 6, an authentication-path overload on August 17, a Copilot Cloud Agent database regional outage on August 20, an Actions database saturation event on August 26, and a Kimi K3 upstream model provider degradation on August 27. Each incident writeup covers root cause, response steps, and planned mitigations such as autoscaling fixes, circuit breakers, and improved failover runbooks. The report also covers ongoing infrastructure work: migrating MySQL primaries to Azure, reducing query load on the mysql1 shared database, Actions job-routing capacity improvements, and better monitoring for pull request and API health.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://github.blog/news-insights/company-news/github-availability-report-august-2026>

## Questions this post answers

### What caused the GitHub Actions outage on August 6, 2026?

A routine deployment to an internal Actions event-processing service briefly reduced pod capacity in one site, pushing remaining sites past their concurrency limits as traffic shifted. This caused service mesh sidecar CPU throttling and out-of-memory restarts, cascading into cache, DNS, and API errors. Recovery was slowed by a latent bug that made runners retry already-revoked jobs instead of picking up valid work, creating a self-amplifying backlog. The incident lasted 10 hours and 42 minutes.

_Teams debugging cascading service mesh failures can find similar incident breakdowns on daily.dev._

### Why did GitHub Copilot fail for users on the Kimi K3 model in August 2026?

The upstream provider serving the Kimi K3 model experienced a serving degradation that caused a large share of Kimi K3 requests to fail, peaking at over half of requests failing. Requests using other models or the Auto routing setting were unaffected since they were served by different models, so switching models or retrying would have worked during the incident, which lasted 2 hours and 8 minutes.

_Anyone weighing model reliability tradeoffs for AI coding tools can track incidents like this via daily.dev._

### How much database load did GitHub remove by migrating its authentication tables off mysql1?

Moving a 24-table authentication-core cohort off GitHub's oldest shared database, mysql1, removed approximately one million queries per second from its replicas. Separate query-hygiene changes eliminated another 120,000 queries per second and cut roughly 59,000 seconds of wasted database work per hour, as part of broader efforts to improve database health during GitHub's migration to Azure.

_Engineers planning large-scale database migrations can compare real-world numbers like these on daily.dev._

## Similar posts on daily.dev

- [GitHub availability report: July 2026](https://daily.dev/posts/github-availability-report-july-2026-jlsbk76s3) · GitHub Blog · 0 upvotes · 1 comments
- [GitHub availability report: March 2026](https://daily.dev/posts/github-availability-report-march-2026-c2dt15scg) · GitHub Blog · 0 upvotes · 0 comments
- [GitHub has another tough day](https://daily.dev/posts/github-has-another-tough-day-dvefjjxpq) · Surfing Complexity · 18 upvotes · 4 comments
- [GitHub appears to be struggling with one nine availability](https://daily.dev/posts/github-appears-to-be-struggling-with-one-nine-availability-d4tedw2tw) · The Register · 0 upvotes · 0 comments

---

Tags: [#github](https://daily.dev/tags/github), [#github-actions](https://daily.dev/tags/github-actions)

[View this post on daily.dev](https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"GitHub availability report: August 2026","url":"https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb"},"datePublished":"2026-09-10T02:09:13.332Z","dateModified":"2026-09-13T18:35:39.140Z","description":"GitHub's August availability report details five incidents causing degraded service, including an Actions capacity cascade on August 6, an authentication-path...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/176ac63f3f100fbd0d859de07f2c0c1b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/176ac63f3f100fbd0d859de07f2c0c1b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/106cf162b88840808484d4b5429b59b1","url":"https://daily.dev/sources/ghblog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,github-actions","timeRequired":"PT15M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Blog","item":"https://daily.dev/sources/ghblog"},{"@type":"ListItem","position":3,"name":"GitHub availability report: August 2026"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/github-availability-report-august-2026-oqngghwfb#faq","mainEntity":[{"@type":"Question","name":"What caused the GitHub Actions outage on August 6, 2026?","acceptedAnswer":{"@type":"Answer","text":"A routine deployment to an internal Actions event-processing service briefly reduced pod capacity in one site, pushing remaining sites past their concurrency limits as traffic shifted. This caused service mesh sidecar CPU throttling and out-of-memory restarts, cascading into cache, DNS, and API errors. Recovery was slowed by a latent bug that made runners retry already-revoked jobs instead of picking up valid work, creating a self-amplifying backlog. The incident lasted 10 hours and 42 minutes. Teams debugging cascading service mesh failures can find similar incident breakdowns on daily.dev."}},{"@type":"Question","name":"Why did GitHub Copilot fail for users on the Kimi K3 model in August 2026?","acceptedAnswer":{"@type":"Answer","text":"The upstream provider serving the Kimi K3 model experienced a serving degradation that caused a large share of Kimi K3 requests to fail, peaking at over half of requests failing. Requests using other models or the Auto routing setting were unaffected since they were served by different models, so switching models or retrying would have worked during the incident, which lasted 2 hours and 8 minutes. Anyone weighing model reliability tradeoffs for AI coding tools can track incidents like this via daily.dev."}},{"@type":"Question","name":"How much database load did GitHub remove by migrating its authentication tables off mysql1?","acceptedAnswer":{"@type":"Answer","text":"Moving a 24-table authentication-core cohort off GitHub's oldest shared database, mysql1, removed approximately one million queries per second from its replicas. Separate query-hygiene changes eliminated another 120,000 queries per second and cut roughly 59,000 seconds of wasted database work per hour, as part of broader efforts to improve database health during GitHub's migration to Azure. Engineers planning large-scale database migrations can compare real-world numbers like these on daily.dev."}}]}
```

