IBM Security Outage History

IBM Security partial outage · 1 active incident View live status →

There were 11 IBM Security outages since February 10, 2026 totaling 1125h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://statuspage.ibmcloudsecurity.com

Notice April 30, 2026

IBM Verify - authentication issues in Canada region

Detected by Pingoru
Apr 30, 2026, 12:38 PM UTC
Resolved
Apr 30, 2026, 01:41 PM UTC
Duration
1h 3m
Affected: Authentication with Cloud Directory ( Cluster B )Authentication with SAML Identity Provider ( Cluster B )Authentication with IBMid for admin users ( Cluster B )Authentication with External LDAP ( Cluster B )User ID and password authentication from API ( Cluster B )Single sign on for SAML applications ( Cluster B )Single sign on for OIDC applications ( Cluster B )Application Onboarding ( Cluster B )Account Lifecycle ( Cluster B )
Timeline · 2 updates
  1. monitoring Apr 30, 2026, 12:38 PM UTC

    IBM Verify Canada Cluster B experienced an issue affecting authentications. Issue has been resolved at this time and we are currently monitoring.

  2. resolved Apr 30, 2026, 01:41 PM UTC

    Monitoring has been successful. Issue is remediated. x

Read the full incident report →

Major April 29, 2026

Outliers/Risk Events service outage

Detected by Pingoru
Apr 29, 2026, 07:55 PM UTC
Resolved
Apr 30, 2026, 04:35 PM UTC
Duration
20h 40m
Affected: OutliersRisk Events
Timeline · 2 updates
  1. investigating Apr 29, 2026, 07:55 PM UTC

    The Risk Events service is currently experiencing issues, which may impact risk generation. The development team is actively investigating and will provide updates as more information becomes available.

  2. investigating Apr 29, 2026, 10:48 PM UTC

    The Outliers and Risk Events services are currently experiencing issues, which may impact outliers and/or risk generation. The development team is actively investigating and will provide updates as more information becomes available.

Read the full incident report →

Notice April 23, 2026

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

Detected by Pingoru
Apr 23, 2026, 11:00 PM UTC
Resolved
Apr 24, 2026, 10:02 PM UTC
Duration
23h 2m
Affected: 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)Account Lifecycle (Cluster A)Authentication with Cloud Directory (Cluster B)Authentication with SAML Identity Provider (Cluster B)Authentication with IBMid for admin users (Cluster B)Authentication with External LDAP (Cluster B)User ID and password authentication from API (Cluster B)Single sign on for SAML applications (Cluster B)Single sign on for OIDC applications (Cluster B)Application Onboarding (Cluster B)Cloud Directory Users and Groups management (Cluster B)User and Group management with API client (Cluster B)Account Lifecycle (Cluster B)Authentication with Cloud Directory (Cluster C)Authentication with SAML Identity Provider (Cluster C)Authentication with IBMid for admin users (Cluster C)Authentication with External LDAP (Cluster C)User ID and password authentication from API (Cluster C)Single sign on for SAML applications (Cluster C)Single sign on for OIDC applications (Cluster C)Application Onboarding (Cluster C)Cloud Directory Users and Groups management (Cluster C)User and Group management with API client (Cluster C)Account Lifecycle (Cluster C)Authentication with Cloud Directory (Cluster E)Authentication with SAML Identity Provider (Cluster E)Authentication with IBMid for admin users (Cluster E)User ID and password authentication from API (Cluster E)Single sign on for SAML applications (Cluster E)Single sign on for OIDC applications (Cluster E)Application Onboarding (Cluster E)Cloud Directory Users and Groups management (Cluster E)Account Lifecycle (Cluster E)User and Group management with API client (Cluster E)
Timeline · 6 updates
  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.

Read the full incident report →

Minor April 16, 2026

IBM Verify - authentication issues in Canada cluster

Detected by Pingoru
Apr 16, 2026, 07:44 AM UTC
Resolved
Apr 17, 2026, 07:05 PM UTC
Duration
1d 11h
Affected: 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 OnboardingAccount Lifecycle
Timeline · 5 updates
  1. investigating Apr 16, 2026, 07:44 AM UTC

    IBM Verify team is investigating authentication failures in Canada region Cluster A

  2. investigating Apr 16, 2026, 08:35 AM UTC

    We are continuing to investigate the issue

  3. monitoring Apr 16, 2026, 10:39 AM UTC

    Authentication services are recovering at this time. We are continuing to investigate the cause and will continue to monitor

  4. monitoring Apr 16, 2026, 11:41 AM UTC

    Service continues to be fully available. We are continuing to monitor

  5. resolved Apr 17, 2026, 07:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 8, 2026

IBM Verify (US Region. Potential service impacting issues cluster B

Detected by Pingoru
Apr 08, 2026, 02:54 PM UTC
Resolved
Apr 16, 2026, 07:41 AM UTC
Duration
7d 16h
Affected: Authentication with Cloud Directory (Cluster B)Authentication with SAML Identity Provider (Cluster B)Authentication with IBMid for admin users (Cluster B)Authentication with External LDAP (Cluster B)User ID and password authentication from API (Cluster B)Single sign on for SAML applications (Cluster B)Single sign on for OIDC applications (Cluster B)Application Onboarding (Cluster B)Cloud Directory Users and Groups management (Cluster B)User and Group management with API client (Cluster B)Account Lifecycle (Cluster B)
Timeline · 2 updates
  1. investigating Apr 08, 2026, 02:54 PM UTC

    IBM Verify (US Region) customers may be experiencing issues with the service in Cluster B. We are currently investigating.

  2. resolved Apr 16, 2026, 07:41 AM UTC

    issue is fully resolved

Read the full incident report →

Major March 19, 2026

IBM Verify Australia Region - Invesgigating service impacting issues

Detected by Pingoru
Mar 19, 2026, 09:38 AM UTC
Resolved
Mar 23, 2026, 12:13 PM UTC
Duration
4d 2h
Affected: Authentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersUser ID and password authentication from APISingle sign on for SAML applicationsApplication OnboardingCloud Directory Users and Groups managementUser and Group management with API clientSingle sign on for OIDC applicationsAccount Lifecycle
Timeline · 4 updates
  1. investigating Mar 19, 2026, 09:38 AM UTC

    We are currently investigating issues in IBM Verify Australia Region affecting services Cluster A

  2. investigating Mar 19, 2026, 09:56 AM UTC

    Services are being restored and coming on-line.

  3. monitoring Mar 19, 2026, 10:53 AM UTC

    Service has been restored and services operating successfully for past hour. We are continuing to monitor.

  4. resolved Mar 23, 2026, 12:13 PM UTC

    Issue was fully resolved on March 19th

Read the full incident report →

Notice March 4, 2026

GDSC system slowness

Detected by Pingoru
Mar 04, 2026, 04:43 PM UTC
Resolved
Mar 05, 2026, 12:15 AM UTC
Duration
7h 31m
Affected: Data Management – Ingestion (Datamart)Reports / Dashboard
Timeline · 4 updates
  1. investigating Mar 04, 2026, 04:43 PM UTC

    We are experiencing slowness in the GDSC platform and we are currently investigating the issue

  2. investigating Mar 04, 2026, 07:46 PM UTC

    We have identified the issue and we are currently working on the fix

  3. identified Mar 04, 2026, 07:46 PM UTC

    The issue has been identified and a fix is being implemented.

  4. resolved Mar 05, 2026, 12:15 AM UTC

    The issue was resolved and now we are monitoring the system

Read the full incident report →

Notice February 23, 2026

GDSC facing login issues

Detected by Pingoru
Feb 23, 2026, 04:51 PM UTC
Resolved
Feb 24, 2026, 01:45 AM UTC
Duration
8h 54m
Affected: User Interface LoginUser Interface Login
Timeline · 3 updates
  1. investigating Feb 23, 2026, 04:51 PM UTC

    We are facing issues with the login, we will provide an update soon

  2. identified Feb 23, 2026, 04:56 PM UTC

    We're experiencing intermittent problems; we'll update as soon as they're fixed.

  3. resolved Feb 24, 2026, 01:45 AM UTC

    We have received confirmation that the login issue has been resolved

Read the full incident report →

Major February 23, 2026

IBM Security Verify (US Region) experiencing service impacting issues.

Detected by Pingoru
Feb 23, 2026, 02:38 PM UTC
Resolved
Feb 24, 2026, 12:48 AM UTC
Duration
10h 9m
Affected: Authentication with Cloud Directory (Cluster A)Authentication with SAML Identity Provider (Cluster A)Authentication with IBMid for admin users (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)Account Lifecycle (Cluster A)
Timeline · 10 updates
  1. investigating Feb 23, 2026, 02:38 PM UTC

    IBM Security Verify (US Region) customers may be experiencing issues with the service in some clusters. We are currently investigating.

  2. investigating Feb 23, 2026, 03:09 PM UTC

    We are continuing to investigate the issue.

  3. identified Feb 23, 2026, 03:30 PM UTC

    Services are restoring at present.

  4. monitoring Feb 23, 2026, 05:21 PM UTC

    Following a number of remediation actions to address issues, services have been restored. We are moving to a monitoring state

  5. investigating Feb 23, 2026, 05:30 PM UTC

    Some additional issues have been reported. Currently investigating,

  6. identified Feb 23, 2026, 07:09 PM UTC

    The recent issues are associated with latency and timeouts. An issue has been identified and a change is being applied. It may take some time to take effect.

  7. identified Feb 23, 2026, 09:16 PM UTC

    We have identified specific database contention within a shared database environment. Our database engineering experts are actively engaged, and we are working through mitigation and remediation options to reduce the contention and restore optimal performance. Further updates will be provided as we progress.

  8. identified Feb 23, 2026, 10:06 PM UTC

    Database engineering experts are continuing to work to mitigate the issue.

  9. monitoring Feb 23, 2026, 11:41 PM UTC

    A fix was applied to a common database by our database engineers. This has stabilised the performance issue. IBM is continuing to monitor.

  10. resolved Feb 24, 2026, 12:48 AM UTC

    Confirming that the performance/database issue in US data centers is resolved.

Read the full incident report →

Minor February 13, 2026

GDSC Europe - Tenant provisioning failing

Detected by Pingoru
Feb 13, 2026, 01:54 AM UTC
Resolved
Feb 20, 2026, 03:48 PM UTC
Duration
7d 13h
Affected: Account Management
Timeline · 2 updates
  1. identified Feb 13, 2026, 01:54 AM UTC

    We have identified an issue impacting tenant provisioning and want to assure you that our team is actively working on a fix. We appreciate your patience as we resolve it.

  2. resolved Feb 20, 2026, 03:48 PM UTC

    The issues has been resolved

Read the full incident report →

Notice February 10, 2026

GDSC Datamart proccessing bug

Detected by Pingoru
Feb 10, 2026, 11:23 PM UTC
Resolved
Mar 06, 2026, 01:23 AM UTC
Duration
23d 1h
Affected: Data Management – Ingestion (Datamart)Outliers
Timeline · 8 updates
  1. investigating Feb 10, 2026, 07:57 PM UTC

    We are currently experiencing an issue where outliers are not being generated as expected. Our engineering team is actively investigating the cause. We will provide more updates as soon as they become available.

  2. identified Feb 10, 2026, 10:04 PM UTC

    We have identified the issue and we are working on a potential solution.

  3. monitoring Feb 10, 2026, 10:47 PM UTC

    We have implemented a fix and we can see datamart ingestion again, we are currently monitoring and validating that the issue doesn't happen again

  4. monitoring Feb 10, 2026, 10:47 PM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Feb 10, 2026, 11:23 PM UTC

    We have identified a bug on Datamart processing and we are currently working on a fix for this

  6. monitoring Feb 17, 2026, 02:03 AM UTC

    We have identified a bug on Datamart processing and we are currently working on a fix for this

  7. monitoring Feb 17, 2026, 02:03 AM UTC

    We are continuing to monitor for any further issues.

  8. resolved Mar 06, 2026, 01:23 AM UTC

    The issue was resolved and all the pending data was re-processed successfully.

Read the full incident report →

Looking to track IBM Security downtime and outages?

Pingoru polls IBM Security's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when IBM Security reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track IBM Security alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring IBM Security for free

5 free monitors · No credit card required