Skip to content

Outage tracker / Asana

Is Asana down?

I'm having a problem

Operationalchecked 8 minutes ago

We reached Asana from all 4 regions we check.

Functional endpoints verified

No outage recorded in the 14 days we have measured Asana (since Aug 20, 2026).

our independent probeslive · checked Sep 3, 2026, 1:22 AM UTC
US-East443 msOperational
US-West128 msOperational
Europe194 msOperational
Asia-Pacific711 msOperational
their status pagetheir claim, not our reading

Asana reports: All systems operational (“All Systems Operational”)

from Asana's own status page, checked Sep 3, 2026, 12:26 AM UTC
Our probes and Asana's own status page agree: both show Asana as reachable right now.

Asana's own component breakdown, as they publish it

  • AppOperational
  • AppOperational
  • AppOperational
  • AppOperational
  • AppOperational
  • APIOperational
  • APIOperational
  • APIOperational
  • APIOperational
  • APIOperational
  • MobileOperational
  • MobileOperational
  • MobileOperational
  • MobileOperational
  • MobileOperational
  • Automations and Background ActionsOperational
  • Automations and Background ActionsOperational
  • Automations and Background ActionsOperational
  • Automations and Background ActionsOperational
  • Automations and Background ActionsOperational
  • Webhooks and Event StreamsOperational
  • Webhooks and Event StreamsOperational
  • Webhooks and Event StreamsOperational
  • Webhooks and Event StreamsOperational
  • Webhooks and Event StreamsOperational
  • NotificationsOperational
  • NotificationsOperational
  • NotificationsOperational
  • NotificationsOperational
  • NotificationsOperational

These are Asana's components, named and scored by Asana. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Asana's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Asana response time, by region

US-East
553msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 332ms2026-08-21 UTC: p95 255ms2026-08-22 UTC: p95 373ms2026-08-23 UTC: p95 531ms2026-08-24 UTC: p95 554ms2026-08-25 UTC: p95 556ms2026-08-26 UTC: p95 389ms2026-08-27 UTC: p95 393ms2026-08-28 UTC: p95 454ms2026-08-29 UTC: p95 607ms2026-08-30 UTC: p95 532ms2026-08-31 UTC: p95 514ms2026-09-01 UTC: p95 180ms2026-09-02 UTC: p95 616ms2026-09-03 UTC: p95 553ms
Aug 5Aug 19Sep 3
US-West
299msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 587ms2026-08-21 UTC: p95 342ms2026-08-22 UTC: p95 302ms2026-08-23 UTC: p95 369ms2026-08-24 UTC: p95 439ms2026-08-25 UTC: p95 415ms2026-08-26 UTC: p95 462ms2026-08-27 UTC: p95 492ms2026-08-28 UTC: p95 627ms2026-08-29 UTC: p95 416ms2026-08-30 UTC: p95 392ms2026-08-31 UTC: p95 443ms2026-09-01 UTC: p95 451ms2026-09-02 UTC: p95 502ms2026-09-03 UTC: p95 299ms
Aug 5Aug 19Sep 3
Europe
217msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 343ms2026-08-21 UTC: p95 336ms2026-08-22 UTC: p95 337ms2026-08-23 UTC: p95 459ms2026-08-24 UTC: p95 419ms2026-08-25 UTC: p95 429ms2026-08-26 UTC: p95 377ms2026-08-27 UTC: p95 483ms2026-08-28 UTC: p95 396ms2026-08-29 UTC: p95 425ms2026-08-30 UTC: p95 580ms2026-08-31 UTC: p95 553ms2026-09-01 UTC: p95 599ms2026-09-02 UTC: p95 441ms2026-09-03 UTC: p95 217ms
Aug 5Aug 19Sep 3
Asia-Pacific
727msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 689ms2026-08-21 UTC: p95 832ms2026-08-22 UTC: p95 776ms2026-08-23 UTC: p95 1.2s2026-08-24 UTC: p95 1.2s2026-08-25 UTC: p95 1.2s2026-08-26 UTC: p95 937ms2026-08-27 UTC: p95 1.2s2026-08-28 UTC: p95 971ms2026-08-29 UTC: p95 955ms2026-08-30 UTC: p95 998ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 1.1s2026-09-02 UTC: p95 1.2s2026-09-03 UTC: p95 727ms
Aug 5Aug 19Sep 3

Is it Asana, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Asana -- it cannot diagnose Asana's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • US-East
    Operationallatency: 443msstatus code: 401checked: Sep 3, 2026, 12:43 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Asana normally. We do not have enough reports from US-East to say anything about what people there are seeing.
  • US-West
    Operationallatency: 128msstatus code: 401checked: Sep 3, 2026, 12:43 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Asana normally. We do not have enough reports from US-West to say anything about what people there are seeing.
  • Europe
    Operationallatency: 194msstatus code: 401checked: Sep 3, 2026, 1:22 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Asana normally. We do not have enough reports from Europe to say anything about what people there are seeing.
  • Asia-Pacific
    Operationallatency: 711msstatus code: 401checked: Sep 3, 2026, 1:22 AM UTC
    0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Asana normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
  • US-Central
    Not monitored from this regionAsana is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Canada
    Not monitored from this regionAsana is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • UK
    Not monitored from this regionAsana is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Southeast Asia
    Not monitored from this regionAsana is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Australia
    Not monitored from this regionAsana is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionAsana is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Asana, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Asana yet, which is not evidence that nothing is wrong.

Recent outages

We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment., 42mdeclared on their status page2026-09-02
Asana full outage for some users (2 hours, 25% outage), 2h 4mdeclared on their status page2026-08-31
Webhooks and event streams partial data loss, 1mdeclared on their status page2026-08-04
Errors loading the Asana web app for some users in US, 35mdeclared on their status page2026-07-07
Date Time Trigger Automation Failues, 1mdeclared on their status page2026-04-29
Notifications and Background Actions delayed in EU, 1mdeclared on their status page2026-04-29
Errors loading Asana, 3h 31mdeclared on their status page2026-03-26
AWS UAE issues might affect the ME region, 321h 28mdeclared on their status page2026-03-01

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Asana since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Asana covering any window you pick, with our measurements and Asana's own claim at the time, side by side.

Full availability history for Asana: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Asana, and again when they can reach it again. That is our own measurement from ten regions, not Asana's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Asana uptime measured by RealUptimeLive, from this page's own readings.
[![Asana uptime measured by RealUptime](https://realuptime.io/outages/asana/badge.svg?days=30)](https://realuptime.io/outages/asana)
<a href="https://realuptime.io/outages/asana"><img src="https://realuptime.io/outages/asana/badge.svg?days=30" alt="Asana uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Asana's SLA implies, from our measurement

At or above your target

We measured none of downtime for Asana over the 337h 30m since we started watching it on 2026-08-20, which is 100% uptime by our reading. A 99.9% target allows 20 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from Asana's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://app.asana.com/api/1.0/users/me
secondary
https://status.asana.com/
RealUptime is not affiliated with Asana; the name identifies what we measured, and nothing here speaks for Asana's own team. We send a single web request to Asana from 4 regions on our own schedule and time the response. We do not see inside Asana's systems, do not use an account or real transaction, and are not the same signal Asana's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Asana is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Asana operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. Read the full methodology.