Skip to content

Which companies just had a verified incident, who lends to them and who owns them. Every claim carries its evidence level and its source. How we decide what is confirmed

US critical infrastructure monitor

Asana

Cloud, identity and critical software · CA (headquarters)

Monitoring
Not checked: the site's robots.txt does not allow it.: last success Nov 6 12:35 UTC
Public findings
0
Provider status posts on record
50

Cyber and operational findings

Analyst-reviewed records. The grade states how well the cause is established; event, first public observation and acknowledgement are separate dates.

No public findings for this organisation.

Provider status posts

Collected from the organisation's own public status page. These are its words; DFX adds only the wording classification.

  • Background jobs partial outageOct 23 23:57 UTC · resolved · major impact
    Service restricted or degradedRestoration reported
    1. Oct 23 23:57 UTC investigating: We have a significant degradation in our system for processing asynchronous work. We previously had some crashes from web application users, but that appears to have resolved. We're monitoring the asynchronous work.
    2. Oct 24 00:03 UTC monitoring: We've paused some problematic workloads, and we think we're seeing recovery.
    3. Oct 24 02:35 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • Asana downtimeOct 21 15:33 UTC · postmortem · major impact
    Service restricted or degradedRestoration reported
    1. Oct 21 15:33 UTC identified: Asana services are currently experiencing a major service disruption. We have identified a likely cause and are working on applying a fix. This affects all services and all regions.
    2. Oct 21 15:51 UTC identified: We have identified the cause of this outage and have initiated changes to address this. We are seeing some signs of recovery, and will post an update once we've confirmed recovery.
    3. Oct 21 16:08 UTC identified: We are continuing to work on a fix for this issue.
    4. Oct 21 16:10 UTC resolved: The fix has been applied. We have observed recovery of error rates and traffic, and believe this incident is now resolved. We will post a postmortem/RCA within 72 hours.
    5. Oct 24 00:22 UTC postmortem: **Incident:** An infrastructure update targeting security caused DynamoDB to become inaccessible across Asana's production environment. This change was related to a production isolation initiative, and was applied in a way that left all of our production services unable to use...
    View on the provider's status page
  • Partial API outageSep 30 14:31 UTC · resolved · major impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Sep 30 14:31 UTC investigating: We are currently investigating this issue.
    2. Sep 30 15:09 UTC identified: We are currently seeing system recovery and are actively monitoring the situation to ensure a full recovery.
    3. Sep 30 15:21 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • Partial API outage in EUSep 29 12:14 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Sep 29 12:14 UTC investigating: We are currently investigating the issue.
    2. Sep 29 15:25 UTC resolved: The incident has been resolved.
    View on the provider's status page
  • Automations not running for EU usersSep 21 14:59 UTC · resolved · minor impact
    Restoration reported
    1. Sep 21 14:59 UTC identified: We've heard reports of rules and automations not running in the EU region. We've identified the source of the issue and fixed it for new automations triggers going forward. Our engineers are currently working on the backlog of automations that triggered and did not run during...
    2. Sep 21 15:00 UTC identified: We are continuing to work on a fix for this issue.
    3. Sep 21 15:39 UTC monitoring: We're currently working our way through the backlog of automations that did not run.
    4. Sep 21 16:10 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • Slow performance for a subset of Asana usersSep 17 14:36 UTC · resolved · minor impact
    Investigation mentionedRestoration reported
    1. Sep 17 14:36 UTC investigating: We received an alert for unusual slow performance in several regions. We're investigating.
    2. Sep 17 15:12 UTC investigating: We are continuing to investigate this issue.
    3. Sep 17 15:13 UTC resolved: This incident has been resolved.
    View on the provider's status page
  • We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.Sep 2 18:08 UTC · postmortem · major impact
    Investigation mentionedRestoration reported
    1. Sep 2 18:08 UTC investigating: We are currently investigating this issue.
    2. Sep 2 18:13 UTC investigating: We are continuing to investigate this issue.
    3. Sep 2 18:14 UTC investigating: The rollback seems to have completely resolved errors. We're monitoring closely, but users should be able to access Asana again.
    4. Sep 2 18:14 UTC monitoring: A fix has been implemented and we are monitoring the results.
    5. Sep 2 18:49 UTC resolved: This incident has been resolved.
    6. Sep 4 19:52 UTC postmortem: 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...
    View on the provider's status page
  • Asana full outage for some users (2 hours, 25% outage)Aug 31 15:14 UTC · postmortem · major impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    1. Aug 31 15:14 UTC investigating: We are investigating alerts for slow performance and application errors.
    2. Aug 31 15:55 UTC investigating: We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.
    3. Aug 31 16:24 UTC investigating: We have made configuration changes and see partial recovery, but we continue to see some elevated errors.
    4. Aug 31 16:47 UTC monitoring: We've applied a fix are seeing signs of recovery.
    5. Aug 31 17:18 UTC resolved: User-facing symptoms have recovered. We'll continue to monitor, and will prioritize a retrospective to understand and prevent similar incidents in the future.
    6. Sep 2 21:29 UTC postmortem: 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...
    View on the provider's status page
  • Webhooks and event streams partial data lossAug 4 15:30 UTC · resolved · minor impact
    No classified wording
    1. Aug 6 17:24 UTC resolved: 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...
    View on the provider's status page
  • Errors loading the Asana web app for some users in USJul 7 18:49 UTC · postmortem · major impact
    Service restricted or degradedRestoration reported
    1. Jul 7 18:49 UTC identified: We are seeing errors for part (about 10%) of users in US for the Asana webapp. We've identified the root cause and are working on identifying a resolution.
    2. Jul 7 19:12 UTC monitoring: We have implemented a mitigation and are monitoring to ensure recovery.
    3. Jul 7 19:21 UTC monitoring: We are continuing to monitor for any further issues.
    4. Jul 7 19:24 UTC resolved: This incident has been resolved.
    5. Jul 8 21:28 UTC postmortem: **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...
    View on the provider's status page
  • Date Time Trigger Automation FailuesApr 21 19:00 UTC · postmortem
    Service restricted or degraded
    View on the provider's status page
  • Notifications and Background Actions delayed in EUApr 20 17:00 UTC · postmortem
    Service restricted or degraded
    View on the provider's status page
  • Errors loading AsanaMar 26 15:03 UTC · resolved
    Service taken offlineInvestigation mentionedRestoration reported
    View on the provider's status page
  • AWS UAE issues might affect the ME regionMar 1 20:31 UTC · resolved
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • API monitoringFeb 5 23:49 UTC · resolved
    Service restricted or degradedRestoration reported
    View on the provider's status page
  • EU App and API issuesJan 26 03:01 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Asana webapp unavailableJan 22 17:48 UTC · postmortem · critical impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • Issues in with Asana in non-US regionsJan 6 00:00 UTC · resolved
    Service restricted or degraded
    View on the provider's status page
  • Downtime for the Asana web appJan 5 21:17 UTC · resolved · major impact
    Investigation mentionedRestoration reported
    View on the provider's status page
  • Permissions bug between 2025-11-18 and 2025-11-19Nov 18 17:00 UTC · resolved
    Restoration reported
    View on the provider's status page
  • Partial downtime for Asana's MCP serverNov 18 11:30 UTC · postmortem
    Service restricted or degradedProvider used security languageInvestigation mentionedRestoration reported
    View on the provider's status page
  • Asana downtime in all regionsNov 7 21:22 UTC · postmortem · critical impact
    Service restricted or degradedRestoration reported
    View on the provider's status page
  • Issues in with Asana in EU regionOct 31 16:17 UTC · resolved · minor impact
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • App DownOct 20 14:28 UTC · postmortem
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page
  • App DownOct 20 07:10 UTC · postmortem
    Service restricted or degradedInvestigation mentionedRestoration reported
    View on the provider's status page