SecurID incident

SecurID Service Incident

Minor Resolved View vendor source →

SecurID experienced a minor incident on April 4, 2023 affecting access-eu Authentication Service and access-anz Authentication Service and 1 more component, lasting 1h 8m. The incident has been resolved; the full update timeline is below.

Started
Apr 04, 2023, 03:26 PM UTC
Resolved
Apr 04, 2023, 04:35 PM UTC
Duration
1h 8m
Detected by Pingoru
Apr 04, 2023, 03:26 PM UTC

Affected components

access-eu Authentication Serviceaccess-anz Authentication Servicena.access Authentication Serviceaccess-in Authentication Servicena2.access Authentication Serviceeu2.access-eu Authentication Servicena3.access Authentication Servicena4.access Authentication Service

Update timeline

  1. investigating Apr 04, 2023, 03:26 PM UTC

    We have detected an issue affecting the SecurID Cloud Authentication Service. SaaS Operations is investigating the issue and will post updates as they become available.

  2. investigating Apr 04, 2023, 03:30 PM UTC

    Customers have reported intermittent issues with the Approve and Biometric authentication methods. As a workaround, end users may be able to use Tokencode authentication instead while we continue to investigate and mitigate the problem. Thank you, The SecurID Team

  3. resolved Apr 04, 2023, 04:35 PM UTC

    The incident affecting Approve and Biometric authentication methods has been resolved. We will post a root cause analysis as soon as it is available.

  4. postmortem Apr 21, 2023, 05:04 PM UTC

    An incident occurred April 4th 6:30 PDT – 10:05 PDT that prevented Android users from receiving push notifications. This incident was not specific to RSA SecurID, but impacted all Android applications that leverage Google Firebase notification services. Google Firebase suffered a service outage, the details of which can be found here: [https://status.firebase.google.com/incidents/9ZPv9faHLen8bzLVSaft](https://status.firebase.google.com/incidents/9ZPv9faHLen8bzLVSaft).