Vercel Outage History

Vercel experienced elevated build errors that prevented new deployments from being created successfully during the build phase. The incident affected the Builds component while existing deployments and live traffic remained unaffected. The issue was resolved after 43 minutes with a fix implementation and monitoring period.

Vercel experienced elevated queue message latency and increased message retry times in the iad1 region, along with longer sleep times and more step retries in Workflow functionality. The issue affected message processing performance and workflow execution reliability for 31 minutes. The problem was identified and resolved through an implemented fix that restored normal service performance.

Vercel experienced elevated errors affecting deployments with Edge Middleware that were created between 11:20 UTC and 15:14 UTC on March 6th, 2026. The issue caused middleware invocation failures for affected deployments, while deployments created outside this timeframe and those using Node runtime middleware remained unaffected. The incident was resolved after 6.2 hours with a fix applied by Vercel, though users were recommended to redeploy affected applications to ensure full recovery.

Vercel experienced a 4-hour incident where dashboard pages using Observability data had significant delays loading and ingesting new data. The affected services included Observability, Speed Insights, Web Analytics, Usage, Firewall, and Activity pages. A fix was implemented and the incident was fully resolved with normal data loading and ingestion restored.

Vercel's Dubai region (dxb1) became unavailable due to operational issues, causing traffic to be automatically re-routed to the Mumbai region (bom1) and preventing new function deployments in Dubai. Users with existing deployments in dxb1 experienced elevated function invocation errors and were advised to redeploy to the nearest region. The incident lasted approximately 14 days before being resolved, with deployments using multiple regions or failover configurations remaining unaffected throughout the outage.

Vercel experienced degraded Logs and Traces collection in the Dubai region (dxb1) for 5.3 hours. The service mitigated impact by rerouting Dubai edge traffic to the nearest region (Mumbai/bom1). The incident was fully resolved after implementing a fix for the logging infrastructure issues.

Vercel experienced deployment and function invocation failures starting at 5:00 AM UTC, initially affecting the Dubai region (dxb1) but expanding to impact deployments with Middleware Functions globally since these are deployed across all regions. The incident affected builds, serverless functions, edge functions, and edge middleware for 9.3 hours. The issue was resolved by temporarily excluding the Dubai region from deployment targets and rerouting Dubai edge traffic to the nearest region (Mumbai).

Vercel experienced deployment failures for customers using Static IPs when deploying functions to the Dubai region (dxb1), affecting the Builds component for 3.1 hours. Customers could work around the issue by temporarily removing the Dubai region from their Static IPs configuration, while deployments to other regions remained unaffected. The issue was resolved with an implemented fix that restored normal deployment functionality.

Vercel experienced delays loading Observability, Analytics, and Speed Insights data on their dashboard for 44 minutes. The incident affected the Dashboard, Speed Insights, and Web Analytics components. The issue was resolved and all services returned to normal operation.