Vercel

Apr 7, 18:56 UTC Resolved - This incident has been resolved. Apr 7, 18:27 UTC Update - A fix has been rolled out, and we are monitoring the results. Queued deployments are being processed and new deployments are building normally now. Apr 7, 18:06 UTC Identified - We have identified an issue causing elevated queue times for deployments on the Hobby plan. We are investigating a fix and will share more updates as soon as we have more information.

Apr 7, 08:37 UTC Resolved - The incident has been resolved. If you don't see build logs for a specific deployment, please redeploy. Apr 7, 08:29 UTC Monitoring - We identified the cause of build logs stuck in the loading state affecting iad1 and are working around the issue for new builds. Please redeploy to your build to view build logs. Apr 7, 07:19 UTC Investigating - We are investigating reports of build logs stuck in loading state.

Apr 2, 23:09 UTC Resolved - This incident has been resolved. Apr 2, 20:02 UTC Monitoring - The fix has been rolled out and we are monitoring the results. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue. Apr 2, 19:26 UTC Identified - We have identified the issue and are rolling out a fix. Deployments created between 16:10 to 19:12 UTC may be affected. If you are still seeing issues, we recommend redeploying or performing an instant ro...

Apr 2, 18:53 UTC Resolved - This incident has been resolved. Apr 2, 18:09 UTC Monitoring - The root cause has been identified, a fix has been rolled out, and we are actively monitoring. Newly deployed Vercel Functions on Node.js 20 in cle1 and dub1 no longer terminate with SIGSEGV. We recommend redeploying affected Vercel Functions if you are still seeing issues. Apr 2, 16:13 UTC Update - We are continuing to investigate increased rates of Vercel Functions running on Node.js 20 terminating wi...

Apr 1, 22:17 UTC Resolved - This incident has been resolved. Apr 1, 21:57 UTC Monitoring - A fix has been implemented and we are monitoring the results. Webhook events are being delivered normally, and deployments with integrations are building successfully. Apr 1, 20:48 UTC Identified - We have identified an issue causing elevated latency and errors with delivering webhooks and creating deployments that use integrations. We are working on a fix for this issue and will provide further updates...

Mar 31, 21:23 UTC Resolved - This incident has been resolved. Mar 31, 21:17 UTC Monitoring - A fix has been applied for an issue where deployments were erroring with "invalid request" and we are monitoring the results. We recommend redeploying any failed deployments. Mar 31, 21:11 UTC Investigating - We are investigating reports of elevated errors when creating deployments. Existing deployments and live traffic are unaffected. We will provide updates as they become available.

Mar 31, 13:29 UTC Resolved - This incident has been resolved. Mar 31, 13:16 UTC Update - Support case submission has been confirmed to be functioning normally. We will share updates as they become available. Mar 31, 13:16 UTC Monitoring - A fix has been implemented and we are monitoring the results. We will share updates as they become available. Mar 31, 13:10 UTC Investigating - We are currently investigating reports of elevated errors when submitting support cases. Some customers may experienc...

Mar 25, 17:31 UTC Resolved - This incident has been resolved. Mar 25, 16:41 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 25, 16:32 UTC Investigating - We are currently investigating reports of elevated error rates on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.

Mar 24, 16:31 UTC Resolved - This incident has been resolved. Mar 24, 16:14 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 24, 15:19 UTC Investigating - We are currently investigating reports of elevated error rates loading the Deployment Overview on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.

Mar 24, 05:01 UTC Resolved - This incident has been resolved. Mar 24, 04:40 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 24, 03:43 UTC Identified - We are observing elevated errors creating Vercel Functions in the `sin1` region. To mitigate errors creating deployments, we have temporarily disabled provisioning new Vercel Functions in this region. Existing deployments and live traffic are not affected by this issue. We will share updates as they become availa...

Mar 16, 18:44 UTC Resolved - Due to ongoing issues in the dxb1 region, traffic and regional Vercel services are currently re-routed to bom1. We will share more details on recovery when they become available. Mar 2, 18:23 UTC Monitoring - We are monitoring the situation and continue to work toward restoring capacity in the dxb1 region. We will send further updates when new information is available. Mar 2, 15:29 UTC Identified - Due to operational issues in the dxb1 region, traffic is currently ...

Mar 13, 23:15 UTC Resolved - This incident has been resolved. Mar 13, 22:53 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 13, 22:32 UTC Investigating - We are currently investigating elevated error reports of deployment creation during the build phase. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.

Mar 12, 01:15 UTC Resolved - Between 01:15 and 05:45 UTC, customers might have experienced elevated GitHub deployment failures, including delays in triggering new deployments for commits and redeploy errors displaying the message "There is no GitHub account connected to this Vercel account". This was due to GitHub API degradations, which they have since resolved. https://www.githubstatus.com/incidents/lw6j95nyw3py https://www.githubstatus.com/incidents/02z04m335tvv

Mar 6, 21:38 UTC Resolved - This incident has been resolved. Mar 6, 21:20 UTC Monitoring - A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor. Mar 6, 19:18 UTC Update - We are applying a fix for the deployments experiencing elevated errors. We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required....

Mar 6, 21:22 UTC Resolved - This incident has been resolved. Mar 6, 21:10 UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar 6, 21:00 UTC Identified - The issue has been identified and a fix is being implemented. Mar 6, 20:53 UTC Investigating - We are investigating reports of elevated queue message latency and message retry latency in iad1, as well as elevated sleep times and increased step retries in Workflow. We will provide additional updates as they becom...

Mar 3, 21:10 UTC Resolved - This incident has been resolved. Mar 3, 19:14 UTC Monitoring - A fix has been implemented and we are seeing recovery for data loading and ingestion across services. We are continuing to monitor and will provide additional updates as they become available. Mar 3, 17:10 UTC Investigating - Dashboard pages that use Observability data, including Observability, Speed Insights, Web Analytics, Usage, Firewall, and Activity, are experiencing delays while loading data. Thes...

Mar 2, 15:20 UTC Resolved - This incident has been resolved. Mar 2, 14:59 UTC Monitoring - We have rolled out a second mitigation for elevated Build errors and are seeing recovery. All builds are now excluding the Dubai region (dxb1) from their deployment targets as a temporary measure. We will provide additional updates as they become available. Mar 2, 13:00 UTC Update - We have rolled out a first mitigation for elevated Build errors. Builds that use Middleware are now excluding the Dubai re...

Mar 2, 12:08 UTC Resolved - This incident was resolved. Mar 2, 08:49 UTC Monitoring - The dxb1 Edge traffic is currently being rerouted to the nearest Edge region (bom1) to mitigate the impact. We will provide additional updates as they become available. Mar 2, 08:01 UTC Identified - We are continuing to work on a fix for this issue. Mar 2, 06:54 UTC Investigating - We are currently investigating issues collecting Logs and Traces in Dubai (dxb1). We will share updates as they become availabl...

Mar 2, 00:22 UTC Resolved - A fix has been implemented and new deployments are no longer failing. Mar 1, 21:17 UTC Identified - Deployments for customers that use Static IPs are failing when deploying functions to the Dubai region. Customers can remove the Dubai region from the Static IPs configuration to avoid deployment failures. Our team is actively investigating the issue. Deployments to other regions are not affected.

Feb 28, 06:28 UTC Resolved - This incident has been resolved. Feb 28, 05:46 UTC Monitoring - We experienced delays in loading Observability, Analytics and Speed Insights data on the dashboard. We will provide additional updates as they become available.