rewindex

CompaniesVercelIncidents

Vercel: Dynamic API routes returned 404 errors for some deployments

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestspg.io (opens in new tab)

Affected components: Build & Deploy - BuildsBuilds

Timeline of updates

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

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Vercel, started 2026-08-14 13:08 UTC, resolved after 0 min, 1 update(s).

Title
Dynamic API routes returned 404 errors for some deployments
Vendor
Vercel
Date
URL
https://rewindex.com/company/vercel/incidents/ysczd6rxyl7z

Vercel profileRecent Vercel incidentsAll outages on August 14, 2026Vercel in August 2026MarkdownJSON