Incident with Pull Requests and Issues

What to do

• Check whether you use GitHub Issues, Pull Requests. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 25m it lasted.

  Anything that failed between 2026-08-12 16:16 UTC and 2026-08-12 16:41 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 5

1. investigatingAug 12, 2026, 4:16 PM UTC

   We are investigating reports of degraded performance for Issues and Pull Requests

   provider

2. investigatingAug 12, 2026, 4: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.

   provider

3. monitoringAug 12, 2026, 4:35 PM UTC

   The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

   provider

4. monitoringAug 12, 2026, 4: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.

   provider

5. resolvedAug 12, 2026, 4:41 PM 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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.