Vercel deployment returns 502 ROUTER_CANNOT_MATCH error when status is READY

Help
, ,
1

Any assistance with the following would be greatly appreciated.

Summary

Deployments complete successfully (build logs show no errors, all static pages generated, serverless functions created), but when visiting the deployment URL, I receive a 502 BAD_GATEWAY error with code ROUTER_CANNOT_MATCH. The deployment appears as READY in the Vercel system but is not actually serving traffic.

Error Message

502: BAD_GATEWAY
Code: ROUTER_CANNOT_MATCH
ID: sfo1::bxmb5-1773283529392-3eb78a179784
"This is an error with the platform itself, not the application."

Timeframe

  • First attempt: 2026-03-12 ~16:32 UTC
  • Second attempt: 2026-03-12 ~17:00 UTC

Troubleshooting Attempted

  1. Redeployed without cache.
  2. Set VERCEL_FORCE_NO_BUILD_CACHE=1.
  3. Build completes cleanly with 21 static pages and serverless functions generated.
  4. Deployment stalls/fails after “Deploying outputs…” with no completion confirmation in UI (though API shows READY status).

Observed Behavior

The Vercel API shows the deployment as READY with readySubstate: STAGED, but the deployment URL returns a platform-level routing error. This appears to be an infrastructure issue rather than an application problem.

Details

1 Like
5

Thanks for the detailed report, I can’t find an immediate cause so I’m escalating internally. One thing I notice is that between the working and the failed deployments you started using a newer Vercel CLI version, can you try adding this to your environment variables and redeploying to see if that’s the culprit?

This will pin it to a version of the CLI you have successfully deployed from recently

VERCEL_CLI_VERSION=vercel@50.11.0
6

Hi Jacob,

Thanks for the suggestion, sadly it didn’t work. I received a different error stating that the specific CLI version couldn’t be found.