Vercel Outage Check
Is Vercel Down Right Now?
✅ Vercel is up and working normally. Checked: 4:05 AM (GMT+8).
Auto-refreshing live data in 60s
Vercel's Official Status Page
- Production website deployments
- Serverless function execution
- Preview deployment links in PRs
| Component | Status |
|---|---|
| AI Gateway | Operational |
| API | Operational |
| ARN1 - Stockholm, Sweden | Operational |
| Blob | Operational |
| BOM1 - Mumbai, India | Operational |
| Build & Deploy | Operational |
| Builds | Operational |
| Builds | Operational |
| CDG1 - Paris, France, Europe | Operational |
| CDN | Operational |
| CI/CD | Operational |
| CLE1 - Cleveland, East US | Operational |
| Community | Operational |
| CPT1 - Cape Town, South Africa | Operational |
| Cron Jobs | Operational |
| Dashboard | Operational |
| Dashboard | Operational |
| Dashboard | Operational |
| Data Cache | Operational |
| Deploy Hooks | Operational |
| DNS | Operational |
| Domain Registration | Operational |
| Drains | Operational |
| DUB1 - Dublin, Ireland | Operational |
| DXB1 - Dubai, UAE | Operational |
| Firewall | Operational |
| FRA1 - Frankfurt, Germany, Europe | Operational |
| Functions | Operational |
| Git Integrations | Operational |
| Global Config | Operational |
| GRU1 - São Paulo, Brazil | Operational |
| HKG1 - Hong Kong | Operational |
| HND1 - Tokyo, Japan | Operational |
| IAD1 - Washington DC, USA | Operational |
| ICN1 - Seoul, South Korea | Operational |
| Image Optimization | Operational |
| Integration Webhooks | Operational |
| KIX1 - Osaka, Japan | Operational |
| LHR1 - London, UK | Operational |
| Logs | Operational |
| Marketplace | Operational |
| npm Registry | Operational |
| Observability | Operational |
| Observability | Operational |
| Output Generation | Operational |
| PDX1 - Portland, West US | Operational |
| Queues | Operational |
| Remote Caching | Operational |
| Routing Middleware | Operational |
| SAML Single Sign-On | Operational |
| Sandbox | Operational |
| Secure Compute | Operational |
| SFO1 - San Francisco, CA, USA | Operational |
| SIN1 - Singapore | Operational |
| Speed Insights | Operational |
| Storage | Operational |
| Support Center | Operational |
| Support Chat | Operational |
| SYD1 - Sydney, Australia | Operational |
| TLS Certificates | Operational |
| v0 | Operational |
| Web Analytics | Operational |
| Workflow | Operational |
| YUL1 - Montréal, Canada | Operational |
SLA Grade: B
Based on 90-day verified uptime
98.556%
Uptime
43m
Mean Resolution Time (MTTR)
8.3
Avg Incidents / Month
11d ago
Last Incident
90 Days AgoToday
Vercel Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Vercel Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Vercel Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Vercel Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Vercel Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Are you having problems with Vercel?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns. - 3Check with alternative networkTry loading the site on a mobile cellular network or over a VPN. If it loads, the issue lies in your local ISP provider network routing.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, Vercel maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 43 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.
GitLab Status
Bitbucket Status
npm Registry Status
Netlify Status