SecureAuth experienced a major incident on June 8, 2023, lasting 12h 53m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Jun 08, 2023, 02:29 PM UTC
Our Telephony provider is having an issue with SMS and Telephony.
- identified Jun 08, 2023, 02:36 PM UTC
The issue has been identified as a fault out the telephony provider side so we are switching to a backup provider.
- monitoring Jun 08, 2023, 02:39 PM UTC
Switching to the secondary provider for SMS appears to have resolved the issue for now. We will continue to monitor.
- monitoring Jun 08, 2023, 02:41 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jun 08, 2023, 02:58 PM UTC
We are continuing to monitor for any further issues.
- resolved Jun 09, 2023, 03:23 AM UTC
We have switched back to our primary provider and all services are operational
- postmortem Jun 09, 2023, 11:25 PM UTC
# 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.