Vercel / Next.js threat watch

Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is recovering, Vercel Queues backlogs are being processed, and Vercel Workflows are unblocked.

Between 18:36 and 19:04 UTC, issuing SSL certificates was delayed for new domains. These certificates have now been issued. Certificate renewals were not affected.

We've identified an issue where some customers may experience delays in builds starting and/or builds stuck in an initializing state. We are applying a fix and will provide additional updates as they become available.

Some Vercel functions that run in the IAD1 region are experiencing elevated invocation failures. We are investigating the issue and will share more information as it becomes available.

We are investigating an issue affecting new deployments that are stuck in the provisioning state. We will share more information as it becomes available.

We are experiencing increased error rates with Workflows running on Vercel. We have identified the issue and are implementing a fix.

We've identified an issue where various services in the Vercel dashboard, API, and CLI are failing to load data. These services include Observability, Speed Insights, Alerts, Usage, Web Analytics, Firewall, and CDN observability. Broadly, areas backed by analytical data are affected. We have identified the issue and are working on a fix. Production applications running on Vercel are not impacted.

Between 21:45–21:52 UTC, some users may have experienced request failures in ICN1. The issue has been identified, a fix has been applied, and the issue has been resolved.

Between May 1, 11:01 am – May 1, 11:09 am UTC, users may have seen increased function invocation errors for traffic originated near the ICN1 Vercel CDN region. Requests to static assets/cached content were unaffected this time. We have reverted the change that caused the issue to mitigate this.

We are currently investigating this issue.

We are currently investigating this issue.

We are investigating an issue causing elevated error rates across domains operations, including renewals, nameserver changes, search, and checkout. We will provide additional updates as they become available.

We're investigating reports of unexpected errors when trying to create and deploy new projects from templates. We will provide additional updates as they become available.

We have identified an issue resulting in delayed and/or missing usage data for observability events between 9:00 - 10:30 UTC and 16:50 - 19:30 UTC. The issue has been identified and resolved. Usage data for observability events for the affected time buckets have been recovered. The affected windows will continue to show missing data - the recovered data will show up as additional usage at recovery timestamps. The total usage count for the period is accurate and no additional actions are required for customers at this time.

We've identified an issue causing missing observability data for compute products between April 22, 2026 23:00 UTC and April 23, 2026 05:00 UTC affecting a subset of customers, resulting in missing or incomplete metrics in Observability dashboard during this period. All underlying compute services - including Vercel Functions, Workflows, and Cron Jobs - continued to operate normally. Logs were not affected and remain fully available.

We're investigating reports of customers being unable to checkout with domains purchases. We'll provide additional updates as they become available.

We're investigating an issue causing delays in loading logs. We will provide additional updates as they become available.

We are currently investigating this issue.

We have identified an issue causing elevated error rates on the Vercel Dashboard and API endpoints. Some users may experience an issue creating new deployments, but existing deployments are not impacted. We will share more updates as they become available.

We are currently investigating runtime logs not loading properly in the dashboard. We will share more updates as soon as we have more information.