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…

i think its related with middleware (changed to proxy) and experimental Next.js models

My build tool longer than usual to build during deployment. It resulted in below response error ” We encountered an internal error. Please try again” [image]

I’m also expriencing same issue.

!!!MIGRATE FROM MIDDLEWARE TO PROXY for nextjs - WILL FIX IT!!!

Working for me in setting region to france (cdg1)

renaming middleware.ts to proxy.ts worked for me.

I didn’t change anything meaningful but getting the same error

It’s working well now!:slightly_smiling_face:

Thanks, my deploy is working now.

Vercel deployment failure with internal error during deploying outputs phase

Help

Topic		Replies	Views
Vercel deployment internal error during output upload in iad1 and sfo1 regions Help nextjs , cli , builds , dashboard , turbopack	0	393	March 2, 2026
Vercel deployment fails with internal error during deploying outputs phase Discussions nextjs , builds , turbopack	0	173	March 2, 2026
Next.js middleware fails to execute after Vercel CLI 50.28.0 build regression Help nextjs , cli , builds	28	462	March 9, 2026
Ongoing incident: elevated errors across multiple services Help	54	1854	October 21, 2025
Deploying outputs fails with internal error — zero output artifacts Help	2	52	July 11, 2026

Vercel deployment failure with internal error during deploying outputs phase

Related topics