Next.js application platform, deployment workflow, and Vercel service status watch.
Watch items
Showing the 20 most recent items, newest first. Each row links to the official advisory.
20 rows · sorted newest first
Operations viewWe've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.
We are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC.
We are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected.
We're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard.
Between Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE. As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989 We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed.
We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period.
We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.
We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.
We are currently investigating this issue.
We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.
We are currently investigating this issue.
Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.
We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.
We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.
We are investigating an issue where support cannot be submitted through the dashboard.
A vulnerability was found in vercel ai up to 3.0.97. The affected element is the function validateDownloadUrl of the file packages/provider-utils/src/download-blob.ts of the component provider-utils. The manipulation results in server-side request forgery. The attack can be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
| Alert | Exposure | Status | Published | Source |
|---|---|---|---|---|
Increase in Workflow runs stuck in pending, failedWe've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state. New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available. Workflow | minor Watch | resolved | Jul 1, 2026, 11:57 AM | Status incidentOpen source |
Intermittent Login Failures on Vercel DashboardWe are currently investigating the issue. Some users are experiencing errors logging in. The issue started at 11:30 AM UTC. Dashboard | major Watch | resolved | Jun 26, 2026, 8:08 AM | Status incidentOpen source |
Increase in Workflow runs stuck as pendingWe are currently investigating an issue where some recently deployed Workflow projects are stuck as pending and not delivering queued messages as expected. Workflow | major Watch | resolved | Jun 25, 2026, 2:45 AM | Status incidentOpen source |
Degraded Domain Search in Vercel DashboardWe're investigating an issue preventing customers from searching for and purchasing domains in the Vercel Dashboard. Domain Registration | minor Watch | resolved | Jun 23, 2026, 6:24 PM | Status incidentOpen source |
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel FunctionsBetween Jun 19 09:09 and 16:16 UTC, a subset of Vercel Functions using node-fetch@2 may have experienced intermittent invocation errors that surfaced as ERR_STREAM_PREMATURE_CLOSE. As part of Node.js June 2026 security releases, we began rolling out new Node.js versions. Those versions contain an upstream regression that breaks response streaming for node-fetch@2, which caused the errors https://github.com/nodejs/node/issues/63989 We have resolved the issue by reverting to the previous Node.js version. No action is required — affected functions are now operating normally. We will re-land the Node.js upgrade once the upstream issue is fixed. Functions | none Watch | resolved | Jun 19, 2026, 12:54 PM | Status incidentOpen source |
Partial disruption of Observability, Analytics, Firewall, and Usage in dashboardWe are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features. Dashboard | minor Watch | resolved | Jun 16, 2026, 8:39 AM | Status incidentOpen source |
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue. FRA1 - Frankfurt, Germany, Europe | major Watch | resolved | Jun 14, 2026, 4:03 PM | Status incidentOpen source |
Elevated Build Errors for Secure Compute/Static IPs ProjectsWe are currently investigating this issue. Builds | major Watch | resolved | Jun 9, 2026, 9:09 AM | Status incidentOpen source |
Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) RegionThe issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period. Functions | minor Watch | resolved | Jun 8, 2026, 1:57 PM | Status incidentOpen source |
Elevated Errors Creating New DeploymentsWe are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available. Builds | minor Watch | resolved | Jun 1, 2026, 2:21 PM | Status incidentOpen source |
Elevated Function Invocation Errors in Stockholm region (ARN1)We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue. Functions | minor Watch | resolved | May 28, 2026, 11:00 AM | Status incidentOpen source |
Elevated Errors on Vercel Dashboard (Project Overview Page)We are currently investigating this issue. Dashboard | minor Watch | resolved | May 26, 2026, 11:50 PM | Status incidentOpen source |
Delays Loading Runtime LogsWe are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time. Logs | minor Watch | resolved | May 25, 2026, 9:58 AM | Status incidentOpen source |
Elevated Build Failures (GitHub connected projects)We are currently investigating this issue. Builds | minor Watch | resolved | May 23, 2026, 1:44 PM | Status incidentOpen source |
Build Failures for Some Next.js DeploymentsBetween 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error. Builds | none Watch | resolved | May 22, 2026, 12:11 PM | Status incidentOpen source |
Elevated Build ErrorsWe are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix. Builds | minor Watch | resolved | May 21, 2026, 10:01 AM | Status incidentOpen source |
Missing Build CPU Minutes Usage DataWe've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data. Builds | minor Watch | resolved | May 20, 2026, 3:07 PM | Status incidentOpen source |
Increased Function Invocation Errors - ERR_MODULE_NOT_FOUNDWe're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7. Next.js / Vercel | minor Watch | resolved | May 18, 2026, 4:42 PM | Status incidentOpen source |
Support cases cannot be submittedWe are investigating an issue where support cannot be submitted through the dashboard. Support Chat | minor Watch | resolved | May 18, 2026, 10:00 AM | Status incidentOpen source |
ai vulnerability (CVE-2026-8768)A vulnerability was found in vercel ai up to 3.0.97. The affected element is the function validateDownloadUrl of the file packages/provider-utils/src/download-blob.ts of the component provider-utils. The manipulation results in server-side request forgery. The attack can be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way. ai | MEDIUMCVE-2026-8768 Watch | watch | May 17, 2026, 6:17 PM | NVDOpen source |
Vendor watch hub
The Vercel / Next.jswatch hub is a vendor-specific view inside ITECS MSP Threat Radar. We pull the latest security advisories, incidents, and known-exploited CVEs directly from the official feeds below, score each one for MSP relevance, and surface what's most likely to need attention this week.
At a glance
Tracked
Active
Featured
Unique CVEs
Most recent entry
Jul 1, 2026, 11:57 AM
Feed refreshes daily · 5:15 a.m. Central
Sources·Vercel status page (vercel-status.com)
"Most recent entry" is the newest item the upstream feed has published — not our sync time.
Related vendors
ITECS response pathways
These pathways connect the vendor watch feed into service-owner resources that already carry 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.
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.