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: General Statement During the procurement of a new production region (APAC), an incorrect DNS change was applied to one of our DNS providers (AWS Route53). This led to intermittent DNS resolution issues, affecting customer reachability of IdP services. Due to the nature of DNS propagation, and the intermittentness of the issue, a delay of our monitors' ability to detect the problem occurred. Once identified, the DNS change was reverted, and DNS propagation of the fix began, completing at approximately 10:30AM PST. Timeline of Events Mar 26 7:30 PST Incorrect DNS change applied to Route53 Mar 26 8:30 PST DevOps team began diagnosing the issue Mar 26 8:55 PST DevOps team removed duplicate record Mar 26 10:30 PST DNS Propagation appears complete. Corrective Actions Additional approvals required for any DNS changes. Review opportunity to expand endpoint monitoring from multiple regions and DNS name servers.
Status: Resolved
Impact: Minor | Started At: March 26, 2024, 4:27 p.m.
Description: General Statement During the procurement of a new production region (APAC), an incorrect DNS change was applied to one of our DNS providers (AWS Route53). This led to intermittent DNS resolution issues, affecting customer reachability of IdP services. Due to the nature of DNS propagation, and the intermittentness of the issue, a delay of our monitors' ability to detect the problem occurred. Once identified, the DNS change was reverted, and DNS propagation of the fix began, completing at approximately 10:30AM PST. Timeline of Events Mar 26 7:30 PST Incorrect DNS change applied to Route53 Mar 26 8:30 PST DevOps team began diagnosing the issue Mar 26 8:55 PST DevOps team removed duplicate record Mar 26 10:30 PST DNS Propagation appears complete. Corrective Actions Additional approvals required for any DNS changes. Review opportunity to expand endpoint monitoring from multiple regions and DNS name servers.
Status: Resolved
Impact: Minor | Started At: March 26, 2024, 4:27 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: None | Started At: Feb. 19, 2024, 12:02 p.m.
Description: This incident has been resolved.End users should no longer experience delays receiving SMS messages
Status: Resolved
Impact: Minor | Started At: Jan. 30, 2024, 1:59 p.m.
Description: This incident has been resolved.End users should no longer experience delays receiving SMS messages
Status: Resolved
Impact: Minor | Started At: Jan. 30, 2024, 1: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.