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

Affected components

• Functions

1. resolvedJun 8, 2026, 20:00 UTC

   This incident has been resolved.

2. monitoringJun 8, 2026, 19:36 UTC

   We are continuing to monitor for any further issues.

3. monitoringJun 8, 2026, 19:36 UTC

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

4. identifiedJun 8, 2026, 19:04 UTC

   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.

5. identifiedJun 8, 2026, 18:57 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Vercel's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Akamai: Edge Delivery - HTTP Content Delivery in EuropeMinor · Jun 5, 2026, 16:36 UTC
• Snyk: Email-to-Case Temporarily DisabledMinor · Jun 8, 2026, 15:47 UTC
• Airtable: Increased latency for requests to AirtableMinor · Jun 8, 2026, 19:44 UTC

How often does Vercel have incidents?

Vercel reported 24 incidents in the last 90 days, 10 of them major or critical. A typical incident lasted 59 min. See Vercel's uptime and incident history