Hey @garymast, welcome to the community!

Thanks for the detailed information, have passed this onto the CLI team to check out.

Same problems on my side. Seems that 50.28.0 broke something with the middleware. My multi-tenants app is not redirecting the users to their own sub-domains.

Same issue here. Next.js 15.5.12 with next-intl middleware (localePrefix: ‘as-needed’). All new deployments since March 6 ignore middleware.ts — unprefixed routes 404 while /en/* works. Vercel AI support confirmed NEXT_ENABLE_ADAPTER is being injected by the platform, causing Next.js 16 proxy.ts behavior on a Next.js 15 project. Production site is down. Vercel CLI 50.28.0, Node 24.x.

Same issue, but on 15.5.9 I’m getting this error from clerk

1
Clerk: auth() was called but Clerk can’t detect usage of clerkMiddleware(). Please ensure the following:
2

3
Your Middleware exists at ./middleware.(ts|js)
4

5
clerkMiddleware() is used in your Next.js Middleware.
6

7
Your Middleware matcher is configured to match this route or page.
8

9
If you are using the src directory, make sure the Middleware file is inside of it.
10

11
For more details, see https://clerk.com/err/auth-middleware

Thanks all, raising with relevant teams!

same here!

I just quickly migrated out of vercel, all production was down.

I will monitor this, move back when it’s fixed

same here. all rewrites in middlewear not working

Thank you everyone for sharing, the team is actively looking into this - will post when I have further updates.

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 related or not…

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

Environment

• Framework: Next.js 15.5.9 (App Router)
• Deployment: Vercel (Production & Preview)
• Dependencies: @clerk/nextjs 6.36.5, but issue persists even with minimal middleware
• Local dev: Works fine with Edge Runtime (next dev)

Configuration

1
// middleware.ts (Edge - NOT working on Vercel)
2
import { clerkMiddleware } from '@clerk/nextjs/server'
3
export default clerkMiddleware()
4
export const config = {
5
  matcher: ['/((?!_next/static|_next/image|favicon.ico).*)'],
6
}

1
// middleware.ts (Node.js - WORKING on Vercel)
2
export const runtime = 'nodejs' // Adding this fixes it
3
import { clerkMiddleware } from '@clerk/nextjs/server'
4
export default clerkMiddleware()

Observed Behavior

• With default Edge Runtime: Middleware never executes (no logs in Vercel Function Logs).
• Error: auth() throws:

"can’t detect usage of clerkMiddleware()" (because the middleware chain is broken).

• With runtime = 'nodejs': Middleware executes correctly on every matched request.

Steps Tried

1. Simplified matcher to catch-all patterns
2. Cleared Vercel build cache & redeployed
3. Upgraded to latest Next.js and @clerk/nextjs versions
4. Verified file location (src/middleware.ts at project root level)

Expected Behavior

Edge Runtime should work as documented for Middleware, or documentation should clarify when Node.js runtime is required.

Additional Context

Issue appears specific to Vercel build environment; local next dev works fine with Edge Runtime.

Team is actively investigating, status page here: https://www.vercel-status.com/incidents/963t8qqbk77b

Edit: incident resolved.

Same here.

The issue is not about CLI 50.28.0.

This deployment work fine, pls check the log.

1
Running build in Washington, D.C., USA (East) – iad1
2
Build machine configuration: 2 cores, 8 GB
3
Cloning github.com/RCFans/StrategyLogic (Branch: main, Commit: 8a6fc5f)
4
Cloning completed: 1.806s
5
Restored build cache from previous deployment (DQrH1rmBSHDcQhpyaYjNHWWAEPRd)
6
Running "vercel build"
7
Vercel CLI 50.28.0
8
Detected `pnpm-lock.yaml` 9 which may be generated by pnpm@9.x or pnpm@10.x
9
Using pnpm@9.x based on project creation date

deployment link is below, if you can visit.

https://vercel.com/strategylogic/platform/4kzdVAaqeMz4cs7tWMD414fsGnAh

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 middleware invocation whatsoever.

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 search to find this community thread.

Welcome to the community, feel free to make posts in the future so you don't have to debug alone But yeah, heard. Appreciate the feedback, Dalyan!

Rollback has resolved the issue for now.

We recommend redeploying, more to follow.

Appreciate your patience everyone!

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

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

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.

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:

1
skipTrailingSlashRedirect: true,
2
trailingSlash: false,
3
reactCompiler: true,
4
cacheComponents: true

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

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! 🙏

Hey @kieranmcguire, welcome to the community!

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

Hey @tim-9762, welcome to the community

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?

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