Vercel outage: New container functions are failing

Affected components

• Functions

1. resolvedAug 20, 2026, 18:34 UTC

   This incident has been resolved.

2. monitoringAug 20, 2026, 18:23 UTC

   We have deployed a fix. Newly deployed container functions are working as expected.

3. identifiedAug 20, 2026, 17:46 UTC

   We've identified an issue where newly deployed container functions may return 5XX errors. Customers can use a previously working container function deployment as a temporary mitigation. We are working on a fix and will provide additional updates as they become available.

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.

• GitHub: Intermittent failures creating agent tasksCritical · Aug 20, 2026, 14:43 UTC
• Render: Deployment IssuesMajor · Aug 20, 2026, 15:47 UTC
• Confluent Cloud: Elevated error rates and latency in GCP us-west1Major · Aug 20, 2026, 17:10 UTC
• Supabase: 401 errors due to JWT rejectionsMinor · Aug 14, 2026, 02:23 UTC
• Telnyx: Programmable Wireless data loss in AustraliaMinor · Aug 17, 2026, 19:27 UTC
• Akamai: Reporting data availability issues in 'Traffic by Hostname' reportMinor · Aug 20, 2026, 16:43 UTC
• Anthropic: Elevated errors on Google connectorsMinor · Aug 20, 2026, 18:32 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