GitHub experienced a minor incident on August 12, 2026 affecting Issues and Pull Requests, lasting 25m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 12, 2026, 04:16 PM UTC
We are investigating reports of degraded performance for Issues and Pull Requests
- investigating Aug 12, 2026, 04:24 PM 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.
- monitoring Aug 12, 2026, 04:35 PM UTC
The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
- monitoring Aug 12, 2026, 04:38 PM 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.
- resolved Aug 12, 2026, 04:41 PM UTC
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.