Problem I am experiencing a deployment failure on Vercel even though the build completes successfully. Current Behavior The failure occurs during the “Deploying outputs” phase with the following message: Error: We encountered an internal error. Please try again. The build logs show: Next.js 16…

Glad it’s working! Latest update: Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments. [image] Dubai region (dxb1) is unavailable Vercel's Status Page - Dubai regio…

same error here, and we are not in Dubai!!! we are in Germany. What is going on?

[SOLVED] “We encountered an internal error” when deploying with Middleware/Proxy on Next.js Spent a while debugging a generic deploy error and want to leave this here for anyone who runs into the same issue. The problem Every deployment consistently failed at the Deploying outputs... step with the…

Hi there, Thank you for your patience while we investigated this. As the dxb1 (Dubai) region is still unhealthy, and we’ve deployed a mitigation to address the elevated build errors. As part of this temporary measure, builds that use Middleware or Edge Functions will exclude dxb1 from their deploym…

I am experiencing a persistent deployment failure with my project after attempting to change the deployment region. I have followed all the standard troubleshooting steps, but the issue remains unresolved.

Same issue. Even after updating regions in vercel.json its still failed 4-5 times. Is there any timeline on this issue fix. Asking to push fixes from users instead of doing somewhere in a generic fashion by the Vercel staff is a hilarious RCA fix

Your deployment is still using edge function which are affected: [image] You can consider swiching to node runtime Using the Node.js Runtime with Vercel Functions until we rollout the fix for edge functions

Yes you can switch to Node runtime to unblock immediately, you can do this by removing export const runtime = 'edge'; from your function

I saw the Vercel Staff recommendation to switch Middleware from Edge to Node.js runtime as a workaround. Before I make that change, I have a billing concern: Our middleware currently runs on the Edge runtime, which is included in the Pro plan. If I switch to the Node.js runtime (nodeMiddleware: tru…

Vercel deployment failure with internal error during deploying outputs phase

Help

saidaitmbarek (Said Aitmbarek) March 2, 2026, 12:56pm 140

Same on my side, iad1 issue:

Running build in Washington, D.C., USA (East) – iad1

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

Topic		Replies	Views
Vercel deployment internal error during output upload in iad1 and sfo1 regions Help nextjs , cli , builds , dashboard , turbopack	3	357	March 2, 2026
Vercel deployment fails with internal error during deploying outputs phase Discussions nextjs , builds , turbopack	2	142	March 2, 2026
Next.js middleware fails to execute after Vercel CLI 50.28.0 build regression Help nextjs , cli , builds	29	259	March 23, 2026
Ongoing incident: elevated errors across multiple services Help	55	1652	November 4, 2025
Vercel Internal Build Error since yesterday! Help nextjs , builds	2	243	October 26, 2025

Vercel deployment failure with internal error during deploying outputs phase

Related topics