Vercel deployment internal error during output upload in iad1 and sfo1 regions

Problem

Every deployment fails at the “Deploying outputs…” step with “We encountered an internal error. Please try again.” The build itself completes successfully — Next.js compiles, TypeScript passes, all 36 pages generate, serverless functions are created.

Expected behavior is that outputs deploy normally after a successful build.

Inspecting failed deployments via the Vercel CLI shows:

readyState: ERROR
errorCode: null
errorMessage: null
output: [ ] (0 artifacts)

The last successful deployment produced 180 output artifacts from the same codebase.

Steps to Reproduce

  1. Push any commit to main (or manually redeploy from the dashboard)
  2. Build completes successfully: Build Completed in /vercel/output [1m]
  3. “Deploying outputs…” hangs for ~20 seconds
  4. Fails with:

Error: We encountered an internal error. Please try again.

Tried 6+ consecutive deployments including manual redeploys with build cache disabled. All fail identically.

Environment

  • Framework: Next.js 16.1.6 (Turbopack, App Router)
  • Plan: Hobby
  • Build region: iad1 (Washington DC)
  • Build output region: sfo1
  • Last successful deploy: ~07:00 UTC, 1 Mar 2026
  • First failure: ~07:00 UTC, 2 Mar 2026

This is not related to the active Dubai (dxb1) incident on the status page — my deployments use iad1/sfo1. Vercel’s AI support confirmed this is a platform-side issue based on the null error codes and zero output artifacts pattern, and recommended a support case. Is anyone else seeing deployment failures on iad1/sfo1 today?

3 Likes

8 posts were merged into an existing topic: Vercel deployment failure with internal error during deploying outputs phase

A post was merged into an existing topic: Vercel deployment failure with internal error during deploying outputs phase