Vercel outage, 14 August 2026

Dynamic API routes returned 404 errors for some deployments

Started
Resolved
14 Aug 2026, 13:08 UTC
Impact
Not stated
Affected
Builds

Last update from Vercel

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 impac...

14 Aug 2026, 13:08 UTC

Read the full incident on the official Vercel status page

Is Vercel down now?

This page is the record of one past incident. For the live status, see Is Vercel down right now? - it reads the official status page every 2 minutes.

Other Vercel incidents

  1. Increased build and deployment failures

  2. Delays in Drains, Observability, and Workflow in Washington (iad1)

  3. Vercel Auth login failures for pages with Deployment Protection enabled

  4. Elevated Sandbox error rates in Paris (cdg1)

  5. Build failures and 500 errors for functions using Edge runtime

  6. Deployment stuck in initializing state

  7. Elevated Errors Triggering Deployments

  8. Elevated Vercel KMS and Connect Errors

All recorded Vercel incidents