Incident with Pull Requests and Issues
Final update
Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors.
Timeline
- Resolved · Aug 12, 16:41 UTC
Between 16:03 and 16:29 UTC on August 12, some users encountered errors when viewing pull requests, issues, and search results. During this period, about 1.9% of Pull Request requests and 0.9% of Issues requests failed. During a database migration, two indexes were removed while application settings still referenced them, causing affected requests to fail. We detected the issue after the migration reached one database shard and before it progressed to the remaining shards. We restored service by disabling both settings. We are improving safeguards around database migrations and application configuration to prevent similar mismatches from causing errors.
- Monitoring · Aug 12, 16:38 UTC
We identified the source of errors affecting Pull Requests, Issues, and Search on GitHub.com and have applied a mitigation. A database index hint was referencing an index that had been removed by a recent migration, causing query failures for some users. We disabled the problematic configuration and are seeing recovery across affected services. We are continuing to monitor to confirm full resolution.
- Monitoring · Aug 12, 16:35 UTC
The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
- Investigating · Aug 12, 16:24 UTC
We are investigating reports of errors affecting Pull Requests and Issues on GitHub.com. Some users may encounter 500 errors when loading pull request and issue pages. Our engineering teams are actively investigating the root cause, which appears to be related to a database infrastructure issue. We will provide an update as soon as we have more information.
- Investigating · Aug 12, 16:16 UTC
We are investigating reports of degraded performance for Issues and Pull Requests
More from GitHub
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2310:11 UTC | Incident across several services | minor | Ongoing |
| Sep 2022:13 UTC | Incident with Pull Requests | minor | 1h 9m |
| Sep 1720:59 UTC | Elevated rate of errors for OpenAI models provided by Copilot | minor | 50m |
| Sep 1607:20 UTC | Degradation with Gemini 3.8 Flash | major | 10h 28m |
| Sep 1519:11 UTC | Disruption with some GitHub services | minor | 49m |
| Sep 1509:47 UTC | Disruption with some GitHub services | minor | 1h 30m |
Also caused by database
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 921:53 UTC | INC20000211 | critical | 1h 58m | |
| Aug 2616:17 UTC | Issues performance is degraded in the US | minor | 4h 19m | |
| Aug 818:57 UTC | Account Registration, Droplets, and Related Services | minor | 6h 3m | |
| Jul 2817:41 UTC | Event ingestion and retrieval delays for some North America customers | none | 2h | |
| Jul 300:11 UTC | Partial outage in ORD | major | 5h 48m | |
| Jun 1920:13 UTC | Snyk Code (SAST) Scan service degraded | minor | 2h |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.