SecureAuth Outage History

18 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live SecureAuth status100.00% uptime history

Every Recorded SecureAuth Incident

SecureAuth incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 8, 2026IAM SaaS US Region - Something has gone wrongFalse Positive. Adjusting alerting system.3 minResolved
Sep 15, 2026SecureAuth Cloud Services Maintenance - Tuesday, September 15, 2026The scheduled maintenance has been completed.3h 0mScheduled
Jun 22, 2026SecureAuth Cloud Services Maintenance - Monday, June 22, 2026The scheduled maintenance has been completed.3h 0mScheduled
May 4, 2026SecureAuth Cloud Services Maintenance - Monday, May 4, 2026The scheduled maintenance has been completed.3h 0mScheduled
Apr 23, 2026IAM SaaS AU Region - Something has gone wrongThe problem has been resolved.<br><b style='color: green'>Resolved</b> - The component IAM SaaS AU Region is down and we&#x27;re working on it.2 minResolved
Apr 21, 2026Emergency maintenance window for https://sso.acceptto.com/The scheduled maintenance has been completed.3h 0mScheduled
Apr 21, 2026Passwordless- Investigating Issue affecting mfa.acceptto.comThis incident has been resolved. An RCA will be added to the post mortem once the investigation is complete. If you have any questions regarding this matter or are experiencing any problems, please let us know by…1h 1mResolved
Apr 18, 2026Intermittent SSL Errors Affecting Workforce Cloud IdPWe have identified the issue and have implemented a solution. SSL errors have all been resolved. An RCA will be provided as soon as the investigation has been complete. If you have any questions, please reach out to…8 minResolved
Apr 6, 2026SecureAuth Cloud Services Maintenance - April 6, 2026The scheduled maintenance has been completed.3h 0mScheduled
Mar 7, 2026SecureAuth Cloud Services Maintenance - March 6, 2026The scheduled maintenance has been completed.1h 0mScheduled
Mar 6, 2026IAM SaaS US Region - Something has gone wrongThe problem has been resolved.<br><b style='color: green'>Resolved</b> - The component IAM SaaS US Region is down and we&#x27;re working on it.2 minResolved
Feb 22, 2026CIAM US Service DegradationThe issue has been identified and resolved. The system is now operating normally.3 minResolved
Feb 17, 2026CIAM US Region DisruptionWe observed a ~1 minute disruption within our CIAM product in the US region. The disruption was quickly fixed, with no risk for further issues. If you have any questions regarding this matter, please reach out to our…0 minResolved
Jan 14, 2026SMS Service - Operator Service AlertOur SMS and Telephony provider has informed us that the network issues previously reported by Multiple Operators from the US have been resolved. Operator end users should no longer experience delays receiving SMS…9h 19mResolved
Jan 3, 2026System Maintenance - SecureAuth Cloud Services - January 3rd, 2026The scheduled maintenance has been completed.3h 0mScheduled
Dec 15, 2025Cloud Services Issue**RCA - Cascading Service Failure – 12-15-2025**  **Incident date:** December 15, 2025 **Duration:** ~90 minutes **Severity:** SEV-1 **Services affected:** Polaris platform services  **Summary**  On December…1h 11mResolved
Dec 6, 2025Investigating intermittent issues with Mobile Service affecting Push and TOTP**RCA - Intermittent Mobile Service issues - 12.05.2025** **Issue Description:** On December 5, 2025, a subset of customers experienced intermittent disruptions affecting the Push-2-Accept and TOTP multi-factor…9h 47mResolved
Nov 18, 2025Cloudflare global network incidentAll workaround actions for SAIdP and Acceptto have been successfully reverted, and our systems have fully returned to their normal operating state. We have confirmed stable service across all components and no customer…21h 39mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next SecureAuth incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This SecureAuth Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before SecureAuth acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single SecureAuth outage in this window ran 21h 39m, against a mean recovery of 3h 28m. If you depend on SecureAuth in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.