Skip to main content

v0 (Vercel) · 127d ago

Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region

Resolved

Yes — v0 had a problem on June 8, 2026, and v0 (Vercel) has since marked it resolved. v0 (Vercel)'s latest word: “This incident has been resolved.”

See v0's live status →

Timeline

Started: 6/8/2026, 6:57:47 PM

Last update: 6/8/2026, 8:00:11 PM

Resolved: 6/8/2026, 8:00:11 PM

Affected: kgcsn9c73xzf

v0 (Vercel)'s official report →

Updates

  • resolved

    This incident has been resolved.

    6/8/2026, 8:00:11 PM

  • monitoring

    We are continuing to monitor for any further issues.

    6/8/2026, 7:36:44 PM

  • monitoring

    A fix has been implemented and we are monitoring the results.

    6/8/2026, 7:36:38 PM

  • identified

    We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region. If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue.

    6/8/2026, 7:04:25 PM

  • identified

    The issue has been identified and a fix is being implemented. A small number of requests may have seen elevated error rates in function invocations during this period.

    6/8/2026, 6:57:47 PM

More v0 (Vercel) incidents

Is v0 down right now?All outage history →

Is v0 down? v0 is up now — Jun 8, 2026 outage | AI Status