Historial de interrupciones de Ibm Security

1. August 25, 2026 at 12:48 PM UTCmonitoring

   IBM Verify (US Region Cluster C) experimentó una breve interrupción del servicio a las 12 horas UTC durante aproximadamente 5 minutos. El servicio se restablece y IBM está monitoreando

2. August 25, 2026 at 6:45 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 20, 2026 at 3:39 PM UTCinvestigating

   Los clientes de IBM Verify (Europa Región) pueden estar experimentando problemas con el servicio. Actualmente estamos investigando. Hemos tomado medidas para pasar al entorno de procesamiento alternativo.

2. August 20, 2026 at 4:11 PM UTCinvestigating

   El problema es volver a ocurrir. Los usuarios pueden experimentar algunos fallos de autenticación intermitente. Seguimos investigando la cuestión.

3. August 20, 2026 at 4:44 PM UTCinvestigating

   Continuamos investigando. Los servicios están generalmente disponibles, pero pueden haber fallos intermitentes.

4. August 20, 2026 at 5:26 PM UTCidentified

   Hemos identificado el área que ha estado causando el problema. Continuamos investigando. El servicio sigue funcionando en este momento.

5. August 20, 2026 at 6:26 PM UTCidentified

   El servicio sigue siendo estable. Todavía estamos investigando la causa del problema.

6. August 20, 2026 at 10:22 PM UTCidentified

   Hemos experimentado otras cuestiones intermitentes y seguimos investigando la causa.

7. August 21, 2026 at 8:08 AM UTCmonitoring

   El servicio en Europa sigue siendo estable. Seguimos monitoreando.

8. August 25, 2026 at 8:02 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 11, 2026 at 9:29 AM UTCinvestigating

   IBM Security Verify (US Region Cluster C) customers may be experiencing issues with the service. We are currently investigating. This is affecting IBMid login from other clusters

2. August 11, 2026 at 9:41 AM UTCmonitoring

   Issue has been identified. Service is restored. IBM is monitoring.

3. August 11, 2026 at 10:30 AM UTCresolved

   The incident is fully resolved.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 5, 2026 at 1:10 PM UTCinvestigating

   IBM Verify users in US that rely on SMS for OTP may be experiencing delays in SMS delivery. We are currently investigating.

2. August 5, 2026 at 1:56 PM UTCmonitoring

   Services have been generally restored and SMS based MFA messages are now being received.

3. August 5, 2026 at 11:13 PM UTCresolved

   Service has remained stable following the corrective actions implemented by our engineering teams. No further issues related to this incident have been observed.

1. August 4, 2026 at 4:42 AM UTCinvestigating

   We are currently investigating alerts for Japan.

2. August 4, 2026 at 8:26 AM UTCmonitoring

   The issue was identified and recovery actions were completed at 05:35 UTC. Services have recovered and are operating normally. We are continuing to monitor the environment closely.

3. August 4, 2026 at 3:31 PM UTCresolved

   This incident has been resolved.

1. August 1, 2026 at 1:58 PM UTCidentified

   Los eventos de riesgo GDSC están presentando un ligero retraso en el proceso, nuestro equipo es consciente de esta situación y está monitoreando y analizando de cerca.

2. August 1, 2026 at 2:00 PM UTCidentified

   Seguimos trabajando para solucionar este problema.

3. August 2, 2026 at 3:37 PM UTCmonitoring

   Esto se está vigilando continuamente. La causa ha sido identificada y estamos monitoreando la actividad de comportamiento de los eventos de riesgo ahora.

4. August 6, 2026 at 10:12 PM UTCresolved

   This incident has been resolved. After careful review by our team, we can determine the issue is contained.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 5:02 PM UTCinvestigating

   Estamos investigando el rendimiento degradado que afecta a múltiples inquilinos IBM Security Verify. Los clientes pueden experimentar mayor latencia, intervalos intermitentes, fallos de autenticación y errores elevados HTTP 503. Los equipos de ingeniería están trabajando activamente para mitigar el problema y restaurar el servicio normal. Se proporcionarán más actualizaciones cuando estén disponibles.

2. July 27, 2026 at 6:41 PM UTCinvestigating

   Hemos implementado acciones de mitigación y estamos observando un mejor desempeño de servicios en los inquilinos afectados de IBM Security Verify. Nuestros equipos de ingeniería siguen vigilando estrechamente el medio ambiente para garantizar la estabilidad de los servicios mientras la investigación sigue en curso. Proporcionaremos actualizaciones adicionales a medida que se disponga de más información.

3. July 27, 2026 at 7:41 PM UTCinvestigating

   Seguimos investigando esta cuestión.

4. July 27, 2026 at 10:55 PM UTCidentified

   Los equipos de ingeniería han identificado los factores que contribuyen a la degradación de los servicios y están aplicando activamente un arreglo permanente. Se han aplicado medidas de mitigación para restablecer la estabilidad de las plataformas y reducir el impacto en los inquilinos afectados. Se siguen llevando a cabo actividades de vigilancia y validación. Se proporcionarán más actualizaciones cuando estén disponibles.

5. July 28, 2026 at 8:24 PM UTCmonitoring

   Se han aplicado medidas correctivas y el desempeño de los servicios sigue siendo estable. Se han completado con éxito las actividades de validación y las cargas de trabajo afectadas han seguido funcionando normalmente bajo los niveles de tráfico de producción. Los equipos de ingeniería mantienen una vigilancia mejorada mientras continúan las actividades finales de seguimiento y el examen posterior al incidente. Proporcionaremos actualizaciones adicionales a medida que continúe el progreso.

6. July 29, 2026 at 7:49 PM UTCresolved

   El servicio ha permanecido estable tras las acciones correctivas implementadas por nuestros equipos de ingeniería. La validación del cliente se ha completado con éxito y no se han observado otras cuestiones relacionadas con este incidente. Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 22, 2026 at 2:37 PM UTCinvestigating

   IBM Security Verify (Japón Region) clientes pueden estar experimentando problemas con el servicio. Actualmente estamos investigando alertas para Japón.

2. July 22, 2026 at 2:59 PM UTCidentified

   Se ha identificado la cuestión. El equipo de verificación está trabajando para remediar.

3. July 22, 2026 at 3:52 PM UTCidentified

   Continuamos trabajando en la rehabilitación.

4. July 22, 2026 at 4:43 PM UTCmonitoring

   Tras las medidas de recuperación adoptadas, se han recuperado los servicios. Seguimos monitoreando.

5. July 22, 2026 at 4:52 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

6. July 22, 2026 at 6:15 PM UTCresolved

   El número en ISV Japón se resuelve. Toda vigilancia ha sido clara.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 1:49 PM UTCinvestigating

   Seguimos investigando una cuestión que afecta al servicio de ingestión de datos. Nuestro equipo de ingeniería está trabajando activamente para restaurar operaciones normales. Durante este tiempo, algunos datos pueden ser retrasados o incompletos. Proporcionaremos más actualizaciones a medida que se disponga de más información.

2. July 22, 2026 at 4:42 PM UTCinvestigating

   Hemos identificado un retraso en el proceso de ingestión de datos Datamart hoy. Nuestro equipo está examinando activamente la cuestión y estamos monitoreando continuamente el servicio. Se proporcionarán más actualizaciones a medida que se disponga de más información.

3. July 22, 2026 at 10:34 PM UTCmonitoring

   Se ha aclarado el atraso de la ingestión y se ha normalizado el procesamiento. El servicio sigue siendo estable y seguiremos monitoreando como precaución.

4. August 6, 2026 at 1:03 AM UTCmonitoring

   Hemos detectado una ligera degradación en la ingestión de eventos. El equipo está examinando activamente y ha identificado la causa de ello.

5. August 12, 2026 at 12:15 PM UTCinvestigating

   Hemos detectado una ligera degradación en la ingestión de eventos. El equipo está monitoreando e investigando activamente.

6. August 18, 2026 at 10:32 PM UTCinvestigating

   Seguimos investigando esta cuestión.

7. August 20, 2026 at 7:54 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 1, 2026 at 9:09 PM UTCidentified

   Actualmente estamos investigando los problemas internos que afectan al ChatBot de IA. Durante este tiempo, es posible que los usuarios experimenten retrasos en las respuestas.

2. July 29, 2026 at 8:55 PM UTCmonitoring

   Se ha identificado una solución, actualmente se está examinando, probando y supervisando. Estaremos actualizando una vez que se haya logrado una solución completa.

3. August 20, 2026 at 7:49 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

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

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

Traducido automáticamente desde la actualización oficial del incidente.

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

2. June 24, 2026 at 8:26 PM UTCresolved

   Service has been operational for some time. Closing this incident.

Traducido automáticamente desde la actualización oficial del incidente.

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

2. June 15, 2026 at 6:55 PM UTCidentified

   We have identified the issue and are taking steps to address

3. June 17, 2026 at 4:03 PM UTCresolved

   This issue is resolved. Closing

Traducido automáticamente desde la actualización oficial del incidente.

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

Traducido automáticamente desde la actualización oficial del incidente.

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

Traducido automáticamente desde la actualización oficial del incidente.

1. June 8, 2026 at 10:41 PM UTCidentified

   Actualmente tenemos problemas que afectan al aprovisionamiento de los arrendatarios de demostración. Los usuarios pueden sufrir retrasos o fallos durante el proceso de configuración. Nuestro equipo está investigando y trabajando activamente para restablecer la funcionalidad normal lo antes posible.

2. July 29, 2026 at 8:27 PM UTCresolved

   Se ha implementado una solución para el retraso de provisión de Demo Tenant y / o fracaso.

Traducido automáticamente desde la actualización oficial del incidente.

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

Traducido automáticamente desde la actualización oficial del incidente.

1. May 5, 2026 at 6:36 AM UTCinvestigating

   We are currently investigating the issue.

2. May 5, 2026 at 7:08 AM UTCidentified

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

3. May 5, 2026 at 7:32 AM UTCmonitoring

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

4. May 6, 2026 at 11:48 AM UTCresolved

   This incident has been resolved.

Traducido automáticamente desde la actualización oficial del incidente.

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

2. April 30, 2026 at 1:41 PM UTCresolved

   Monitoring has been successful. Issue is remediated. x

Traducido automáticamente desde la actualización oficial del incidente.

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

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

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

4. April 29, 2026 at 12:45 PM UTCidentified

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

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

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

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

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

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

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

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

Traducido automáticamente desde la actualización oficial del incidente.