← Back to Asana's check readings
We started checking Asana on August 20, 2026, which is 62 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Asana reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Asana's own status page declared. Below it, any public chatter we saw about Asana and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Asana's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Asana in the last 24 hours, which is not evidence that nothing is wrong.
Asana's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Asana's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Asana next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Their declared record
Asana's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Partial API outagePartial outage
Sep 30, 2026, 2:31 PM UTC to Sep 30, 2026, 3:21 PM UTC (50 min)resolved
their latest update (Sep 30, 2026, 3:21 PM UTC): This incident has been resolved.
Partial API outage in EUMinor incident
Sep 29, 2026, 12:14 PM UTC to Sep 29, 2026, 3:25 PM UTC (3h 12m)resolved
their latest update (Sep 29, 2026, 3:25 PM UTC): The incident has been resolved.
Automations not running for EU usersMinor incident
Sep 21, 2026, 2:59 PM UTC to Sep 21, 2026, 4:10 PM UTC (1h 10m)resolved
their latest update (Sep 21, 2026, 4:10 PM UTC): This incident has been resolved.
Slow performance for a subset of Asana usersMinor incident
Sep 17, 2026, 2:36 PM UTC to Sep 17, 2026, 3:13 PM UTC (36 min)resolved
their latest update (Sep 17, 2026, 3:13 PM UTC): This incident has been resolved.
We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.Partial outage
Sep 2, 2026, 6:08 PM UTC to Sep 2, 2026, 6:49 PM UTC (42 min)postmortem published
their latest update (Sep 4, 2026, 7:52 PM UTC): Incident: An internal system responsible for automatically scaling backend server capacity in one of our compute clusters stopped replacing capacity that had been cycled out during routine maintenance. This caused a gradual reduction in available capacity over several hours. A su…
Asana full outage for some users (2 hours, 25% outage)Partial outage
Aug 31, 2026, 3:14 PM UTC to Aug 31, 2026, 5:18 PM UTC (2h 4m)postmortem published
their latest update (Sep 2, 2026, 9:29 PM UTC): We’ve been working to add a caching layer to our update pipeline, tuning it carefully and rolling it out gradually. On Wednesday, August 26 we enabled it for most use cases, and it initially performed well.
On Monday, August 31, a combination of unrelated infrastructure changes …
Webhooks and event streams partial data lossMinor incident
Aug 4, 2026, 3:30 PM UTC to Aug 4, 2026, 3:30 PM UTC (0 min)resolved
their latest update (Aug 4, 2026, 3:30 PM UTC): From 2026-08-04 15:25 UTC until 2026-08-06 03:51 UTC, Asana failed to send some events to registered webhooks and to return them in the event streams API. Apps which rely on this should refetch the underlying data from the Asana API. Existing webhooks and event streams will conti…
Errors loading the Asana web app for some users in USPartial outage
Jul 7, 2026, 6:49 PM UTC to Jul 7, 2026, 7:24 PM UTC (35 min)postmortem published
their latest update (Jul 8, 2026, 9:28 PM UTC): **Incident**: A configuration change inadvertently removed a critical resource required by one of our services. While existing infrastructure continued to operate normally, newly scaled infrastructure could not become ready. As morning traffic increased, there was a growing gap b…
Date Time Trigger Automation FailuesAll systems operational
Apr 21, 2026, 7:00 PM UTC to Apr 21, 2026, 7:00 PM UTC (0 min)postmortem published
their latest update (Apr 30, 2026, 12:43 AM UTC): Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour dela…
Notifications and Background Actions delayed in EUAll systems operational
Apr 20, 2026, 5:00 PM UTC to Apr 20, 2026, 5:00 PM UTC (0 min)postmortem published
their latest update (Apr 30, 2026, 12:34 AM UTC): Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour dela…
Showing the 10 most recent of 56 incidents Asana has declared in the history we hold.
These entries are Asana's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Asana's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.