Vercel Outage History

Vercel experienced a brief minor outage affecting the Optional Third Party Dependencies / GitHub Pull Requests component, which may have disrupted GitHub PR workflows. The outage lasted about 25 minutes, beginning at 6:36 AM UTC and ending at 7:01 AM UTC.

The provider issued 2 status updates during the incident and the status returned to normal by 7:01 AM UTC.

An incident affected Vercel Functions and Edge Middleware traffic in fra1, cpt1, and arn1 regions, resulting in elevated error rates and intermittent failures for requests routed through these components. The outage began at Feb 26, 2025 11:26 AM UTC and lasted about 35 minutes, with users experiencing disrupted function executions and degraded middleware routing during the event.

Sites hosted on Vercel experienced SSL/TLS errors due to SSL certificate issues, leading to failed secure connections for visitors. The problem was centered on the SSL Certificates component and caused degraded access for end users during the incident.

The outage lasted about 1 hour, from 5:31 AM UTC to 6:31 AM UTC. The Vercel status page published 2 updates detailing the investigation and restoration.

Vercel experienced a brief minor outage affecting the Optional Third Party Dependencies / GitHub Pull Requests component, causing intermittent issues with GitHub PR integrations for about 55 minutes. The outage began at 4:16 PM UTC and was resolved by 5:11 PM UTC. The incident included two official status updates as Vercel worked to restore the affected path, with no wider impact to other Vercel services. The issue appeared isolated to the GitHub PR dependency path.

Vercel experienced an authentication email delivery issue that affected Outlook / Microsoft Exchange users, preventing login verification emails from arriving. Registration emails could also be delayed. The Dashboard component was listed as degraded during the incident. Workarounds included registering via GitHub, GitLab, or Bitbucket. The incident began at Feb 20, 2025 4:06 PM UTC and spanned several hours as the team investigated and monitored the situation, with two official status updates published.

The issue was resolved with the Dashboard component returning to normal at Feb 20, 2025 11:21 PM UTC, after roughly 7 hours and 15 minutes. The provider confirmed the resolution and updated the status accordingly.

Vercel experienced degraded authentication when login verification emails were not delivered to Outlook/Microsoft Exchange users, impacting the login flow for a subset of users. The issue affected the Dashboard component and led to a degradation on the status page, with two updates issued during the incident. The outage began at Feb 20, 2025 2:41 PM UTC and was resolved by Feb 20, 2025 3:41 PM UTC, lasting about one hour. This appears limited to email delivery during login rather than a full service outage.

Some Vercel users could not receive login verification emails, disrupting authentication and delaying sign-ins. The Dashboard component was identified as affected during the incident. The outage began at Feb 18, 2025 7:16 PM UTC and caused email delivery failures for verification links.

The incident lasted roughly 14 hours and 5 minutes, ending with the issue resolved by Feb 19, 2025 9:21 AM UTC. During the period, Vercel issued two status updates detailing the investigation and remediation efforts, and the login email delivery issue was resolved as the Dashboard component returned to normal operation.

Vercel experienced a minor outage affecting GitHub-related dependencies, including GitHub Git Operations, GitHub API Requests, Webhooks, and Pull Requests. Users relying on GitHub-based deployments or automatic syncs could have seen delays or partial failures during the incident. The issue began at 12:11 PM UTC and was resolved by 12:46 PM UTC, lasting about 35 minutes. Three status updates were issued as the situation progressed on Vercel's status page.

An outage in Vercel's ARN1 (Stockholm) Edge Network caused increased request latency, with end users in the Stockholm region experiencing slower responses as traffic was rerouted to nearby regions. The incident also affected the Build & Deploy / Builds component, leading to deployment delays and transient failures during the outage. The issue began with the ARN1 edge node dropping to a degraded state and progressed through a period of instability before recovery.

The Vercel Dashboard Observability feature experienced a data delay affecting observability dashboards and metrics. The issue began at 10:15 AM UTC and was publicly acknowledged later that day with an update at 11:06 PM UTC noting Investigating a data delay in the Dashboard component, with the delay lasting roughly 16 hours.