Vercel incident

Elevated INTERNAL_UNEXPECTED_ERROR error rates for some deployments

Resolved after 4 hours 29 minutes, affecting Builds, on April 2, 2026.

monitoring Apr 02, 2026, 08: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.

Started
Apr 02, 2026, 06:39 PM UTC
Resolved
Apr 02, 2026, 11:09 PM UTC
Duration
4h 29m
Detected by Pingoru
Apr 02, 2026, 06:39 PM UTC

Affected components

Builds

Update timeline

  1. investigating Apr 02, 2026, 06: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.

  2. identified Apr 02, 2026, 07: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.

  3. monitoring Apr 02, 2026, 08: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.

  4. resolved Apr 02, 2026, 11:09 PM UTC

    This incident has been resolved.

Your product runs on more than Vercel

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →