- Website
- Vercel-status
- Followers
- —
- Following
- —
Key Highlights
Elevated GitHub deployment failures occurred between 01:15 and 05:45 UTC on Mar 12, including delays in triggering new deployments and redeploy errors. 1 post
The issue was caused by GitHub API degradations, which have since been resolved. 1 post
Customers might have experienced redeploy errors with the message 'There is no GitHub account connected to this Vercel account'. 1 post
Main Topics (3)
Latest posts
Degraded Domain Search in Vercel Dashboard
Jun 23, 23:34 UTC Resolved - This incident has been resolved. Jun 23, 23:28 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 23, 23:26 UTC Identified - The issue has been identified and a fix is being implemented. Jun 23, 23:24 UTC Investigating - We're
Resolved: Elevated ERR_STREAM_PREMATURE_CLOSE errors in Vercel Functions
Jun 19, 17:54 UTC Resolved - 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
Partial disruption of Observability, Analytics, Firewall, and Usage in dashboard
Jun 16, 15:39 UTC Resolved - The incident has been resolved. Jun 16, 15:26 UTC Monitoring - The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor. Jun 16, 15:16 UTC
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
Jun 15, 01:24 UTC Resolved - This incident has been resolved. Jun 15, 00:25 UTC Monitoring - All traffic has been restored to the FRA1 Vercel Region. Jun 14, 23:15 UTC Update - The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel
Elevated Build Errors for Secure Compute/Static IPs Projects
Jun 9, 14:46 UTC Resolved - This incident has been resolved. Jun 9, 14:39 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 9, 14:33 UTC Identified - The issue has been identified and a fix is being implemented. Jun 9, 14:09 UTC Investigating - We ar
Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region
Jun 8, 20:00 UTC Resolved - This incident has been resolved. Jun 8, 19:36 UTC Update - We are continuing to monitor for any further issues. Jun 8, 19:36 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 8, 19:04 UTC Update - We're continuing to work
Elevated Errors Creating New Deployments
Jun 1, 20:02 UTC Resolved - This incident has been resolved. Jun 1, 19:55 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 1, 19:50 UTC Identified - The issue has been identified and a fix is being implemented. Jun 1, 19:21 UTC Investigating - We ar
Elevated Function Invocation Errors in Stockholm region (ARN1)
May 28, 16:59 UTC Resolved - This incident has been resolved. May 28, 16:37 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 28, 16:18 UTC Identified - The issue has been identified and a fix is being implemented. May 28, 16:00 UTC Investigating - We've
Elevated Errors on Vercel Dashboard (Project Overview Page)
May 27, 05:02 UTC Resolved - This incident has been resolved. We've rolled back a bad release to resolve the issue. Customers were unable to access the project overview page between 04:13 and 05:00 AM UTC. May 27, 04:50 UTC Investigating - We are currently investigating this issue.
Delays Loading Runtime Logs
May 25, 16:22 UTC Resolved - This incident has been resolved. May 25, 16:05 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 25, 15:25 UTC Identified - The issue has been identified and a fix is being implemented. May 25, 14:58 UTC Investigating - We ar
Elevated Build Failures (GitHub connected projects)
May 23, 18:44 UTC Resolved - This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt May 23, 18:21 UTC Monitoring - GitHub has implemented a fix, and we are monitoring the results. May 23, 15:46 UTC Ide
Build Failures for Some Next.js Deployments
May 22, 17:11 UTC Resolved - 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.
Elevated Build Errors
May 21, 21:31 UTC Resolved - This incident has been resolved. May 21, 21:20 UTC Monitoring - The mitigation was successfully rolled out, and builds are stable. May 21, 19:55 UTC Update - The root cause has been identified and we are rolling out a mitigation. May 21, 15:01 UTC Identified
Missing Build CPU Minutes Usage Data
May 21, 06:08 UTC Resolved - This incident has been resolved. Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up as we backfill the data for the affected window. May 20, 2
Increased Function Invocation Errors - ERR_MODULE_NOT_FOUND
May 18, 23:52 UTC Resolved - This incident has been resolved. Some deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments created outside of this window are unaffected. The fi
Support cases cannot be submitted
May 18, 15:41 UTC Resolved - The incident is resolved and support cases can be submitted again. May 18, 15:17 UTC Monitoring - We have implemented a fix. New support cases can be created. We continue to monitor. May 18, 15:00 UTC Investigating - We are investigating an issue where support c
Workflow usage amounts are incorrectly calculated
May 15, 16:18 UTC Resolved - The usage tracking system is fully recovered. May 15, 15:39 UTC Monitoring - The team fixed the incorrect calculations. We are resuming usage tracking and continuing to monitor. May 15, 13:40 UTC Update - We are continuing to work on the fix. Usage tracking for
Vercel Queues, and Vercel Workflow runs were delayed
May 9, 05:40 UTC Resolved - This incident has been resolved. May 9, 04:45 UTC Monitoring - Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is r
SSL Certificate Generation Delays
May 8, 19:15 UTC Resolved - Between 18:36 and 19:04 UTC, issuing SSL certificates was delayed for new domains. These certificates have now been issued. Certificate renewals were not affected.
Delays Processing Builds
May 8, 16:41 UTC Resolved - This incident has been resolved. May 8, 16:33 UTC Monitoring - We have applied a fix and are observing recovery across all builds. We'll provide additional updates as-needed. May 8, 16:30 UTC Identified - We've identified an issue where some customers may expe
Elevated errors across multiple services in IAD1 (Washington, D.C., USA)
May 8, 06:39 UTC Resolved - We've deployed mitigations and all services are operating normally. Traffic may continue to reroute to nearby regions for the next few hours, but we will restore traffic gradually after verifying system availability in the IAD1 region. May 8, 04:54 UTC Monitoring -
Elevated Errors Creating New Deployments
May 7, 21:48 UTC Resolved - This issue has been resolved and new deployments are being created successfully. May 7, 21:14 UTC Investigating - We are investigating an issue affecting new deployments that are stuck in the provisioning state. We will share more information as it becomes availabl
Increased error rate in Workflows
May 6, 00:19 UTC Resolved - This incident has been resolved. May 6, 00:13 UTC Monitoring - A fix has been implemented and we are monitoring the results. May 5, 23:30 UTC Identified - We are experiencing increased error rates with Workflows running on Vercel. We have identified the issue
Failures to load data across multiple services on the Vercel dashboard, API, and CLI
May 6, 00:38 UTC Resolved - All services remain operational. New data is being processed as expected. The majority of the backfill is complete and a long tail of data will be processed within the next couple of hours. May 5, 17:14 UTC Update - All systems are operational. We are continuing to
Request Failures in ICN1 (Seoul, South Korea)
May 4, 21:30 UTC Resolved - Between 21:45–21:52 UTC, some users may have experienced request failures in ICN1. The issue has been identified, a fix has been applied, and the issue has been resolved.