minor impact Vercel โœ“ Resolved

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

Started
2026-03-02 15:29 UTC
Resolved
2026-03-16 18:44 UTC
Duration
20354 minutes
Date
2026-03-02

Incident Timeline

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

identified 2026-03-02 15:29 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

monitoring 2026-03-02 18:23 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

resolved 2026-03-16 18:44 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.

โ† All Vercel incidents Other incidents on 2026-03-02