Elevated INTERNAL_UNEXPECTED_ERROR error rates for some deployments

What to do

• Check whether you use Vercel Builds. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 4h 29m it lasted.

  Anything that failed between 2026-04-02 18:39 UTC and 2026-04-02 23:09 UTC may need a replay.

• Subscribe to Vercel's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vercel 4

1. investigatingApr 2, 2026, 6:39 PM UTC

   We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.

   provider

2. identifiedApr 2, 2026, 7:26 PM UTC

   We have identified the issue and are rolling out a fix. Deployments created between 16:10 to 19:12 UTC may be affected. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.

   provider

3. monitoringApr 2, 2026, 8:02 PM UTC

   The fix has been rolled out and we are monitoring the results. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.

   provider

4. resolvedApr 2, 2026, 11:09 PM UTC

   This incident has been resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.