Netlify Status · History · Incident #4066
RESOLVEDFailed & delayed builds due to Github incident
Major · Started May 27, 2026 · 12:13 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'] . '/'; ?>
Netlify Status · History · Incident #4066
RESOLVEDMajor · Started May 27, 2026 · 12:13 PM
Duration
2h 4m
Severity
Major
Detection lead
—
User reports
—
Summary
This incident has been resolved, and builds have returned to functioning normally.
Started
May 27, 2026 · 12:13 PM
Resolved
May 27, 2026 · 2:17 PM
Duration
2h 4m
Severity
Major
Event timeline
Investigating
May 27 · 12:13 PM NetlifyWe are currently experiencing delays in our build pipeline due to a current incident at Github.
Identified
May 27 · 12:58 PM NetlifyIn addition to delayed builds, we are also experiencing build failures due to the current incident at Github.
Resolved
May 27 · 2:17 PM NetlifyThis incident has been resolved, and builds have returned to functioning normally.
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