Looking for an update now? Check the current status, or follow Vercel for future changes.
84.2%of 57 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
86.7%
30
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We're investigating elevated initialization times for some builds. We will provide updates as we learn more.
Legacy Incident Archive
61 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
June 2026
Elevated latency and errors in FRA1 Vercel Region (Frankfurt, Germany)
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
All traffic has been restored to the FRA1 Vercel Region.
identified
The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.
identified
The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
identified
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
investigating
We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
Elevated Build Errors for Secure Compute/Static IPs Projects
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Elevated Functions Invocation Errors in DUB1 (Dublin, Ireland) Region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We are continuing to monitor for any further issues.
monitoring
A fix has been implemented and we are monitoring the results.
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.
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.
Elevated Errors Creating New Deployments
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.
May 2026
Elevated Function Invocation Errors in Stockholm region (ARN1)
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We've identified an issue where some customers may experience elevated error rates when invoking functions in the ARN1 Edge Region. We are currently investigating this issue.
Elevated Errors on Vercel Dashboard (Project Overview Page)
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We are currently investigating this issue.
Delays Loading Runtime Logs
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating elevated latency in loading runtime logs (Vercel Functions) in live mode. Log Drains are unaffected at this time.
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and are working closely with GitHub to resolve it.
investigating
We are working closely with GitHub to resolve this issue. Failures are intermittent — if your deployment fails, redeploying should resolve it in the meantime. We will provide updates as the situation develops.
investigating
We are continuing to investigate this issue.
investigating
We've been observing increased failures of git operations with GitHub since around 06:00 UTC. Some deployments triggered by GitHub commits might have seen git-related errors in failed build logs.
CLI deployments are unaffected at this time.
investigating
We are currently investigating this issue.
Elevated Build Errors
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The mitigation was successfully rolled out, and builds are stable.
identified
The root cause has been identified and we are rolling out a mitigation.
identified
We are currently investigating elevated build failures affecting a subset of Vite projects. Affected deployments may be timing out. We’ve identified an issue and are working on the fix.
Missing Build CPU Minutes Usage Data
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've identified an issue where some users may see missing Build CPU Minutes data on Usage pages in the Vercel Dashboard. The issue has been resolved, and we are backfilling the affected usage data.
