Vercel: In-Function Concurrency (Beta) update
Timeline of updates
- resolved
We have identified and resolved an issue impacting a subset of customers in the In-Function Concurrency Beta program. This issue only affects projects deployed between 2025-01-15 09:27 UTC and 14:33 UTC with In-Function Concurrency (Beta) enabled. This issue solely impacts the cost-saving benefits of In-Function Concurrency. The issue has been identified and resolved. To re-enable In-Function Concurrency savings, please redeploy your affected projects.
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-15 09:00 UTC, resolved after 0 min, 1 update(s).
- Title
- In-Function Concurrency (Beta) update
- Vendor
- Vercel
- Date
- URL
- https://rewindex.com/company/vercel/incidents/44xjzdln5t1z
Vercel profileRecent Vercel incidentsAll outages on January 15, 2025Vercel in January 2025MarkdownJSON