Vercel Outage History

Vercel experienced intermittent errors when creating new deployments, impacting the Build & Deploy / Builds component. Users attempting to deploy projects may have encountered failures or errors during the deployment flow. The incident began at 7:01 PM UTC and lasted about 50 minutes, with Build & Deploy / Builds degraded during the period and returning to normal by 7:51 PM UTC. Vercel acknowledged the issue and announced an investigation at 6:57 PM UTC, followed by a second update as the service recovered. The incident involved 2 status updates from Vercel. The issue did not show clear regional patterns, suggesting a global impact on deployment workflows.

The Vercel Build & Deploy builds component experienced a degraded state starting at May 15, 2025 7:51 AM UTC and was resolved by May 15, 2025 9:06 AM UTC, causing a brief disruption to builds and deployments. Deployments may have been delayed and queue times could be longer during this period.

The provider's status page indicated an investigation was underway and subsequently provided updates as the issue was resolved. The incident was contained to the Build & Deploy / Builds component and lasted roughly 1 hour 15 minutes, with 2 official status updates issued during the event.

Vercel's Build & Deploy service experienced degraded builds starting at 1:01 PM UTC, affecting users attempting to build or deploy projects. The disruption lasted about 40 minutes, with builds failing or running slowly until 1:41 PM UTC when the status returned to normal.

The provider posted two updates during the incident: an investigation notice at 1:01 PM UTC and a final resolution at 1:41 PM UTC. The issue impacted the Build & Deploy / Builds component across projects, with no regional pattern indicated.

Vercel experienced elevated errors during some deployments, with the Build & Deploy / Builds component showing degraded behavior. The status page indicated the issue was under investigation and that existing deployments and live traffic were not affected. The incident began at 1:16 PM UTC and was resolved by 1:51 PM UTC. Two status updates were issued during the incident as the team worked toward a fix.

By the end of the incident, Build & Deploy / Builds had returned to normal operation and the issue was considered resolved, with the outage lasting roughly 35 minutes.

Vercel experienced a short regional degradation in the iad1 region that affected builds using functions. Deploys in that region may have failed or been delayed as the Build & Deploy / Builds path and the v0 / Output Generation component were impacted. The issue began at Apr 28, 2025 12:01 PM UTC and lasted about 35 minutes, with the Output Generation path recovering by Apr 28, 2025 12:16 PM UTC and the Build & Deploy path fully back to normal by Apr 28, 2025 12:36 PM UTC. The status page issued four updates during the incident to communicate investigation progress and restoration.

A partial outage at Vercel disrupted the submission of messages with attachments to the v0 service, impacting the Output Generation and Dashboard components. The outage began at 6:11 PM UTC and was resolved by 7:21 PM UTC, lasting about 1 hour and 10 minutes. The incident affected two v0 components as teams investigated and worked toward restoration.

A transient issue affected Vercel's Build & Deploy / npm Registry, causing private npm package installations to fail with 4xx errors. This disrupted builds that depend on private packages, with authentication problems reported to prevent token-based access. The outage began at Apr 11, 2025 2:41 AM UTC and was resolved by Apr 11, 2025 3:21 PM UTC, lasting about 12 hours and 40 minutes. The root cause was tied to private registry authentication, and a recommended workaround involved regenerating tokens. The incident included two official status updates during its course. Note that there was no public guidance from npm or GitHub regarding the root cause.

Vercel experienced a brief incident where the Dashboard indicated elevated reports of projects being paused even though the Spend Limit had not been reached. The Dashboard component was affected, and users may have seen paused statuses within the UI, impacting project management for a period. The incident lasted approximately 1 hour and 40 minutes, beginning at 1:16 PM UTC and resolving by 2:56 PM UTC. Vercel issued two official status updates during the incident, moving from warn to up as the issue was resolved.

Between Apr 8, 2025 8:11 PM UTC and Apr 8, 2025 8:26 PM UTC, the Vercel Community site experienced a brief outage that made the Community section inaccessible to some users. The Community component was listed as degraded during this window and returned to normal by Apr 8, 2025 8:26 PM UTC. The incident lasted about 15 minutes, and Vercel issued 2 status updates during the event, acknowledging the investigation and later confirming recovery.

Vercel reported a degraded condition in the Logs component due to missing OTEL traces for Datadog exports. The issue affected telemetry data used by Datadog integrations, with users potentially seeing incomplete traces. The incident began with an investigation at 5:37 PM UTC and was reflected on the status page at 10:36 PM UTC. The problem persisted for about 1 hour and 20 minutes and was resolved by 11:56 PM UTC when the component returned to normal. Other aspects of Vercel's services were reported as unaffected.