Incident History

This incident has been resolved.

This incident has been resolved.

This incident has been resolved.

The system is operating normally and fully recovered.

From 10:57pm to 11:43pm UTC, a percentage of Workflows streams calls failed. Workflow steps that had a failing stream call would retry, and if the step hit the max retries, the workflow failed. Workflow streams have recovered and are working correctly now.

Services have recovered. We are still working to ingest missing observability data during this period.

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.

This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.

Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience.

Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported.

We have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future.

We know how much you rely on this data, and we sincerely apologize for the disruption.