Is there an SecureAuth outage?
SecureAuth status: Systems Active
Last checked: 8 minutes ago
Get notified about any outages, downtime or incidents for SecureAuth and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 8 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: # SecureAuth Production Incident Root Cause Analysis \(RCA\) ## Incident Description The Push to Accept \(P2A\) service was sending push requests to users; however, approval of those requests were not getting back to the Identity Platform \(IdP\) to finish the login process for a user with P2A multi-factor authentication \(MFA\). All other MFA methods were still available to users. ## Root Cause During normal, automated auto-scaling of the Amazon Elastic Kubernetes Service \(EKS\), there was an issue with the networking components of the EKS nodes, which caused the Redis databases used within the environment to lose access with other services. It is suspected that the auto-scaling of the EKS environment impacted the core networking and DNS services of the cluster due to a single auto-scaling policy for the entire cluster. ## Resolution * Alerts were generated and investigated by the DevOps Team within minutes of the networking issues; however, these alerts were generated from multiple services, and it was eventually determined to be the Redis services after multiple other services were also cycled. * The Redis Pods were cycled, and the Push Service was restored to normal operation. ## Corrective Actions * The DevOps Team is working to move from Redis pods on EKS to utilizing the AWS Elasticache service to allow for redundancy and additional stability for the service. ETA is the end of 2022. * Additional alerts have been created updated procedures have been added to runbooks to minimize a potential future failure. * The DevOps team is modifying the auto-scaling policies to separate the core services into one auto-scaling group \(ASG\) and the application itself into a separate ASG. This is expected to be completed by the end of October 2022.
Status: Postmortem
Impact: Major | Started At: Oct. 6, 2022, 3:52 p.m.
Description: # SecureAuth Production Incident Root Cause Analysis \(RCA\) ## Incident Description The Push to Accept \(P2A\) service was sending push requests to users; however, approval of those requests were not getting back to the Identity Platform \(IdP\) to finish the login process for a user with P2A multi-factor authentication \(MFA\). All other MFA methods were still available to users. ## Root Cause During normal, automated auto-scaling of the Amazon Elastic Kubernetes Service \(EKS\), there was an issue with the networking components of the EKS nodes, which caused the Redis databases used within the environment to lose access with other services. It is suspected that the auto-scaling of the EKS environment impacted the core networking and DNS services of the cluster due to a single auto-scaling policy for the entire cluster. ## Resolution * Alerts were generated and investigated by the DevOps Team within minutes of the networking issues; however, these alerts were generated from multiple services, and it was eventually determined to be the Redis services after multiple other services were also cycled. * The Redis Pods were cycled, and the Push Service was restored to normal operation. ## Corrective Actions * The DevOps Team is working to move from Redis pods on EKS to utilizing the AWS Elasticache service to allow for redundancy and additional stability for the service. ETA is the end of 2022. * Additional alerts have been created updated procedures have been added to runbooks to minimize a potential future failure. * The DevOps team is modifying the auto-scaling policies to separate the core services into one auto-scaling group \(ASG\) and the application itself into a separate ASG. This is expected to be completed by the end of October 2022.
Status: Postmortem
Impact: Major | Started At: Oct. 6, 2022, 3:52 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: July 2, 2022, 4:03 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: July 2, 2022, 4:03 p.m.
Description: This incident has been resolved, Root Cause Analysis pending
Status: Resolved
Impact: Critical | Started At: July 1, 2022, 3:56 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.
