Is there an SecureAuth outage?
SecureAuth status: Systems Active
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for SecureAuth and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for SecureAuth and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for SecureAuth.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Operator Alerts | Active |
| CIAM | Active |
| Application | Active |
| AU Region | Active |
| EU Region | Active |
| Push | Active |
| SMS | Active |
| US Region | Active |
| Voice | Active |
| Passwordless | Active |
| Application | Active |
| Device Trust | Active |
| Mobile App | Active |
| Push | Active |
| SMS | Active |
| Voice | Active |
| SaaS/Full Cloud Components | Active |
| SaaS/Full Cloud Identity Platform | Active |
| SecureAuth Connector | Active |
| SecureAuth Cloud Services | Active |
| 3rd Party Mobile Carrier | Active |
| Enhanced Geolocation Resolution Service - US1 | Active |
| Enhanced Geolocation Resolution Service - US2 | Active |
| Fraud Service - US1 | Active |
| Fraud Service - US2 | Active |
| Geolocation Resolution Service - US1 | Active |
| Geolocation Resolution Service - US2 | Active |
| Nexmo Voice API | Active |
| Push-to-Accept Service - US1 | Active |
| Push-to-Accept Service - US2 | Active |
| SMS Service - US1 | Active |
| SMS Service - US2 | Active |
| Telephony Extension/DTMF Service - US1 | Active |
| Telephony Extension/DTMF Service - US2 | Active |
| Telephony Provider SMS API | Active |
| Telephony Service - US1 | Active |
| Telephony Service - US2 | Active |
| Threat Service - US1 | Active |
| Threat Service - US2 | Active |
| X.509 Certificate Service (SHA2) - US1 | Active |
| X.509 Certificate Service (SHA2) - US2 | Active |
| SecureAuth IdP Frontend Services | Active |
| SecureAuth Application Templates | Active |
| SecureAuth Web Admin | Active |
| SecureAuth Polaris Services | Active |
| FIDO Service | Active |
| Mobile Services | Active |
| Polaris Base Infrastructure | Active |
| SaaS IdP Broker | Active |
| SecureAuth Titan Services | Active |
| Dashboard Service | Active |
| Device Enrollment Service | Active |
| Fraud Service | Active |
| IP Blocking Service | Active |
| IP Intel Service | Active |
| IP Reporting Service | Active |
| Licensing Service | Active |
| Link-to-Accept Service | Active |
| OAuth Service | Active |
| Push-to-Accept Service | Active |
| SMS Service | Active |
| Symbol-to-Accept Service | Active |
| Telephony Service | Active |
| Titan Proxy Services (SA IdP 9.3 and older only) | Active |
| Transaction Service | Active |
| User Risk Scoring Service | Active |
| User Risk Service | Active |
| User Stats Service | Active |
| Workforce | Active |
| Certificate Enrollment | Active |
| Cloud IdP | Active |
| Dashboard | Active |
| FIDO WebAuthn | Active |
| Kerberos Authentication | Active |
| Link-to-Accept Service | Active |
| Mobile App | Active |
| Push | Active |
| SMS | Active |
| Voice | Active |
View the latest incidents for SecureAuth and check for official updates:
Description: We apologize for any inconvenience experienced during this incident, and we treat such disruptions seriously. Below is a summary of the issue, a root cause, and what we are doing to improve service going forward. Incident Description A TLS certificate that is used on an endpoint for SA IdP dashboard metric data collection expired on May 9. This meant HTTPS connections to this endpoint failed and caused SA IdP dashboard metric data to become outdated, degrading service for part of the administrative console. After some customers reported an issue with outdated metrics, the SecureAuth team investigated and fixed the issue by renewing the TLS certificate. The new certificate was in place by 6:10 PM on May 12. Data was refreshed around 1:30 AM on May 13, allowing the normal metric refresh period to run its course. Root Cause The DevOps team recently replaced several expiring certificates, and this one was missed due to a monitoring gap. Corrective Actions The DevOps team is following up by ensuring the TLS certificate monitoring gap is addressed and by reviewing additional monitoring requirements for the endpoint in question. Note: All times/dates are UTC.
Status: Postmortem
Impact: Minor | Started At: May 12, 2023, 5:32 p.m.
Description: We apologize for any inconvenience experienced during this incident, and we treat such disruptions seriously. Below is a summary of the issue, a root cause, and what we are doing to improve service going forward. Incident Description A TLS certificate that is used on an endpoint for SA IdP dashboard metric data collection expired on May 9. This meant HTTPS connections to this endpoint failed and caused SA IdP dashboard metric data to become outdated, degrading service for part of the administrative console. After some customers reported an issue with outdated metrics, the SecureAuth team investigated and fixed the issue by renewing the TLS certificate. The new certificate was in place by 6:10 PM on May 12. Data was refreshed around 1:30 AM on May 13, allowing the normal metric refresh period to run its course. Root Cause The DevOps team recently replaced several expiring certificates, and this one was missed due to a monitoring gap. Corrective Actions The DevOps team is following up by ensuring the TLS certificate monitoring gap is addressed and by reviewing additional monitoring requirements for the endpoint in question. Note: All times/dates are UTC.
Status: Postmortem
Impact: Minor | Started At: May 12, 2023, 5:32 p.m.
Description: # Incident Description At 4/28/2023 3:15 AM UTC, the DevOps team did a planned, minor update to traffic management appliances during a maintenance window. While no downtime was expected and all configurations were tested in lower environments, the new update in production did not respect TLS cipher suite configuration as expected. This created a TLS negotiation issue between the SA IdP appliances and the traffic management appliances, blocking some logins from occurring. Unfortunately, the post-change test suite did not detect the issue. After hearing about difficulties from some customer reports and first-hand observations, the DevOps team identified the issue and rolled back the change to restore service at 4:15 AM UTC \(4/28/23\). # Root Cause An update to the update to traffic management appliances did not obey a declarative configuration for TLS cipher suites. This caused a TLS negotiation failure between SA IdP appliances and the traffic management appliances, blocking some logins. # Corrective Actions We apologize for any inconvenience caused during this disruption in service. The SecureAuth team will pause any further changes to the traffic management appliances until we have sorted out the associated configuration issue \(which we plan to solve in the next few weeks\). In addition, any future updates done to these appliances will be done during a planned maintenance window where we notify customers that there may be downtime expected \(regardless of such risk\). Finally, we will review our post-change test plan to evaluate adding tests that would discover such trouble points in the future.
Status: Postmortem
Impact: Minor | Started At: April 28, 2023, 3:15 a.m.
Description: # Incident Description At 4/28/2023 3:15 AM UTC, the DevOps team did a planned, minor update to traffic management appliances during a maintenance window. While no downtime was expected and all configurations were tested in lower environments, the new update in production did not respect TLS cipher suite configuration as expected. This created a TLS negotiation issue between the SA IdP appliances and the traffic management appliances, blocking some logins from occurring. Unfortunately, the post-change test suite did not detect the issue. After hearing about difficulties from some customer reports and first-hand observations, the DevOps team identified the issue and rolled back the change to restore service at 4:15 AM UTC \(4/28/23\). # Root Cause An update to the update to traffic management appliances did not obey a declarative configuration for TLS cipher suites. This caused a TLS negotiation failure between SA IdP appliances and the traffic management appliances, blocking some logins. # Corrective Actions We apologize for any inconvenience caused during this disruption in service. The SecureAuth team will pause any further changes to the traffic management appliances until we have sorted out the associated configuration issue \(which we plan to solve in the next few weeks\). In addition, any future updates done to these appliances will be done during a planned maintenance window where we notify customers that there may be downtime expected \(regardless of such risk\). Finally, we will review our post-change test plan to evaluate adding tests that would discover such trouble points in the future.
Status: Postmortem
Impact: Minor | Started At: April 28, 2023, 3:15 a.m.
Description: # Incident Description A routine database automatic scaling operation failed around 9:30 AM ET on 4/19/2023. This caused the database cluster to become unresponsive and fail to accept connections. While data integrity was unaffected, data availability was compromised. The SecureAuth team worked to restore service and forced the scaling operation to finish. Once the scaling operation finished, the database cluster once again was accepting connections and service was restored around 12:30 PM ET on 4/19/2023. # Root Cause It appears that the automatic scaling operation failed to complete due to an issue with the database platform in general. One cluster node was marked unhealthy by the scaling algorithm incorrectly, and this prevented the rest of the cluster nodes from scaling properly. The database cluster began rejecting connections soon thereafter. # Corrective Actions Typically such automatic scaling operations are seamless and without incident. However, given the conditions for auto-scale failure on 4/19/2023, we acknowledge there is still risk with such activity. The SecureAuth team is following up with a database platform vendor for more information regarding the scaling operation failure. In the meantime, any auto-scale operations for this database cluster have been suspended, and the SecureAuth team will monitor capacity and do any scaling activity for this database cluster during planned maintenance windows. Finally, the SecureAuth team is confirming vendor best practices are being followed for any/all connections to this database cluster and will make adjustments as needed. Note: times are Eastern time zone.
Status: Postmortem
Impact: Critical | Started At: April 19, 2023, 2:48 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
