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

[Help](/c/help/9)

# Vercel deployment returns 502 ROUTER_CANNOT_MATCH error when status is READY

25 views · 1 like · 3 posts


Keithnickas (@keithnickas) · 2026-03-12 · ♥ 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
```bash
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
- **Project:** `keith-nickas-dot-com`
- **Account Type:** Hobby
- **Function Region:** `iad1`
- **Failing Deployment URL:** [https://keith-nickas-dot-b3r41ye2k-keithnickas-projects.vercel.app](https://keith-nickas-dot-b3r41ye2k-keithnickas-projects.vercel.app)
- **Deployment ID:** `dpl_2bVthrHNtREe9cGdWS5QcdLN5Umg`
- **Commit Hash:** `a51e5e27bce09071e4c567b0e932bca7f143e778`
- **Working Production URL:** [https://keith-nickas-dot-rhcn95wvh-keithnickas-projects.vercel.app/](https://keith-nickas-dot-rhcn95wvh-keithnickas-projects.vercel.app/)


Jacob Paris (@jacobparis) · 2026-03-12

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


Keithnickas (@keithnickas) · 2026-03-12

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.