Last checked: 7 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: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 30, 2023, 2:42 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: June 15, 2023, 3:02 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: June 15, 2023, 3:02 p.m.
Description: # Incident Description Starting around 1:12 PM on June 8, our monitors detected an issue with our primary, third-party SMS \(simple message service\) provider used for sending MFA \(multi-factor authentication\) codes. This issue caused intermittent delays when sending messages. While we have a secondary provider, the automatic failover did not occur as expected due to the nature of the primary provider’s SMS issue: the primary actually acknowledged our system’s call to send a message and would queue it but ultimately fail to deliver it promptly. Once our team detected the issue via our monitoring system and performed an investigation, we initiated a manual failover to our secondary SMS provider to reduce any service disruptions for our customers around 2:34 PM. Our primary provider resolved their issue at 5:06 PM, and we manually switched back around 8:43 PM. # Root Cause One of our 3rd party service providers experienced an intermittent service disruption which impacted MFA SMS delivery. # Follow Up Actions We apologize for any disruption in services during this incident. We will review our SMS provider failover thresholds to make them more sensitive to prevent this type of challenge from affecting our customers again. # Reference Telesign Status Page Incident: [https://status.telesign.com/incidents/t201ymq6kl1f](https://status.telesign.com/incidents/t201ymq6kl1f) All dates/times are UTC.
Status: Postmortem
Impact: Major | Started At: June 8, 2023, 2:29 p.m.
Description: # Incident Description Starting around 1:12 PM on June 8, our monitors detected an issue with our primary, third-party SMS \(simple message service\) provider used for sending MFA \(multi-factor authentication\) codes. This issue caused intermittent delays when sending messages. While we have a secondary provider, the automatic failover did not occur as expected due to the nature of the primary provider’s SMS issue: the primary actually acknowledged our system’s call to send a message and would queue it but ultimately fail to deliver it promptly. Once our team detected the issue via our monitoring system and performed an investigation, we initiated a manual failover to our secondary SMS provider to reduce any service disruptions for our customers around 2:34 PM. Our primary provider resolved their issue at 5:06 PM, and we manually switched back around 8:43 PM. # Root Cause One of our 3rd party service providers experienced an intermittent service disruption which impacted MFA SMS delivery. # Follow Up Actions We apologize for any disruption in services during this incident. We will review our SMS provider failover thresholds to make them more sensitive to prevent this type of challenge from affecting our customers again. # Reference Telesign Status Page Incident: [https://status.telesign.com/incidents/t201ymq6kl1f](https://status.telesign.com/incidents/t201ymq6kl1f) All dates/times are UTC.
Status: Postmortem
Impact: Major | Started At: June 8, 2023, 2:29 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.