Incident with Pull Requests and Issues

Timeline

1. 18 Aug · 15:52 UTC 🟡 Resolved atom

   Aug 12, 16:41 UTC
   Resolved - 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.
   
   Aug 12, 16:38 UTC
   Update - 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.
   
   Aug 12, 16:35 UTC
   Monitoring - The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
   
   Aug 12, 16:24 UTC
   Update - 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.
   
   Aug 12, 16:16 UTC
   Investigating - We are investigating reports of degraded performance for Issues and Pull Requests

2. 18 Aug · 15:52 UTC 🟡 Resolved atom

   Aug 12, 16:41 UTC
   Resolved - 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.
   
   Aug 12, 16:38 UTC
   Update - 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.
   
   Aug 12, 16:35 UTC
   Monitoring - The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
   
   Aug 12, 16:24 UTC
   Update - 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.
   
   Aug 12, 16:16 UTC
   Investigating - We are investigating reports of degraded performance for Issues and Pull Requests