Company Logo

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.

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: March 24, 2022, 3:49 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 23, 2022, 4:04 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: March 22, 2022, 6:19 p.m.
    Status: Identified
    Update: We are currently investigating SMS delivery issues to US T Mobile users. Our service provider is currently investigating the issue, and we will provide an update as soon as we receive more information.

Updates:

  • Time: Dec. 8, 2021, 11:12 p.m.
    Status: Postmortem
    Update: On Dec 7th around 7:42 am PST, SecureAuth detected that several services were encountering issues and customers were impacted. Upon further investigation, the root cause of the service interruption was due to a wide-spread outage in AWS US-East-1 region.  At 8:39 am PST, SecureAuth switched the MFA Cloud Services to the backup cluster hosted in AWS’s US-West-2 region. However, IdPs that run from the AWS US-East-1 region could not be moved and certain customers were continuing to be impacted. AWS started recovery around 2 PM PST and SecureAuth’s services started to recover as well. The AWS US-East-1 region eventually became fully functional around Dec 8th 1:32 PM PST. SecureAuth will engage with AWS to discuss the root cause of the outage and devise plans for future reliability improvements.
  • Time: Dec. 8, 2021, 5:44 p.m.
    Status: Resolved
    Update: AWS service has been fully restored and all SecureAuth services returned back to normal.
  • Time: Dec. 7, 2021, 7:39 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Dec. 7, 2021, 7:36 p.m.
    Status: Monitoring
    Update: AWS has restored some of the impacted services but has no ETA on full resolution. We will continue to monitor.
  • Time: Dec. 7, 2021, 6:22 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Dec. 7, 2021, 5:19 p.m.
    Status: Investigating
    Update: AWS is encountering networking issues in US-East-1 region and impacted several services. There is currently no ETA from AWS on the resolution timeline.
  • Time: Dec. 7, 2021, 4:54 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Dec. 7, 2021, 4:37 p.m.
    Status: Investigating
    Update: We are investigating increased error rates in SecureAuth Identity Platform and selected Cloud Services.

Updates:

  • Time: Dec. 8, 2021, 11:12 p.m.
    Status: Postmortem
    Update: On Dec 7th around 7:42 am PST, SecureAuth detected that several services were encountering issues and customers were impacted. Upon further investigation, the root cause of the service interruption was due to a wide-spread outage in AWS US-East-1 region.  At 8:39 am PST, SecureAuth switched the MFA Cloud Services to the backup cluster hosted in AWS’s US-West-2 region. However, IdPs that run from the AWS US-East-1 region could not be moved and certain customers were continuing to be impacted. AWS started recovery around 2 PM PST and SecureAuth’s services started to recover as well. The AWS US-East-1 region eventually became fully functional around Dec 8th 1:32 PM PST. SecureAuth will engage with AWS to discuss the root cause of the outage and devise plans for future reliability improvements.
  • Time: Dec. 8, 2021, 5:44 p.m.
    Status: Resolved
    Update: AWS service has been fully restored and all SecureAuth services returned back to normal.
  • Time: Dec. 7, 2021, 7:39 p.m.
    Status: Monitoring
    Update: We are continuing to monitor for any further issues.
  • Time: Dec. 7, 2021, 7:36 p.m.
    Status: Monitoring
    Update: AWS has restored some of the impacted services but has no ETA on full resolution. We will continue to monitor.
  • Time: Dec. 7, 2021, 6:22 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Dec. 7, 2021, 5:19 p.m.
    Status: Investigating
    Update: AWS is encountering networking issues in US-East-1 region and impacted several services. There is currently no ETA from AWS on the resolution timeline.
  • Time: Dec. 7, 2021, 4:54 p.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: Dec. 7, 2021, 4:37 p.m.
    Status: Investigating
    Update: We are investigating increased error rates in SecureAuth Identity Platform and selected Cloud Services.

Updates:

  • Time: March 24, 2022, 3:48 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 26, 2022, 11:58 p.m.
    Status: Monitoring
    Update: SecureAuth Authenticate implements Firebase Cloud Messaging to safely deliver push notifications to user’s devices. To uniquely identify each device, FCM generates and assigns a token to each device. While that token might remain unchanged for long periods of time, it might change unexpectedly due to a few conditions: • When an app is restored on a new device. • When the user uninstalls/reinstalls the app (we consider updates as new installation as well). • When the user clears app data. Given the current capabilities of our solution, we can’t dynamically update that token, so the users will need to re-enroll their accounts in order to use push notifications. They’ll continue to receive notifications for a short period of time, but they won’t be able to reply to them and at some point they’ll stop receiving them. The remediation measure includes showing an error to the end-users whenever the token changes so that they know they’ll need to perform a re-enrollment in order to keep using push notification capabilities. This remediation measure is included in the latest version of our Android app, available on the Google play store.
  • Time: Nov. 16, 2021, 6:52 p.m.
    Status: Investigating
    Update: Investigating: Users using Android mobile devices or tablets may encounter Push notification failures. User Impact: Users using Android mobile devices or tablets may be unable to log on using Push2Accept or Symbol2Accept due to push notification failures. The issue may manifest itself in a number of ways: 1. In some cases, the push notification may not be received 2. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, no error will be displayed on the mobile device 3. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, an error may be displayed on the mobile device Preliminary RCA: This issue is caused by the Android OS app update process. For some devices, when the app is updated, the unique identifier used to validate the device to our cloud is modified by the Android OS, resulting in push notifications failing. The SecureAuth development team is currently investigating this issue with the Google Android team. Remediation: Users must reenroll the impacted devices

Updates:

  • Time: March 24, 2022, 3:48 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Jan. 26, 2022, 11:58 p.m.
    Status: Monitoring
    Update: SecureAuth Authenticate implements Firebase Cloud Messaging to safely deliver push notifications to user’s devices. To uniquely identify each device, FCM generates and assigns a token to each device. While that token might remain unchanged for long periods of time, it might change unexpectedly due to a few conditions: • When an app is restored on a new device. • When the user uninstalls/reinstalls the app (we consider updates as new installation as well). • When the user clears app data. Given the current capabilities of our solution, we can’t dynamically update that token, so the users will need to re-enroll their accounts in order to use push notifications. They’ll continue to receive notifications for a short period of time, but they won’t be able to reply to them and at some point they’ll stop receiving them. The remediation measure includes showing an error to the end-users whenever the token changes so that they know they’ll need to perform a re-enrollment in order to keep using push notification capabilities. This remediation measure is included in the latest version of our Android app, available on the Google play store.
  • Time: Nov. 16, 2021, 6:52 p.m.
    Status: Investigating
    Update: Investigating: Users using Android mobile devices or tablets may encounter Push notification failures. User Impact: Users using Android mobile devices or tablets may be unable to log on using Push2Accept or Symbol2Accept due to push notification failures. The issue may manifest itself in a number of ways: 1. In some cases, the push notification may not be received 2. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, no error will be displayed on the mobile device 3. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, an error may be displayed on the mobile device Preliminary RCA: This issue is caused by the Android OS app update process. For some devices, when the app is updated, the unique identifier used to validate the device to our cloud is modified by the Android OS, resulting in push notifications failing. The SecureAuth development team is currently investigating this issue with the Google Android team. Remediation: Users must reenroll the impacted devices

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

Systems Active

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

Start monitoring now!

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.

Get Started for Free