[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Help](/c/help/9)

# Vercel deployment failure with internal error during deploying outputs phase

5586 views · 137 likes · 195 posts


Yashank D (@yashank-d) · 2026-03-02 · ♥ 23

## 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: 
```bash
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.


Robertcowherd 4461 (@robertcowherd-4461) · 2026-03-02 · ♥ 3

I’m experiencing the same issue


Cpfitz14 5325 (@cpfitz14-5325) · 2026-03-02 · ♥ 1

same issue here


Abdul0398 (@abdul0398) · 2026-03-02 · ♥ 2

Same issue here


Logan Brenningmeyer (@loganbrenningmeyer) · 2026-03-02 · ♥ 1

I’m also getting the same error on a successful build, been retrying with no luck


Tatsuo (@tatsuonomura-6136) · 2026-03-02 · ♥ 3

I’m getting this on preview deployment:
Error: We encountered an internal error. Please try again.

No luck with retries.


Jayesh Sadhwani (@jayeshsadhwani-7544) · 2026-03-02 · ♥ 1

same, is vercel delpoyment down?


Brainergy (@timekast) · 2026-03-02 · ♥ 1

Same problem


Asher Cohen (@asherccohen) · 2026-03-02

same problem


Timppp 4635 (@tim3wang-4635) · 2026-03-02

exact same problem


L G (@leonardogazdek) · 2026-03-02 · ♥ 3

Same problem on iad1, this is not dxb1 exclusive.


Björn (@bsgoods77-7754) · 2026-03-02 · ♥ 1

Same problem here, although I operate from within the EU.


Tyrone Robb (@ty-priority) · 2026-03-02

Same problem, in the Washington D.C. (`iad1`) region. 

https://www.vercel-status.com/ 

"Deployments with Middleware Functions are also impacted, because **Middleware Functions are deployed globally** for production deployments."


Jarno (@jarnow) · 2026-03-02

Same here.

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

Build machine configuration: 4 cores, 8 GB


Will (@wukongsch) · 2026-03-02

Same problem


Jennifer Lai (@jenlai1345) · 2026-03-02 · ♥ 2

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.”


ulyngs (@ulyngs) · 2026-03-02

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


Zabsalahid (@zabsalahid) · 2026-03-02

sam issue,
Error: We encountered an internal error. Please try again.


Enorvaisa (@enorvaisa) · 2026-03-02

Same for me, EU region.


Lucas Verdiell (@lukasver) · 2026-03-02

Yep, same error here in EU


BYL8697 (@ben860228) · 2026-03-02 · ♥ 1

same here.
”We encountered an internal error. Please try again.”


kylemediagroupwwcom (@kyle-3729) · 2026-03-02 · ♥ 1

Same here UK


Fractalwind (@fractalwind) · 2026-03-02

Same issue here. Washington build from EU.
https://www.vercel-status.com


Armando Baños Pascual (@armandobanos-7756) · 2026-03-02

Same issue over here


Muhammad Aryo Muzakki (@aryomuzakki) · 2026-03-02

same issue

```
Traced Next.js server files in: 33.907ms
Created all serverless functions in: 336.095ms
Collected static files (public/, static/, .next/static): 9.119ms
Build Completed in /vercel/output \[48s\]
Deploying outputs...
Error: We encountered an internal error. Please try again.
```

vercel help chat answer:

> 
> Thank you for sharing those details. I can see your build completed successfully but failed during the "Deploying outputs" phase with an internal error. Let me look into your recent deployments to get more context. I can see you have multiple recent deployments all failing with the same internal error. This appears to be a platform-side issue rather than something with your code or configuration, since the build completes successfully but fails during the deployment phase.
> 
> Let me check your project's region configuration to help investigate further. I can confirm your project is currently set to the Singapore region (`sin1`). I see you have multiple failed deployments all with the same internal error - this is a platform-side issue.
> 
> **Good news:** There's currently an identified incident affecting deployments and function invocations. While it's primarily impacting the Dubai region, internal deployment errors like yours may be related to broader infrastructure issues our team is actively working on.
> 
> Here's what I recommend:
> 
> * **Try a different region:** Since you've tried Washington and Singapore, consider temporarily switching to a different region like San Francisco (`sfo1`) or Frankfurt (`fra1`) to see if it resolves the issue.
> 
> * **Wait and retry:** Since this appears to be an infrastructure-related issue, waiting 15-30 minutes and redeploying may help as mitigations are being rolled out.
> 
> To change your function region:
> 
> 1. Go to your project's **Settings** → **Functions**
> 
> 2. Under "Serverless Function Region", select a different region
> 
> 3. Redeploy your project

but still not work


The Borderland (@theborderland) · 2026-03-02

Same here, also in EU region


Dan 8786 (@dan-8786) · 2026-03-02

Same issue, in EU :frowning:


Anshuman Bhardwaj (@anshumanb) · 2026-03-02 · ♥ 11

Hi everyone, I can also see the same issue. Let me escalate it and keep you all posted here.


Rwwwn (@rwwwn) · 2026-03-02

yup same here “Error: We encountered an internal error. Please try again.”


coredeveloper (@coredeveloper) · 2026-03-02

same here for the EU region, looks like it’s not a dubai. Its a Post Build issue


Anas Dib (@anas-4786) · 2026-03-02

Same issue


verbose (@whatamanoffical) · 2026-03-02

Can confirm the same, even with functions in EU/ARN


Kllakm (@kllakm) · 2026-03-02

Same issue! when will this be resolved?


Adilmohak (@adilmohak) · 2026-03-02

Same issue!


Alex (@predam) · 2026-03-02

Same issue here …


Hamishclulee (@hamishclulee) · 2026-03-02

Same issue for me


Jdick (@jdick-9942) · 2026-03-02

Same here in EU


Mike (@reex-mike) · 2026-03-02

Are we going to be refunded the build costs for all these failed deployments? Builds aren’t cheap as it is and now I have a flood of failed builds and deployments


AmityEdge (@amityedge) · 2026-03-02

iam facing the same issue in 

| bom1	| ap-south-1	| Mumbai, India |
|----|----|----|

tony (@tonyluong) · 2026-03-02

me same here


Kllakm (@kllakm) · 2026-03-02 · ♥ 2

would love them to acknowledge this and not just pretend its dubai only.


Qu2stion (@qu2stion) · 2026-03-02

## Problem

My `Next.js` project builds successfully, but the deployment fails during the `Deploying outputs...` phase with the following error:

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

## Current Behavior

Build completes successfully:

* Serverless functions created
* Static files collected
* Output generated in `/vercel/output`

The failure happens only during the deploy outputs stage.

## Environment Details

* **Project name:** `gdghyonsei`
* **Deployment ID:** `DFheubcpo`
* **Framework:** `Next.js 16.1.1`
* **Environment:** Production
* **Redeploy attempted:** Yes (same result)

I only modified a page component in this commit. Could you please check the internal logs for this deployment?

Thank you.

ƒ Proxy (Middleware)

○  (Static)   prerendered as static content

ƒ  (Dynamic)  server-rendered on demand

Traced Next.js server files in: 50.641ms

Created all serverless functions in: 255.38ms

Collected static files (public/, static/, .next/static): 5.443ms

Build Completed in /vercel/output \[24s\]

Deploying outputs...

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


pe (@pierreascone-5131) · 2026-03-02

Same in EU


Anshuman Bhardwaj (@anshumanb) · 2026-03-02 · ♥ 10

Hi everyone, this is an active issue and our team is working to resolve it. 

> Deployments with Middleware Functions from **all regions** are also impacted because Middleware is deployed globally. Our team is rolling out a fix for this. 

I'll keep this thread updated but in the meantime you can follow the updates here: https://www.vercel-status.com/


Anshuman Bhardwaj (@anshumanb) · 2026-03-02 · ♥ 1

Hi Mike, I understand this concern due to failed builds. I'll pass it along with the feedback once our team has rolled out the fix.


xChar (@aicharacter2024-3700) · 2026-03-02

This is sad


Woody Chau (@woodychau) · 2026-03-02

Same error. 

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

Build Completed in /vercel/output \[3m\]

Deploying outputs...

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


jack879tw (@chiayusu) · 2026-03-02

### Build Failed

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


unav4ila8le (@unav4ila8le) · 2026-03-02

Same problem for us


jack879tw (@chiayusu) · 2026-03-02

same issue for hk


Lucas Monnerat (@lucasmmonnerat) · 2026-03-02 · ♥ 3

Hi Anshuman, quick question: wouldn't it make sense to have a fail open option for middleware? It feels like a considerable risk for the whole pipeline to depend on every single region being 100% healthy at once

Has the team considered allowing deploys to proceed even if one region is down? Would love to see more resilience here


Adrianamlmc1230 (@adrianamlmc1230) · 2026-03-02

can some one tell me which region can use it.


Anshuman Bhardwaj (@anshumanb) · 2026-03-02 · ♥ 2

Hi @lucasmmonnerat, firstly, welcome to the Vercel Community!

I'm happy to see one positive and optimistic post here. Haha. 

I think this incident will definitely raise such question among the infra team and lead to a discussion. I'll pass on this feedback to the team. :handshake:


Anshuman Bhardwaj (@anshumanb) · 2026-03-02

I'm afraid your deployments will fail if they are using a Middleware.


jack879tw (@chiayusu) · 2026-03-02

We would appreciate it if you could share the current progress of the fix.
Also, please let us know the expected timeline for completion.


welytics (@kellerfabian) · 2026-03-02 · ♥ 1

same issue here. in Paris `cdg1`

Besides, I started 3 chats with the AI chat system, but every time I couldn’t create a case due to a missing submit button at the end, maybe that’s just on my client but kind of odd….


Justintemps (@justintemps) · 2026-03-02 · ♥ 1

The Vercel status page only talks about issues affecting dxb1 region but it looks like the outage is more widespread than that (I’m in Europe and having the same issue). Probably good to update the Status page if we can. https://www.vercel-status.com/


Rosana Fern (@rosana) · 2026-03-02 · ♥ 1

I’m experiencing the same issue even if Vercel built went totally fine… **Error: We encountered an internal error. Please try again.**


MG301 (@manishguhe301) · 2026-03-02

Same issue (Error: We encountered an internal error. Please try again.), tried changing region but still did not worked (re-deployment failed)


jack879tw (@chiayusu) · 2026-03-02

Agree, it may cause users to be unclear about the root cause at first.


jack879tw (@chiayusu) · 2026-03-02 · ♥ 1

@anshumanb 

This issue has been pending for some time.
Could you provide a clear update on the current progress and a firm estimated completion date?


Lucas Monnerat (@lucasmmonnerat) · 2026-03-02 · ♥ 4

[quote="anshumanb, post:57, topic:34782"]
Hi @lucasmmonnerat, firstly, welcome to the Vercel Community!

I’m happy to see one positive and optimistic post here. Haha.

I think this incident will definitely raise such question among the infra team and lead to a discussion. I’ll pass on this feedback to the team. :handshake:

[/quote]

Couldn't be any other way haha never really had serious issues with Vercel, but this one escalated pretty quickly. Tbh, I have a big launch planned for tomorrow, so I’m definitely a bit worried about the ETA for a fix

Please keep us posted on any progress or decisions here if you can. The status page feels a bit generic sometimes, and an issue like this requires some contingency planning on our end


Lucas2005gao (@lucas2005gao) · 2026-03-02 · ♥ 1

Same issue here, Function Region - syd1


Allthatityoung 7174 (@allthatityoung-7174) · 2026-03-02 · ♥ 1

Me either, same issue even if Vercel built went totally fine… Error: We encountered an internal error. Please try again.


Alex (@predam) · 2026-03-02 · ♥ 1

wow the incident started 4hrs ago :grinning_face:  any ETA?


corbrink (@corbrink) · 2026-03-02

<!-- My deployment build correctly until the last step where I get the inernal error. I tried other regional centers with the same unfortunate outcome. Any help or feedback from others with similar issues will be appreciated. --

<!-- Current versus Expected behavior -->

<!-- Code, configuration, and steps that reproduce this issue -->

<!-- Project information (URL, framework, environment, project settings) -->


jack879tw (@chiayusu) · 2026-03-02

Hi everyone,

I know several of you have been experiencing issues recently, and since the situation is still ongoing, I just wanted to share something that might help in the meantime.

If you need a temporary workaround to keep things running, you might consider trying Zeabur ([https://zeabur.com](https://zeabur.com)). It’s a Taiwan-based startup that offers fairly straightforward deployment, and it could be an option while waiting for the official fix.

I’m not affiliated with them — just sharing in case it helps anyone who needs a quick alternative.

Hope this helps.


AdaRam (@aramshaw) · 2026-03-02 · ♥ 2

## 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:

```bash
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?


Bob Bass (@robertjbass) · 2026-03-02 · ♥ 1

Same here. I tried changing to other regions in the US and they all have the same error


Haripriya (@haripriya-7531) · 2026-03-02

The status says dubai but I believe its across. 

https://www.vercel-status.com/



Hi Vercel Team,
Kindly do the needful at the earliest. This is huge downtime for builds and release.


Yan (@mockee) · 2026-03-02

Same here. `hkg1` `hnd1`


Mereyabdenbekuly (@mereyabdenbekuly) · 2026-03-02

i think vercel now has problem with registry or smth


Pauline P. Narvas (@pawlean) · 2026-03-02 · ♥ 1

Thank you all for your patience! We'll keep this thread updated when we get more updates.


Mereyabdenbekuly (@mereyabdenbekuly) · 2026-03-02

why u think that?


Rosana Fern (@rosana) · 2026-03-02

I’m in the United Kingdom. My build was: `Running build in Washington, D.C., USA (East) – iad1` and then:

`11:00:25.656 ƒ Proxy (Middleware)`
`11:00:25.656 `
`11:00:25.656 ƒ  (Dynamic)  server-rendered on demand`
`11:00:25.656 `
`11:00:26.155 Traced Next.js server files in: 63.691ms`
`11:00:27.471 Created all serverless functions in: 1.316s`
`11:00:27.491 Collected static files (public/, static/, .next/static): 6.805ms`
`11:00:27.624 Build Completed in /vercel/output [50s]`
`11:00:27.959 Deploying outputs...`
`11:00:51.215 Error: We encountered an internal error. Please try again.`


Vatafumarian 1423 (@vatafumarian-1423) · 2026-03-02

Thank you for helping us ! Patiently waiting :slight_smile:


jack879tw (@chiayusu) · 2026-03-02

Hi @pawlean 

This issue has been ongoing, and we still lack visibility into the actual progress.
Please provide a detailed breakdown of the current status and a firm estimated completion date.


Pauline P. Narvas (@pawlean) · 2026-03-02 · ♥ 2

The best source of truth for information is here:

https://www.vercel-status.com/incidents/nt2llc4k0p41

We'll also update this thread! Thanks for your understanding :slight_smile:


hassan hayat (@hasanhayat) · 2026-03-02

same problem here in **Pakistan**

[Portfolio](https://hassan-hayat.web.app)


Yarnb 2596 (@yarnb-2596) · 2026-03-02

![image|690x140](upload://8ptDE3OiS9ECdwPYQ8cnmabcZjY.png)Running build in Washington, D.C., USA (East) – iad1 (Turbo Build Machine)


xeon007 (@xeon007-cmd) · 2026-03-02

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.


ae (@eduardosilveiradev) · 2026-03-02

Same issue here on iad1 and EU


Ion2088 (@ion2088) · 2026-03-02

same problem, us-east-1


Ridd0 (@ridd0) · 2026-03-02

I hope the issue gets resolved quickly. Need to make a release to [sklls matrix](https://matricsy.com/skills-matrix) app


Paul (@superbien-works) · 2026-03-02

Same problem here on iad1


Timg456 (@timg456) · 2026-03-02

Same issue, but it only happens for particular projects. All my projects are in the same region Washington DC.


Noora (@nqasid) · 2026-03-02

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.


APPIFY (@appify-gr) · 2026-03-02

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.


Lord Noval (@lord-noval) · 2026-03-02

Despite changing regions multiple times, it still fails due to an internal error.


Paul (@superbien-works) · 2026-03-02

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.”


https://www.vercel-status.com/



Hi @pawlean :smiling_face_with_three_hearts:


hassan hayat (@hasanhayat) · 2026-03-02

same problem here in **Pakistan**


[Portfolio](https://hassan-hayat.web.app)

[github](https://github.com/hasanhayat)


Min Hinthar (@min-hinthar) · 2026-03-02

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: https://vercel.com/minhinthars-projects/mandalay-morning-star-delivery-app/7iNwUkufDDmrLtnpTRb1J1B8VBWZ
* Framework: Next.js 16.1.2
* Region: **Washington, D.C., USA (East) - us-east-1 - iad1**


Dev Ravens (@devravens) · 2026-03-02

Same issue here..

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


Trottatigno (@trottaalexandre-3320) · 2026-03-02

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**


Suwethan (@suwe-dev) · 2026-03-02

The same issue is occurring in the India (ap-south-1) Mumbai region as well.


Lord Noval (@lord-noval) · 2026-03-02

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.


Pauline P. Narvas (@pawlean) · 2026-03-02 · ♥ 5

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.

https://www.vercel-status.com/incidents/nt2llc4k0p41


Takatoshi Tenko (@takatoshi-tenko) · 2026-03-02

same issue here.

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


Lucas Monnerat (@lucasmmonnerat) · 2026-03-02 · ♥ 1

Spot on!! Thanks for listening @pawlean. Feeling way more confident for tomorrow hahah cheers!


Pauline P. Narvas (@pawlean) · 2026-03-02 · ♥ 3

Our team is on it! I'll keep you updated :heart_hands:


rolki (@rolki-png) · 2026-03-02

I'm getting a persistent "We encountered an internal error. Please try again." error during the "Deploying outputs..." phase. The build completes successfully every time, but deployment fails.

**Details:**

* **Project:** Next.js 16.1.6 (Turbopack)


* **First fail:** 3 hours ago


* **Regions tried:** pdx1 (Portland), lhr1 (London) - same error in both

**Build log (truncated):**

Build Completed in /vercel/output \[47s\]

Deploying outputs...

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

**What I've tried:**

* Redeploying multiple times


* Switching from bun to npm


* Changing deployment region to lhr1

* Triggering redeployment of previously working builds

The build phase succeeds consistently - static pages generate, serverless functions are created, static files are collected. The error only occurs during "Deploying outputs" which seems to be Vercel infrastructure, not my code.

Is there something in my build output that could trigger this? Or is this a known infrastructure issue? Please note that if I trigger redeployment of previously working builds, they fail with the same error message.


Mereyabdenbekuly (@mereyabdenbekuly) · 2026-03-02

I just renamed `proxy.ts` and the build finished successfully.

**Build Log:**
```bash
Collected static files (public/, static/, .next/static): 116.513ms
Build Completed in /vercel/output [1m]
Deploying outputs…
Deployment completed
Creating build cache…
Created build cache: 19s
Uploading build cache [205.14 MB]
Build cache uploaded: 2.959s
```


corbrink (@corbrink) · 2026-03-02

[quote="lord-noval, post:109, topic:34782"]
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.

[/quote]

You are lucky, my project has no middleware.ts or proxy.ts. Auth is handled by AuthGuard and SubscriptionGuard in the dashboard layout, however I still get the internal error.


Moeinich (@db-9271) · 2026-03-02

I have the same issues. Just getting ‘Error: We encountered an internal error. Please try again.’


Kllakm (@kllakm) · 2026-03-02

you may be using edge functions; I am and thats why mine is failing


jack879tw (@chiayusu) · 2026-03-02

still failed.

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


vpetridis (@vpetridis) · 2026-03-02

same here:
Traced Next.js server files in: 107.893ms

Created all serverless functions in: 2.095s

Collected static files (public/, static/, .next/static): 72.326ms

Build Completed in /vercel/output \[5m\]

Deploying outputs...

Warning: Provided \`memory\` setting in \`vercel.json\` is ignored on Active CPU billing. You can safely remove this setting from your configuration. Learn more: [https://vercel.com/docs/fluid-compute/pricing](https://vercel.com/docs/fluid-compute/pricing)

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


Teemu Sormunen (@teemusormunen-1532) · 2026-03-02

Same here, all projects fail.


Timg456 (@timg456) · 2026-03-02

The issue is fixed for me now.


EugenDD (@lionmause999-3436) · 2026-03-02

any status?


Djtazma (@djtazma) · 2026-03-02 · ♥ 1

Same issue here: 
12:18:33.169 Running build in Washington, D.C., USA (East) – iad1
…

12:20:44.680 Installing required dependencies from api/requirements.txt...
12:20:45.478 Build Completed in /vercel/output \[2m\]
12:20:45.848 Deploying outputs...
12:21:12.215 Error: We encountered an internal error. Please try again.


Lucas Monnerat (@lucasmmonnerat) · 2026-03-02

P.S. Hope you guys aren't using Middleware to deploy this fix hahahah


Justintemps (@justintemps) · 2026-03-02

No joy here, all build still failing for me.


shades2134 (@cmraad1-3208) · 2026-03-02

I changed middleware to proxy and it worked


Tarsharipriya 1505 (@tarsharipriya-1505) · 2026-03-02

Same - Every build is failing for me.


Devix Old (@devix-old) · 2026-03-02

**Same issue here – solved by removing middleware
**
I was hitting the exact same error during production deployment on Vercel:

*Build Completed in /vercel/output
Deploying outputs…
Error: We encountered an internal error. Please try again.
*
The build always succeeded, but deployment failed at the **“Deploying outputs”** step with no useful logs.

In my case, the cause was a **Next.js middleware**. I had a `middleware.ts` using `next/server` and Supabase auth logic (Edge runtime). Even though it worked locally and the build passed, Vercel failed during deploy.

After **removing the middleware entirely**, the project deployed immediately without errors.

Auth was already handled server-side in layouts/pages, so the middleware was redundant.

It seems like **Next.js 15/16 + Vercel can fail at deploy time when Edge middleware is present**, even if the build compiles fine.

Hope this helps others running into the same “internal error” on deploy.


corbrink (@corbrink) · 2026-03-02

you’re right


Clemente (@clementeserrano) · 2026-03-02 · ♥ 1

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


jack879tw (@chiayusu) · 2026-03-02

still failed, any update?


Diogo Felizardo (@diogofelizardo) · 2026-03-02 · ♥ 2

# [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 message:

```

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

```

The build itself completed successfully (all pages generated, no TypeScript or build errors), but the artifact upload step kept failing. I tried multiple times, switched Node.js versions, ran `vercel --debug` — nothing worked.

---

## The cause

There was an active Vercel incident affecting the Dubai region (`dxb1`). The key detail: **this incident impacts any project that uses Middleware or Edge Functions**, regardless of your primary region — because these functions are deployed *globally* by default, including to `dxb1`.

You can check for active incidents at: https://www.vercel-status.com

---

## The fix

Create (or edit) the `vercel.json` file at the root of your project and explicitly define your deployment regions, excluding the problematic one:

```json

{

"regions": ["iad1", "gru1"]

}

```

> **Note:** the Pro plan allows a maximum of 3 regions for serverless functions. Pick the ones closest to your users (`iad1` = Virginia/US, `gru1` = São Paulo/BR, `sfo1` = San Francisco, `cdg1` = Paris, `lhr1` = London, etc.).

After adding this, the deployment went through immediately.

---

Hope this helps someone!


Swarnava Sengupta (@swarnava) · 2026-03-02 · ♥ 4

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 deployment targets. You can redeploy to test this.

If you’re still seeing failures, especially with Edge Function deployments, please switch the function to the Node runtime. With the Node runtime, the function will deploy only to your project’s Functions Regions rather than all Edge regions, which avoids the impacted Dubai Edge region during this incident. https://vercel.com/docs/functions/runtimes/node-js

We are now working on a mitigation for Builds that are using Edge Functions. However the above workaround should unblock you immediately. 

Please let us know if you continue to see errors after applying this change. Happy to help with any questions.


Mykim Aus (@mykim-aus) · 2026-03-02

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.


Said Aitmbarek (@saidaitmbarek) · 2026-03-02

Same on my side, iad1 issue:

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


anupsahu (@anupsahu02-7453) · 2026-03-02

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


Swarnava Sengupta (@swarnava) · 2026-03-02 · ♥ 1

Your deployment is still using edge function which are affected: 

![image|690x49](upload://eogg86i7dH1d0cLLMRKsi871y3q.png)

You can consider swiching to node runtime https://vercel.com/docs/functions/runtimes/node-js until we rollout the fix for edge functions


Swarnava Sengupta (@swarnava) · 2026-03-02 · ♥ 1

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


soon (@ncs-dev-kr) · 2026-03-02

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: true in next.config), will this start incurring Vercel Functions usage charges separately?

Our middleware handles every request (multi-tenant routing, subdomain detection, cookie injection), so the invocation count would be significant. I want to make sure this temporary workaround won’t result in unexpected charges.


Lucas Monnerat (@lucasmmonnerat) · 2026-03-02 · ♥ 1

Nice to see a BR in the loop! Valeu Diogo! Tried it out here but in my case, even with the regions explicitly set, it only worked after I checked for any files using edge runtime. I had two files set to edge, and switching them back to nodejs as @swarnava suggested finally allowed the deploy to bypass incident. If anyone is still stuck, double check your runtimes!


Tukang Ketik (@kangaroohealth) · 2026-03-02 · ♥ 1

No luck after changing the region and runtime.

However, I managed to fix it by simply renaming middleware.ts to proxy.ts and renaming the middleware() func to proxy()


Simeondodov 8631 (@simeondodov-8631) · 2026-03-02 · ♥ 2

I have the same issue for `Running build in Washington, D.C., USA (East) – iad1`

it is not resolved for me after the new update at Mar 02, 2026 - 13:00 UTC


Swarnava Sengupta (@swarnava) · 2026-03-02 · ♥ 1

**There’s no billing difference between Edge and Node.js runtime for middleware.** Both are now part of the unified Vercel Functions infrastructure with consistent pricing based on Active CPU time.

The key points:

* **Edge Middleware has been unified** — It’s now called “Vercel Routing Middleware” and runs on the same Vercel Functions infrastructure regardless of whether you use the Edge or Node.js runtime

* **Same pricing model** — Both runtimes use [Active CPU pricing](https://vercel.com/changelog/lower-pricing-with-active-cpu-pricing-for-fluid-compute), so switching to `nodeMiddleware: true` won’t introduce a different billing structure

* **Pro plan includes 10M Edge Requests** — Your invocations count against this allowance either way

Since you’re already running middleware on every request with the Edge runtime, you’re already being billed under this unified model. Switching to Node.js runtime won’t suddenly add new charges.

You should be safe to make the switch as a workaround for the current [Dubai region incident](https://www.vercel-status.com/) without worrying about unexpected billing surprises. Otherwise, if you can afford to wait, we are working on mitigating Edge function as well.


rolki (@rolki-png) · 2026-03-02

just add the following to your edge functions: (NOTE: you had to add it to each as Next.js doesn't support re-exporting config values from another file…

```
export const runtime = "edge";
// Exclude dxb1 (Dubai) - Vercel outage workaround
export const preferredRegion = [
  "arn1",
  "bom1",
  "cdg1",
  "cle1",
  "cpt1",
  "fra1",
  "gru1",
  "hkg1",
  "hnd1",
  "iad1",
  "icn1",
  "kix1",
  "lhr1",
  "pdx1",
  "sfo1",
  "sin1",
  "syd1",
  "yul1",
];
```


Jawuilp (@jawuilp) · 2026-03-02

Same error, it still continues


Estellechoi (@estellechoi) · 2026-03-02 · ♥ 1

Same issue with the region:
Region: **Washington, D.C., USA (East) - us-east-1 - iad1**


Marian Carnoky (@marian-carnoky) · 2026-03-02 · ♥ 1

AWS Dubai is down, that’s the reason why the deploy is not working.

https://www.reuters.com/world/middle-east/amazon-cloud-unit-flags-issues-bahrain-uae-data-centers-amid-iran-strikes-2026-03-02/


thehumanx (@thehumanx) · 2026-03-02 · ♥ 1

same issue. changing region and redeploying still takes iad1.


Alexis (@ah-6538) · 2026-03-02

This is unacceptable, guys. We are losing a day of work with critical patches we can’t apply to prod. Switching to Node.js has a real impact on latency. from 5ms to 100 ms-200 ms on some clients.


Tone Monte (@tonelopes) · 2026-03-02

The same proble here in Brazil gru1


Mykim Aus (@mykim-aus) · 2026-03-02

Changed to node runtime and also changed the regions, but deployment still fails.
When will it be fixed?


Anton Prokopev (@anto2) · 2026-03-02

still fails with every deployment


Swarnava Sengupta (@swarnava) · 2026-03-02 · ♥ 1

We are investigating this.


Swarnava Sengupta (@swarnava) · 2026-03-02

For anyone who have switched to Node.js middleware in Next.js and still facing issue. Can you confirm if you have `nodeMiddleware` flag enabled? https://vercel.com/changelog/middleware-now-supports-node-js


Mohithkaranth (@mohithkaranth) · 2026-03-02 · ♥ 3

## Status Update

> **Update** - We have rolled out a first mitigation for elevated Build errors. Builds that use Middleware are now excluding the Dubai region (`dxb1`) from their deployment targets as a temporary measure, and should complete successfully again. We are now working on a mitigation for Builds that are using Edge Functions.  
> Mar 02, 2026 - 13:00 UTC

## Problem

My deployment is still failing despite the status update. The build completes successfully, but it fails during the "Deploying outputs" phase.

## Build Log

```bash
21:26:33.967 Running build in Washington, D.C., USA (East) – iad1  
21:26:33.967 Build machine configuration: 2 cores, 8 GB  
21:26:33.978 Cloning GitHub - mohithkaranth/tonehouse-ai-coach (Branch: main, Commit: 76724fb)  
21:26:33.978 Skipping build cache, deployment was triggered without cache.  
21:26:34.629 Cloning completed: 651.000ms  
21:26:36.504 Running “vercel build”  
21:26:37.282 Vercel CLI 50.23.2  
21:26:37.626 Installing dependencies…  
21:26:56.722  
21:26:56.723 added 585 packages in 19s  
21:26:56.723  
21:26:56.723 249 packages are looking for funding  
21:26:56.723 run `npm fund` for details  
21:26:56.799 Detected Next.js version: 16.1.4  
21:26:56.805 Running “npm run build”  
21:26:56.904  
21:26:56.905 > tonehouse-ai-coach@0.1.0 build  
21:26:56.905 > prisma generate && next build  
21:26:56.905  
21:26:57.873 Loaded Prisma config from prisma.config.ts.  
21:26:57.873  
21:26:57.996 Prisma schema loaded from prisma/schema.prisma.  
21:26:58.127  
21:26:58.129 ![:check_mark:](https://emoji.discourse-cdn.com/unicode/check_mark.png?v=15 ":check_mark:") Generated Prisma Client (v7.3.0) to ./node_modules/@prisma/client in 61ms  
21:26:58.129  
21:26:58.129 Start by importing your Prisma Client (See: https://pris.ly/d/importing-client )  
21:26:58.130  
21:26:58.130  
21:26:58.921 Attention: Next.js now collects completely anonymous telemetry regarding usage.  
21:26:58.922 This information is used to shape Next.js’ roadmap and prioritize features.  
21:26:58.922 You can learn more, including how to opt-out if you’d not like to participate in this anonymous program, by visiting the following URL:  
21:26:58.922 https://nextjs.org/telemetry  
21:26:58.922  
21:26:58.933 ▲ Next.js 16.1.4 (Turbopack)  
21:26:58.934  
21:26:58.945 ![:warning:](https://emoji.discourse-cdn.com/unicode/warning.png?v=15 ":warning:") The “middleware” file convention is deprecated. Please use “proxy” instead. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy  
21:26:58.973 Creating an optimized production build …  
21:27:11.421 ✓ Compiled successfully in 11.9s  
21:27:11.430 Running TypeScript …  
21:27:16.591 Collecting page data using 1 worker …  
21:27:17.149 Generating static pages using 1 worker (0/23) …  
21:27:17.325 Generating static pages using 1 worker (5/23)  
21:27:17.459 Generating static pages using 1 worker (11/23)  
21:27:17.521 Generating static pages using 1 worker (17/23)  
21:27:17.526 ✓ Generating static pages using 1 worker (23/23) in 376.2ms  
21:27:17.534 Finalizing page optimization …  
21:27:17.538  
21:27:17.542 Route (app)  
21:27:17.542 ┌ ƒ /  
21:27:17.542 ├ ○ /_not-found  
21:27:17.542 ├ ○ /about  
21:27:17.542 ├ ƒ /api/auth/[…nextauth]  
21:27:17.542 ├ ƒ /api/coach  
21:27:17.542 ├ ƒ /api/debug-lessons  
21:27:17.542 ├ ƒ /api/me  
21:27:17.542 ├ ƒ /api/sheet  
21:27:17.542 ├ ƒ /api/youtube-search  
21:27:17.542 ├ ○ /backing-tracks  
21:27:17.542 ├ ○ /coach  
21:27:17.542 ├ ○ /contact  
21:27:17.543 ├ ○ /ear-training  
21:27:17.543 ├ ○ /finder  
21:27:17.543 ├ ○ /lessons  
21:27:17.543 ├ ƒ /lessons/[lessonId]  
21:27:17.543 ├ ○ /lessons/guitar  
21:27:17.543 ├ ○ /metronome  
21:27:17.543 ├ ○ /privacy  
21:27:17.543 ├ ○ /progressions  
21:27:17.543 ├ ○ /robots.txt  
21:27:17.543 ├ ○ /signin  
21:27:17.543 ├ ○ /sitemap.xml  
21:27:17.543 ├ ○ /start  
21:27:17.543 └ ○ /tuner  
21:27:17.543  
21:27:17.543  
21:27:17.543 ƒ Proxy (Middleware)  
21:27:17.544  
21:27:17.544 ○ (Static) prerendered as static content  
21:27:17.544 ƒ (Dynamic) server-rendered on demand  
21:27:17.544  
21:27:18.299 Traced Next.js server files in: 59.538ms  
21:27:18.552 Created all serverless functions in: 252.871ms  
21:27:18.635 Collected static files (public/, static/, .next/static): 4.154ms  
21:27:18.849 Build Completed in /vercel/output [41s]  
21:27:19.168 Deploying outputs…  
21:27:42.293 Error: We encountered an internal error. Please try again.
```

I get this error when deploying:

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


Justintemps (@justintemps) · 2026-03-02

You mean this?

import type { NextRequest } from “next/server”;

export function middleware(request: NextRequest) {
// Your middleware logic here
}

export const config = {
runtime: “nodejs”, // Specify the runtime environment as Node.js
};


Joris Delorme (@joris-delorme) · 2026-03-02 · ♥ 1

I changed middleware.ts to proxy.ts and everything works fine after 4 failed builds.


Rafaelsales2633 6379 (@rafaelsales2633-6379) · 2026-03-02

I am in brazil and im having the same problem with my next.js application.. this is the shape of my midleware.ts import type { NextRequest } from "next/server";

import { NextResponse } from "next/server";



const COOKIE_KEY = …….

const LOGIN_PATH =……

const STUDENT_DASHBOARD =…..



function **isPrivateRoute**(*path*: string): boolean {

  return (

    *path*.startsWith("/dashboard/estudante") ||

    *path*.startsWith("/dashboard/admin")

  );

}



export function **middleware**(*request*: NextRequest) {

  const token = *request*.cookies.get(COOKIE_KEY);

  const currentPath = *request*.nextUrl.pathname;



  if (!token?.value && isPrivateRoute(currentPath)) {

    const url = new URL(\`${LOGIN_PATH}?callback=${currentPath}\`, *request*.url);

    return NextResponse.redirect(url);

  }



  if (token?.value && currentPath === LOGIN_PATH) {

    return NextResponse.redirect(new URL(STUDENT_DASHBOARD, *request*.url));

  }



  return NextResponse.next();

}



export const config = {

  matcher: \[

    *// Página pública (login)*

    "/",



    *// Rotas do student (área privada)*

    "/dash…",

    *// Rotas do admin (área privada)*

    "/dashb…",

  \],

};


Anas Dib (@anas-4786) · 2026-03-02

same problem is this related to the politics situation and current event or what :slight_smile:


Arnas Puidokas (@arnasp13) · 2026-03-02

Same issue


Vatafumarian 1423 (@vatafumarian-1423) · 2026-03-02 · ♥ 1

Try modifying middleware.ts to proxy.ts and it will work :slight_smile:


Rafaelsales2633 6379 (@rafaelsales2633-6379) · 2026-03-02

<span lang="en">Won't this break my project? Will it continue to function as expected?</span> 

```

```


Justintemps (@justintemps) · 2026-03-02 · ♥ 1

Switching to Node.js middleware fixed it for me.


Kndwajsinfo 1011 (@kndwajsinfo-1011) · 2026-03-02

any ideas when it will be fixed?


Chen Jiaxing (@rcfans) · 2026-03-02

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

```
Traced Next.js server files in: 94.658ms
Created all serverless functions in: 700.549ms
Collected static files (public/, static/, .next/static): 73.428ms
Build Completed in /vercel/output [4m]
Deploying outputs...
Error: We encountered an internal error. Please try again.
```


Stan Degen (@standegen) · 2026-03-02

same issue there :

Function Region

iad1

```
ƒ Proxy (Middleware)

○  (Static)   prerendered as static content

ƒ  (Dynamic)  server-rendered on demand

Traced Next.js server files in: 54.455ms

Created all serverless functions in: 1.187s

Collected static files (public/, static/, .next/static): 13.147ms

Build Completed in /vercel/output [2m]

Deploying outputs...

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


Rodrigo Sclosa (@rodrigo-sclosa) · 2026-03-02 · ♥ 1

Same error here in São Paulo - BR region… Local build is all fine…


Matt Newnham (@mattnewnham-6535) · 2026-03-02

Still broken after changing middleware.ts to proxy.ts.

`Running build in Washington, D.C., USA (East) – iad1`
`…`
`Traced Next.js server files in: 86.723ms`
`Created all serverless functions in: 113.409ms`
`Collected static files (public/, static/, .next/static): 9.057ms`
`Build Completed in /vercel/output [58s]`
`Deploying outputs...`
`Error: We encountered an internal error. Please try again.`


Pavanhasabnis (@pavanhasabnis) · 2026-03-02

Facing same issue since morning with region **iad1** 

```
19:49:09.153 
Traced Next.js server files in: 49.168ms
19:49:09.461 
Created all serverless functions in: 306.335ms
19:49:09.580 
Collected static files (public/, static/, .next/static): 6.49ms
19:49:10.046 
Build Completed in /vercel/output [1m]
19:49:10.440 
Deploying outputs...
19:49:33.693 
Error: We encountered an internal error. Please try again.
```


Shariati (@shariati) · 2026-03-02

Facing the same issue
Function Region: \*\*iad1

**Note**: I am already using **proxy** not middleware

```
Traced Next.js server files in: 164.055ms

Created all serverless functions in: 829.732ms

Collected static files (public/, static/, .next/static): 14.495ms

Build Completed in /vercel/output [2m]

Deploying outputs...

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


Anshuman Bhardwaj (@anshumanb) · 2026-03-02 · ♥ 4

Hi @mattnewnham-6535, welcome to the Vercel Community!
 
The reason for builds breaking isn't the filename but the infrastructure to support Middleware functions. 

Our team is working on a fix and update here once we have rolled out fixes.


Realpro90 (@realpro90) · 2026-03-02

same problem here


Novee Tech (@noveetechcloud-4705) · 2026-03-02

Same issue here. I’m on Washington region (default). No functions.


Federicochavazza (@federicochavazza) · 2026-03-02

Same here from ARG


coredeveloper (@coredeveloper) · 2026-03-02 · ♥ 1

middleware to proxy migration worked for my nodejs project


Abdurrahman Harits Ghiffary (@abdurrahmanharitshg) · 2026-03-02

Same here from Indonesia.
Function region: iad1


N (@office-9764) · 2026-03-02 · ♥ 1

Same here, fra1 region (EU). Any workaround?


Anshuman Bhardwaj (@anshumanb) · 2026-03-02

Thanks for sharing this. Please upvote this post to get more eyeballs.


nthoftype (@nthoftype) · 2026-03-02

Same for me


Mihai C. (@jobfulio321) · 2026-03-02

same problem, EU area


Ozzie Code Alt (@ozzie-code-alt) · 2026-03-02

for me running npx @next/codemod@canary middleware-to-proxy .  seems to work


Shekhu10 (@shekhu10) · 2026-03-02

There was this 1 build that was success. After that I did some changes in the code, and then deployed again. The build is failing but passing on local system. I tried to debug this, but nothing helped. To test that is it because of me or not, I re-deployed the build that was earlier successful on vercel, but now that build is also failing. Not, sure why this is happening. Any suggestion on what i can try to debug this ? this is what i am getting in error. Build is success, but deploying the build its failing.

![image|690x104](upload://trdOw9IKrJa2ta4GEM5HUWcSkOG.jpeg)


nthoftype (@nthoftype) · 2026-03-02 · ♥ 1

I am already using proxy.ts and this is failing for me, so not sure that is a direct fix


Matheen (@matheen636-2025) · 2026-03-02

same for me


Letscagefdn (@letscagefdn) · 2026-03-02

I was working on https://proxybase.xyz/openclaw part and tried to deploy my feature branch, but ended up with this error.


nthoftype (@nthoftype) · 2026-03-02

My latest Production build is fine when I redeploy it, a new code change is failing to deploy to Preview though.


Nidiannurc 7437 (@nidiannurc-7437) · 2026-03-02

Having the same issue here.

Temporary fix it by rename into middleware.disabled.ts


Spero (@speroseq) · 2026-03-02

I have the same error as well. Running convex with next.js


jonnyapples (@mlgsniperkingpro-599) · 2026-03-02

same issue for me in the UK,


Shivam Selam (@shivamselam) · 2026-03-02

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


mateusemth (@mateusemths-projects) · 2026-03-02

same issue here


Angwan (@wesleykoros-9253) · 2026-03-02

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|408x258](upload://dhu5NMyvahY284HwNNwn5nc205Q.png)


Onexabhishek (@onexabhishek) · 2026-03-02

I’m also expriencing same issue.


coredeveloper (@coredeveloper) · 2026-03-02

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


Theodore (@theodoreriant) · 2026-03-02

Working for me in setting region to france (cdg1)


Zabsalahid (@zabsalahid) · 2026-03-02 · ♥ 1

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


mcandan (@mustafacandan) · 2026-03-02

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


Angwan (@wesleykoros-9253) · 2026-03-02

It’s working well now!:slightly_smiling_face:


Matt Newnham (@mattnewnham-6535) · 2026-03-02 · ♥ 1

Thanks, my deploy is working now.


lightnet (@jnuenlist-8649) · 2026-03-02 · ♥ 1

Thanks! Build is working again!


Matheen (@matheen636-2025) · 2026-03-02 · ♥ 1

It's working 😭


Pauline P. Narvas (@pawlean) · 2026-03-02 · ♥ 1

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.


https://www.vercel-status.com/incidents/20v5r3njkcwc


aweful1 (@aweful1) · 2026-03-02

I’m experiencing the same issue and I’m not in Dubai. Is my issue related or not?


Vikramkaldoke (@vikramkaldoke) · 2026-03-02

The issue has been fixed. I’m now able to deploy the app successfully.


aweful1 (@aweful1) · 2026-03-02

I think it’s fixed in some places. It works for me now.


Zoomlookllc (@zoomlookllc) · 2026-03-02

I am also having this issue. 
What I do not understand is how they could design a platform to be so fragile. 
And now that War has broken out, this kind of thing is going to make Vercel a less attractive solution. 
Anyone have any alternatives to Vercel in production?


mcandan (@mustafacandan) · 2026-03-02 · ♥ 1

:backhand_index_pointing_right:  Upgrading NextJS to latest  solved my problem