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.
May 04, 2026 - 21:06 UTC
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.
May 04, 2026 - 14:32 UTC
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.
Apr 30, 2026 - 23:50 UTC
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.
Apr 30, 2026 - 16:25 UTC
Update - A fix has been applied and issue is resolved. We are monitoring the service.
Apr 29, 2026 - 12:45 UTC
Update - 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.
Apr 27, 2026 - 22:21 UTC
Identified - The root cause has been identified, and we are currently working on implementing a potential fix for the issue.
Apr 27, 2026 - 18:51 UTC
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.
Apr 27, 2026 - 15:58 UTC
IBM Verify (Europe)
Operational
Authentication with Cloud Directory
Operational
Authentication with SAML Identity Provider
Operational
Authentication with IBMid for admin users
Operational
Authentication with External LDAP
Operational
User ID and password authentication from API
Operational
Single sign on for SAML applications
Operational
Single sign on for OIDC applications
Operational
Application Onboarding
Operational
Cloud Directory Users and Groups management
Operational
User and Group management with API client
Operational
Account Lifecycle
Operational
IBM Verify (US)
Operational
Authentication with Cloud Directory (Cluster A)
Operational
Authentication with SAML Identity Provider (Cluster A)
Operational
Authentication with IBMid for admin users (Cluster A)
Operational
Authentication with External LDAP (Cluster A)
Operational
User ID and password authentication from API (Cluster A)
Operational
Single sign on for SAML applications (Cluster A)
Operational
Single sign on for OIDC applications (Cluster A)
Operational
Application Onboarding (Cluster A)
Operational
Cloud Directory Users and Groups management (Cluster A)
Operational
User and Group management with API client (Cluster A)
Operational
Account Lifecycle (Cluster A)
Operational
Authentication with Cloud Directory (Cluster B)
Operational
Authentication with SAML Identity Provider (Cluster B)
Operational
Authentication with IBMid for admin users (Cluster B)
Operational
Authentication with External LDAP (Cluster B)
Operational
User ID and password authentication from API (Cluster B)
Operational
Single sign on for SAML applications (Cluster B)
Operational
Single sign on for OIDC applications (Cluster B)
Operational
Application Onboarding (Cluster B)
Operational
Cloud Directory Users and Groups management (Cluster B)
Operational
User and Group management with API client (Cluster B)
Operational
Account Lifecycle (Cluster B)
Operational
Authentication with Cloud Directory (Cluster C)
Operational
Authentication with SAML Identity Provider (Cluster C)
Operational
Authentication with IBMid for admin users (Cluster C)
Operational
Authentication with External LDAP (Cluster C)
Operational
User ID and password authentication from API (Cluster C)
Operational
Single sign on for SAML applications (Cluster C)
Operational
Single sign on for OIDC applications (Cluster C)
Operational
Application Onboarding (Cluster C)
Operational
Cloud Directory Users and Groups management (Cluster C)
Operational
User and Group management with API client (Cluster C)
Operational
Account Lifecycle (Cluster C)
Operational
Authentication with Cloud Directory (Cluster E)
Operational
Authentication with SAML Identity Provider (Cluster E)
Operational
Authentication with IBMid for admin users (Cluster E)
Operational
User ID and password authentication from API (Cluster E)
Operational
Single sign on for SAML applications (Cluster E)
Operational
Single sign on for OIDC applications (Cluster E)
Operational
Application Onboarding (Cluster E)
Operational
Cloud Directory Users and Groups management (Cluster E)
Operational
Account Lifecycle (Cluster E)
Operational
User and Group management with API client (Cluster E)
Operational
IBM Verify (Japan)
Operational
Authentication with Cloud Directory
Operational
Authentication with SAML Identity Provider
Operational
Authentication with IBMid for admin users
Operational
Authentication with External LDAP
Operational
User ID and password authentication from API
Operational
Single sign on for SAML applications
Operational
Single sign on for OIDC applications
Operational
Application Onboarding
Operational
Cloud Directory Users and Groups management
Operational
User and Group management with API client
Operational
Account Lifecycle
Operational
IBM Verify (Canada)
Operational
Authentication with Cloud Directory
Operational
Authentication with SAML Identity Provider
Operational
Authentication with IBMid for admin users
Operational
Authentication with External LDAP
Operational
User ID and password authentication from API
Operational
Single sign on for SAML applications
Operational
Single sign on for OIDC applications
Operational
Application Onboarding
Operational
Account Lifecycle
Operational
Authentication with Cloud Directory ( Cluster B )
Operational
Authentication with SAML Identity Provider ( Cluster B )
Operational
Authentication with IBMid for admin users ( Cluster B )
Operational
Authentication with External LDAP ( Cluster B )
Operational
User ID and password authentication from API ( Cluster B )
Operational
Single sign on for SAML applications ( Cluster B )
Operational
Single sign on for OIDC applications ( Cluster B )
Operational
Application Onboarding ( Cluster B )
Operational
Account Lifecycle ( Cluster B )
Operational
IBM Verify (Australia)
Operational
Authentication with Cloud Directory
Operational
Authentication with SAML Identity Provider
Operational
Authentication with IBMid for admin users
Operational
User ID and password authentication from API
Operational
Single sign on for SAML applications
Operational
Application Onboarding
Operational
Cloud Directory Users and Groups management
Operational
User and Group management with API client
Operational
Single sign on for OIDC applications
Operational
Account Lifecycle
Operational
Authentication with Cloud Directory ( Cluster B )
Operational
Authentication with SAML Identity Provider ( Cluster B )
Operational
Authentication with IBMid for admin users ( Cluster B )
Operational
User ID and password authentication from API ( Cluster B )
Operational
Single sign on for SAML applications ( Cluster B )
Operational
Application Onboarding ( Cluster B )
Operational
Cloud Directory Users and Groups management ( Cluster B )
Operational
User and Group management with API client ( Cluster B )
Operational
Single sign on for OIDC applications ( Cluster B )
Operational
Account Lifecycle ( Cluster B )
Operational
X-Force Exchange
Partial Outage
X-Force Exchange Platform
Operational
Threat Intelligence
Operational
Notifications
Partial Outage
Login
Operational
IBM Guardium Data Security Center (US)
Partial Outage
Account Management
Operational
AI ChatBot (Chat with watsonx)
Operational
API Key Authentication from API
Operational
Audit Process / Workflow
Operational
Cloud / SaaS 3rd Parties
Operational
Cloud / SaaS Connections
Operational
Cloud / SaaS Discover and Classification
Operational
Cloud / SaaS Stores
Operational
Cloud / SaaS Vulnerabilities
Operational
Data Management – Ingestion (Datamart)
Partial Outage
Data Management – Retention / Archive
Operational
Database Asset Management
Operational
Integration Ecosystem
Operational
Outliers
Partial Outage
Reports / Dashboard
Operational
Risk Events
Partial Outage
User Interface Login
Operational
IBM Guardium Data Security Center (EU)
Partial Outage
Account Management
Operational
AI ChatBot (Chat with watsonx)
Operational
API Key Authentication from API
Operational
Audit Process / Workflow
Operational
Cloud / SaaS 3rd Parties
Operational
Cloud / SaaS Connections
Operational
Cloud / SaaS Discover and Classification
Operational
Cloud / SaaS Stores
Operational
Cloud / SaaS Vulnerabilities
Operational
Data Management – Ingestion (Datamart)
Partial Outage
Update -
Start Date: 2026-05-05 18:00 UTC End Date: 2026-05-06 00:00 UTC Expected Duration: 6 hours Event Type: Deployment of the Latest Updates to All Production Environments Impact: High. Expect up to 30 minutes of degraded service following the deployment.
We will be conducting essential maintenance to deploy the latest updates across all production environments in EMEA. This maintenance is scheduled to last approximately 6 hours.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to enhance our services.
Best regards, IBM QRadar Suite SRE Team
Apr 29, 2026 - 20:30 UTC
Scheduled -
Start Date: 2026-05-05 18:00 UTC End Date: 2026-05-06 00:00 UTC Expected Duration: 6 hours Event Type: Deployment of the Latest Updates to All Production Environments Impact: High. Expect up to 30 minutes of degraded service following the deployment.
We will be conducting essential maintenance to deploy the latest updates across all production environments in EMEA. This maintenance is scheduled to last approximately 6 hours.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to enhance our services.
Best regards, IBM QRadar Suite SRE Team
Apr 29, 2026 - 19:15 UTC
Completed -
The scheduled maintenance has been completed.
May 5, 10:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 5, 04:00 UTC
Update -
Start Date: 2026-05-05 04:00 UTC End Date: 2026-05-05 10:00 UTC Expected Duration: 6 hours Event Type: Deployment of the Latest Updates to All Production Environments Impact: High. Expect up to 30 minutes of degraded service following the deployment.
We will be conducting essential maintenance to deploy the latest updates across all production environments in AMER. This maintenance is scheduled to last approximately 6 hours.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to enhance our services.
Best regards, IBM QRadar Suite SRE Team
Apr 29, 20:29 UTC
Scheduled -
Start Date: 2026-05-05 04:00 UTC End Date: 2026-05-05 10:00 UTC Expected Duration: 6 hours Event Type: Deployment of the Latest Updates to All Production Environments Impact: High. Expect up to 30 minutes of degraded service following the deployment.
We will be conducting essential maintenance to deploy the latest updates across all production environments in AMER. This maintenance is scheduled to last approximately 6 hours.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to enhance our services.
Best regards, IBM QRadar Suite SRE Team
Apr 29, 19:14 UTC
Resolved -
Monitoring has been successful. Issue is remediated. x
Apr 30, 13:41 UTC
Monitoring -
IBM Verify Canada Cluster B experienced an issue affecting authentications. Issue has been resolved at this time and we are currently monitoring.
Apr 30, 12:38 UTC
Completed -
The scheduled maintenance has been completed.
Apr 30, 12:35 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 30, 09:00 UTC
Scheduled -
We are performing scheduled maintenance on Thursday.
Date: 30-April-2026 Time: 7:00 PM - 12:00 AM AEDT (Sydney time) Expected Impact: Minimal to none
Action Required Before Maintenance ------------------------------------------- As part of this maintenance, egress IP addresses used by IBM Verify services will be updated. If your network restricts inbound traffic, you may need to update your firewall rules to allow the new IPs to ensure uninterrupted communication.
During the Maintenance Window ------------------------------------- User services remain operational - Authentication, registration, and all user activities will continue without interruption.
Admin operations - A brief interruption may be seen when using admin APIs or while using the admin console to perform certain operations. A notification banner will appear on the admin console indicating temporary restrictions on configuration changes. The interruption is expected to last for only a few minutes.
What to do if you experience issues ------------------------------------------ If you encounter any problems during the maintenance window, please wait a few minutes and retry.
Post-maintenance ---------------------- We will confirm full service availability once maintenance is complete. For questions or concerns, please raise a support case.
Apr 29, 13:36 UTC
Completed -
The scheduled maintenance has been completed.
Apr 28, 16:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 28, 08:00 UTC
Scheduled -
IBM Cloud Pak for Security will be performing a middleware upgrade within our North American data centers starting 2026-04-28 at 08:00 UTC.
The maintenance is expected to last approximately 8 hours.
IBM Cloud Pak for Security DevOps Team
Apr 21, 16:27 UTC
Completed -
The scheduled maintenance has been completed.
Apr 27, 10:43 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 27, 09:00 UTC
Scheduled -
We are performing scheduled maintenance on Monday.
Date: 27-April-2026 Time: 7:00 PM - 12:00 AM AEDT (Sydney time) Expected Impact: Minimal to none
Action Required Before Maintenance ------------------------------------------- As part of this maintenance, egress IP addresses used by IBM Verify services will be updated. If your network restricts inbound traffic, you may need to update your firewall rules to allow the new IPs to ensure uninterrupted communication.
During the Maintenance Window ------------------------------------- User services remain operational - Authentication, registration, and all user activities will continue without interruption.
Admin operations - A brief interruption may be seen when using admin APIs or while using the admin console to perform certain operations. A notification banner will appear on the admin console indicating temporary restrictions on configuration changes. The interruption is expected to last for only a few minutes.
What to do if you experience issues ------------------------------------------ If you encounter any problems during the maintenance window, please wait a few minutes and retry.
Post-maintenance ---------------------- We will confirm full service availability once maintenance is complete. For questions or concerns, please raise a support case.
Apr 23, 13:48 UTC
Resolved -
This incident has been resolved. We will still continue to monitor to ensure there are no regression issues.
Apr 24, 22:02 UTC
Update -
We are continuing to monitor for any further issues.
Apr 24, 16:42 UTC
Monitoring -
We will continue to monitor.
Apr 24, 16:41 UTC
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.
Apr 24, 15:44 UTC
Monitoring -
Issue is mitigated and we are monitoring the system.
Apr 24, 04:19 UTC
Investigating -
We are currently investigating this issue.
Apr 23, 23:00 UTC
Completed -
The scheduled maintenance has been completed.
Apr 24, 00:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 23, 18:00 UTC
Scheduled -
Start Date: 2025-04-23 18:00 UTC End Date: 2025-04-24 00:00 UTC Expected Duration: 6 hours Event Type: Deployment of the Latest Updates to All Production Environments Impact: High. Expect up to 30 minutes of degraded service following the deployment.
We will be conducting essential maintenance to deploy the latest updates across all production environments in EMEA. This maintenance is scheduled to last approximately 6 hours.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to enhance our services.
Best regards, IBM QRadar Suite SRE Team
Apr 20, 16:21 UTC
Completed -
The scheduled maintenance has been completed.
Apr 23, 10:00 UTC
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 23, 04:00 UTC
Scheduled -
Start Date: 2025-04-23 04:00 UTC End Date: 2025-04-23 10:00 UTC Expected Duration: 6 hours Event Type: Deployment of the Latest Updates to All Production Environments Impact: High. Expect up to 30 minutes of degraded service following the deployment.
We will be conducting essential maintenance to deploy the latest updates across all production environments in AMER. This maintenance is scheduled to last approximately 6 hours.
We apologize for any inconvenience this may cause and appreciate your understanding as we continue to enhance our services.
Best regards, IBM QRadar Suite SRE Team
Apr 20, 16:20 UTC