IBM Security incident

We believe the issue with the SMS send failures has been resolved.

Notice Resolved View vendor source →

IBM Security experienced a notice incident on April 23, 2026 affecting Authentication with Cloud Directory (Cluster A) and Authentication with SAML Identity Provider (Cluster A) and 1 more component, lasting 23h 2m. The incident has been resolved; the full update timeline is below.

Started
Apr 23, 2026, 11:00 PM UTC
Resolved
Apr 24, 2026, 10:02 PM UTC
Duration
23h 2m
Detected by Pingoru
Apr 23, 2026, 11:00 PM UTC

Affected components

Authentication with Cloud Directory (Cluster A)Authentication with SAML Identity Provider (Cluster A)Authentication with IBMid for admin users (Cluster A)Authentication with External LDAP (Cluster A)User ID and password authentication from API (Cluster A)Single sign on for SAML applications (Cluster A)Single sign on for OIDC applications (Cluster A)Application Onboarding (Cluster A)Cloud Directory Users and Groups management (Cluster A)User and Group management with API client (Cluster A)

Update timeline

  1. investigating Apr 23, 2026, 11:00 PM UTC

    We are currently investigating this issue.

  2. monitoring Apr 24, 2026, 04:19 AM UTC

    Issue is mitigated and we are monitoring the system.

  3. identified Apr 24, 2026, 03:44 PM UTC

    We are still experiencing a partial outage for SMS delivery to some US cellphone numbers. Our team is actively working with vendors to resolve the issue as quickly as possible.

  4. monitoring Apr 24, 2026, 04:41 PM UTC

    We will continue to monitor.

  5. monitoring Apr 24, 2026, 04:42 PM UTC

    We are continuing to monitor for any further issues.

  6. resolved Apr 24, 2026, 10:02 PM UTC

    This incident has been resolved. We will still continue to monitor to ensure there are no regression issues.