Following Vercel Status - Incident History's news feed is very easy. Subscribe using the "follow" button on the top right and if you want to, choose the updates by topic or tag.
We will deliver them to your inbox, your phone, or you can use follow.it like your own online RSS reader. You can unsubscribe whenever you want with one click.
Keep up to date with Vercel Status - Incident History!
Vercel Status - Incident History: Vercel Status
Is this your feed? Claim it!
Mar 3, 21:10 UTCResolved - This incident has been resolved.
Mar 3, 19:14 UTCMonitoring - A fix has been implemented and we are seeing recovery for data loading and ingestion across services. We are continuing to monitor and will provide additional updates as they become available.
Mar 3, 17:10 UTCInvestigating ...
Mar 2, 18:23 UTCMonitoring - We are monitoring the situation and continue to work toward restoring capacity in the dxb1 region. We will send further updates when new information is available.
Mar 2, 15:29 UTCIdentified - Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is current...
Mar 2, 12:08 UTCResolved - This incident was resolved.
Mar 2, 08:49 UTCMonitoring - The dxb1 Edge traffic is currently being rerouted to the nearest Edge region (bom1) to mitigate the impact. We will provide additional updates as they become available.
Mar 2, 08:01 UTCIdentified - We are continuing to work on a...
Mar 2, 11:59 UTCUpdate - We are currently deploying a mitigation for elevated Build errors. Builds that use Middleware or Edge Functions will exclude the Dubai region (dxb1) from their deployment targets as a temporary measure. We will provide additional updates as they become available.
Mar 2, 10:50 UTCUpdate - We are still seeing el...
Mar 1, 21:17 UTCIdentified - Deployments for customers that use Static IPs are failing when deploying functions to the Dubai region. Customers can remove the Dubai region from the Static IPs configuration to avoid deployment failures. Our team is actively investigating the issue. Deployments to other regions are not affected.