GitHub outage: Incident with Pull Requests

1. resolvedMay 6, 2026, 19:04 UTC

   On May 6, 2026 between 15:12 and 19:02 UTC creation of new pull request review threads on GitHub.com failed. This included new line comments and file comments on pull requests. Existing PRs and previously created comments were unaffected. This incident was caused by a 32-bit integer key reaching its maximum value in a Vitess lookup table used during PR thread creation. The primary table had been migrated to a 64-bit integer key but the Vitesse lookup table remained 32-bit. Once the values in the primary table passed the available 32-bit ID space in the lookup table, attempts to create new review threads began failing, resulting in near 100% failure rate for new thread creation requests. We mitigated the issue by updating the impacted lookup table definitions across all shards to use 64-bit integer column types, increasing the available ID range and restoring normal operation. Service was fully restored once the schema changes competed globally. To help prevent similar incidents, we

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Anthropic: Elevated errors across multiple modelsMajor · May 6, 2026, 15:29 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Twilio: Voice Call Audio Quality Degradation Between Twilio Phone Numbers and Multiple Networks in United KingdomMinor · May 2, 2026, 18:00 UTC
• Twilio: SMS Delivery Failures from a Subset of Twilio Short Codes to Google Voice United StatesMinor · May 4, 2026, 20:40 UTC
• Shippo: Royal Mail InterSoft Tracking Degradation (Third-Party Issue)Minor · May 4, 2026, 20:48 UTC
• Netlify: Elevated Errors and LatencyMinor · May 6, 2026, 15:29 UTC
• Snyk: Snyk Recurring Tests DelayedMinor · May 6, 2026, 15:32 UTC
• Cursor: Investigating service degradation — Cloud Agents, CLI, and IDEMinor · May 6, 2026, 15:33 UTC
• Mailgun: Automatic Sender Security Records Not ProvisioningMinor · May 6, 2026, 15:40 UTC
• Twilio: Voice Call Failures From Twilio to Multiple Networks in SpainMinor · May 6, 2026, 16:27 UTC

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history