GitHub Status · History · Incident #284
RESOLVEDIncident with Issues and Webhooks
Critical · Started May 4, 2026 · 3:45 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
GitHub Status · History · Incident #284
RESOLVEDCritical · Started May 4, 2026 · 3:45 PM
Duration
54m
Severity
Critical
Detection lead
—
User reports
—
Summary
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.
Started
May 4, 2026 · 3:45 PM
Resolved
May 4, 2026 · 4:40 PM
Duration
54m
Severity
Critical
Event timeline
Investigating
May 4 · 3:45 PM GitHubWe are investigating reports of degraded performance for Issues and Webhooks
Investigating
May 4 · 3:48 PM GitHubWe are investigating Increased latency and timeouts across multiple GitHub services.
Investigating
May 4 · 3:48 PM GitHubGit Operations is experiencing degraded performance. We are continuing to investigate.
Investigating
May 4 · 3:50 PM GitHubPackages is experiencing degraded performance. We are continuing to investigate.
Investigating
May 4 · 3:51 PM GitHubPull Requests is experiencing degraded availability. We are continuing to investigate.
Investigating
May 4 · 3:51 PM GitHubActions is experiencing degraded performance. We are continuing to investigate.
Investigating
May 4 · 3:56 PM GitHubPull Requests is experiencing degraded performance. We are continuing to investigate.
Investigating
May 4 · 4:05 PM GitHubCodespaces is experiencing degraded performance. We are continuing to investigate.
Investigating
May 4 · 4:06 PM GitHubPages is experiencing degraded performance. We are continuing to investigate.
Investigating
May 4 · 4:25 PM GitHubGit Operations is operating normally.
Investigating
May 4 · 4:28 PM GitHubActions and Packages are operating normally.
Investigating
May 4 · 4:29 PM GitHubLatency across services has normalized. We are continuing to investigate the root cause and prevent reoccurrence.
Investigating
May 4 · 4:29 PM GitHubPages is operating normally.
Investigating
May 4 · 4:32 PM GitHubPull Requests is operating normally.
Investigating
May 4 · 4:34 PM GitHubThe degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
Investigating
May 4 · 4:35 PM GitHubThe degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
Investigating
May 4 · 4:35 PM GitHubWebhooks is operating normally.
Monitoring
May 4 · 4:36 PM GitHubThe degradation has been mitigated. We are monitoring to ensure stability.
Resolved
May 4 · 4:40 PM GitHubOn 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.
Pattern
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT