Vercel Outage Check
Is Vercel Down Right Now?
✅ Vercel is up and working normally. Checked: 5:10 PM (GMT+8).
Auto-refreshing live data in 60s
| 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 |
| Edge Config | Operational |
| Firewall | Operational |
| FRA1 - Frankfurt, Germany, Europe | Operational |
| Functions | Operational |
| Git Integrations | 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 |
99.833%
Uptime
57m
MTTR
7
Avg Incidents / Mo
90 Days AgoToday
Vercel Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Vercel Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 28m
Affected: Website, DNS Services
Vercel API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 35m
Affected: API Requests, API Portal
Vercel API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 29m
Affected: API Requests, API Portal
Vercel Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 38m
Affected: Website, DNS Services
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.
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 57 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.