IBM Security Outage History

IBM Security partial outage · 1 active incident View live status →

IBM Security had 42 outages in the last 2 years totaling 2455h 19m of downtime — averaging 1.7 incidents per month.

There were 42 IBM Security outages since May 8, 2025 totaling 2455h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://statuspage.ibmcloudsecurity.com

Major June 15, 2026

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

Detected by Pingoru
Jun 15, 2026, 06:33 PM UTC
Resolved
Jun 17, 2026, 04:03 PM UTC
Duration
1d 21h
Affected: 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)User ID and password authentication from API (Cluster A)Single sign on for SAML applications (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)Account Lifecycle (Cluster A)
Timeline · 3 updates
  1. investigating Jun 15, 2026, 06:33 PM UTC

    IBM Security Verify (US Region Cluster A) customers is experiencing intermittent issues with the service. We are currently investigating.

  2. identified Jun 15, 2026, 06:55 PM UTC

    We have identified the issue and are taking steps to address

  3. resolved Jun 17, 2026, 04:03 PM UTC

    This issue is resolved. Closing

Read the full incident report →

Notice June 15, 2026

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

Detected by Pingoru
Jun 15, 2026, 03:20 PM UTC
Resolved
Jun 15, 2026, 03:20 PM UTC
Duration
—
Affected: Authentication with Cloud Directory (Cluster C)Authentication with SAML Identity Provider (Cluster C)Authentication with IBMid for admin users (Cluster C)Authentication with External LDAP (Cluster C)User ID and password authentication from API (Cluster C)Single sign on for SAML applications (Cluster C)Single sign on for OIDC applications (Cluster C)Application Onboarding (Cluster C)Cloud Directory Users and Groups management (Cluster C)User and Group management with API client (Cluster C)Account Lifecycle (Cluster C)
Timeline · 1 update
  1. resolved Jun 15, 2026, 03:20 PM UTC

    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.

Read the full incident report →

Minor June 11, 2026

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

Detected by Pingoru
Jun 11, 2026, 10:46 AM UTC
Resolved
Jun 11, 2026, 07:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 11, 2026, 10:46 AM UTC

    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.

Read the full incident report →

Critical May 5, 2026

IBM Verify - authentication issues in Canada cluster

Detected by Pingoru
May 05, 2026, 06:36 AM UTC
Resolved
May 06, 2026, 11:48 AM UTC
Duration
1d 5h
Affected: Authentication with Cloud DirectoryUser ID and password authentication from APISingle sign on for SAML applicationsSingle sign on for OIDC applicationsApplication Onboarding
Timeline · 4 updates
  1. investigating May 05, 2026, 06:36 AM UTC

    We are currently investigating the issue.

  2. identified May 05, 2026, 07:08 AM UTC

    An issue has been identified and we are working on remediation steps.

  3. monitoring May 05, 2026, 07:32 AM UTC

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

  4. resolved May 06, 2026, 11:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 30, 2026

IBM Verify - authentication issues in Canada region

Detected by Pingoru
Apr 30, 2026, 12:38 PM UTC
Resolved
Apr 30, 2026, 01:41 PM UTC
Duration
1h 3m
Affected: 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 )User ID and password authentication from API ( Cluster B )Single sign on for SAML applications ( Cluster B )Single sign on for OIDC applications ( Cluster B )Application Onboarding ( Cluster B )Account Lifecycle ( Cluster B )
Timeline · 2 updates
  1. monitoring Apr 30, 2026, 12:38 PM UTC

    IBM Verify Canada Cluster B experienced an issue affecting authentications. Issue has been resolved at this time and we are currently monitoring.

  2. resolved Apr 30, 2026, 01:41 PM UTC

    Monitoring has been successful. Issue is remediated. x

Read the full incident report →

Major April 29, 2026

Outliers/Risk Events service outage

Detected by Pingoru
Apr 29, 2026, 07:55 PM UTC
Resolved
Apr 30, 2026, 04:35 PM UTC
Duration
20h 40m
Affected: OutliersRisk Events
Timeline · 2 updates
  1. investigating Apr 29, 2026, 07:55 PM UTC

    The Risk Events service is currently experiencing issues, which may impact risk generation. The development team is actively investigating and will provide updates as more information becomes available.

  2. investigating Apr 29, 2026, 10:48 PM UTC

    The Outliers and Risk Events services are currently experiencing issues, which may impact outliers and/or risk generation. The development team is actively investigating and will provide updates as more information becomes available.

Read the full incident report →

Notice April 23, 2026

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

Detected by Pingoru
Apr 23, 2026, 11:00 PM UTC
Resolved
Apr 24, 2026, 10:02 PM UTC
Duration
23h 2m
Affected: 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)User ID and password authentication from API (Cluster A)Single sign on for SAML applications (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)Account Lifecycle (Cluster A)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)User ID and password authentication from API (Cluster B)Single sign on for SAML applications (Cluster B)Single sign on for OIDC applications (Cluster B)Application Onboarding (Cluster B)Cloud Directory Users and Groups management (Cluster B)User and Group management with API client (Cluster B)Account Lifecycle (Cluster B)Authentication with Cloud Directory (Cluster C)Authentication with SAML Identity Provider (Cluster C)Authentication with IBMid for admin users (Cluster C)Authentication with External LDAP (Cluster C)User ID and password authentication from API (Cluster C)Single sign on for SAML applications (Cluster C)Single sign on for OIDC applications (Cluster C)Application Onboarding (Cluster C)Cloud Directory Users and Groups management (Cluster C)User and Group management with API client (Cluster C)Account Lifecycle (Cluster C)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)Single sign on for SAML applications (Cluster E)Single sign on for OIDC applications (Cluster E)Application Onboarding (Cluster E)Cloud Directory Users and Groups management (Cluster E)Account Lifecycle (Cluster E)User and Group management with API client (Cluster E)
Timeline · 6 updates
  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

Detected by Pingoru
Apr 08, 2026, 02:54 PM UTC
Resolved
Apr 16, 2026, 07:41 AM UTC
Duration
7d 16h
Affected: 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)User ID and password authentication from API (Cluster B)Single sign on for SAML applications (Cluster B)Single sign on for OIDC applications (Cluster B)Application Onboarding (Cluster B)Cloud Directory Users and Groups management (Cluster B)User and Group management with API client (Cluster B)Account Lifecycle (Cluster B)
Timeline · 2 updates
  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.

Detected by Pingoru
Apr 01, 2026, 07:37 PM UTC
Resolved
May 04, 2026, 09:16 PM UTC
Duration
33d 1h
Affected: AI ChatBot (Chat with watsonx)AI ChatBot (Chat with watsonx)
Timeline · 4 updates
  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

Detected by Pingoru
Mar 19, 2026, 09:38 AM UTC
Resolved
Mar 23, 2026, 12:13 PM UTC
Duration
4d 2h
Affected: Authentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersUser ID and password authentication from APISingle sign on for SAML applicationsApplication OnboardingCloud Directory Users and Groups managementUser and Group management with API clientSingle sign on for OIDC applicationsAccount Lifecycle
Timeline · 4 updates
  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

Detected by Pingoru
Mar 04, 2026, 04:43 PM UTC
Resolved
Mar 05, 2026, 12:15 AM UTC
Duration
7h 31m
Affected: Data Management – Ingestion (Datamart)Reports / Dashboard
Timeline · 4 updates
  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

Detected by Pingoru
Feb 23, 2026, 04:51 PM UTC
Resolved
Feb 24, 2026, 01:45 AM UTC
Duration
8h 54m
Affected: User Interface LoginUser Interface Login
Timeline · 3 updates
  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

Detected by Pingoru
Feb 13, 2026, 01:54 AM UTC
Resolved
Feb 20, 2026, 03:48 PM UTC
Duration
7d 13h
Affected: Account Management
Timeline · 2 updates
  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

Detected by Pingoru
Feb 10, 2026, 11:23 PM UTC
Resolved
Mar 06, 2026, 01:23 AM UTC
Duration
23d 1h
Affected: Data Management – Ingestion (Datamart)Outliers
Timeline · 8 updates
  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

Detected by Pingoru
Jan 20, 2026, 09:27 PM UTC
Resolved
Jan 21, 2026, 04:06 PM UTC
Duration
18h 39m
Affected: Risk EventsRisk Events
Timeline · 3 updates
  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 →

Notice January 14, 2026

US- RiskEvent service is partially down.

Detected by Pingoru
Jan 14, 2026, 05:56 AM UTC
Resolved
Jan 14, 2026, 10:14 AM UTC
Duration
4h 17m
Affected: Risk Events
Timeline · 3 updates
  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

Detected by Pingoru
Dec 19, 2025, 06:30 PM UTC
Resolved
Dec 19, 2025, 07:51 PM UTC
Duration
1h 21m
Affected: Account ManagementAI ChatBot (Chat with watsonx)API Key Authentication from APIAudit Process / WorkflowCloud / SaaS 3rd PartiesCloud / SaaS ConnectionsCloud / SaaS Discover and ClassificationCloud / SaaS StoresCloud / SaaS VulnerabilitiesData Management – Ingestion (Datamart)Data Management – Retention / ArchiveDatabase Asset ManagementIntegration EcosystemOutliersReports / DashboardRisk EventsUser Interface Login
Timeline · 2 updates
  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

Detected by Pingoru
Nov 18, 2025, 03:21 PM UTC
Resolved
Nov 18, 2025, 08:20 PM UTC
Duration
4h 59m
Affected: OutliersOutliers
Timeline · 4 updates
  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

Detected by Pingoru
Nov 16, 2025, 03:29 PM UTC
Resolved
Nov 17, 2025, 09:42 AM UTC
Duration
18h 13m
Affected: Authentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersUser ID and password authentication from APISingle sign on for SAML applicationsApplication OnboardingCloud Directory Users and Groups managementUser and Group management with API clientSingle sign on for OIDC applicationsAccount Lifecycle
Timeline · 6 updates
  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

Detected by Pingoru
Nov 11, 2025, 05:55 PM UTC
Resolved
Nov 11, 2025, 08:23 PM UTC
Duration
2h 28m
Affected: Authentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersUser ID and password authentication from APISingle sign on for SAML applicationsApplication OnboardingCloud Directory Users and Groups managementUser and Group management with API clientSingle sign on for OIDC applicationsAccount Lifecycle
Timeline · 4 updates
  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

Detected by Pingoru
Oct 28, 2025, 12:45 PM UTC
Resolved
Oct 31, 2025, 09:56 AM UTC
Duration
2d 21h
Affected: Authentication with Cloud DirectoryAuthentication with SAML Identity ProviderAuthentication with IBMid for admin usersUser ID and password authentication from APISingle sign on for SAML applicationsApplication OnboardingCloud Directory Users and Groups managementUser and Group management with API clientSingle sign on for OIDC applicationsAccount Lifecycle
Timeline · 3 updates
  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

Detected by Pingoru
Oct 22, 2025, 08:38 PM UTC
Resolved
Oct 24, 2025, 09:28 AM UTC
Duration
1d 12h
Affected: 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)Single sign on for SAML applications (Cluster E)Single sign on for OIDC applications (Cluster E)Application Onboarding (Cluster E)Cloud Directory Users and Groups management (Cluster E)Account Lifecycle (Cluster E)User and Group management with API client (Cluster E)
Timeline · 2 updates
  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 →