← Live dashboard

AWS UAE issues might affect the ME region

ResolvedminorOfficial source confirmedSingle region affectedFirst recorded update 01-03-2026 21:31 · Resolved 15-03-2026 06:58

This incident has been resolved.

Asana live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

View all comments
    Having problems with Asana now? Check the current status

    Affected services

    AppMobileNotificationsAutomations and Background ActionsWebhooks and Event StreamsAPI

    Updates (9)

    1. 15-03-2026 06:58
      AWS UAE issues might affect the ME region

      This incident has been resolved.

      Asana ↗
    2. 13-03-2026 19:44
      AWS UAE issues might affect the ME region

      A small number of users were affected by the AWS outage in UAE (me-central-1); following AWS's recommendations, we have moved processing to other regions, and believe there is no user impact.

      Asana ↗
    3. 02-03-2026 13:03
      AWS UAE issues might affect the ME region

      We are still seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We are continuing to monitor the situation. The cause is widespread AWS incidents affecting the infrastructure in the Middle East region: https://health.aws.amazon.com/health/status

      Asana ↗
    4. 02-03-2026 11:27
      AWS UAE issues might affect the ME region

      We are still seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We are continuing to monitor the situation. The cause is AWS incidents affecting the infrastructure in the Middle East region: https://health.aws.amazon.com/health/status

      Asana ↗
    5. 02-03-2026 10:05
      AWS UAE issues might affect the ME region

      We are seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We have taken steps to avoid additional loss of EC2 resources, but are continuing to see high error rates. This cause is AWS incidents affecting the infrastructure (az1 and az3) in the Middle East region: https://health.aws.amazon.com/health/status

      Asana ↗
    6. 02-03-2026 10:02
      AWS UAE issues might affect the ME region

      We are continuing to investigate this issue.

      Asana ↗
    7. 01-03-2026 22:03
      AWS UAE issues might affect the ME region

      We no longer see impact on our servers. We're monitoring, as the AWS incident has not resolved.

      Asana ↗
    8. 01-03-2026 22:02
      AWS UAE issues might affect the ME region

      We are continuing to investigate this issue.

      Asana ↗
    9. 01-03-2026 21:31
      AWS UAE issues might affect the ME region

      Asana remains accessible to customers in the ME region, but we are seeing backends impacted by an AWS ME outage. If that isn't resolved soon, we expect to see some performance degradation and possible outages of the Asana application. This is only for the ME region; other regions are unaffected.

      Asana ↗

    What to do next

    • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
    • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
    • Watch the provider going forward. Follow Asana's status feed →

    GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.