Dynamic API routes returned 404 errors for some deployments

What to do

• Check whether you use Vercel Builds. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-08-14 13:08 UTC and 2026-08-14 13:08 UTC may need a replay.

• Subscribe to Vercel's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vercel 1

1. resolvedAug 14, 2026, 1:08 PM UTC

   This incident has been resolved. Between August 12, 17:12 UTC and August 13, 20:33 UTC, some Vercel deployments could return 404 errors from dynamic API routes. Deployments built on Vercel during this period were affected only if they met all three conditions: used Next.js 16.2 or earlier, used the Pages Router with internationalization (i18n configured in next.config.js), and used dynamic API routes, such as pages/api/[slug].ts or pages/api/[...path].ts. Deployments built outside Vercel (with vercel deploy --prebuilt) were not affected, and existing deployments not rebuilt during this period were not affected. If your project matches the conditions above and you deployed during the impact window, redeploy your project. Affected deployments are not fixed automatically; a new deployment is required to restore the affected routes.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.