SecurID Outage History

SecurID is up right now

SecurID had 9 outages in the last 2 years totaling 11h 35m of downtime — averaging 0.4 incidents per month.

There were 9 SecurID outages since October 10, 2024 totaling 11h 35m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.securid.com

Minor October 2, 2026

RSA ID Plus Service Incident (IN Region)

Detected by Pingoru
Oct 02, 2026, 12:05 AM UTC
Resolved
Oct 02, 2026, 02:36 AM UTC
Duration
2h 30m
Affected: access-in Authentication Service
Timeline · 3 updates
  1. investigating Oct 02, 2026, 12:05 AM UTC

    We have detected an issue affecting RSA ID Plus. SaaS Operations is investigating the issue and will post updates as they become available.

  2. monitoring Oct 02, 2026, 12:43 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 02, 2026, 02:36 AM UTC

    After monitoring the fix, SaaS Operations has determined that the incident affecting RSA ID Plus has been resolved. We will post a root cause analysis as soon as it is available.

Read the full incident report →

Minor August 5, 2025

RSA ID Plus Service Incident (Multiple Regions)

Detected by Pingoru
Aug 05, 2025, 04:17 PM UTC
Resolved
Aug 05, 2025, 05:25 PM UTC
Duration
1h 8m
Affected: access-anz Administration Consoleaccess-in Administration Consoleaccess-jp Administration Consoleaccess-ca Administration Consoleaccess-sg Administration Console
Timeline · 3 updates
  1. investigating Aug 05, 2025, 04:17 PM UTC

    We have detected an issue affecting RSA ID Plus. SaaS Operations is investigating the issue and will post updates as they become available.

  2. monitoring Aug 05, 2025, 04:43 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 05, 2025, 05:25 PM UTC

    After monitoring the fix, SaaS Operations has determined that the incident affecting RSA ID Plus Administration Service has been resolved. No Authentication Services were impacted by this incident. We will post a root cause analysis as soon as it is available.

Read the full incident report →