SAML Login Failures
Final update
**Incident:** From April 4 to April 8, 2025, a subset of users were blocked from logging in with SAML, despite no changes to their identity provider setup. We believe the root cause to be a combination of recent code changes upgrading our infrastructure. These changes inadvertently affected how SAML responses were processed. **Impact:** Approximately 0.5% of users who authenticate through SAML were unable to log in to their Asana accounts during this period. No customer data was lost or compromised, and users who do not use SAML were unaffected. Our Customer Support team worked with affected domains to restore access while we resolved the issue. **Moving forward:** Our existing monitors did not trigger for this incident, which led to an extended period of downtime. We are improving existing monitoring and increasing monitor coverage to allow us to detect and respond to authentication issues more quickly in the future. 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.
Timeline
- Postmortem · Apr 16, 22:47 UTC
**Incident:** From April 4 to April 8, 2025, a subset of users were blocked from logging in with SAML, despite no changes to their identity provider setup. We believe the root cause to be a combination of recent code changes upgrading our infrastructure. These changes inadvertently affected how SAML responses were processed. **Impact:** Approximately 0.5% of users who authenticate through SAML were unable to log in to their Asana accounts during this period. No customer data was lost or compromised, and users who do not use SAML were unaffected. Our Customer Support team worked with affected domains to restore access while we resolved the issue. **Moving forward:** Our existing monitors did not trigger for this incident, which led to an extended period of downtime. We are improving existing monitoring and increasing monitor coverage to allow us to detect and respond to authentication issues more quickly in the future. 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 · Apr 8, 22:47 UTC
From April 4th to April 8th, approximately 0.5% of users using SAML for authentication experienced errors during login.
More from Asana
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2114:59 UTC | Automations not running for EU users | minor | 1h 10m |
| Sep 1714:36 UTC | Slow performance for a subset of Asana users | minor | 36m |
| Sep 218:08 UTC | We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment. | major | 42m |
| Aug 3115:14 UTC | Asana full outage for some users (2 hours, 25% outage) | major | 2h 4m |
| Aug 415:30 UTC | Webhooks and event streams partial data loss | minor | 0m |
| Jul 718:49 UTC | Errors loading the Asana web app for some users in US | major | 35m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.