CyberArk Identity Cloud incident

CyberArk Identity Advisory - Pod1304

Minor Resolved View vendor source →

CyberArk Identity Cloud experienced a minor incident on March 11, 2024 affecting pod1313 APAC, lasting 1d 20h. The incident has been resolved; the full update timeline is below.

Started
Mar 11, 2024, 05:31 PM UTC
Resolved
Mar 13, 2024, 02:01 PM UTC
Duration
1d 20h
Detected by Pingoru
Mar 11, 2024, 05:31 PM UTC

Affected components

pod1313 APAC

Update timeline

  1. investigating Mar 11, 2024, 01:58 PM UTC

    Customers on pod1304 may experience slowness or failure when logging into or loading the Identity console. We are currently investigating this issue.

  2. identified Mar 11, 2024, 03:12 PM UTC

    We have identified the issue and are working to restore our service. Next Update: 1 hour or upon earlier status change.

  3. identified Mar 11, 2024, 04:15 PM UTC

    Cyberark Engineers have identified the issue and are working with the vendor on issue resolution. Next Update: 1 hour or upon earlier status change.

  4. identified Mar 11, 2024, 05:31 PM UTC

    We are continuing triage and working on a resolution. Next Update: 1 hour or upon earlier status change.

  5. identified Mar 11, 2024, 06:50 PM UTC

    Team is continuing to triage and working on resolution. Next Update: 1 hour or upon earlier status change.

  6. identified Mar 11, 2024, 07:56 PM UTC

    CyberArk teams have identified a possible solution to the issue. Internal testing is ongoing to verify behavior. Next Update: 2 hours or upon earlier status change.

  7. identified Mar 11, 2024, 09:54 PM UTC

    Teams have identified a possible solution to the issue. Internal testing is ongoing to verify behavior. Next Update: 2 hours or upon earlier status change.

  8. identified Mar 11, 2024, 11:55 PM UTC

    Team is continuing to triage and working on resolution. Next Update: 2 hours or upon earlier status change.

  9. identified Mar 12, 2024, 01:56 AM UTC

    Teams have identified a possible solution to the issue. Internal testing is ongoing to verify behavior. Next Update: 2 hours or upon earlier status change.

  10. identified Mar 12, 2024, 04:22 AM UTC

    Teams are working on implementing a potential fix and restore the service. Next Update: 2 hours or upon earlier status change.

  11. identified Mar 12, 2024, 06:30 AM UTC

    We are continuing to work on implementing the fix. Appreciate your patience and support. Next Update: 3 hours or upon earlier status change.

  12. identified Mar 12, 2024, 09:49 AM UTC

    We are still continuing to work on implementing the fix. Next Update: 4 hours or upon earlier status change.

  13. identified Mar 12, 2024, 01:58 PM UTC

    A confirmed remediation has been implemented and is rolling out to affected customers. We’re actively monitoring the environment for any new conditions. Next Update: 8 hours or upon earlier status change.

  14. identified Mar 12, 2024, 10:39 PM UTC

    A confirmed remediation has been implemented and is rolling out to affected customers. We’re actively monitoring the environment for any new conditions. Next Update: 8 hours or upon earlier status change.

  15. identified Mar 13, 2024, 03:13 AM UTC

    The remediation process is currently underway for affected customers. During this period, users may encounter difficulties accessing the Identity portal for a few minutes. Please reach out to https://www.cyberark.com/customer-support/ for any queries. Next Update: 4 hours or upon earlier status change.

  16. monitoring Mar 13, 2024, 09:06 AM UTC

    The remediation process for all impacted customers on this pod is now complete. We are continuing to monitor.

  17. resolved Mar 13, 2024, 02:01 PM UTC

    All services are now operating in normal conditions. This incident is now closed. Thank you for your patience and support.