All Systems Operational

Uptime over the past 90 days. View historical uptime.
AI Gateway Operational
90 days ago
100.0 % uptime
Today
API Operational
90 days ago
99.97 % uptime
Today
Build & Deploy Operational
90 days ago
99.96 % uptime
Today
Builds Operational
90 days ago
99.93 % uptime
Today
npm Registry Operational
90 days ago
100.0 % uptime
Today
CI/CD Operational
90 days ago
100.0 % uptime
Today
Deploy Hooks Operational
90 days ago
100.0 % uptime
Today
Git Integrations Operational
90 days ago
100.0 % uptime
Today
Integration Webhooks Operational
90 days ago
100.0 % uptime
Today
Community Operational
90 days ago
100.0 % uptime
Today
Cron Jobs Operational
90 days ago
100.0 % uptime
Today
Dashboard Operational
90 days ago
99.99 % uptime
Today
Dashboard Operational
90 days ago
99.97 % uptime
Today
Support Center Operational
90 days ago
99.99 % uptime
Today
Support Chat Operational
90 days ago
100.0 % uptime
Today
Data Cache Operational
90 days ago
100.0 % uptime
Today
DNS Operational
90 days ago
100.0 % uptime
Today
Domain Registration Operational
90 days ago
99.98 % uptime
Today
Edge Functions Operational
90 days ago
99.99 % uptime
Today
Edge Middleware Operational
90 days ago
100.0 % uptime
Today
Edge Network Operational
90 days ago
98.75 % uptime
Today
ARN1 - Stockholm, Sweden Operational
90 days ago
100.0 % uptime
Today
BOM1 - Mumbai, India Operational
90 days ago
100.0 % uptime
Today
CDG1 - Paris, France, Europe Operational
90 days ago
100.0 % uptime
Today
CLE1 - Cleveland, East US Operational
90 days ago
100.0 % uptime
Today
CPT1 - Cape Town, South Africa Operational
90 days ago
100.0 % uptime
Today
DUB1 - Dublin, Ireland Operational
90 days ago
100.0 % uptime
Today
DXB1 - Dubai, UAE Operational
90 days ago
75.16 % uptime
Today
FRA1 - Frankfurt, Germany, Europe Operational
90 days ago
100.0 % uptime
Today
GRU1 - São Paulo, Brazil Operational
90 days ago
100.0 % uptime
Today
HKG1 - Hong Kong Operational
90 days ago
100.0 % uptime
Today
HND1 - Tokyo, Japan Operational
90 days ago
100.0 % uptime
Today
IAD1 - Washington DC, USA Operational
90 days ago
100.0 % uptime
Today
ICN1 - Seoul, South Korea Operational
90 days ago
100.0 % uptime
Today
KIX1 - Osaka, Japan Operational
90 days ago
100.0 % uptime
Today
LHR1 - London, UK Operational
90 days ago
100.0 % uptime
Today
PDX1 - Portland, West US Operational
90 days ago
100.0 % uptime
Today
SFO1 - San Francisco, CA, USA Operational
90 days ago
100.0 % uptime
Today
SIN1 - Singapore Operational
90 days ago
100.0 % uptime
Today
SYD1 - Sydney, Australia Operational
90 days ago
100.0 % uptime
Today
YUL1 - Montréal, Canada Operational
90 days ago
100.0 % uptime
Today
Firewall Operational
90 days ago
100.0 % uptime
Today
Image Optimization Operational
90 days ago
100.0 % uptime
Today
Logs Operational
90 days ago
99.99 % uptime
Today
Drains Operational
90 days ago
100.0 % uptime
Today
Marketplace Operational
90 days ago
100.0 % uptime
Today
Remote Caching Operational
90 days ago
100.0 % uptime
Today
SAML Single Sign-On Operational
90 days ago
100.0 % uptime
Today
Sandbox Operational
90 days ago
100.0 % uptime
Today
Serverless Functions Operational
90 days ago
100.0 % uptime
Today
Secure Compute Operational
90 days ago
100.0 % uptime
Today
Builds Operational
90 days ago
100.0 % uptime
Today
Speed Insights Operational
90 days ago
99.97 % uptime
Today
SSL Certificates Operational
90 days ago
100.0 % uptime
Today
Storage Operational
90 days ago
100.0 % uptime
Today
Blob Operational
90 days ago
100.0 % uptime
Today
Edge Config Operational
90 days ago
100.0 % uptime
Today
v0 Operational
90 days ago
100.0 % uptime
Today
Output Generation Operational
90 days ago
100.0 % uptime
Today
Dashboard Operational
90 days ago
100.0 % uptime
Today
Web Analytics Operational
90 days ago
99.97 % uptime
Today
Queues Operational
90 days ago
100.0 % uptime
Today
Workflow Operational
90 days ago
99.99 % uptime
Today
Observability Operational
90 days ago
99.92 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

May 23, 2026
Elevated Build Failures (GitHub connected projects)
Resolved - This incident has been resolved.
May 23, 18:44 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 23, 18:21 UTC
Identified - We have identified the issue and are working closely with GitHub to resolve it.
May 23, 15:46 UTC
Update - 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.
May 23, 14:30 UTC
Update - We are continuing to investigate this issue.
May 23, 12:15 UTC
Update - 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.
May 23, 11:09 UTC
Investigating - We are currently investigating this issue.
May 23, 10:43 UTC
May 22, 2026
Build Failures for Some Next.js Deployments
Resolved - Between 16:10 and 16:43 UTC on May 22, some customers using Next.js above 16.2.0-canary.28 with Preview Comments enabled experienced build failures during deployments. The issue has been mitigated and follow-up deployments should no longer encounter this error.
May 22, 17:11 UTC
May 21, 2026
Elevated Build Errors
Resolved - This incident has been resolved.
May 21, 21:31 UTC
Monitoring - The mitigation was successfully rolled out, and builds are stable.
May 21, 21:20 UTC
Update - The root cause has been identified and we are rolling out a mitigation.
May 21, 19:55 UTC
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.
May 21, 15:01 UTC
Missing Build CPU Minutes Usage Data
Resolved - This incident has been resolved.

Usage data for Build CPU Minutes between May 15, 2026, 19:30, and May 20, 2026, 18:00 UTC is currently incomplete. Customers will see usage data for Build CPU Minutes catch up over the next business day as we backfill the data for the affected window.
May 21, 06:08 UTC
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.
May 20, 20:07 UTC
May 20, 2026
May 19, 2026

No incidents reported.

May 18, 2026
Increased Function Invocation Errors - ERR_MODULE_NOT_FOUND
Resolved - This incident has been resolved.

Some deployments created between May 18, 2026, 06:15 PM - 10:16 PM UTC may have experienced increased ERR_MODULE_NOT_FOUND function invocation errors due to a bad rollout. Deployments created outside of this window are unaffected.

The fix is being rolled out to existing deployments retrospectively and is expected to finish in the next few hours.
May 18, 23:52 UTC
Update - We are continuing to monitor for any further issues.
May 18, 22:19 UTC
Monitoring - A fix is rolled out for the function invocation errors affecting React Router 7 deployments. To recover, redeploy your application or use Instant Rollback to a previous deployment from the dashboard. We're continuing to monitor.
May 18, 22:16 UTC
Update - We're continuing to work on rolling out a fix. In the mean time, customers may use Instant Rollback to a previous deployment version as an immediate workaround in order to recover.
May 18, 22:11 UTC
Identified - The issue has been identified and a fix is being implemented.
May 18, 21:53 UTC
Investigating - We're investigating an issue where customers are currently experiencing application failures due to function invocation errors when using React Router 7.
May 18, 21:42 UTC
Support cases cannot be submitted
Resolved - The incident is resolved and support cases can be submitted again.
May 18, 15:41 UTC
Monitoring - We have implemented a fix. New support cases can be created. We continue to monitor.
May 18, 15:17 UTC
Investigating - We are investigating an issue where support cannot be submitted through the dashboard.
May 18, 15:00 UTC
May 17, 2026

No incidents reported.

May 16, 2026

No incidents reported.

May 15, 2026
Workflow usage amounts are incorrectly calculated
Resolved - The usage tracking system is fully recovered.
May 15, 16:18 UTC
Monitoring - The team fixed the incorrect calculations. We are resuming usage tracking and continuing to monitor.
May 15, 15:39 UTC
Update - We are continuing to work on the fix. Usage tracking for Workflow Storage remains paused. The incorrect calculations will not be charged.
May 15, 13:40 UTC
Identified - The team has identified the source of the incorrect usage data calculations and has paused usage tracking while a fix is being prepared.
May 15, 11:37 UTC
Investigating - Workflow Storage Retention and Workflow Storage Writes are being incorrectly calculated in usage data. The team is investigating and working to resolve the discrepancy.
May 15, 10:34 UTC
May 14, 2026

No incidents reported.

May 13, 2026

No incidents reported.

May 12, 2026

No incidents reported.

May 11, 2026

No incidents reported.

May 10, 2026

No incidents reported.

May 9, 2026
Vercel Queues, and Vercel Workflow runs were delayed
Resolved - This incident has been resolved.
May 9, 05:40 UTC
Monitoring - Between 1:30 to 3:44 UTC, messages in Vercel Queues in iad1 were enqueued but not processed, and Vercel Workflows were blocked from making progress (i.e. remaining in pending / active states). This is recovering, Vercel Queues backlogs are being processed, and Vercel Workflows are unblocked.
May 9, 04:45 UTC
← Incident History Powered by Atlassian Statuspage