WhatBrokeToday
Today's Trends
mediumArchivedVercelvNext.js 16.2 or earlier

Vercel: Dynamic API routes returned 404 errors for some deployments

  1. Investigating(done)
  2. Trending(skipped)
  3. Workaround available(skipped)
  4. Resolved(done)
  5. Archived

Executive summary

Between August 12 and August 13, 2026, some Vercel deployments returned 404 errors for dynamic API routes. The issue affected deployments built with Next.js 16.2 or earlier utilizing the Pages Router with internationalization and dynamic API routes.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 StatusShow
  1. [1]
    Status First report
    Dynamic API routes returned 404 errors for some deployments(opens official status page in a new tab)

    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…

    by vercel status

Timeline

  1. First report on status page

    Dynamic API routes returned 404 errors for some deployments

    Source
  2. Official statement

    Resolved: This incident has been resolved.

    Source
  3. Status changed

    Status changed: new → archived (resolved more than 14 days ago).