Vercel: Serverless Functions deployed to incorrect region
Timeline of updates
- resolved
Between 16:04 and 18:33 (UTC) on January 21st, a small subset of deployments created Serverless Functions in the sfo1 (San Francisco, USA/us-west-1) region instead of their specified region. All functions remained fully operational during this period, with some users experiencing slightly elevated latency. Vercel's systems have automatically relocated the affected functions to their correct regions. No action is required from customers.
From Vercel’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on www.vercel-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Vercel, started 2025-01-21 18:32 UTC, resolved after 0 min, 1 update(s).
- Title
- Serverless Functions deployed to incorrect region
- Vendor
- Vercel
- Date
- URL
- https://rewindex.com/company/vercel/incidents/dl8gldnfqcnx
Vercel profileRecent Vercel incidentsAll outages on January 21, 2025Vercel in January 2025MarkdownJSON