Vercel Outage History

Vercel experienced elevated queue times for deployments on the Hobby plan, affecting the Builds component for 51 minutes. The issue caused delays in deployment processing, with queued deployments backing up during the incident. A fix was rolled out and deployments returned to normal processing times, with the incident fully resolved.

Vercel experienced an incident where build logs were stuck in a loading state, affecting users' ability to view deployment build information in the iad1 region. The issue impacted the Builds and Logs components for 1.3 hours. Vercel identified the root cause, implemented a workaround for new builds, and resolved the incident, advising users to redeploy if they still couldn't see build logs for specific deployments.

Vercel experienced elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments for 4.5 hours, with the Builds component impacted. Deployments created between 16:10 to 19:12 UTC were particularly affected, and customers were advised to redeploy or perform instant rollbacks to resolve issues. The incident was resolved after Vercel identified the root cause and rolled out a fix.

Vercel Functions running Node.js 20 in the cle1 and dub1 regions experienced elevated SIGSEGV termination errors for 4.8 hours. The issue affected Serverless Functions specifically in those two regions, while other regions remained unaffected. Vercel identified the root cause, deployed a fix, and resolved the incident with recommendations for users to redeploy affected functions or upgrade to Node.js 22 or 24.

Vercel experienced elevated errors and latency issues affecting webhook delivery and deployments that use integrations, impacting the Builds component. The service disruption lasted 1.5 hours before a fix was implemented and normal operations were restored.

Vercel experienced elevated errors when creating new deployments, with users encountering "invalid request" errors during the build process. Existing deployments and live traffic remained unaffected throughout the incident. The issue was resolved after 14 minutes with a fix applied, and users were advised to redeploy any failed deployments.

Vercel experienced elevated errors and timeouts in their Support Center, preventing customers from successfully submitting support cases. The incident affected the support ticket creation system for 20 minutes. The issue was resolved after implementing a fix and confirming normal functionality.

Vercel experienced elevated error rates on their Dashboard, affecting the API, Builds, and Dashboard components for 1 hour. Existing deployments and live traffic remained unaffected during the incident. The issue was resolved after implementing a fix and monitoring the results.

Vercel experienced elevated error rates when users attempted to load the Deployment Overview section of their Dashboard for 1.2 hours. The issue only affected the Dashboard interface and did not impact existing deployments or live traffic. A fix was implemented and the service was restored to normal operation.

Vercel experienced elevated errors when creating new Functions in the Singapore (sin1) region, affecting the Builds component for 1.3 hours. To prevent deployment failures, Vercel temporarily disabled provisioning of new Functions in this region while existing deployments and live traffic remained unaffected. The issue was resolved after implementing a fix and monitoring the results.