Skip to content
GitHub · Developer toolsAug 12, 2026, 16:16 UTC

Incident with Pull Requests and Issues

MinorDatabaseUpdated 18h ago
Aug 12, 16:16 UTCAug 12, 16:41 UTC
Duration
25m
Impact
Minor
Root cause
Database
GitHub, 90 days
68 incidents
Affected
IssuesPull Requests
Status page

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

  1. 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.
  2. 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.
  3. Monitoring · Aug 12, 16:35 UTC
    The degradation affecting Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.
  4. 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.
  5. Investigating · Aug 12, 16:16 UTC
    We are investigating reports of degraded performance for Issues and Pull Requests

More from GitHub

Full history
StartedIncidentDuration
Sep 2310:11 UTCIncident across several servicesOngoing
Sep 2022:13 UTCIncident with Pull Requests1h 9m
Sep 1720:59 UTCElevated rate of errors for OpenAI models provided by Copilot50m
Sep 1607:20 UTCDegradation with Gemini 3.8 Flash10h 28m
Sep 1519:11 UTCDisruption with some GitHub services49m
Sep 1509:47 UTCDisruption with some GitHub services1h 30m

Also caused by database

All
StartedIncidentDuration
Sep 921:53 UTCINC20000211Snowflake1h 58m
Aug 2616:17 UTCIssues performance is degraded in the USSentry4h 19m
Aug 818:57 UTCAccount Registration, Droplets, and Related ServicesDigitalOcean6h 3m
Jul 2817:41 UTCEvent ingestion and retrieval delays for some North America customersHubSpot2h
Jul 300:11 UTCPartial outage in ORDFly.io5h 48m
Jun 1920:13 UTCSnyk Code (SAST) Scan service degradedSnyk2h

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.