Provider
VercelIncident detail
Dynamic API routes returned 404 errors for some deployments
Resolved incidentMinor1 affected service
Timeline window
to
Outage alerts
Get alerted the next time Vercel breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Vercel posted, oldest to newest, exactly as it appeared on their official status page.
Resolved
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.
Keep exploring
More from Vercel
Neighboring incidents on Vercel's timeline and the rest of their record on OutageDeck.