Company Logo

Is there an SecureAuth outage?

SecureAuth status: Systems Active

Last checked: 3 minutes ago

Get notified about any outages, downtime or incidents for SecureAuth and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

SecureAuth outages and incidents

Outage and incident data over the last 30 days for SecureAuth.

There have been 1 outages or incidents for SecureAuth in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

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 Now

Components and Services Monitored for SecureAuth

Outlogger tracks the status of these components for Xero:

Operator Alerts Active
Application Active
AU Region Active
EU Region Active
Push Active
SMS Active
US Region Active
Voice Active
Application Active
Device Trust Active
Mobile App Active
Push Active
SMS Active
Voice Active
SaaS/Full Cloud Identity Platform Active
SecureAuth Connector 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 Application Templates Active
SecureAuth Web Admin Active
FIDO Service Active
Mobile Services Active
Polaris Base Infrastructure Active
SaaS IdP Broker 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
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
Component Status
Operator Alerts Active
Active
Application Active
AU Region Active
EU Region Active
Push Active
SMS Active
US Region Active
Voice Active
Active
Application Active
Device Trust Active
Mobile App Active
Push Active
SMS Active
Voice Active
Active
SaaS/Full Cloud Identity Platform Active
SecureAuth Connector Active
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
Active
SecureAuth Application Templates Active
SecureAuth Web Admin Active
Active
FIDO Service Active
Mobile Services Active
Polaris Base Infrastructure Active
SaaS IdP Broker Active
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
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

Latest SecureAuth outages and incidents.

View the latest incidents for SecureAuth and check for official updates:

Updates:

  • Time: April 20, 2023, 3:54 a.m.
    Status: Postmortem
    Update: # 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.
  • Time: April 19, 2023, 5:39 p.m.
    Status: Resolved
    Update: All customers should have returned to normal. Please contact SecureAuth Support ([email protected]) if you are still having issues.
  • Time: April 19, 2023, 4:42 p.m.
    Status: Monitoring
    Update: Services have been restored and we will continue to monitor the situation to ensure no further issues.
  • Time: April 19, 2023, 4:23 p.m.
    Status: Identified
    Update: Updated estimated resolution time 1:00pm Eastern Time. Continuing to recover the underlying database infrastructure components.
  • Time: April 19, 2023, 3:41 p.m.
    Status: Identified
    Update: Identified an issue with the underlying database infrastructure which should be resolved by 12:15pm Eastern Time (9:15am Pacific/16:15 UTC).
  • Time: April 19, 2023, 2:48 p.m.
    Status: Investigating
    Update: The SecureAuth Authentication services have been impacted by a issue within the backend services - we are working with the appropriate teams and third-parties to isolate and resolve.

Updates:

  • Time: Nov. 15, 2022, 2:34 a.m.
    Status: Postmortem
    Update: Incident Description  * On November 14, multiple customers reported issues with the renewal of PFX personal certificates.  Root Cause  * SecureAuth utilizes Cloud-based Hardware Security Modules \(HSM\) through Thales.  * Thales was performing maintenance on the Cloud HSM infrastrucuture over the weekend which caused the SecureAuth Certificate Authority \(CA\) systems to be unable to connect to the Cloud HSM for key validation.  * The SecureAuth CA’s regularly renews the Certificate Revocation Lists \(CRL\) for multiple CA’s - tthe expiration of the delta CRLs is approximately 48 hours, which is why we did not have any impacts from the Thales maintenance until Sunday evening with customers not being impacted until Monday morning.  * To further exacerbate the problem, the alerts generated by the monitoring systems were not going to the location the L1 team monitors.  Corrective Actions  * Restarting the CA’s on all of the “NGE” servers corrected the issue  * Documentation was not completely up-to-date on the configuration of the multiple-region deployment of the NGE certificates. The DevOps team will be reviewing the documentation and updating as necessary.  * Review of all DevOps alerts has been conducted to ensure all alerts are going to the location that is actively monitored vs. the Slack channel that also has the alerts, but is not routinely monitored.  * The DevOps Team has enrolled in status updates through the Thales Status Page and will review any changes or maintenance that is posted to that site to ensure internal testing can be performed to validate all SecureAuth operations are not impacted.
  • Time: Nov. 15, 2022, 2:34 a.m.
    Status: Postmortem
    Update: Incident Description  * On November 14, multiple customers reported issues with the renewal of PFX personal certificates.  Root Cause  * SecureAuth utilizes Cloud-based Hardware Security Modules \(HSM\) through Thales.  * Thales was performing maintenance on the Cloud HSM infrastrucuture over the weekend which caused the SecureAuth Certificate Authority \(CA\) systems to be unable to connect to the Cloud HSM for key validation.  * The SecureAuth CA’s regularly renews the Certificate Revocation Lists \(CRL\) for multiple CA’s - tthe expiration of the delta CRLs is approximately 48 hours, which is why we did not have any impacts from the Thales maintenance until Sunday evening with customers not being impacted until Monday morning.  * To further exacerbate the problem, the alerts generated by the monitoring systems were not going to the location the L1 team monitors.  Corrective Actions  * Restarting the CA’s on all of the “NGE” servers corrected the issue  * Documentation was not completely up-to-date on the configuration of the multiple-region deployment of the NGE certificates. The DevOps team will be reviewing the documentation and updating as necessary.  * Review of all DevOps alerts has been conducted to ensure all alerts are going to the location that is actively monitored vs. the Slack channel that also has the alerts, but is not routinely monitored.  * The DevOps Team has enrolled in status updates through the Thales Status Page and will review any changes or maintenance that is posted to that site to ensure internal testing can be performed to validate all SecureAuth operations are not impacted.
  • Time: Nov. 14, 2022, 11:06 p.m.
    Status: Resolved
    Update: RCA to be posted soon
  • Time: Nov. 14, 2022, 11:06 p.m.
    Status: Resolved
    Update: RCA to be posted soon
  • Time: Nov. 14, 2022, 8:07 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Nov. 14, 2022, 8:07 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: Nov. 14, 2022, 5:57 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Nov. 14, 2022, 5:57 p.m.
    Status: Identified
    Update: The issue has been identified and a fix is being implemented.
  • Time: Nov. 14, 2022, 4:53 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Nov. 14, 2022, 4:53 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Nov. 14, 2022, 4:53 p.m.
    Status: Investigating
    Update: We are currently investigating reports of our PFX/Certificate creation not working for some customers.
  • Time: Nov. 14, 2022, 4:53 p.m.
    Status: Investigating
    Update: We are currently investigating reports of our PFX/Certificate creation not working for some customers.

Updates:

  • Time: Oct. 19, 2022, 8:15 p.m.
    Status: Resolved
    Update: We have moved to our secondary provider and all carriers appear to be working. Please note, for a few days, the numbers will be coming over as "short codes" - this is normal and we are working with the secondary carrier to get to full numbers soon.
  • Time: Oct. 19, 2022, 5:58 p.m.
    Status: Monitoring
    Update: SMS messages are being received from our test devices, continuing to monitor the situation
  • Time: Oct. 19, 2022, 5:57 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Oct. 19, 2022, 5:48 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Oct. 19, 2022, 3:55 p.m.
    Status: Identified
    Update: There is an issue with the 3rd party vendor we are using to send SMS messages to the carrier. The issue appears to be with the vendor delivering messages to AT&T
  • Time: Oct. 19, 2022, 3:53 p.m.
    Status: Investigating
    Update: We are investigating an issue with one of the cell providers (AT&T) where users are not able to utilize SMS as an MFA factor.

Updates:

  • Time: Oct. 19, 2022, 8:15 p.m.
    Status: Resolved
    Update: We have moved to our secondary provider and all carriers appear to be working. Please note, for a few days, the numbers will be coming over as "short codes" - this is normal and we are working with the secondary carrier to get to full numbers soon.
  • Time: Oct. 19, 2022, 5:58 p.m.
    Status: Monitoring
    Update: SMS messages are being received from our test devices, continuing to monitor the situation
  • Time: Oct. 19, 2022, 5:57 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Oct. 19, 2022, 5:48 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue.
  • Time: Oct. 19, 2022, 3:55 p.m.
    Status: Identified
    Update: There is an issue with the 3rd party vendor we are using to send SMS messages to the carrier. The issue appears to be with the vendor delivering messages to AT&T
  • Time: Oct. 19, 2022, 3:53 p.m.
    Status: Investigating
    Update: We are investigating an issue with one of the cell providers (AT&T) where users are not able to utilize SMS as an MFA factor.

Updates:

  • Time: Oct. 14, 2022, 6:02 a.m.
    Status: Resolved
    Update: No further issues have been reported and internal checks continue to be successful
  • Time: Oct. 14, 2022, 6:02 a.m.
    Status: Resolved
    Update: No further issues have been reported and internal checks continue to be successful
  • Time: Oct. 12, 2022, 9:43 p.m.
    Status: Monitoring
    Update: The 3rd Party carriers have appeared to have resolved the issue - we are monitoring to ensure no further issues. If you continue to see any issues, please contact [email protected]
  • Time: Oct. 12, 2022, 9:43 p.m.
    Status: Monitoring
    Update: The 3rd Party carriers have appeared to have resolved the issue - we are monitoring to ensure no further issues. If you continue to see any issues, please contact [email protected]
  • Time: Oct. 12, 2022, 3:38 p.m.
    Status: Investigating
    Update: We are currently investigating SMS delivery issues to for some Cell Networks. Our service provider is currently investigating the issue, and we will provide an update as soon as we receive more information.
  • Time: Oct. 12, 2022, 3:38 p.m.
    Status: Investigating
    Update: We are currently investigating SMS delivery issues to for some Cell Networks. Our service provider is currently investigating the issue, and we will provide an update as soon as we receive more information.

Check the status of similar companies and alternatives to SecureAuth

NetSuite
NetSuite

Systems Active

ZoomInfo
ZoomInfo

Systems Active

SPS Commerce
SPS Commerce

Systems Active

Miro
Miro

Systems Active

Field Nation
Field Nation

Systems Active

Outreach
Outreach

Systems Active

Own Company

Issues Detected

Mindbody
Mindbody

Systems Active

TaskRabbit
TaskRabbit

Systems Active

Nextiva
Nextiva

Systems Active

6Sense

Systems Active

BigCommerce
BigCommerce

Systems Active

Frequently Asked Questions - SecureAuth

Is there a SecureAuth outage?
The current status of SecureAuth is: Systems Active
Where can I find the official status page of SecureAuth?
The official status page for SecureAuth is here
How can I get notified if SecureAuth is down or experiencing an outage?
To get notified of any status changes to SecureAuth, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of SecureAuth every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here