What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Asana now? Check the current statusAffected services
Updates (12)
- 02-08-2024 02:16Application and API errors
**Incident:** On 2024-08-01 at 14:09 UTC, an increased connection rate on a central database saturated the database’s ability to accept new connections. As a result, Asana became unavailable to users in all regions. In response, Asana engineers throttled traffic for automations, webhooks, and API, and were able to restore primary functionality of the Asana application at 15:01 UTC. The application continued to run with sporadic unavailability until 18:22 UTC, when the underlying cause of the increased connections was determined and disabled. At this point the application was fully operational
Asana ↗ - 01-08-2024 21:49Application and API errors
This incident has been resolved.
Asana ↗ - 01-08-2024 20:35Application and API errors
We've identified the root cause and are monitoring our systems
Asana ↗ - 01-08-2024 20:13Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 19:33Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 19:05Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 19:03Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 18:58Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 18:37Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 18:34Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 18:04Application and API errors
We are continuing to work on a fix for this issue.
Asana ↗ - 01-08-2024 17:21Application and API errors
We are investigating application issues related to overload, and will provide updates.
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.
View all comments