Skip to content

Outage tracker / Asana

Is Asana down?

I'm having a problem

Vendor reports no incidentWhat Asana reports

Asana reports no incident on its status page.

As of the last successful poll, 2026-11-05 15:11 UTC.

Asana's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 1 minute ago

Our checks of Asana pass from all 10 regions we check.

As of Nov 5, 2026, 3:14 PM UTC, RealUptime's checks of Asana passed in all 10 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 3:14 PM UTC
US-East536 msChecks passing
US-West772 msChecks passing
Europe487 msChecks passing
Asia-Pacific1484 msChecks passing
US-Central332 msChecks passing
Canada362 msChecks passing
UK768 msChecks passing
Southeast Asia561 msChecks passing
Australia1614 msChecks passing
South America570 msChecks passing
their status pagetheir claim, not our reading

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

from Asana's own status page, checked Nov 5, 2026, 2:27 PM UTC
Asana's own status page shows no incident, and our checks of Asana pass 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
  • AI MeetingsOperational
  • AI MeetingsOperational
  • AI MeetingsOperational
  • AI MeetingsOperational
  • AI MeetingsOperational

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
1.9sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 329ms2026-10-08 UTC: p95 557ms2026-10-09 UTC: p95 288ms2026-10-10 UTC: p95 295ms2026-10-11 UTC: p95 454ms2026-10-12 UTC: p95 280ms2026-10-13 UTC: p95 470ms2026-10-14 UTC: p95 233ms2026-10-15 UTC: p95 245ms2026-10-16 UTC: p95 196ms2026-10-17 UTC: p95 528ms2026-10-18 UTC: p95 1.3s2026-10-19 UTC: p95 1.3s2026-10-20 UTC: p95 1.4s2026-10-21 UTC: p95 623ms2026-10-22 UTC: p95 540ms2026-10-23 UTC: p95 1.3s2026-10-24 UTC: p95 702ms2026-10-25 UTC: p95 640ms2026-10-26 UTC: p95 827ms2026-10-27 UTC: p95 832ms2026-10-28 UTC: p95 837ms2026-10-29 UTC: p95 820ms2026-10-30 UTC: p95 973ms2026-10-31 UTC: p95 1.2s2026-11-01 UTC: p95 1.4s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.1s2026-11-05 UTC: p95 1.9s
Oct 7Oct 21Nov 5
US-West
1.6sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 290ms2026-10-08 UTC: p95 399ms2026-10-09 UTC: p95 477ms2026-10-10 UTC: p95 480ms2026-10-11 UTC: p95 339ms2026-10-12 UTC: p95 369ms2026-10-13 UTC: p95 495ms2026-10-14 UTC: p95 404ms2026-10-15 UTC: p95 458ms2026-10-16 UTC: p95 418ms2026-10-17 UTC: p95 508ms2026-10-18 UTC: p95 599ms2026-10-19 UTC: p95 555ms2026-10-20 UTC: p95 838ms2026-10-21 UTC: p95 660ms2026-10-22 UTC: p95 493ms2026-10-23 UTC: p95 368ms2026-10-24 UTC: p95 761ms2026-10-25 UTC: p95 776ms2026-10-26 UTC: p95 775ms2026-10-27 UTC: p95 1.4s2026-10-28 UTC: p95 1.3s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.5s2026-10-31 UTC: p95 1.6s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.7s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Europe
1.3sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 444ms2026-10-08 UTC: p95 309ms2026-10-09 UTC: p95 385ms2026-10-10 UTC: p95 432ms2026-10-11 UTC: p95 351ms2026-10-12 UTC: p95 322ms2026-10-13 UTC: p95 391ms2026-10-14 UTC: p95 315ms2026-10-15 UTC: p95 396ms2026-10-16 UTC: p95 350ms2026-10-17 UTC: p95 546ms2026-10-18 UTC: p95 717ms2026-10-19 UTC: p95 992ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 338ms2026-10-22 UTC: p95 434ms2026-10-23 UTC: p95 436ms2026-10-24 UTC: p95 498ms2026-10-25 UTC: p95 498ms2026-10-26 UTC: p95 573ms2026-10-27 UTC: p95 562ms2026-10-28 UTC: p95 536ms2026-10-29 UTC: p95 580ms2026-10-30 UTC: p95 612ms2026-10-31 UTC: p95 588ms2026-11-01 UTC: p95 619ms2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.0s2026-11-04 UTC: p95 771ms2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Asia-Pacific
2.0sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 774ms2026-10-08 UTC: p95 772ms2026-10-09 UTC: p95 743ms2026-10-10 UTC: p95 811ms2026-10-11 UTC: p95 738ms2026-10-12 UTC: p95 908ms2026-10-13 UTC: p95 922ms2026-10-14 UTC: p95 679ms2026-10-15 UTC: p95 920ms2026-10-16 UTC: p95 744ms2026-10-17 UTC: p95 1.3s2026-10-18 UTC: p95 1.7s2026-10-19 UTC: p95 1.5s2026-10-20 UTC: p95 2.0s2026-10-21 UTC: p95 1.6s2026-10-22 UTC: p95 1.9s2026-10-23 UTC: p95 689ms2026-10-24 UTC: p95 1.7s2026-10-25 UTC: p95 1.7s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 3.4s2026-10-28 UTC: p95 1.4s2026-10-29 UTC: p95 1.6s2026-10-30 UTC: p95 1.4s2026-10-31 UTC: p95 1.5s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.9s2026-11-04 UTC: p95 2.0s2026-11-05 UTC: p95 2.0s
Oct 7Oct 21Nov 5
US-Central
559msp95 · latest
2s1s0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 822ms2026-10-08 UTC: p95 566ms2026-10-09 UTC: p95 805ms2026-10-10 UTC: p95 486ms2026-10-11 UTC: p95 257ms2026-10-12 UTC: p95 199ms2026-10-13 UTC: p95 289ms2026-10-14 UTC: p95 454ms2026-10-15 UTC: p95 434ms2026-10-16 UTC: p95 396ms2026-10-17 UTC: p95 326ms2026-10-18 UTC: p95 361ms2026-10-19 UTC: p95 464ms2026-10-20 UTC: p95 543ms2026-10-21 UTC: p95 1.8s2026-10-22 UTC: p95 189ms2026-10-23 UTC: p95 913ms2026-10-24 UTC: p95 262ms2026-10-25 UTC: p95 259ms2026-10-26 UTC: p95 235ms2026-10-27 UTC: p95 286ms2026-10-28 UTC: p95 808ms2026-10-29 UTC: p95 228ms2026-10-30 UTC: p95 216ms2026-10-31 UTC: p95 650ms2026-11-01 UTC: p95 516ms2026-11-02 UTC: p95 658ms2026-11-03 UTC: p95 856ms2026-11-04 UTC: p95 890ms2026-11-05 UTC: p95 559ms
Oct 7Oct 21Nov 5
Canada
899msp95 · latest
2s1s0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 516ms2026-10-08 UTC: p95 606ms2026-10-09 UTC: p95 388ms2026-10-10 UTC: p95 363ms2026-10-11 UTC: p95 389ms2026-10-12 UTC: p95 410ms2026-10-13 UTC: p95 508ms2026-10-14 UTC: p95 251ms2026-10-15 UTC: p95 367ms2026-10-16 UTC: p95 366ms2026-10-17 UTC: p95 269ms2026-10-18 UTC: p95 214ms2026-10-19 UTC: p95 232ms2026-10-20 UTC: p95 302ms2026-10-21 UTC: p95 758ms2026-10-22 UTC: p95 265ms2026-10-23 UTC: p95 280ms2026-10-24 UTC: p95 256ms2026-10-25 UTC: p95 282ms2026-10-26 UTC: p95 305ms2026-10-27 UTC: p95 270ms2026-10-28 UTC: p95 302ms2026-10-29 UTC: p95 377ms2026-10-30 UTC: p95 480ms2026-10-31 UTC: p95 713ms2026-11-01 UTC: p95 793ms2026-11-02 UTC: p95 626ms2026-11-03 UTC: p95 1.2s2026-11-04 UTC: p95 671ms2026-11-05 UTC: p95 899ms
Oct 7Oct 21Nov 5
UK
906msp95 · latest
2s1s0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 315ms2026-10-08 UTC: p95 353ms2026-10-09 UTC: p95 395ms2026-10-10 UTC: p95 358ms2026-10-11 UTC: p95 329ms2026-10-12 UTC: p95 356ms2026-10-13 UTC: p95 316ms2026-10-14 UTC: p95 294ms2026-10-15 UTC: p95 632ms2026-10-16 UTC: p95 332ms2026-10-17 UTC: p95 339ms2026-10-18 UTC: p95 333ms2026-10-19 UTC: p95 356ms2026-10-20 UTC: p95 387ms2026-10-21 UTC: p95 326ms2026-10-22 UTC: p95 361ms2026-10-23 UTC: p95 410ms2026-10-24 UTC: p95 851ms2026-10-25 UTC: p95 1.1s2026-10-26 UTC: p95 1.1s2026-10-27 UTC: p95 1.1s2026-10-28 UTC: p95 1.0s2026-10-29 UTC: p95 1.1s2026-10-30 UTC: p95 997ms2026-10-31 UTC: p95 1.1s2026-11-01 UTC: p95 1.1s2026-11-02 UTC: p95 1.0s2026-11-03 UTC: p95 922ms2026-11-04 UTC: p95 1.0s2026-11-05 UTC: p95 906ms
Oct 7Oct 21Nov 5
Southeast Asia
1.6sp95 · latest
2.5s1.3s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 937ms2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1s2026-10-10 UTC: p95 1.1s2026-10-11 UTC: p95 1.2s2026-10-12 UTC: p95 980ms2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.1s2026-10-16 UTC: p95 946ms2026-10-17 UTC: p95 986ms2026-10-18 UTC: p95 953ms2026-10-19 UTC: p95 904ms2026-10-20 UTC: p95 978ms2026-10-21 UTC: p95 1.1s2026-10-22 UTC: p95 971ms2026-10-23 UTC: p95 883ms2026-10-24 UTC: p95 1.5s2026-10-25 UTC: p95 1.3s2026-10-26 UTC: p95 1.5s2026-10-27 UTC: p95 1.9s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.3s2026-10-30 UTC: p95 1.2s2026-10-31 UTC: p95 1.8s2026-11-01 UTC: p95 1.6s2026-11-02 UTC: p95 1.5s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
Australia
2.1sp95 · latest
2.5s1.3s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 1.1s2026-10-08 UTC: p95 1.1s2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 905ms2026-10-11 UTC: p95 830ms2026-10-12 UTC: p95 1.1s2026-10-13 UTC: p95 1.1s2026-10-14 UTC: p95 1.0s2026-10-15 UTC: p95 1.3s2026-10-16 UTC: p95 1.1s2026-10-17 UTC: p95 830ms2026-10-18 UTC: p95 888ms2026-10-19 UTC: p95 954ms2026-10-20 UTC: p95 895ms2026-10-21 UTC: p95 1.7s2026-10-22 UTC: p95 2.0s2026-10-23 UTC: p95 881ms2026-10-24 UTC: p95 2.4s2026-10-25 UTC: p95 2.4s2026-10-26 UTC: p95 2.2s2026-10-27 UTC: p95 2.2s2026-10-28 UTC: p95 2.1s2026-10-29 UTC: p95 1.9s2026-10-30 UTC: p95 2.3s2026-10-31 UTC: p95 2.1s2026-11-01 UTC: p95 2.1s2026-11-02 UTC: p95 2.1s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
South America
1.3sp95 · latest
5s2.5s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-10-07 UTC: p95 773ms2026-10-08 UTC: p95 961ms2026-10-09 UTC: p95 1.1s2026-10-10 UTC: p95 995ms2026-10-11 UTC: p95 1.5s2026-10-12 UTC: p95 875ms2026-10-13 UTC: p95 790ms2026-10-14 UTC: p95 803ms2026-10-15 UTC: p95 620ms2026-10-16 UTC: p95 656ms2026-10-17 UTC: p95 567ms2026-10-18 UTC: p95 525ms2026-10-19 UTC: p95 762ms2026-10-20 UTC: p95 1.1s2026-10-21 UTC: p95 551ms2026-10-22 UTC: p95 671ms2026-10-23 UTC: p95 3.2s2026-10-24 UTC: p95 552ms2026-10-25 UTC: p95 599ms2026-10-26 UTC: p95 2.3s2026-10-27 UTC: p95 2.5s2026-10-28 UTC: p95 2.2s2026-10-29 UTC: p95 2.4s2026-10-30 UTC: p95 2.6s2026-10-31 UTC: p95 2.4s2026-11-01 UTC: p95 2.4s2026-11-02 UTC: p95 2.4s2026-11-03 UTC: p95 1.6s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5

Check your own site while you wait on Asana

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 we measured, function by function

Asana answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the web row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
  • WebsiteUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing

Email me when Asana reports an incident on its status page, and again when it reports it resolved.

Get an email when Asana reports an incident

Email me when Asana reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

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

This is Asana's own statement from its status page, with our regional reading beside it.

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 our checks show, and what people reported

  • North America
    Checks passingUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 536msstatus code: 401checked: Nov 5, 2026, 2:56 PM 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
      Checks passinglatency: 772msstatus code: 401checked: Nov 5, 2026, 2:55 PM 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.
    • US-Central
      Checks passinglatency: 332msstatus code: 401checked: Nov 5, 2026, 3:14 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Asana normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Checks passinglatency: 362msstatus code: 401checked: Nov 5, 2026, 3:12 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Asana normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Checks passinglatency: 570msstatus code: 401checked: Nov 5, 2026, 2:27 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Asana normally. We do not have enough reports from South America to say anything about what people there are seeing.
  • Europe
    Checks passingEurope, UK
    • Europe
      Checks passinglatency: 487msstatus code: 401checked: Nov 5, 2026, 2:46 PM 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.
    • UK
      Checks passinglatency: 768msstatus code: 401checked: Nov 5, 2026, 2:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Asana normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    Checks passingAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1484msstatus code: 401checked: Nov 5, 2026, 3:08 PM 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.
    • Southeast Asia
      Checks passinglatency: 561msstatus code: 401checked: Nov 5, 2026, 2:35 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Asana normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Checks passinglatency: 1614msstatus code: 401checked: Nov 5, 2026, 2:31 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Asana normally. We do not have enough reports from Australia to say anything about what people there are seeing.

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 probe events

Background jobs partial outage, 2h 38mdeclared on their status page2026-10-23
Asana downtime, 37mdeclared on their status page2026-10-21
Partial API outage, 50mdeclared on their status page2026-09-30
Partial API outage in EU, 3h 12mdeclared on their status page2026-09-29
Automations not running for EU users, 1h 10mdeclared on their status page2026-09-21
Slow performance for a subset of Asana users, 36mdeclared on their status page2026-09-17
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

check 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 check readings and Asana's own claim at the time, side by side.

Full check history for Asana: 90 days of check results by region, month-by-month uptime by our checks, and every probe event 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

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Asana uptime by RealUptime's checksLive, from this page's own readings.
[![Asana uptime by RealUptime's checks](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 by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Asana down?", https://realuptime.io/outages/asana. The readings change with every check, so give the date you read them.

What we check

primaryfunctional
https://app.asana.com/api/1.0/users/me
secondary
https://status.asana.com/
secondary
https://asana.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: app.asana.com

RealUptime is not affiliated with Asana; the name identifies what we checked, and nothing here speaks for Asana's own team. We send a single web request to Asana from 10 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 passing check there says an API answered, though it still does not show that every feature of the service works for you. Read the full methodology.