GitHub Status · History · Incident #4625
RESOLVEDIncreased latency with webhooks
Minor · Started Jun 15, 2026 · 3:37 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 #4625
RESOLVEDMinor · Started Jun 15, 2026 · 3:37 PM
Duration
2h
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
Jun 15, 2026 · 3:37 PM
Resolved
Jun 15, 2026 · 5:37 PM
Duration
2h
Severity
Minor
Event timeline
Investigating
Jun 15 · 3:37 PM GitHubWe are investigating reports of degraded performance for Webhooks
Investigating
Jun 15 · 4:39 PM GitHubWebhooks delivery latency has returned to normal levels. The backlog that built up during the incident has been cleared at approximately 4:29 UTC. We consider this incident resolved.
Monitoring
Jun 15 · 4:39 PM GitHubThe degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Resolved
Jun 15 · 5:37 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.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026