v0 (Vercel) · 85d ago
Increased invocation failures for Hobby Team functions
ResolvedYes — v0 had a problem on July 17, 2026, and v0 (Vercel) has since marked it resolved. v0 (Vercel)'s latest word: “This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected.”
Timeline
Started: 7/17/2026, 2:12:58 PM
Last update: 7/17/2026, 3:31:34 PM
Resolved: 7/17/2026, 3:19:53 PM
Affected: kgcsn9c73xzf
Updates
resolved
This incident has been resolved. A subset of deployments created under the Hobby plan teams during Jul 17, 2026 10:18 - Jul 17, 2026 14:10 UTC were impacted by this incident. New deployments after this window are unaffected.
7/17/2026, 3:19:53 PM
monitoring
We have deployed a fix and are continuing to monitor. Function invocations for new Hobby Team deployments should no longer fail. If you are still experiencing function invocation errors, redeploy or rollback to a previous deployment.
7/17/2026, 2:27:39 PM
identified
We have identified the source of errors and are implementing a fix.
7/17/2026, 2:19:52 PM
investigating
There are elevated rates of invocation failures for Hobby Team functions in new deployments. Existing deployments are unaffected. We are investigating. Mitigation is possible by rolling back to a previous deployment.
7/17/2026, 2:12:58 PM
More v0 (Vercel) incidents
- Delays in Drains, Observability, and Workflow in Washington (iad1) — resolved, 17h ago
- Vercel Auth login failures for pages with Deployment Protection enabled — resolved, 4d ago
- Elevated Sandbox error rates in Paris (cdg1) — resolved, 4d ago
- Build failures and 500 errors for functions using Edge runtime — resolved, 12d ago
- Deployment stuck in initializing state — resolved, 22d ago
- Elevated Errors Triggering Deployments — resolved, 22d ago