Jun 1, 20:02 UTC
Resolved - This incident has been resolved.

Jun 1, 19:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Jun 1, 19:50 UTC
Identified - The issue has been identified and a fix is being implemented.

Jun 1, 19:21 UTC
Investigating - We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.

May 28, 16:59 UTC
Resolved - This incident has been resolved.

May 28, 16:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

May 28, 16:18 UTC
Identified - The issue has been identified and a fix is being implemented.

May 28, 16:00 UTC
Investigating - We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.

May 27, 05:02 UTC
Resolved - This incident has been resolved.

We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC.

May 27, 04:50 UTC
Investigating - We are currently investigating this issue.

May 25, 16:22 UTC
Resolved - This incident has been resolved.

May 25, 16:05 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

May 25, 15:25 UTC
Identified - The issue has been identified and a fix is being implemented.

May 25, 14:58 UTC
Investigating - We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.

May 23, 18:44 UTC
Resolved - This incident has been resolved.

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

May 23, 18:21 UTC
Monitoring - GitHub has implemented a fix, and we are monitoring the results.

May 23, 15:46 UTC
Identified - We have identified the issue and are working closely with GitHub to resolve it.

May 23, 14:30 UTC
Update - 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.

May 23, 12:15 UTC
Update - We are continuing to investigate this issue.

May 23, 11:09 UTC
Update - 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.

May 23, 10:43 UTC
Investigating - We are currently investigating this issue.

May 22, 17:11 UTC
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.

May 21, 21:31 UTC
Resolved - This incident has been resolved.

May 21, 21:20 UTC
Monitoring - The mitigation was successfully rolled out, and builds are stable.

May 21, 19:55 UTC
Update - The root cause has been identified and we are rolling out a mitigation.

May 21, 15:01 UTC
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.

May 21, 06:08 UTC
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 as we backfill the data for the affected window.

May 20, 20:07 UTC
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.

May 18, 23:52 UTC
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.

May 18, 22:19 UTC
Update - We are continuing to monitor for any further issues.

May 18, 22:16 UTC
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.

May 18, 22:11 UTC
Update - 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.

May 18, 21:53 UTC
Identified - The issue has been identified and a fix is being implemented.

May 18, 21:42 UTC
Investigating - We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.

May 18, 15:41 UTC
Resolved - The incident is resolved and support cases can be submitted again.

May 18, 15:17 UTC
Monitoring - We have implemented a fix. New support cases can be created. We continue to monitor.

May 18, 15:00 UTC
Investigating - We are investigating an issue where support cannot be submitted through the dashboard.