IBM Security Outage History

IBM Security is up right now

Pingoru has recorded 54 incidents for IBM Security: 49 in the last 12 months and 16 in the last 90 days.

Source: statuspage.ibmcloudsecurity.com

54incidents recorded
49last 12 months
16last 90 days
5 daystypical duration
Incidents per month
048AprMayJunJulAugSepOct3
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct12%
Pingoru began tracking IBM Security in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20267487 of 720 (68%)
May 20262256 of 744 (34%)
June 20266430 of 720 (60%)
July 20264672 of 744 (90%)
August 20266254 of 744 (34%)
September 2026633 of 720 (5%)
October 2026371 of 590 (12%)

Incidents, newest first

Major April 27, 2026 GDSC Datamart Ingestion Issue 14d 8h Data Management – Ingestion (Datamart), Data Management – Ingestion (Datamart)

Started Apr 27, 2026, 03:58 PM UTC· resolved May 12, 2026, 12:01 AM UTC

  1. investigating Apr 27, 2026, 03:58 PM UTC

    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.

  2. identified Apr 27, 2026, 06:51 PM UTC

    The root cause has been identified, and we are currently working on implementing a potential fix for the issue.

  3. identified Apr 27, 2026, 10:21 PM UTC

    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.

  4. identified Apr 29, 2026, 12:45 PM UTC

    A fix has been applied and seems issue is resolved. We are monitoring the service.

  5. investigating Apr 30, 2026, 04:25 PM UTC

    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.

  6. monitoring Apr 30, 2026, 11:50 PM UTC

    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.

  7. identified May 04, 2026, 02:32 PM UTC

    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.

  8. monitoring May 04, 2026, 09:06 PM UTC

    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.

  9. monitoring May 05, 2026, 03:10 PM UTC

    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.

  10. monitoring May 05, 2026, 11:44 PM UTC

    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.

  11. resolved May 12, 2026, 12:01 AM UTC

    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.

Read the full incident report →

Notice April 23, 2026 We believe the issue with the SMS send failures has been resolved. 23h 2m 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) and 39 more

Started Apr 23, 2026, 11:00 PM UTC· resolved Apr 24, 2026, 10:02 PM UTC

  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 →

Notice April 8, 2026 IBM Verify (US Region. Potential service impacting issues cluster B 7d 16h 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) and 7 more

Started Apr 08, 2026, 02:54 PM UTC· resolved Apr 16, 2026, 07:41 AM UTC

  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 →

Minor April 1, 2026 GDSC AI Chatbot is having issues on US and EU region. 33d 1h AI ChatBot (Chat with watsonx), AI ChatBot (Chat with watsonx)

Started Apr 01, 2026, 07:37 PM UTC· resolved May 04, 2026, 09:16 PM UTC

  1. investigating Apr 01, 2026, 07:37 PM UTC

    Service is temporary down. We are investigating the issue.

  2. investigating Apr 01, 2026, 07:38 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 24, 2026, 02:55 PM UTC

    We are continuing to investigate this issue.

  4. resolved May 04, 2026, 09:16 PM UTC

    The issue is now resolved

Read the full incident report →

Major March 19, 2026 IBM Verify Australia Region - Invesgigating service impacting issues 4d 2h Authentication with Cloud Directory, Authentication with SAML Identity Provider, Authentication with IBMid for admin users, User ID and password authentication from API and 6 more

Started Mar 19, 2026, 09:38 AM UTC· resolved Mar 23, 2026, 12:13 PM UTC

  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 7h 31m Data Management – Ingestion (Datamart), Reports / Dashboard

Started Mar 04, 2026, 04:43 PM UTC· resolved Mar 05, 2026, 12:15 AM UTC

  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 8h 54m User Interface Login, User Interface Login

Started Feb 23, 2026, 04:51 PM UTC· resolved Feb 24, 2026, 01:45 AM UTC

  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 →

Minor February 13, 2026 GDSC Europe - Tenant provisioning failing 7d 13h Account Management

Started Feb 13, 2026, 01:54 AM UTC· resolved Feb 20, 2026, 03:48 PM UTC

  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 23d 5h Data Management – Ingestion (Datamart), Outliers

Started Feb 10, 2026, 07:57 PM UTC· resolved Mar 06, 2026, 01:23 AM UTC

  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 →

Minor January 20, 2026 Service Degradation – Risk Events Not Generated 18h 39m Risk Events, Risk Events

Started Jan 20, 2026, 09:27 PM UTC· resolved Jan 21, 2026, 04:06 PM UTC

  1. investigating Jan 20, 2026, 09:27 PM UTC

    We are aware of an intermittent issue preventing risk events from being generated. The team is currently working to restore functionality. Thank you for your patience.

  2. monitoring Jan 21, 2026, 02:36 PM UTC

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

  3. resolved Jan 21, 2026, 04:06 PM UTC

    The issue affecting risk event generation has now been fully resolved. Our team has verified that no data was lost during this period. The only impact was that risk events were being generated intermittently.

Read the full incident report →

Major January 16, 2026 EU GDSC Risk Event service is impacted due to mongo connectivity 6h 25m Risk Events

Started Jan 16, 2026, 12:23 PM UTC· resolved Jan 16, 2026, 06:49 PM UTC

  1. investigating Jan 16, 2026, 12:23 PM UTC

    We are currently investigating this issue.

  2. resolved Jan 16, 2026, 06:49 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 14, 2026 US- RiskEvent service is partially down. 4h 17m Risk Events

Started Jan 14, 2026, 05:56 AM UTC· resolved Jan 14, 2026, 10:14 AM UTC

  1. investigating Jan 14, 2026, 05:56 AM UTC

    We are working on it to restore the service back online.

  2. investigating Jan 14, 2026, 06:39 AM UTC

    Mongodb went down and impacted our microservices.

  3. resolved Jan 14, 2026, 10:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 19, 2025 US- Unscheduled infrastructure maintenance 1h 21m Account Management, AI ChatBot (Chat with watsonx), API Key Authentication from API, Audit Process / Workflow and 13 more

Started Dec 19, 2025, 06:30 PM UTC· resolved Dec 19, 2025, 07:51 PM UTC

  1. identified Dec 19, 2025, 07:23 PM UTC

    We apologize for the unexpected infrastructure maintenance currently in progress, which may affect service availability. Our team is working to complete this as quickly as possible and will keep you updated. Thank you for your patience.

  2. resolved Dec 19, 2025, 07:51 PM UTC

    The unscheduled infrastructure change from our provider has been completed, and all services are now fully restored. We will follow up with them to understand the reason behind this change and ensure steps are taken to prevent unanticipated changes in the future. Thank you for your patience and understanding.

Read the full incident report →

Minor November 18, 2025 GDSC - Potential degradation in Outliers 4h 59m Outliers, Outliers

Started Nov 18, 2025, 03:21 PM UTC· resolved Nov 18, 2025, 08:20 PM UTC

  1. investigating Nov 18, 2025, 03:21 PM UTC

    We are currently investigating a potential degradation in Outliers. We are working on this with the highest priority. A new update will be provided as soon as more information is available.

  2. identified Nov 18, 2025, 04:09 PM UTC

    We have identified an issue affecting Outliers where the most recent events are not being displayed. This may impact dependent services. No data loss has occurred. Estimated Resolution Time: Within the next two hours.

  3. monitoring Nov 18, 2025, 05:16 PM UTC

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

  4. resolved Nov 18, 2025, 08:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 16, 2025 IBM Verify - Australia Region alerts 18h 13m Authentication with Cloud Directory, Authentication with SAML Identity Provider, Authentication with IBMid for admin users, User ID and password authentication from API and 6 more

Started Nov 16, 2025, 03:29 PM UTC· resolved Nov 17, 2025, 09:42 AM UTC

  1. investigating Nov 16, 2025, 03:29 PM UTC

    We are currently investigating alerts in Australia region.

  2. identified Nov 16, 2025, 03:46 PM UTC

    An issue with a local database has been identified. IBM is working to address the issue.

  3. monitoring Nov 16, 2025, 03:53 PM UTC

    Services have been restored. We are continuing work to stabilise the environment.

  4. identified Nov 16, 2025, 03:58 PM UTC

    We are experiencing further issues. Investigating.

  5. monitoring Nov 16, 2025, 04:30 PM UTC

    service has been restored. we will continue to monitor

  6. resolved Nov 17, 2025, 09:42 AM UTC

    Services have been running clean. Resolving the incident

Read the full incident report →

Critical November 11, 2025 IBM Verify - Investigating issues in Australia region 2h 28m Authentication with Cloud Directory, Authentication with SAML Identity Provider, Authentication with IBMid for admin users, User ID and password authentication from API and 6 more

Started Nov 11, 2025, 05:55 PM UTC· resolved Nov 11, 2025, 08:23 PM UTC

  1. investigating Nov 11, 2025, 05:55 PM UTC

    We are currently investigating alerts in Australia region.

  2. monitoring Nov 11, 2025, 06:43 PM UTC

    An issue was identified following a component upgrade. IBM teams implemented a fix and services are restored.

  3. monitoring Nov 11, 2025, 06:43 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Nov 11, 2025, 08:23 PM UTC

    Monitoring period was successful. All services operational. Closing the incident.

Read the full incident report →

Major October 28, 2025 IBM Verify: We are investigating alerts in Australia region 2d 21h Authentication with Cloud Directory, Authentication with SAML Identity Provider, Authentication with IBMid for admin users, User ID and password authentication from API and 6 more

Started Oct 28, 2025, 12:45 PM UTC· resolved Oct 31, 2025, 09:56 AM UTC

  1. investigating Oct 28, 2025, 12:45 PM UTC

    We are currently investigating alerts

  2. identified Oct 28, 2025, 01:48 PM UTC

    We have identified an issue affecting admin console access. We are working on a resolution.

  3. resolved Oct 31, 2025, 09:56 AM UTC

    this issue was resolved on 28th October

Read the full incident report →

Notice October 22, 2025 IBM Verify. Investigating issues in US Region Cluster E 1d 12h 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) and 6 more

Started Oct 22, 2025, 08:38 PM UTC· resolved Oct 24, 2025, 09:28 AM UTC

  1. investigating Oct 22, 2025, 08:38 PM UTC

    We are currently investigating issues on IBM Verify Cluster E. Further updates to follow.

  2. resolved Oct 24, 2025, 09:28 AM UTC

    This incident has been resolved

Read the full incident report →

Notice October 16, 2025 Outliers engine performance issue – Outliers, Outliers

Started Oct 16, 2025, 03:34 PM UTC· resolved Oct 16, 2025, 03:34 PM UTC

  1. resolved Oct 16, 2025, 03:34 PM UTC

    The issue affecting the Outliers Engine has been resolved. We will continue to monitor the system to ensure stability. Recommendation: If you are using GDP, we recommend applying the adhoc patch based on your current version: - v12 - 12.0p1139 - v11 - 11.0p1327

Read the full incident report →

Critical October 11, 2025 The user interface is currently inaccessible due to scheduled maintenance. Our team is actively working to restore full functionality as soon as possible. We’ll provide updates as soon as more information becomes available. 1h 11m User Interface Login

Started Oct 11, 2025, 01:45 PM UTC· resolved Oct 11, 2025, 02:57 PM UTC

  1. investigating Oct 11, 2025, 01:45 PM UTC

    We are currently investigating this issue.

  2. identified Oct 11, 2025, 01:46 PM UTC

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

  3. identified Oct 11, 2025, 01:57 PM UTC

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

  4. monitoring Oct 11, 2025, 02:55 PM UTC

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

  5. resolved Oct 11, 2025, 02:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 7, 2025 IBM Verify: Rescheduled deployment of new SSL Certificates for verify.ibm.com. Monday 13 October at 08:00 UTC 6d 11h Authentication with Cloud Directory, Authentication with Cloud Directory (Cluster A), Authentication with Cloud Directory, Authentication with Cloud Directory and 80 more

Started Oct 07, 2025, 07:58 PM UTC· resolved Oct 14, 2025, 07:42 AM UTC

  1. monitoring Oct 07, 2025, 07:58 PM UTC

    Please see maintenance notice later on this page for renewal of certificate for verify.ibm.com. Now scheduled for Mon 13 October 08:00 UTC

  2. resolved Oct 14, 2025, 07:42 AM UTC

    This activity has been completed

Read the full incident report →

Major September 30, 2025 Risk analytics events lag 29d 23h Risk Events

Started Sep 30, 2025, 09:02 PM UTC· resolved Oct 30, 2025, 08:31 PM UTC

  1. identified Sep 30, 2025, 09:02 PM UTC

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

  2. identified Oct 28, 2025, 08:00 PM UTC

    We are aware of the Risk Analytics issue and investigation is ongoing.

  3. resolved Oct 30, 2025, 08:31 PM UTC

    The remediation has been applied, and the risk analytics service is fully operational.

Read the full incident report →