yashank-d
(Yashank D)
March 2, 2026, 6:10am
1
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.1.6
Build completed successfully
Static files collected
Serverless functions created
Output generated in /vercel/output
There are no build errors, no runtime errors, and no TypeScript errors. The issue happens after the build phase finishes.
Expected Behavior
Deployment should complete successfully since the build phase finishes without errors.
Environment
Framework: Next.js 16.1.6
Router: App Router
Deployment target: Production
Runtime: Node.js
Features: Using serverless functions, no edge middleware errors, no custom build output configuration.
This appears to be an internal deployment infrastructure issue rather than a build or configuration problem.
23 Likes
I’m experiencing the same issue
3 Likes
I’m also getting the same error on a successful build, been retrying with no luck
1 Like
I’m getting this on preview deployment:
Error: We encountered an internal error. Please try again.
No luck with retries.
3 Likes
same, is vercel delpoyment down?
1 Like
Same problem on iad1, this is not dxb1 exclusive.
3 Likes
Same problem here, although I operate from within the EU.
1 Like
Same problem, in the Washington D.C. (iad1) region.
“Deployments with Middleware Functions are also impacted, because Middleware Functions are deployed globally for production deployments.”
jarnow
(Jarno)
March 2, 2026, 9:29am
17
Same here.
Running build in Washington, D.C., USA (East) – iad1
Build machine configuration: 4 cores, 8 GB
jenlai1345
(Jennifer Lai)
March 2, 2026, 9:35am
19
encountering same error here. builds fine, just this error at the end during deployment.
Does this have anything with do with the middle-east war going on? (Dubai region service interrupted) My application is in the Asia-pacific though.
“Error: We encountered an internal error. Please try again.”
2 Likes
ulyngs
(ulyngs)
March 2, 2026, 9:36am
20
Same; builds correctly, says it’s “Deploying outputs..” then gives me “Error: We encountered an internal error. Please try again.”
We’re in eu region
sam issue,
Error: We encountered an internal error. Please try again.
lukasver
(Lucas Verdiell)
March 2, 2026, 9:45am
23
Yep, same error here in EU