GitHub Status · History · Incident #2985
RESOLVEDIncident with CodeQL, Webhooks, Notifications, and Slack Integration
Minor · Started May 12, 2026 · 2:38 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 #2985
RESOLVEDMinor · Started May 12, 2026 · 2:38 PM
Duration
3h 5m
Severity
Minor
Detection lead
—
User reports
—
Summary
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Started
May 12, 2026 · 2:38 PM
Resolved
May 12, 2026 · 5:43 PM
Duration
3h 5m
Severity
Minor
Event timeline
Investigating
May 12 · 2:38 PM GitHubWe are investigating reports of degraded performance for CodeQL
Investigating
May 12 · 3:13 PM GitHubCodeQL actions are currently experiencing delays, which may result in those actions being stuck in a pending state or having failed due to a timeout.
Investigating
May 12 · 3:42 PM GitHubWe're continuing to investigate issues with CodeQL actions workflows. We're additionally seeing delays for notifications, webhooks, and the Slack integration.
Investigating
May 12 · 3:44 PM GitHubWebhooks is experiencing degraded performance. We are continuing to investigate.
Investigating
May 12 · 4:18 PM GitHubWe've established that most delays are related to a queuing service and are working to scale out. Early signals from the scale-out are showing signs of recovery for some services. We'll provide an update when services are fully recovered.
Investigating
May 12 · 4:28 PM GitHubWebhooks is operating normally.
Investigating
May 12 · 4:29 PM GitHubWebhooks have fully recovered. Continuing to work on recovery for the other services.
Investigating
May 12 · 4:59 PM GitHubCodeQL has fully recovered. We're continuing to work on recovery for the remaining impacted services.
Investigating
May 12 · 5:43 PM GitHubAll services have fully recovered.
Resolved
May 12 · 5:43 PM GitHubThis incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
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