Ibm Security outage history and incident timeline

AI ChatBot might experience delayed responses

Started July 1, 2026 at 9:09 PM UTC Ongoing

IssuesMinor incident

Affected components

AI ChatBot (Chat with watsonx)AI ChatBot (Chat with watsonx)

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.

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

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.
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.

IBM Security Verify (US Region) service impacting issue

Started June 24, 2026 at 6:32 PM UTC 1h 54m

Pending

Affected components

Single sign on for SAML applications (Cluster A)Authentication with Cloud Directory (Cluster A)User ID and password authentication from API (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)Authentication with SAML Identity Provider (Cluster A)Authentication with IBMid for admin users (Cluster A)Account Lifecycle (Cluster A)

June 24, 2026 at 6:32 PM UTCmonitoring
IBM Security Verify (US Region) customers may have experienced a brief service impact at approx 18:15 UTC. The issue lasted for approx 5 minutes and affected some tenants / customers. Issue is resolved and service is restored.
June 24, 2026 at 8:26 PM UTCresolved
Service has been operational for some time. Closing this incident.

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

Started June 15, 2026 at 6:33 PM UTC 1d 21h

OutageMajor incident

Affected components

Single sign on for SAML applications (Cluster A)Authentication with Cloud Directory (Cluster A)User ID and password authentication from API (Cluster A)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)User and Group management with API client (Cluster A)Authentication with SAML Identity Provider (Cluster A)Authentication with IBMid for admin users (Cluster A)Account Lifecycle (Cluster A)

June 15, 2026 at 6:33 PM UTCinvestigating
IBM Security Verify (US Region Cluster A) customers is experiencing intermittent issues with the service. We are currently investigating.
June 15, 2026 at 6:55 PM UTCidentified
We have identified the issue and are taking steps to address
June 17, 2026 at 4:03 PM UTCresolved
This issue is resolved. Closing

IBM Security Verify (US Region Cluster C ) experienced short service interruption

Started June 15, 2026 at 3:20 PM UTC 0m

Pending

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)

June 15, 2026 at 3:20 PM UTCresolved
IBM Security Verify experienced a short period of service impact at 14:50 UTC. that resolved at 14:52 UTC. All services are currently available.

IBM Verify Canada - Brief interruptions occurred to traffic on vanity hostnames during planned maintenance activity.

Started June 11, 2026 at 7:30 AM UTC 0m

IssuesMinor incident

June 11, 2026 at 10:46 AM UTCresolved
The planned maintenance has been completed successfully. However, a small number of customers may have experienced brief interruptions affecting traffic on vanity hostnames during the maintenance window. The issue was resolved, and all systems are back to normal working condition.

Guardium Data Security Center (US) - Demo tenants provisioning

Started June 8, 2026 at 10:41 PM UTC Ongoing

IssuesMinor incident

Affected components

Account Management

June 8, 2026 at 10:41 PM UTCidentified
We are currently experiencing issues affecting the provisioning of demo tenants. Users may encounter delays or failures during the setup process. Our team is actively investigating and working to restore normal functionality as quickly as possible.

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

Started May 7, 2026 at 6:00 AM UTC 0m

Pending

May 7, 2026 at 7:28 AM UTCresolved
IBM Security Verify (Europe Region). Some customers may have experienced a short period where services were inaccessible. Services are restored and now fully operational.

IBM Verify - authentication issues in Canada cluster

Started May 5, 2026 at 6:36 AM UTC 1d 5h

OutageCritical incident

Affected components

Single sign on for OIDC applicationsAuthentication with Cloud DirectorySingle sign on for SAML applicationsApplication OnboardingUser ID and password authentication from API

May 5, 2026 at 6:36 AM UTCinvestigating
We are currently investigating the issue.
May 5, 2026 at 7:08 AM UTCidentified
An issue has been identified and we are working on remediation steps.
May 5, 2026 at 7:32 AM UTCmonitoring
A fix has been implemented and we are monitoring the system.
May 6, 2026 at 11:48 AM UTCresolved
This incident has been resolved.

IBM Verify - authentication issues in Canada region

Started April 30, 2026 at 12:38 PM UTC 1h 3m

Pending

Affected components

Authentication with IBMid for admin users ( Cluster B )Single sign on for OIDC applications ( Cluster B )Authentication with Cloud Directory ( Cluster B )Account Lifecycle ( Cluster B )Application Onboarding ( Cluster B )Authentication with External LDAP ( Cluster B )Single sign on for SAML applications ( Cluster B )User ID and password authentication from API ( Cluster B )Authentication with SAML Identity Provider ( Cluster B )

April 30, 2026 at 12:38 PM UTCmonitoring
IBM Verify Canada Cluster B experienced an issue affecting authentications. Issue has been resolved at this time and we are currently monitoring.
April 30, 2026 at 1:41 PM UTCresolved
Monitoring has been successful. Issue is remediated. x

GDSC Datamart Ingestion Issue

Started April 27, 2026 at 3:58 PM UTC 14d 8h

OutageMajor incident

Affected components

Data Management – Ingestion (Datamart)Data Management – Ingestion (Datamart)

April 27, 2026 at 3:58 PM UTCinvestigating
The datamart ingestion pipeline is experiencing partial failures, causing some datasets not to be ingested successfully. We are actively investigating the issue to determine the root cause and restore normal operation.
April 27, 2026 at 6:51 PM UTCidentified
The root cause has been identified, and we are currently working on implementing a potential fix for the issue.
April 27, 2026 at 10:21 PM UTCidentified
We are continuing to investigate an issue affecting the datamart ingestion service. Our engineering team is actively working to identify the root cause and restore normal operations. During this time, some data may be delayed or incomplete. We will provide further updates as more information becomes available.
April 29, 2026 at 12:45 PM UTCidentified
A fix has been applied and issue is resolved. We are monitoring the service.
April 30, 2026 at 4:25 PM UTCinvestigating
Status: Mitigating We are continuing to address degraded data ingestion performance, which is causing delays in downstream components that rely on ingested data. The platform remains available; however, data freshness is impacted. The root cause has not yet been confirmed. In coordination with Cloud provider Support, current findings suggest database lock contention in Data warehouse DB as a contributing factor. We are actively tuning ingestion concurrency, scaling database capacity, and working with Cloud provider to restore normal processing rates. Further updates will be provided as mitigation progresses.
April 30, 2026 at 11:50 PM UTCmonitoring
A mitigation has been successfully implemented and we are monitoring the results. The data warehouse engine rollback has completed, and data ingestion throughput has recovered as expected. The processing backlog is decreasing rapidly, and downstream components dependent on ingestion are beginning to normalize. We will continue to closely monitor ingestion performance and data freshness to ensure sustained stability before marking the incident as fully resolved.
May 4, 2026 at 2:32 PM UTCidentified
We continue to experience material degradation in data ingestion and downstream event generation. While some progress has been made, ingestion throughput remains inconsistent and backlog processing is ongoing. As a result, risk events and outliers may be delayed or incomplete.
May 4, 2026 at 9:06 PM UTCmonitoring
Our Engineering and SRE teams worked through the weekend and made some adjustments to the ingestion service process today. The platform is actively processing queued data now and ingestion throughput is improving. We expect the ingestion of data to catch up by tomorrow morning. Our teams remain closely engaged and are monitoring progress to ensure continued recovery. Further updates will be provided about the progress to completely restoring all services.
May 5, 2026 at 3:10 PM UTCmonitoring
Ingestion continues to make steady progress. The new ingest queue is decreasing, and retry volume is now very low and stable. Queued data is actively being processed, and the platform remains stable under the current operating conditions. We will continue to monitor closely as the remaining backlog drains and ingestion continues toward full normalization.
May 5, 2026 at 11:44 PM UTCmonitoring
Ingestion has caught up to current data, and the platform is operating in a stable state. Backlog queues have been processed successfully, and new incoming data is being handled normally as it arrives. Downstream processing, including risk generation, has resumed and data is flowing as expected. We will continue to monitor closely to ensure sustained stability as regular ingestion cycles continue.
May 12, 2026 at 12:01 AM UTCresolved
The ingestion service has returned to stable operation, and the platform is processing data normally. Ingestion has caught up to current data, and all core services are functioning as expected. Our teams will continue to monitor the system, but no further operational impact is anticipated related to this incident. Thank you for your patience.

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

Started April 23, 2026 at 11:00 PM UTC 23h 2m

Pending

Affected components

Single sign on for SAML applications (Cluster E)Single sign on for SAML applications (Cluster A)Single sign on for OIDC applications (Cluster E)Account Lifecycle (Cluster C)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)Authentication with External LDAP (Cluster C)Cloud Directory Users and Groups management (Cluster A)Authentication with SAML Identity Provider (Cluster C)Authentication with IBMid for admin users (Cluster B)Authentication with SAML Identity Provider (Cluster B)User and Group management with API client (Cluster E)User and Group management with API client (Cluster A)Authentication with Cloud Directory (Cluster E)Account Lifecycle (Cluster B)Application Onboarding (Cluster C)Authentication with IBMid for admin users (Cluster C)Account Lifecycle (Cluster E)Authentication with SAML Identity Provider (Cluster A)Authentication with IBMid for admin users (Cluster A)Cloud Directory Users and Groups management (Cluster C)Application Onboarding (Cluster B)Authentication with IBMid for admin users (Cluster E)User and Group management with API client (Cluster C)User ID and password authentication from API (Cluster E)Account Lifecycle (Cluster A)Authentication with SAML Identity Provider (Cluster E)Single sign on for OIDC applications (Cluster C)User ID and password authentication from API (Cluster B)Single sign on for SAML applications (Cluster C)Cloud Directory Users and Groups management (Cluster E)Authentication with Cloud Directory (Cluster C)Application Onboarding (Cluster E)User ID and password authentication from API (Cluster C)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)

April 23, 2026 at 11:00 PM UTCinvestigating
We are currently investigating this issue.
April 24, 2026 at 4:19 AM UTCmonitoring
Issue is mitigated and we are monitoring the system.
April 24, 2026 at 3:44 PM UTCidentified
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.
April 24, 2026 at 4:41 PM UTCmonitoring
We will continue to monitor.
April 24, 2026 at 4:42 PM UTCmonitoring
We are continuing to monitor for any further issues.
April 24, 2026 at 10:02 PM UTCresolved
This incident has been resolved. We will still continue to monitor to ensure there are no regression issues.

IBM Verify - authentication issues in Canada cluster

Started April 16, 2026 at 7:44 AM UTC 1d 11h

IssuesMinor incident

Affected components

Single sign on for OIDC applicationsAuthentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with External LDAPAccount LifecycleSingle sign on for SAML applicationsApplication OnboardingAuthentication with IBMid for admin usersUser ID and password authentication from API

April 16, 2026 at 7:44 AM UTCinvestigating
IBM Verify team is investigating authentication failures in Canada region Cluster A
April 16, 2026 at 8:35 AM UTCinvestigating
We are continuing to investigate the issue
April 16, 2026 at 10:39 AM UTCmonitoring
Authentication services are recovering at this time. We are continuing to investigate the cause and will continue to monitor
April 16, 2026 at 11:41 AM UTCmonitoring
Service continues to be fully available. We are continuing to monitor
April 17, 2026 at 7:05 PM UTCresolved
This incident has been resolved.

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

Started April 8, 2026 at 2:54 PM UTC 7d 16h

Pending

Affected components

Single sign on for OIDC applications (Cluster B)Authentication with External LDAP (Cluster B)Authentication with Cloud Directory (Cluster B)Authentication with IBMid for admin users (Cluster B)Authentication with SAML Identity Provider (Cluster B)Account Lifecycle (Cluster B)Application Onboarding (Cluster B)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)

April 8, 2026 at 2:54 PM UTCinvestigating
IBM Verify (US Region) customers may be experiencing issues with the service in Cluster B. We are currently investigating.
April 16, 2026 at 7:41 AM UTCresolved
issue is fully resolved

GDSC AI Chatbot is having issues on US and EU region.

Started April 1, 2026 at 7:37 PM UTC 33d 1h

IssuesMinor incident

Affected components

AI ChatBot (Chat with watsonx)AI ChatBot (Chat with watsonx)

April 1, 2026 at 7:37 PM UTCinvestigating
Service is temporary down. We are investigating the issue.
April 24, 2026 at 2:55 PM UTCinvestigating
We are continuing to investigate this issue.
May 4, 2026 at 9:16 PM UTCresolved
The issue is now resolved

IBM Verify Australia Region - Invesgigating service impacting issues

Started March 19, 2026 at 9:38 AM UTC 4d 2h

OutageMajor incident

March 19, 2026 at 9:38 AM UTCinvestigating
We are currently investigating issues in IBM Verify Australia Region affecting services Cluster A
March 19, 2026 at 9:56 AM UTCinvestigating
Services are being restored and coming on-line.
March 19, 2026 at 10:53 AM UTCmonitoring
Service has been restored and services operating successfully for past hour. We are continuing to monitor.
March 23, 2026 at 12:13 PM UTCresolved
Issue was fully resolved on March 19th

GDSC system slowness

Started March 4, 2026 at 4:43 PM UTC 7h 31m

Pending

Affected components

Data Management – Ingestion (Datamart)Reports / Dashboard

March 4, 2026 at 4:43 PM UTCinvestigating
We are experiencing slowness in the GDSC platform and we are currently investigating the issue
March 4, 2026 at 7:46 PM UTCinvestigating
We have identified the issue and we are currently working on the fix
March 4, 2026 at 7:46 PM UTCidentified
The issue has been identified and a fix is being implemented.
March 5, 2026 at 12:15 AM UTCresolved
The issue was resolved and now we are monitoring the system

GDSC facing login issues

Started February 23, 2026 at 4:51 PM UTC 8h 54m

Pending

Affected components

User Interface LoginUser Interface Login

February 23, 2026 at 4:51 PM UTCinvestigating
We are facing issues with the login, we will provide an update soon
February 23, 2026 at 4:56 PM UTCidentified
We're experiencing intermittent problems; we'll update as soon as they're fixed.
February 24, 2026 at 1:45 AM UTCresolved
We have received confirmation that the login issue has been resolved

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

Started February 23, 2026 at 2:38 PM UTC 10h 9m

OutageMajor incident

Affected components

February 23, 2026 at 2:38 PM UTCinvestigating
IBM Security Verify (US Region) customers may be experiencing issues with the service in some clusters. We are currently investigating.
February 23, 2026 at 3:09 PM UTCinvestigating
We are continuing to investigate the issue.
February 23, 2026 at 3:30 PM UTCidentified
Services are restoring at present.
February 23, 2026 at 5:21 PM UTCmonitoring
Following a number of remediation actions to address issues, services have been restored. We are moving to a monitoring state
February 23, 2026 at 5:30 PM UTCinvestigating
Some additional issues have been reported. Currently investigating,
February 23, 2026 at 7:09 PM UTCidentified
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.
February 23, 2026 at 9:16 PM UTCidentified
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.
February 23, 2026 at 10:06 PM UTCidentified
Database engineering experts are continuing to work to mitigate the issue.
February 23, 2026 at 11:41 PM UTCmonitoring
A fix was applied to a common database by our database engineers. This has stabilised the performance issue. IBM is continuing to monitor.
February 24, 2026 at 12:48 AM UTCresolved
Confirming that the performance/database issue in US data centers is resolved.

GDSC Europe - Tenant provisioning failing

Started February 13, 2026 at 1:54 AM UTC 7d 13h

IssuesMinor incident

Affected components

Account Management

February 13, 2026 at 1:54 AM UTCidentified
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.
February 20, 2026 at 3:48 PM UTCresolved
The issues has been resolved