Problem My Next.js 14.2.35 middleware stopped executing on production. After extensive debugging, I traced it to a regression in Vercel CLI 50.28.0. Evidence I have two deployments of the exact same commit (d14ff83): Original build (Vercel CLI 50.27.1) → middleware works perfectly Fresh rebuild (V…

Team is actively investigating, status page here: Vercel Status - Elevated Errors on Middleware Invocations Edit: incident resolved.

looks like I have this issue too.

I am not using the Vercel CLI… just pushing to GitHub… and observe that my middleware seems out of order in the recent deployments… The Vercel Help bot found that between my working deployments (yesterday) and today’s an env variable was added: VERCEL_SKIP_EDGE_FUNCTION_ENDPOINT No idea if it’s re…

Next.js Middleware fails on Edge Runtime but works with runtime: 'nodejs' on Vercel. I’m experiencing an issue where Next.js Middleware (middleware.ts) does not execute at all when deployed to Vercel using the default Edge Runtime. However, adding export const runtime = 'nodejs' makes it work corre…

The issue is not about CLI 50.28.0. This deployment work fine, pls check the log. Running build in Washington, D.C., USA (East) – iad1 Build machine configuration: 2 cores, 8 GB Cloning github.com/RCFans/StrategyLogic (Branch: main, Commit: 8a6fc5f) Cloning completed: 1.806s Restored build cache f…

Same here, this is is crashing our site. I was able to promote a previous deployment from a few hours ago and that has at least brought the site back up. Strangely, that deployment also use CLI 50.28.0 about 5 hours ago and succeeded. Everything after that suffered the issue discussed here - no mid…

[image] Dalyan Parker: Also for future reference, I checked the Vercel status page frequently over the past hour and there was no mention of this - would have been nice to at least have some mention of an investigation instead of me debugging alone, diagnosing the issue, then doing a general sea…

Rollback has resolved the issue for now.

I hear you, it’s under the same issues that’s affecting middleware, as mentioned in the status page here

Next.js middleware fails to execute after Vercel CLI 50.28.0 build regression

Help

pawlean (Pauline P. Narvas) March 6, 2026, 5:01pm 27

We recommend redeploying, more to follow.

Appreciate your patience everyone!

1 Like

Topic		Replies	Views
Next.js middleware fails on Edge Runtime but works with Node.js runtime on Vercel Help nextjs , builds , edge-request	3	63	March 6, 2026
Vercel deployment failure with internal error during deploying outputs phase Help nextjs , builds , dashboard	196	5663	March 16, 2026
Next.js 16 middleware returns 404 sitewide on Vercel Help nextjs	6	16	April 24, 2026
middlewareHandler is not a function Help nextjs	20	358	September 10, 2025
Vercel 500 error with MIDDLEWARE_INVOCATION_FAILED on production deployment v0 nextjs , edge-request	1	13	April 8, 2026

Next.js middleware fails to execute after Vercel CLI 50.28.0 build regression

Related topics