Dynamic API routes returned 404 errors for some deployments
Components
Regions
Dynamic API routes returned 404 errors for some deployments Vercel hosts deployments, serverless functions, edge middleware, and the dashboard used to ship frontend and full-stack apps.
resolved · 14 Aug 2026, 13:08 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.
5
Related incidents
0m
This incident
6h 28m
Avg. resolution time
Faster
vs. average
If your product depends on Vercel, elevated errors during this window often come from upstream, not from your latest commit.
Open official status pageBe the first to know when we launch Pro alerts. No spam — only product updates.
Interested in
This outage lasted 0m. Join the waitlist to get alerted next time.
Join the waitlist for Pro alerts — we'll notify you at launch.