Loading status…
Loading status…
Asana status · Collaboration · checked (8s ago)
No — Asana is not down. All Asana systems are reported operational.
According to Asana's official status page, Asana was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Asana's feed reported no outage in 100.00% of our checks.
Everything above is read from Asana's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Asana in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Asana is work management: tasks, projects, portfolios and workflow automation, used across whole organisations rather than only by engineering. Most of its users are in the web app all day, so an outage is immediately and widely felt.
The status page separates the web and mobile apps from the API and from email notifications and integrations. Asana runs regional data hosting for some customers, and those deployments can be affected independently. Rules and automations are reported separately from the core app, and they fail quietly — nobody notices a rule that did not fire.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Asana's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Asana was down.
14 other services isuptime tracks were also reporting a problem as of the same check, 8s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Asana's status endpoint.
Asana has published 22 incidents in the last 12 months, the 20 most recent shown here. Only what Asana posted itself — not every problem users hit.
resolved · Sep 17, 02:36 PM (2d ago)
postmortem · Sep 2, 06:08 PM (17d ago)
postmortem · Aug 31, 03:14 PM (19d ago)
resolved · Aug 4, 03:30 PM (46d ago)
postmortem · Jul 7, 06:49 PM (74d ago)
postmortem · Apr 21, 07:00 PM (151d ago)
postmortem · Apr 20, 05:00 PM (152d ago)
resolved · Mar 26, 03:03 PM (177d ago)
resolved · Mar 1, 08:31 PM (202d ago)
resolved · Feb 5, 11:49 PM (226d ago)
resolved · Jan 26, 03:01 AM (237d ago)
postmortem · Jan 22, 05:48 PM (240d ago)
resolved · Jan 6, 12:00 AM (257d ago)
resolved · Jan 5, 09:17 PM (257d ago)
resolved · Nov 18, 05:00 PM (305d ago)
postmortem · Nov 18, 11:30 AM (305d ago)
postmortem · Nov 7, 09:22 PM (316d ago)
resolved · Oct 31, 04:17 PM (323d ago)
postmortem · Oct 20, 02:28 PM (334d ago)
postmortem · Oct 20, 07:10 AM (334d ago)
A task that vanished has usually been moved or filtered out of the view rather than deleted; check the project's filters and the task's sections. Notification emails not arriving is frequently your mail provider. API integrations failing after a while are often an expired personal access token, which produces a 401 that reads like an outage.
Asana is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.