Vercel Status

Resolved: This incident has been resolved.

Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt

Monitoring: GitHub has implemented a fix, and we are monitoring the results.

Identified: We have identified the issue and are working closely with GitHub to resolve it.

Investigating: We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops.

Investigating: We are continuing to investigate this issue.

Investigating: We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs.

CLI deployments are unaffected at this time.

Investigating: We are currently investigating this issue.

Resolved: 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.

Resolved: This incident has been resolved.

Monitoring: The mitigation was successfully rolled out, and builds are stable.

Identified: The root cause has been identified and we are rolling out a mitigation.

Identified: We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.

Resolved: This incident has been resolved.

Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up over the next business day as we backfill the data for the affected window.

Monitoring: We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.

Resolved: This incident has been resolved.

Some deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments created outside of this window are unaffected.

The fix is being rolled out to existing deployments retrospectively and is expected to finish in the next few hours.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix is rolled out for the function invocation errors affecting React Router 7 deployments. To recover, redeploy your application or use Instant Rollback to a previous deployment from the dashboard. We're continuing to monitor.

Identified: We're continuing to work on rolling out a fix. In the mean time, customers may use Instant Rollback to a previous deployment version as an immediate workaround in order to recover.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.

Resolved: The incident is resolved and support cases can be submitted again.

Monitoring: We have implemented a fix. New support cases can be created. We continue to monitor.

Investigating: We are investigating an issue where support cannot be submitted through the dashboard.