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.
resolved
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.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Problem, das sich auf den Dienst IBM Security Verify (Region USA) auswirkt
Beginn 24. Juni 2026 um 18:32 UTC · 1h 54m
Pending
Betroffene Komponenten
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)
monitoring
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.
resolved
Service has been operational for some time. Closing this incident.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Bei IBM Security Verify (Region USA) treten Probleme auf, die sich auf den Service auswirken.
Beginn 15. Juni 2026 um 18:33 UTC · 1d 21h
OutageSchwerwiegender Vorfall
Betroffene Komponenten
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)
investigating
IBM Security Verify (US Region Cluster A) customers is experiencing intermittent issues with the service. We are currently investigating.
identified
We have identified the issue and are taking steps to address
resolved
This issue is resolved. Closing
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Bei IBM Security Verify (US Region Cluster C) kam es zu einer kurzen Serviceunterbrechung
Beginn 15. Juni 2026 um 15:20 UTC · 0m
Pending
Betroffene Komponenten
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)
resolved
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.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
IBM Verify Canada — Während der geplanten Wartungsarbeiten kam es zu kurzen Unterbrechungen des Datenverkehrs auf Vanity-Hostnamen.
Beginn 11. Juni 2026 um 07:30 UTC · 0m
IssuesGeringfügiger Vorfall
resolved
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.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Guardium Data Security Center (USA) — Bereitstellung von Demo-Mandanten
Beginn 8. Juni 2026 um 22:41 UTC · Laufend
IssuesGeringfügiger Vorfall
Betroffene Komponenten
Account Management
identified
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.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Bei IBM Security Verify (Region Europa) treten Probleme auf, die sich auf den Service auswirken.
Beginn 7. Mai 2026 um 06:00 UTC · 0m
Pending
resolved
IBM Security Verify (Europe Region). Some customers may have experienced a short period where services were inaccessible. Services are restored and now fully operational.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
IBM Verify — Authentifizierungsprobleme im kanadischen Cluster
Beginn 5. Mai 2026 um 06:36 UTC · 1d 5h
OutageKritischer Vorfall
Betroffene Komponenten
Single sign on for OIDC applicationsAuthentication with Cloud DirectorySingle sign on for SAML applicationsApplication OnboardingUser ID and password authentication from API
investigating
We are currently investigating the issue.
identified
An issue has been identified and we are working on remediation steps.
monitoring
A fix has been implemented and we are monitoring the system.
resolved
This incident has been resolved.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
IBM Verify — Authentifizierungsprobleme in der Region Kanada
Beginn 30. April 2026 um 12:38 UTC · 1h 3m
Pending
Betroffene Komponenten
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 )
monitoring
IBM Verify Canada Cluster B experienced an issue affecting authentications. Issue has been resolved at this time and we are currently monitoring.
resolved
Monitoring has been successful. Issue is remediated. x
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Problem mit der GDSC Datamart-Aufnahme
Beginn 27. April 2026 um 15:58 UTC · 14d 8h
OutageSchwerwiegender Vorfall
Betroffene Komponenten
Data Management – Ingestion (Datamart)Data Management – Ingestion (Datamart)
investigating
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.
identified
The root cause has been identified, and we are currently working on implementing a potential fix for the issue.
identified
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.
identified
A fix has been applied and issue is resolved. We are monitoring the service.
investigating
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.
monitoring
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.
identified
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.
monitoring
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.
monitoring
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.
monitoring
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.
resolved
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.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir glauben, dass das Problem mit den SMS-Versandfehlern behoben wurde.
Beginn 23. April 2026 um 23:00 UTC · 23h 2m
Pending
Betroffene Komponenten
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)
investigating
We are currently investigating this issue.
monitoring
Issue is mitigated and we are monitoring the system.
identified
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.
monitoring
We will continue to monitor.
monitoring
We are continuing to monitor for any further issues.
resolved
This incident has been resolved. We will still continue to monitor to ensure there are no regression issues.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
IBM Verify — Authentifizierungsprobleme im kanadischen Cluster
Beginn 16. April 2026 um 07:44 UTC · 1d 11h
IssuesGeringfügiger Vorfall
Betroffene Komponenten
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
investigating
IBM Verify team is investigating authentication failures in Canada region Cluster A
investigating
We are continuing to investigate the issue
monitoring
Authentication services are recovering at this time. We are continuing to investigate the cause and will continue to monitor
monitoring
Service continues to be fully available. We are continuing to monitor
resolved
This incident has been resolved.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
IBM Verify (Region USA). Mögliche Probleme, die sich auf den Service auswirken (Cluster B)
Beginn 8. April 2026 um 14:54 UTC · 7d 16h
Pending
Betroffene Komponenten
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)
investigating
IBM Verify (US Region) customers may be experiencing issues with the service in Cluster B. We are currently investigating.
resolved
issue is fully resolved
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Der GDSC AI Chatbot hat Probleme in der USA- und EU-Region.
Beginn 1. April 2026 um 19:37 UTC · 33d 1h
IssuesGeringfügiger Vorfall
Betroffene Komponenten
AI ChatBot (Chat with watsonx)AI ChatBot (Chat with watsonx)
investigating
Service is temporary down. We are investigating the issue.
investigating
We are continuing to investigate this issue.
resolved
The issue is now resolved
Automatisch aus der offiziellen Störungsmeldung übersetzt.
IBM Verify Region Australien — Untersuchung von Problemen, die sich auf den Service auswirken
Beginn 19. März 2026 um 09:38 UTC · 4d 2h
OutageSchwerwiegender Vorfall
investigating
We are currently investigating issues in IBM Verify Australia Region affecting services Cluster A
investigating
Services are being restored and coming on-line.
monitoring
Service has been restored and services operating successfully for past hour. We are continuing to monitor.
resolved
Issue was fully resolved on March 19th
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Langsamkeit des GDSC-Systems
Beginn 4. März 2026 um 16:43 UTC · 7h 31m
Pending
Betroffene Komponenten
Data Management – Ingestion (Datamart)Reports / Dashboard
investigating
We are experiencing slowness in the GDSC platform and we are currently investigating the issue
investigating
We have identified the issue and we are currently working on the fix
identified
The issue has been identified and a fix is being implemented.
resolved
The issue was resolved and now we are monitoring the system
Automatisch aus der offiziellen Störungsmeldung übersetzt.
GDSC hat Anmeldeprobleme
Beginn 23. Februar 2026 um 16:51 UTC · 8h 54m
Pending
Betroffene Komponenten
User Interface LoginUser Interface Login
investigating
We are facing issues with the login, we will provide an update soon
identified
We're experiencing intermittent problems; we'll update as soon as they're fixed.
resolved
We have received confirmation that the login issue has been resolved
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Bei IBM Security Verify (Region USA) treten Probleme auf, die sich auf den Service auswirken.
Beginn 23. Februar 2026 um 14:38 UTC · 10h 9m
OutageSchwerwiegender Vorfall
Betroffene Komponenten
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)
investigating
IBM Security Verify (US Region) customers may be experiencing issues with the service in some clusters. We are currently investigating.
investigating
We are continuing to investigate the issue.
identified
Services are restoring at present.
monitoring
Following a number of remediation actions to address issues, services have been restored. We are moving to a monitoring state
investigating
Some additional issues have been reported. Currently investigating,
identified
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.
identified
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.
identified
Database engineering experts are continuing to work to mitigate the issue.
monitoring
A fix was applied to a common database by our database engineers. This has stabilised the performance issue. IBM is continuing to monitor.
resolved
Confirming that the performance/database issue in US data centers is resolved.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
GDSC Europe — Mandantenbereitstellung schlägt fehl
Beginn 13. Februar 2026 um 01:54 UTC · 7d 13h
IssuesGeringfügiger Vorfall
Betroffene Komponenten
Account Management
identified
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.
resolved
The issues has been resolved
Automatisch aus der offiziellen Störungsmeldung übersetzt.