Is there an SecureAuth outage?
SecureAuth status: Systems Active
Last checked: 2 minutes ago
Get notified about any outages, downtime or incidents for SecureAuth and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 2 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: The alerts look stable for our DNS resolution, as well as on the provider side.
Status: Resolved
Impact: Minor | Started At: May 27, 2022, 3:26 a.m.
Description: **Incident Description**: Customers attempting to log into the Cloud IdP platform were experiencing 504s. **Customer Impact**: A subset of Cloud IdP Customers **Root Cause**: Between 4/28/2022 21:00 UTC – 4/29/2022 01:00 UTC; as part of a routing update to backend services, a number of Broker services used by the Cloud IdP platform failed to update to the necessary version which did not support other changes being applied. **Resolution**: All failing Broker services were identified and the appropriate version was applied shortly after. **Corrective Actions**: During the upgrade process a missing flag was not detected by the script and failed to appropriate upgrade all backend services to the correct version. An audit of the update scripts is being performed to ensure important missing flags or settings fail the upgrade and allow the operator to take the appropriate corrective actions prior to the upgrade commencing.
Status: Postmortem
Impact: None | Started At: April 29, 2022, 6:57 a.m.
Description: **Incident Description**: Customers attempting to log into the Cloud IdP platform were experiencing 504s. **Customer Impact**: A subset of Cloud IdP Customers **Root Cause**: Between 4/28/2022 21:00 UTC – 4/29/2022 01:00 UTC; as part of a routing update to backend services, a number of Broker services used by the Cloud IdP platform failed to update to the necessary version which did not support other changes being applied. **Resolution**: All failing Broker services were identified and the appropriate version was applied shortly after. **Corrective Actions**: During the upgrade process a missing flag was not detected by the script and failed to appropriate upgrade all backend services to the correct version. An audit of the update scripts is being performed to ensure important missing flags or settings fail the upgrade and allow the operator to take the appropriate corrective actions prior to the upgrade commencing.
Status: Postmortem
Impact: None | Started At: April 29, 2022, 6:57 a.m.
Description: Incident Description: Any service resolving to [us-services.secureauth.com](http://us-services.secureauth.com) experienced failures to resolve against the URL while making any attempt to contact cloud services including, but not limited to: datastore connection and multifactor services. Root Cause: One of our main DNS providers have changed their nameserver IPs; this directly resulted in our need to update our glue records, which directly caused our loss of name resolution. Resolution/Corrective Actions: Our glue records have been updated respectively to match our DNS provider's new nameserver IPs. We have ensured we are now enlisted on our DNS provider's notifications when major infrastructure changes occur on their end to prevent another occurrence as such.
Status: Postmortem
Impact: Major | Started At: April 23, 2022, 4:59 p.m.
Description: Incident Description: Any service resolving to [us-services.secureauth.com](http://us-services.secureauth.com) experienced failures to resolve against the URL while making any attempt to contact cloud services including, but not limited to: datastore connection and multifactor services. Root Cause: One of our main DNS providers have changed their nameserver IPs; this directly resulted in our need to update our glue records, which directly caused our loss of name resolution. Resolution/Corrective Actions: Our glue records have been updated respectively to match our DNS provider's new nameserver IPs. We have ensured we are now enlisted on our DNS provider's notifications when major infrastructure changes occur on their end to prevent another occurrence as such.
Status: Postmortem
Impact: Major | Started At: April 23, 2022, 4:59 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.
