Vercel Status · History · Incident #3954
RESOLVEDBuild Failures for Some Next.js Deployments
Minor · Started May 22, 2026 · 5:11 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'] . '/'; ?>
Vercel Status · History · Incident #3954
RESOLVEDMinor · Started May 22, 2026 · 5:11 PM
Duration
< 1m
Severity
Minor
Detection lead
—
User reports
—
Summary
Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.
Started
May 22, 2026 · 5:11 PM
Resolved
May 22, 2026 · 5:11 PM
Duration
< 1m
Severity
None
Event timeline
Resolved
May 22 · 5:11 PM VercelBetween 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.
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