Incident with Pull Requests

What to do

• Check whether you use GitHub 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 46m it lasted.

  Anything that failed between 2026-07-24 19:37 UTC and 2026-07-24 20:23 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 6

1. investigatingJul 24, 2026, 7:37 PM UTC

   We are investigating reports of degraded performance for Pull Requests

   provider

2. investigatingJul 24, 2026, 7:40 PM UTC

   We are investigating errors creating pull requests

   provider

3. investigatingJul 24, 2026, 7:43 PM UTC

   Pull Requests is experiencing degraded availability. We are continuing to investigate.

   provider

4. investigatingJul 24, 2026, 7:59 PM UTC

   We have applied a mitigation and are monitoring for recovery

   provider

5. monitoringJul 24, 2026, 8:02 PM UTC

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

   provider

6. resolvedJul 24, 2026, 8:23 PM UTC

   Between July 24, 19:17 UTC and July 24, 20:02 UTC, users were unable to create pull requests due to a database schema change. In total, 113,930 pull request creation attempts were impacted across 50,904 users, with an average error rate of 1.75% and a maximum error rate of 2.25% for all requests to Pull Requests service. Existing pull requests and other GitHub functionality were not affected. The issue was resolved by reverting the change to the affected database, upon which pull request creation immediately resumed. The root cause was related to a backfill workflow into the Vitess keyspace hosting Pull Request data. The backfill Vitess command encountered errors and increased VReplication lag, and the workflow was canceled at 19:17 UTC. The cancellation executed a misunderstood Vitess codepath that dropped the backing table to the target keyspace, leaving a non-existent reference that resulted in errors creating Pull Requests. The mitigation was executing a command to drop the vschema reference to the dropped table, allowing Pull Request creation to resume. We are adding stronger pre-flight validation to our tooling to prevent similar issues and expanding lower-environment support to provide better test coverage end-to-end before promoting them to production. We're also fixing our backfill migration tooling to protect from this specific codepath.

   provider

Corrections

None so far.

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