Next.js application platform, deployment workflow, and Vercel service status watch.
Tracked items
Active or featured
Vendor
Vendor incident stream
Use this vendor page to review the latest official watch items, compare activity against your environment, and decide whether the next step is an assessment, service-owner conversation, or direct remediation planning.
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.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
We are investigating reports of build logs stuck in loading state.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
We are currently investigating increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV. We recommend redeploying affected Vercel Functions or upgrading them to either Node.js 22 or 24.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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 as soon as they become available.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
We are currently investigating reports of elevated errors when submitting support cases. Some customers may experience timeouts when creating support tickets. We will share updates as they become available.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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 available.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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 become available.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
Dashboard pages that use Observability data, including Observability, Speed Insights, Web Analytics, Usage, Firewall, and Activity, are experiencing delays while loading data. These pages are also experiencing delays ingesting new data. We are investigating this issue and will provide additional updates as they become available.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments. If your existing deployments that use the dxb1 region are experiencing elevated function invocation errors, we strongly recommend switching to the nearest region (such as bom1) and redeploy until capacity is restored in dxb1. Deployments using multiple regions or failover regions are not affected since traffic is automatically routed to the nearest region based on the configured settings.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
We are currently investigating issues collecting Logs and Traces in Dubai (dxb1). We will share updates as they become available.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
Starting from 5:00 am UTC, we have started seeing failures to deploy and invoke functions in Dubai region (dxb1). Deployments with Middleware Functions are also impacted in all regions, because Middleware Functions are deployed globally for production deployments. Our team is actively investigating the issue.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
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.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
We experienced delays in loading Observability, Analytics and Speed Insights data on the dashboard. We will provide additional updates as they become available.
Check vercel dependent workflows, notify affected clients if service disruption persists, and review workaround guidance from the official incident page.
ITECS response pathways
The vendor watch page is designed to support your broader cybersecurity architecture, not replace it, so these links point back into the service-owner and resource pages that already carry core commercial authority.
Use the website design & development pathway when this vendor alert needs an ITECS-managed response plan.
Connect the vendor watch page to broader managed detection, response, and governance planning.
Translate current watch items into a faster risk snapshot and prioritized remediation plan.
Review proof-driven material that supports continuity, resilience, and security decision-making.
Use the resource library for longer-form guidance, vendor analysis, and implementation context.
Return to the hub for cross-vendor prioritization, live filtering, and broader MSP threat context.
Vendor watch FAQ
It is the Vercel / Next.js-specific view inside ITECS Threat Radar, built to track recent advisories, incidents, and watch items that may affect Dallas-area business operations.
Use it to confirm whether current Vercel / Next.js issues overlap with your environment, prioritize remediation, and decide whether you need an assessment, managed security follow-through, or vendor-specific hardening work.
Yes. ITECS can help map Vercel / Next.js advisories against your systems, validate affected services, prioritize remediation, and connect the issue to broader managed cybersecurity or managed IT workflows.