VercelStatus record
Latest recorded vendor status
Source checked
A recorded report, not a live test of your application.
Open official status pageCheck the product, region and time against your own logs.
Check counts and incident historyComponent records
Vendor products and regions, with issue records listed first.
| Product / region | Recorded status | Record last seen |
|---|---|---|
Support Chat | Operational | |
SYD1 - Sydney, Australia | Operational | |
TLS Certificates | Operational | |
v0 | Operational | |
Web Analytics | Operational | |
Workflow | Operational | |
YUL1 - Montréal, Canada | Operational |
- Operational
Support Chat
Record last seen - Operational
SYD1 - Sydney, Australia
Record last seen - Operational
TLS Certificates
Record last seen - Operational
v0
Record last seen - Operational
Web Analytics
Record last seen - Operational
Workflow
Record last seen - Operational
YUL1 - Montréal, Canada
Record last seen
61 to 67 of 67 components
“Last seen” is saved when a component changes or its record is refreshed. It is not the time of every status check. These records can differ from the vendor’s overall report.
Recent incidents
Past 30 days
Started or first observed in this window. A record may close when a post disappears or our tracking period expires; this does not confirm recovery. A missing closure time does not confirm an ongoing outage.
Increased build and deployment failures
Started
Closed in record
Delays in Drains, Observability, and Workflow in Washington (iad1)
Started
Closed in record
Vercel Auth login failures for pages with Deployment Protection enabled
Started
Closed in record
Elevated Sandbox error rates in Paris (cdg1)
Started
Closed in record
Build failures and 500 errors for functions using Edge runtime
Started
Closed in record
Deployment stuck in initializing state
Started
Closed in record
Elevated Errors Triggering Deployments
Started
Closed in record
Maintenance and future scheduled work are excluded.
Explore reliability history