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

Help
, ,
28

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

1 Like
29

Spent most of my day debugging issues related to critical redirects defined in the middleware (and project experiencing severe downtime) While periodically checking Vercel Status page.. It would be REALY helpful to proactively report and monitor such kind of issues… 4+ hours delay in status update is unacceptable for such critical problem

30

We hit the same issue. Two changes fixed it immediately:

  1. Set runtime: "nodejs" in the middleware config (instead of Edge Runtime)

  2. Pin Node.js to 22.x via engines.node in package.json

No rollback needed, new deployments work fine with these changes.

1 Like
31

I spent the last two days debugging as well, even tried rewriting a huge part of our app, but had no luck so far. We’re not even using a middleware on the app; however, some pages are unusable now (still) because they keep re-rendering and reloading. We rolled back to a working deployment from Mar 4, 2026, 4:39:11 PM UTC.
All following deployments (even of the same codebase). The older deployments don’t show any Vercel CLI info. So I can’t confirm whether Vercel CLI is working.

I see the middleware incident marked as resolved. Is the team still investigating these kind of issues?

We use Next.js 16.1.6 with:

skipTrailingSlashRedirect: true,
trailingSlash: false,
reactCompiler: true,
cacheComponents: true
32

@mayven there’s a mistake in the email sent to customers about this incident. The email body implies that the issue spanned the period between 11:20 UTC to 18:34 UTC on March 6, 2026, but the link to the filtered list of affected deployments spans 11:20 UTC on March 5 to 18:34 UTC on March 6. Not sure which is correct.

33

Thank you for the feedback, I hear you.

From the first post in this community thread it was raised internally within 30 minutes, and escalated as an incident as we saw folks in this thread sharing they were also having issues. We then had the first status page up within that hour, whilst the team were investigating.

Myself and @pawlean were actively monitoring the situation as the team were working hard on finding the root cause and fixing, and we relayed relevant information here as soon as we knew more.

I appreciate it’s frustrating when these things happen, but I can assure you we all want to get accurate, up to date information out to everyone when it does happen, and we are always wanting to improve.

We appreciate your understanding and patience. And thanks to our community, the issue was on our radar sooner! :folded_hands:

34

Hey @kieranmcguire, welcome to the community!

Thanks for flagging, I’ve passed this to the team.

1 Like
35

Hey @tim-9762, welcome to the community :slight_smile:

Deployments without middleware shouldn’t have been affected by this, so this could be a different issue, hard to say without more information.

Can you open a new post in Help with more details on the issue?

36

Hey Tim,

Im on the team supporting Helius from the Vercel Side.

Shoot me an email and I can see how we can help!

Matthew.valitski@vercel.com

2 Likes