Dubai region (dxb1) is unavailable and traffic is being re-routed

What to do

• Check whether you use Vercel DXB1 - Dubai, UAE in me. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 14d 3h it lasted.

  Anything that failed between 2026-03-02 15:29 UTC and 2026-03-16 18:44 UTC may need a replay.

• Subscribe to Vercel's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vercel works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vercel 3

1. identifiedMar 2, 2026, 3:29 PM UTC

   Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments. If your existing deployments that use the dxb1 region are experiencing elevated function invocation errors, we strongly recommend switching to the nearest region (such as bom1) and redeploy until capacity is restored in dxb1. Deployments using multiple regions or failover regions are not affected since traffic is automatically routed to the nearest region based on the configured settings.

   provider

2. monitoringMar 2, 2026, 6:23 PM UTC

   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.

   provider

3. resolvedMar 16, 2026, 6:44 PM UTC

   Due to ongoing issues in the dxb1 region, traffic and regional Vercel services are currently re-routed to bom1. We will share more details on recovery when they become available.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.