Same issue here. Build passes clean without any errors - but deployment fails “Error: We encountered an internal error. Please try again.”
My regions aren’t set to Dubai either, which is currently experiencing issues.
Same issue here on iad1 and EU
same problem, us-east-1
I hope the issue gets resolved quickly. Need to make a release to sklls matrix app
Same problem here on iad1
Same issue, but it only happens for particular projects. All my projects are in the same region Washington DC.
Just wanted to confirm I’m having the same issue. I choose 3 different deployment regions (2 in the US, one in EU), then I tried another region in ZA, and still the same issue. Build is successful, but failed due to an internal issue.
Same :
Running build in Portland, USA (West) – pdx1 (Turbo Build Machine)
Build machine configuration: 30 cores, 60 GB
…
Traced Next.js server files in: 31.005ms
Created all serverless functions in: 168.371ms
Collected static files (public/, static/, .next/static): 8.274ms
Build Completed in /vercel/output [1m]
Deploying outputs…
Error: We encountered an internal error. Please try again.
Despite changing regions multiple times, it still fails due to an internal error.
Everyone, the build region is not the problem, please see:
”We are still seeing elevated errors in Builds in all regions, because Middleware and Edge Functions may be deployed globally. Builds that don’t use Middleware and Edge Functions are not impacted. We are continuing to work on a fix for this issue.”
Hi @pawlean 
Same issue here. Deployment fails at “Deploying outputs…” with internal error:
[@serwist/build] Building service worker…
[@serwist/build] Service worker built successfully at /vercel/path0/public/sw.js
[@serwist/build] Entries: 11 | Total size: 227.2KB | Git revision: d70e1ae
Traced Next.js server files in: 170.698ms
Created all serverless functions in: 1.212s
Collected static files (public/, static/, .next/static): 14.857ms
Build Completed in /vercel/output [3m]
Deploying outputs…
Error: We encountered an internal error. Please try again.
- Deployment: [project] – Deployment Overview – Vercel
- Framework: Next.js 16.1.2
- Region: Washington, D.C., USA (East) - us-east-1 - iad1
Same issue here..
Error: We encountered an internal error. Please try again.
Same problem during production deployment.**
**
Traced Next.js server files in: 54.167ms
Created all serverless functions in: 566.518ms
Collected static files (public/, static/, .next/static): 4.836ms
Build Completed in /vercel/output [43s]
Deploying outputs…
Error: We encountered an internal error. Please try again.
- NextJs v. 16.1.6
- region: Paris, France (West) - eu-west-3 - cdg1
The same issue is occurring in the India (ap-south-1) Mumbai region as well.
Fix: Vercel “internal error” on deploy with Next.js 16 middleware
If your Next.js 16 build succeeds but deployment fails with:
Error: We encountered an internal error. Please try again.
…right at the “Deploying outputs” step — it may be caused by the
deprecated middleware.ts file convention.
Next.js 16 deprecated middleware in favor of proxy (proxy.ts with export
async function proxy()), but even renaming to proxy.ts can still cause
Vercel deploy failures depending on your setup.
What worked for me: Remove the middleware/proxy entirely. If your pages
already handle auth server-side (e.g. checking session in layouts/pages
and redirecting), the middleware is redundant. In my case every page
already called supabase.auth.getUser() and redirected unauthenticated
users — the middleware was just doing double work.
rm src/middleware.ts # or src/proxy.ts
Build passed and deployed immediately after.
TL;DR: Next.js 16 + Vercel may choke on the old middleware convention at
deploy time even when the build compiles fine. Check if your auth
guards already live in layouts/pages — if so, just delete the
middleware.
Update:
We are currently deploying a mitigation for elevated Build errors. Builds that use Middleware or Edge Functions will exclude the Dubai region (dxb1) from their deployment targets as a temporary measure. We will provide additional updates as they become available.
5 Likes
same issue here.
Error: We encountered an internal error. Please try again.
Spot on!! Thanks for listening @pawlean. Feeling way more confident for tomorrow hahah cheers!
1 Like
Our team is on it! I’ll keep you updated 
3 Likes