Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Ibm Security outage history

    68 recorded Ibm Security incidents since May 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    IBM Verify (US Region) experiencing service impacting issues.

    Started October 22, 2026 at 1:52 PM UTC · 1d 7h

    OutageMajor incident
    Affected components
    Single sign on for SAML applications (Cluster A)Authentication with Cloud Directory (Cluster A)Single sign on for OIDC applications (Cluster B)Authentication with External LDAP (Cluster B)User ID and password authentication from API (Cluster A)Authentication with Cloud Directory (Cluster B)Authentication with External LDAP (Cluster A)Single sign on for OIDC applications (Cluster A)Application Onboarding (Cluster A)Cloud Directory Users and Groups management (Cluster A)Authentication with IBMid for admin users (Cluster B)Authentication with SAML Identity Provider (Cluster B)User and Group management with API client (Cluster A)Account Lifecycle (Cluster B)Authentication with SAML Identity Provider (Cluster A)Authentication with IBMid for admin users (Cluster A)Application Onboarding (Cluster B)Account Lifecycle (Cluster A)User ID and password authentication from API (Cluster B)User and Group management with API client (Cluster B)Cloud Directory Users and Groups management (Cluster B)Single sign on for SAML applications (Cluster B)
    1. October 22, 2026 at 1:52 PM UTCinvestigating

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

    2. October 22, 2026 at 2:11 PM UTCinvestigating

      We are continuing to investigate the issue. Customers may experience increased latency when processing. We are continuing to investigate.

    3. October 22, 2026 at 2:56 PM UTCmonitoring

      Latency issues are mitigated. IBM engineers are still investigating the cause.

    4. October 23, 2026 at 8:56 PM UTCresolved

      This incident has been resolved.

    GDSC EU Login Service Disruption

    Started October 17, 2026 at 12:53 AM UTC · 15h 27m

    OutageCritical incident
    Affected components
    User Interface Login
    1. October 17, 2026 at 12:53 AM UTCinvestigating

      We are currently experiencing an issue affecting the GDSC EU login service. Users may be unable to sign in or could encounter errors during the authentication process. Our team is actively investigating the issue and working to identify the root cause. We will provide further updates as soon as more information becomes available.

    2. October 17, 2026 at 1:11 AM UTCmonitoring

      The application login service has been restored and is operating normally. We are continuing to closely monitor the service to ensure stability and confirm that the issue does not recur.

    3. October 17, 2026 at 4:21 PM UTCresolved

      This incident has been resolved.

    IBM Verify (Europe Region) intermittent issues

    Started October 7, 2026 at 3:50 PM UTC · 23h 57m

    Pending
    Affected components
    Authentication with External LDAPAuthentication with Cloud Directory
    1. October 7, 2026 at 3:50 PM UTCinvestigating

      IBM Verify (Europe Region) customers using the IBM Verify Bridge component may experience intermittent issues during authentication and synchronisation flows. IBM engineers are actively investigating.

    2. October 7, 2026 at 7:18 PM UTCidentified

      We are continuing to investigate this intermittent issue. An area of concern has been identified. Engineers are investigating the cause. The issue is intermittent and affecting a small number of tenants using the Verify Bridge component.

    3. October 8, 2026 at 3:47 PM UTCresolved

      The issue was identified and mitigation steps were implemented to restore service,

    IBM Verify (US Region) experiencing service impacting issues.

    Started September 24, 2026 at 7:08 PM UTC · 3h 6m

    OutageMajor incident
    Affected components
    Single sign on for SAML applications (Cluster A)Authentication with Cloud Directory (Cluster A)Single sign on for OIDC applications (Cluster B)Authentication with External LDAP (Cluster B)User ID and password authentication from API (Cluster A)Authentication with Cloud Directory (Cluster B)Authentication with External LDAP (Cluster A)Single sign on for OIDC applications (Cluster A)Application Onboarding (Cluster A)Cloud Directory Users and Groups management (Cluster A)Authentication with IBMid for admin users (Cluster B)Authentication with SAML Identity Provider (Cluster B)User and Group management with API client (Cluster A)Account Lifecycle (Cluster B)Authentication with SAML Identity Provider (Cluster A)Authentication with IBMid for admin users (Cluster A)Application Onboarding (Cluster B)Account Lifecycle (Cluster A)User ID and password authentication from API (Cluster B)User and Group management with API client (Cluster B)Cloud Directory Users and Groups management (Cluster B)Single sign on for SAML applications (Cluster B)
    1. September 24, 2026 at 7:08 PM UTCinvestigating

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

    2. September 24, 2026 at 7:38 PM UTCidentified

      Action has been taken to restore service. IBM is still investigating the issue.

    3. September 24, 2026 at 8:12 PM UTCmonitoring

      The issue has been identified and service is being monitored.

    4. September 24, 2026 at 10:14 PM UTCresolved

      The issue has been resolved. Closing the incident.

    IBM Verify (Europe Region) experienced service impacting periods.

    Started September 19, 2026 at 8:57 AM UTC · 0m

    Pending
    Affected components
    Single sign on for OIDC applicationsAuthentication with SAML Identity ProviderAuthentication with External LDAPUser and Group management with API clientAccount LifecycleAuthentication with IBMid for admin usersApplication OnboardingAuthentication with Cloud DirectoryCloud Directory Users and Groups managementUser ID and password authentication from APISingle sign on for SAML applications
    1. September 19, 2026 at 8:57 AM UTCresolved

      IBM Verify (Europe Region) experienced periods on Saturday 19 September where service was impacted. Affected time periods were 01:10 UTC and 04:50 UTC. The issue has been resolved and service has been running stable for past several hours.

    IBM Verify Monitoring issue incorrectly showing failures for "Authentication with IBMid for admin users"

    Started September 17, 2026 at 9:58 PM UTC · 6h 57m

    Pending
    1. September 17, 2026 at 9:58 PM UTCinvestigating

      We are currently investigating this issue.

    2. September 18, 2026 at 4:40 AM UTCmonitoring

      Issue was mitigated and we are monitoring the results

    3. September 18, 2026 at 4:55 AM UTCresolved

      This incident has been resolved.

    IBM Verify (Europe Region) experiencing service impacting issues.

    Started September 10, 2026 at 6:32 PM UTC · 15h 21m

    OutageMajor incident
    Affected components
    Single sign on for OIDC applicationsAuthentication with SAML Identity ProviderAuthentication with External LDAPUser and Group management with API clientAccount LifecycleAuthentication with IBMid for admin usersApplication OnboardingAuthentication with Cloud DirectoryCloud Directory Users and Groups managementUser ID and password authentication from APISingle sign on for SAML applications
    1. September 10, 2026 at 6:32 PM UTCinvestigating

      IBM Verify (Europe Region) customers may be experiencing issues with the service. We are currently investigating.

    2. September 10, 2026 at 7:02 PM UTCinvestigating

      We are still investigating the issues in Europe.

    3. September 10, 2026 at 7:24 PM UTCidentified

      An issue has been identified and remediation action taken. Services are operational at this time

    4. September 10, 2026 at 8:03 PM UTCmonitoring

      service continues to be stable. we continue to monitor the environment.

    5. September 11, 2026 at 9:53 AM UTCresolved

      Service has been stable for past several hours. Closing the incident.

    IBM Verify - Authentication with IBMid for admin users monitors failing

    Started September 10, 2026 at 10:45 AM UTC · 3h 30m

    OutageCritical incident
    Affected components
    Authentication with IBMid for admin usersAuthentication with IBMid for admin usersAuthentication with IBMid for admin users (Cluster C)Authentication with IBMid for admin users (Cluster A)Authentication with IBMid for admin usersAuthentication with IBMid for admin users (Cluster E)
    1. September 10, 2026 at 10:45 AM UTCinvestigating

      We are currently observing failures with the "Authentication with IBMid for Admin Users" monitoring check. No authentication impact has been identified at this time. The IBM Verify team is actively investigating and working to restore normal monitor functionality.

    2. September 10, 2026 at 11:50 AM UTCidentified

      The issue in the monitoring scripts has been identified and a fix is being implemented.

    3. September 10, 2026 at 1:58 PM UTCmonitoring

      A fix has been implemented and we are monitoring the results.

    4. September 10, 2026 at 2:15 PM UTCresolved

      This incident has been resolved.

    IBM Verify (Japan Region) service impacting issue - now recovered.

    Started September 8, 2026 at 8:21 AM UTC · 0m

    Pending
    Affected components
    Single sign on for OIDC applicationsAuthentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersUser ID and password authentication from APIApplication OnboardingCloud Directory Users and Groups managementSingle sign on for SAML applicationsUser and Group management with API clientAccount LifecycleAuthentication with External LDAP
    1. September 8, 2026 at 8:21 AM UTCresolved

      IBM Verify (Japan) experienced a brief service disruption from 07:40 UTC for approximately 10 minutes. The disruption was caused by an unexpected interruption to an internal component. During this period, some authentication requests may have failed. Service has been restored, and all systems are operating normally.

    IBM Verify (US Region Cluster C ) had brief service impact

    Started August 25, 2026 at 12:48 PM UTC · 5h 58m

    OutageMajor incident
    Affected components
    Account Lifecycle (Cluster C)Authentication with External LDAP (Cluster C)Authentication with SAML Identity Provider (Cluster C)Application Onboarding (Cluster C)Authentication with IBMid for admin users (Cluster C)Cloud Directory Users and Groups management (Cluster C)User and Group management with API client (Cluster C)Single sign on for OIDC applications (Cluster C)Single sign on for SAML applications (Cluster C)Authentication with Cloud Directory (Cluster C)User ID and password authentication from API (Cluster C)
    1. August 25, 2026 at 12:48 PM UTCmonitoring

      IBM Verify (US Region Cluster C) experienced a brief service disruption at 12 noon UTC for approx 5 minutes. Service is restored and IBM is monitoring

    2. August 25, 2026 at 6:45 PM UTCresolved

      This incident has been resolved.

    IBM Verify (Europe Region) experiencing service impacting issues.

    Started August 20, 2026 at 3:39 PM UTC · 5d 4h

    OutageMajor incident
    Affected components
    Single sign on for OIDC applicationsAuthentication with SAML Identity ProviderAuthentication with External LDAPUser and Group management with API clientAccount LifecycleAuthentication with IBMid for admin usersApplication OnboardingAuthentication with Cloud DirectoryCloud Directory Users and Groups managementUser ID and password authentication from APISingle sign on for SAML applications
    1. August 20, 2026 at 3:39 PM UTCinvestigating

      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. August 20, 2026 at 4:11 PM UTCinvestigating

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

    3. August 20, 2026 at 4:44 PM UTCinvestigating

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

    4. August 20, 2026 at 5:26 PM UTCidentified

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

    5. August 20, 2026 at 6:26 PM UTCidentified

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

    6. August 20, 2026 at 10:22 PM UTCidentified

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

    7. August 21, 2026 at 8:08 AM UTCmonitoring

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

    8. August 25, 2026 at 8:02 PM UTCresolved

      This incident has been resolved.

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

    Started August 11, 2026 at 9:29 AM UTC · 1h 2m

    OutageMajor incident
    Affected components
    Account Lifecycle (Cluster C)Authentication with External LDAP (Cluster C)Authentication with SAML Identity Provider (Cluster C)Application Onboarding (Cluster C)Authentication with IBMid for admin users (Cluster C)Cloud Directory Users and Groups management (Cluster C)User and Group management with API client (Cluster C)Single sign on for OIDC applications (Cluster C)Single sign on for SAML applications (Cluster C)Authentication with Cloud Directory (Cluster C)User ID and password authentication from API (Cluster C)
    1. August 11, 2026 at 9:29 AM UTCinvestigating

      IBM Security Verify (US Region Cluster C) customers may be experiencing issues with the service. We are currently investigating. This is affecting IBMid login from other clusters

    2. August 11, 2026 at 9:41 AM UTCmonitoring

      Issue has been identified. Service is restored. IBM is monitoring.

    3. August 11, 2026 at 10:30 AM UTCresolved

      The incident is fully resolved.

    IBM Verify - delays in SMS delivery for One Time Passcode

    Started August 5, 2026 at 1:10 PM UTC · 10h 3m

    IssuesMinor incident
    Affected components
    User ID and password authentication from API (Cluster A)Authentication with Cloud Directory (Cluster B)Authentication with Cloud DirectoryAuthentication with Cloud Directory (Cluster C)
    1. August 5, 2026 at 1:10 PM UTCinvestigating

      IBM Verify users in US that rely on SMS for OTP may be experiencing delays in SMS delivery. We are currently investigating.

    2. August 5, 2026 at 1:56 PM UTCmonitoring

      Services have been generally restored and SMS based MFA messages are now being received.

    3. August 5, 2026 at 11:13 PM UTCresolved

      Service has remained stable following the corrective actions implemented by our engineering teams. No further issues related to this incident have been observed.

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

    Started August 4, 2026 at 4:42 AM UTC · 10h 49m

    OutageCritical incident
    Affected components
    Authentication with Cloud DirectoryCloud Directory Users and Groups managementUser and Group management with API client
    1. August 4, 2026 at 4:42 AM UTCinvestigating

      We are currently investigating alerts for Japan.

    2. August 4, 2026 at 8:26 AM UTCmonitoring

      The issue was identified and recovery actions were completed at 05:35 UTC. Services have recovered and are operating normally. We are continuing to monitor the environment closely.

    3. August 4, 2026 at 3:31 PM UTCresolved

      This incident has been resolved.

    [GDSC] Risk Events experience delayed processing

    Started August 1, 2026 at 1:58 PM UTC · 5d 8h

    IssuesMinor incident
    Affected components
    Risk Events
    1. August 1, 2026 at 1:58 PM UTCidentified

      The GDSC Risk Events are presenting an slight delay in process, our team are aware of this situation and are closely monitoring and analyzing it.

    2. August 1, 2026 at 2:00 PM UTCidentified

      We are continuing to work on a fix for this issue.

    3. August 2, 2026 at 3:37 PM UTCmonitoring

      This is being continously monitored. The cause has been identified and we're monitoring the Risk events behavior activity now.

    4. August 6, 2026 at 10:12 PM UTCresolved

      This incident has been resolved. After careful review by our team, we can determine the issue is contained.

    Degraded Performance Affecting Multiple Verify Tenants

    Started July 27, 2026 at 5:02 PM UTC · 2d 2h

    Pending
    1. July 27, 2026 at 5:02 PM UTCinvestigating

      We are investigating degraded performance affecting multiple IBM Security Verify tenants. Customers may experience increased latency, intermittent timeouts, authentication failures, and elevated HTTP 503 errors. Engineering teams are actively working to mitigate the issue and restore normal service. Further updates will be provided as they become available.

    2. July 27, 2026 at 6:41 PM UTCinvestigating

      We have implemented mitigation actions and are observing improved service performance across affected IBM Security Verify tenants. Our engineering teams continue to closely monitor the environment to ensure service stability while the investigation remains ongoing. We will provide additional updates as more information becomes available.

    3. July 27, 2026 at 7:41 PM UTCinvestigating

      We are continuing to investigate this issue.

    4. July 27, 2026 at 10:55 PM UTCidentified

      Engineering teams have identified the factors contributing to the service degradation and are actively implementing a permanent fix. Mitigation actions have been implemented to restore platform stability and reduce impact across affected tenants. Monitoring and validation activities remain ongoing. Further updates will be provided as they become available.

    5. July 28, 2026 at 8:24 PM UTCmonitoring

      Corrective actions have been implemented and service performance remains stable. Validation activities have been completed successfully, and affected workloads have continued to operate normally under production traffic levels. Engineering teams are maintaining enhanced monitoring while final follow-up activities and the post-incident review continue. We will provide additional updates as progress continues.

    6. July 29, 2026 at 7:49 PM UTCresolved

      Service has remained stable following the corrective actions implemented by our engineering teams. Customer validation completed successfully, and no further issues related to this incident have been observed. This incident has been resolved.

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

    Started July 22, 2026 at 2:37 PM UTC · 3h 37m

    OutageMajor incident
    Affected components
    Single sign on for OIDC applicationsAuthentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersUser ID and password authentication from APIApplication OnboardingCloud Directory Users and Groups managementSingle sign on for SAML applicationsUser and Group management with API clientAccount LifecycleAuthentication with External LDAP
    1. July 22, 2026 at 2:37 PM UTCinvestigating

      IBM Security Verify (Japan Region) customers may be experiencing issues with the service. We are currently investigating alerts for Japan.

    2. July 22, 2026 at 2:59 PM UTCidentified

      The issue has been identified. Verify team is working to remediate.

    3. July 22, 2026 at 3:52 PM UTCidentified

      We are continuing to work on remediation.

    4. July 22, 2026 at 4:43 PM UTCmonitoring

      Following recovery steps undertaken, services have recovered. We are continuing to monitor.

    5. July 22, 2026 at 4:52 PM UTCmonitoring

      We are continuing to monitor for any further issues.

    6. July 22, 2026 at 6:15 PM UTCresolved

      Issue in ISV Japan is resolved. All monitoring has been clear.

    GDSC Datamart processor performance degradation

    Started July 17, 2026 at 1:49 PM UTC · 34d 6h

    Pending
    Affected components
    Risk EventsData Management – Ingestion (Datamart)Outliers
    1. July 17, 2026 at 1:49 PM UTCinvestigating

      We are continuing to investigate an issue affecting the datamart ingestion service. Our engineering team is actively working to restore normal operations. During this time, some data may be delayed or incomplete. We will provide further updates as more information becomes available.

    2. July 22, 2026 at 4:42 PM UTCinvestigating

      We have identified a delay in the Datamart data ingestion process today. The issue is actively under review by our team, and we are continuously monitoring the service. Further updates will be provided as more information becomes available.

    3. July 22, 2026 at 10:34 PM UTCmonitoring

      The ingestion backlog has been cleared and processing has normalized. The service remains stable, and we will continue monitoring as a precaution.

    4. August 6, 2026 at 1:03 AM UTCmonitoring

      We have detected an slight degradation in the event ingestion. The team is actively reviewing and have identified the cause of it.

    5. August 12, 2026 at 12:15 PM UTCinvestigating

      We have detected an slight degradation in the event ingestion. The team is actively monitoring and investigating.

    6. August 18, 2026 at 10:32 PM UTCinvestigating

      We are continuing to investigate this issue.

    7. August 20, 2026 at 7:54 PM UTCresolved

      This incident has been resolved.

    AI ChatBot might experience delayed responses

    Started July 1, 2026 at 9:09 PM UTC · 49d 22h

    Pending
    Affected components
    AI ChatBot (Chat with watsonx)AI ChatBot (Chat with watsonx)
    1. July 1, 2026 at 9:09 PM UTCidentified

      We are currently investigating internal issues affecting the AI ChatBot. During this time, users may experience delays in responses.

    2. July 29, 2026 at 8:55 PM UTCmonitoring

      A fix has been identified, it is currently under review, testing and monitoring. We will be updating once a complete solution has been achieved.

    3. August 20, 2026 at 7:49 PM UTCresolved

      This incident has been resolved.

    Datamart Ingestion processing slowness

    Started June 25, 2026 at 8:45 PM UTC · 3d 19h

    IssuesMinor incident
    Affected components
    Risk EventsData Management – Ingestion (Datamart)Outliers
    1. June 25, 2026 at 8:45 PM UTCinvestigating

      DataMart, Risk Events, and Outliers services are currently experiencing degraded performance, including slow ingestion processing. This may result in delays in reporting. Our team is actively investigating the issue.

    2. June 29, 2026 at 4:22 PM UTCresolved

      We have been actively monitoring our ingestion and processing rates, and we can now confirm that they have returned to expected levels. The system has been stable and operating normally since the weekend, so this issue is now fully resolved. Thank you for your patience.