Get told when Vercel breaks
One email when Vercel reports an incident, one when it is resolved. No account, nothing else.
Used only for Vercel status alerts. Every email carries an unsubscribe link.
Vercel components
56 of 56 operational
Show all 56 components
- DashboardOperational
- BuildsOperational
- ARN1 - Stockholm, SwedenOperational
- DrainsOperational
- BuildsOperational
- BlobOperational
- Output GenerationOperational
- AI GatewayOperational
- APIOperational
- BOM1 - Mumbai, IndiaOperational
- LogsOperational
- Global ConfigOperational
- npm RegistryOperational
- Support CenterOperational
- DashboardOperational
- CDG1 - Paris, France, EuropeOperational
- Deploy HooksOperational
- Support ChatOperational
- ObservabilityOperational
- CLE1 - Cleveland, East USOperational
- Git IntegrationsOperational
- Speed InsightsOperational
- CPT1 - Cape Town, South AfricaOperational
- Web AnalyticsOperational
- DUB1 - Dublin, IrelandOperational
- CommunityOperational
- Integration WebhooksOperational
- Cron JobsOperational
- DXB1 - Dubai, UAEOperational
- FRA1 - Frankfurt, Germany, EuropeOperational
- GRU1 - São Paulo, BrazilOperational
- Data CacheOperational
- DNSOperational
- HKG1 - Hong KongOperational
- Domain RegistrationOperational
- HND1 - Tokyo, JapanOperational
- IAD1 - Washington DC, USAOperational
- FirewallOperational
- ICN1 - Seoul, South KoreaOperational
- FunctionsOperational
- Image OptimizationOperational
- KIX1 - Osaka, JapanOperational
- LHR1 - London, UKOperational
- PDX1 - Portland, West USOperational
- SFO1 - San Francisco, CA, USAOperational
- MarketplaceOperational
- SIN1 - SingaporeOperational
- QueuesOperational
- SYD1 - Sydney, AustraliaOperational
- Remote CachingOperational
- Routing MiddlewareOperational
- YUL1 - Montréal, CanadaOperational
- SAML Single Sign-OnOperational
- SandboxOperational
- TLS CertificatesOperational
- WorkflowOperational
Recent Vercel incidents
The most recent incidents Vercel has published, newest first.
- major
Failures logging in with Vercel CLI
Resolved in 1h 22m
- minor
Elevated build initialization times
Resolved in 38m
- major
New container functions are failing
Resolved in 47m
- major
Logs unavailable to query in Dashboard
Resolved in 11m
- none
Elevated errors for Workflow streams
Resolved in 0m
- minor
Partial disruption of Observability, Analytics, Firewall, Usage, and Login in Dashboard
Resolved in 6h 55m
- none
Dynamic API routes returned 404 errors for some deployments
Resolved in 0m
- minor
Delays delivering log drains
Resolved in 1h 53m
Vercel status: common questions
- Is Vercel down right now?
- Vercel is not reporting any problems. All 56 components are operational. No incident is open. This page mirrors the official Vercel status feed. PingView last read it on August 31, 2026 at 12:35 PM UTC.
- Where does this Vercel status data come from?
- Directly from the official Vercel status page at www.vercel-status.com. PingView polls that feed, records every incident it publishes and keeps a permanent, dated history that the vendor page itself does not retain.
- How often is this page updated?
- PingView reads the official Vercel feed and rebuilds this page every 5 minutes. The timestamp of the last successful read is shown next to the status, so you can tell how fresh the answer is.
- Vercel reports everything as operational, but my integration is failing. What now?
- A vendor status page is a global signal, not a per customer one. Partial failures, regional routing problems and issues that hit a single account often never appear on it. Check the Vercel endpoints your own product calls, from more than one region, and compare your timeline against the vendor's. That is what PingView does, and the SLA calculator turns the resulting downtime into a number you can put in front of a client.