Live  /  Vercel  /  Incident

Vercel: Increased build and deployment failures

Vercel · vercel.comMajor incidentResolved2026-10-12 20:11 UTC
Public — what happened

Summary

Vercel reported a major incident beginning at 13:35 UTC on October 12, 2026, in which some customers saw builds fail or deployments that would not start. The company said it had found the problem by 14:08 UTC, and later updates noted fewer failures but builds sitting in a queue, with Vercel saying an upstream GitHub incident was still causing failures for some GitHub-connected projects. Vercel also said updates such as deployment status on pull requests were delayed while a backlog was worked through, which it reported as cleared at 19:56 UTC. The incident was marked resolved at 20:11.

Affected

Builds, Git Integrations

As listed on Vercel’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Vercel against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Vercel: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Vercel report →

More from Vercel

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Vercel status & history page.

Related: Vercel status & history. SquidGrid is not affiliated with Vercel.