Asana Status

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

Resolved: This incident has been resolved.

Monitoring: We've paused some problematic workloads, and we think we're seeing recovery.

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.

Resolved: This incident has been resolved.

Monitoring: We've paused some problematic workloads, and we think we're seeing recovery.

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.

Resolved: This incident has been resolved.

Monitoring: We've paused some problematic workloads, and we think we're seeing recovery.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.

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 DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. 

Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.

Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.

Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

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.

Identified: We are continuing to work on a fix for this issue.

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.

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.