GitHub outage: Incident with Issues and Webhooks

1. resolvedMay 4, 2026, 16:40 UTC

   On 2026-05-04 at 3:37:17 PM UTC we detected increased latency on issues resulting in timeouts, and elevated 500 errors on webhooks. A scheduled workload drove high utilization on the primary host of a critical datastore, saturating the connection pool. We paused the job to mitigate the problem at 4:40:05 PM UTC and have implemented measures to prevent recurrence.

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.

• Contentful: Some customers are experiencing issues logging inMajor · May 4, 2026, 13:20 UTC
• Miro: Miro is partially downMajor · May 4, 2026, 16:23 UTC
• Snyk: Snyk recurring tests showing slow performanceMinor · Apr 21, 2026, 18:58 UTC
• Intercom: Investigating: Compromised version of intercom-client npm package and intercom-phpMinor · Apr 30, 2026, 16:58 UTC
• Linode: (Copy Fail) Linux Kernel Local Privilege Escalation Vulnerability [CVE-2026-31431]Minor · May 1, 2026, 17:51 UTC
• Twilio: Voice Call Audio Quality Degradation Between Twilio Phone Numbers and Multiple Networks in United KingdomMinor · May 2, 2026, 18:00 UTC
• LaunchDarkly: Elevated Streaming Errors in EuropeMinor · May 4, 2026, 10:14 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