Provider incident title: “Dynamic API routes returned 404 errors for some deployments”
Started
Friday, August 14, 2026
01:08 PM UTC
Duration
< 1 minute
total
Resolved
01:08 PM UTC
Aug 14, 2026
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.
Get alerted next time
Install Tickerr MCP — your agent auto-reports & routes around outages
When v0 goes down again, your agent reports anonymously and instantly gets a fallback recommendation from the swarm.
v0 is back online
View current status and uptime history
v0 30-day uptime: 100% based on Tickerr's independent monitoring checks.
This incident was sourced from v0's official Atlassian Statuspage. Tickerr ingests updates every 10 minutes to surface incidents as they are posted by the provider.
This incident lasted < 1 minute.
Tickerr monitors 90+ AI tools independently. View live v0 status or all AI tool status.
Get alerted next time v0 goes down
Tickerr monitors 90+ AI tools. We'll email you when an incident starts or resolves.
Weekly AI pricing & uptime digest
Price drops, new model releases, and incident summaries - every Monday. Free.
Also on Tickerr