
Vercel Status
Real-time updates of Vercel issues and outages
Vercel status is Operational
CLE1 - Cleveland, East US
IAD1 - Washington DC, USA
Dashboard
Vercel Functions
Vercel Optional Third Party Dependencies
Atlassian Bitbucket Pipelines
Vercel Workflow
You're checking on Vercel - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
No active incidents
Recently Resolved Incidents
We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.
We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state.
New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.
Vercel Outage Survival Guide
Vercel Components
Vercel AI Gateway
Vercel API
Vercel Build & Deploy
Builds
npm Registry
Vercel CI/CD
Deploy Hooks
Git Integrations
Integration Webhooks
Vercel CDN
ARN1 - Stockholm, Sweden
BOM1 - Mumbai, India
CDG1 - Paris, France, Europe
CLE1 - Cleveland, East US
We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.
CPT1 - Cape Town, South Africa
DUB1 - Dublin, Ireland
DXB1 - Dubai, UAE
FRA1 - Frankfurt, Germany, Europe
Vercel Edge Functions
GRU1 - São Paulo, Brazil
BRU1 - Brussels, Belgium, Europe
HKG1 - Hong Kong
HND1 - Tokyo, Japan
IAD1 - Washington DC, USA
We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.
CHS1 - Charleston, East US
ICN1 - Seoul, South Korea
KIX1 - Osaka, Japan
LHR1 - London, UK
PDX1 - Portland, West US
SFO1 - San Francisco, CA, USA
SIN1 - Singapore
SYD1 - Sydney, Australia
YUL1 - Montréal, Canada
Vercel Community
Vercel Cron Jobs
Vercel Dashboard
Dashboard
We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.
Support Center
Support Chat
Vercel Data Cache
Vercel DNS
Vercel Domain Registration
Vercel Firewall
Vercel Functions
We are investigating an issue causing degraded performance across CDN, Dashboard, & Functions in Washington, Cleveland (iad1, cle1). We'll provide additional updates as they become available.
Vercel Image Optimization
Vercel Optional Third Party Dependencies
Vercel Observability
GitHub Git Operations
Drains
GitHub API Requests
Logs
GitHub Webhooks
Observability
Speed Insights
GitHub Pull Requests
Web Analytics
Atlassian Bitbucket Git via HTTPS
Atlassian Bitbucket Git via SSH
Vercel Marketplace
Atlassian Bitbucket API
Vercel Queues
Vercel Remote Caching
Atlassian Bitbucket Webhooks
Vercel Routing Middleware
Atlassian Bitbucket Pipelines
Vercel SAML Single Sign-On
npm Package installation
KV
Vercel Sandbox
WorkOS SSO
Vercel Secure Compute
WorkOS Directory Sync
Postgres
Builds
Vercel Optional Third Party Dependencies
Vercel Optional Third Party Dependencies
Vercel TLS Certificates
Test
Atlassian Bitbucket Git via HTTPS
Vercel Storage
Blob
Vercel GitHub API Requests
Atlassian Bitbucket Git via SSH
Edge Config
Vercel GitHub Git Operations
Atlassian Bitbucket API
Vercel v0
Vercel GitHub Webhooks
Atlassian Bitbucket Authentication and user management
Output Generation
Vercel GitHub Pull Requests
Atlassian Bitbucket Webhooks
npm Package publishing
Vercel GitHub Actions
Dashboard
Vercel Atlassian Bitbucket API
Vercel Workflow
We've identified an issue where some workflow runs created between June 30 at 22:24 UTC and July 1 at 16:08 UTC may be stuck in a pending state or have reached a failed state.
New workflow runs are not impacted. We are working on a fix for runs stuck in a pending state and will provide additional updates as they become available.