IBM Security incident

IBM Verify (Europe Region) experiencing service impacting issues.

Major Resolved View vendor source →

IBM Security experienced a major incident on August 20, 2026 affecting Authentication with Cloud Directory and Authentication with SAML Identity Provider and 1 more component, lasting 5d 4h. The incident has been resolved; the full update timeline is below.

Started
Aug 20, 2026, 03:39 PM UTC
Resolved
Aug 25, 2026, 08:02 PM UTC
Duration
5d 4h
Detected by Pingoru
Aug 20, 2026, 03:39 PM UTC

Affected components

Authentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersAuthentication with External LDAPUser ID and password authentication from APISingle sign on for SAML applicationsSingle sign on for OIDC applicationsApplication OnboardingCloud Directory Users and Groups managementUser and Group management with API client

Update timeline

  1. investigating Aug 20, 2026, 03:39 PM UTC

    IBM Verify (Europe Region) customers may be experiencing issues with the service. We are currently investigating. We have taken action to move to alternate processing environment.

  2. investigating Aug 20, 2026, 04:11 PM UTC

    Issue is re-occurring. Users may experience some intermittent authentication failures. We are continuing to investigate the issue.

  3. investigating Aug 20, 2026, 04:44 PM UTC

    We are continuing to investigate. Services are generally available, but there may be intermittent failures.

  4. identified Aug 20, 2026, 05:26 PM UTC

    We have identified the area that has been causing the issue. We are continuing to investigate. The service remains operational at this time.

  5. identified Aug 20, 2026, 06:26 PM UTC

    Service continues to be stable. We are still investigating the cause of the issue.

  6. identified Aug 20, 2026, 10:22 PM UTC

    We have experienced some further intermittent issues and continue to investigate the cause.

  7. monitoring Aug 21, 2026, 08:08 AM UTC

    Service in Europe continues to be stable. We are continuing to monitor.

  8. resolved Aug 25, 2026, 08:02 PM UTC

    This incident has been resolved.