Historial de interrupciones de Sysdig Us West 2

1. 14 de agosto de 2026 a las 19:12 UTCidentified

   We have identified an issue causing intermittent KSPM scan failures across all regions. Some scans are completing successfully, while others are not. As a result, Kubernetes posture and compliance data may be incomplete or unavailable for some customers. We have identified the cause and are actively implementing a fix. We will provide another update as progress continues.

2. 14 de agosto de 2026 a las 22:04 UTCmonitoring

   We have rolled out remediation changes across the affected environments, and KSPM scan processing has resumed. Customers may continue to experience delays while the accumulated scan data is processed. We will continue monitoring the service throughout the weekend and provide further updates if the situation changes.

3. 17 de agosto de 2026 a las 16:17 UTCmonitoring

   KSPM data collection has resumed and scan processing is progressing. Kubernetes posture and compliance data is being repopulated, and customers may still see incomplete or delayed results while the remaining scans complete. We are continuing to monitor recovery and will confirm once posture data is fully up to date

4. 17 de agosto de 2026 a las 19:48 UTCresolved

   A permanent fix has been successfully deployed across all environments, and the backlog of pending scans has been fully processed. KSPM scan functionality is operating normally, and posture and compliance data is fully updated across all regions. We have confirmed that service metrics and data processing have returned to baseline performance. This incident is now resolved.

1. 4 de agosto de 2026 a las 9:17 UTCinvestigating

   Los clientes pueden observar retrasos y/o faltas en eventos de política de detección de estado. Actualmente estamos investigando la cuestión.

2. 4 de agosto de 2026 a las 9:28 UTCmonitoring

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

3. 4 de agosto de 2026 a las 9:48 UTCresolved

   This incident has been resolved.

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

1. 3 de agosto de 2026 a las 9:36 UTCinvestigating

   Actualmente estamos investigando la cuestión

2. 3 de agosto de 2026 a las 10:30 UTCresolved

   Este incidente ha sido resuelto.

3. 3 de agosto de 2026 a las 15:59 UTCpostmortem

   Durante este incidente, los servicios de CSPM no pudieron procesar escaneos debido a una falla de inicio de servicio debido a problemas de conectividad a un proveedor externo. Como resultado, los trabajos de escaneo se pusieron en contacto y no fueron procesados durante el periodo de salida. Después de que los servicios afectados hayan sido restaurados, se espera que el atraso de los escaneos pendientes se drene automáticamente, con la funcionalidad de escaneo normal que se reanude progresivamente.

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

1. 3 de julio de 2026 a las 6:01 UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. 3 de julio de 2026 a las 6:01 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 3 de julio de 2026 a las 6:03 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

4. 3 de julio de 2026 a las 10:24 UTCidentified

   Tenemos una solución en el lugar que estamos trabajando en procesar el atraso de los datos y verificar que la solución es correcta.

5. 3 de julio de 2026 a las 10:56 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

6. 3 de julio de 2026 a las 11:16 UTCresolved

   Este incidente ha sido resuelto.

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

1. 1 de julio de 2026 a las 23:29 UTCinvestigating

   Estamos investigando un problema que impacta la función de Reportaje de Gestión de Vulnerabilidad. Los clientes pueden experimentar retrasos y datos de vulnerabilidad desaparecidos en VM Reporting debido a un problema que afecta el procesamiento de los resultados de la exploración. Nuestra investigación indica que la cuestión está relacionada con la reducción del rendimiento de procesamiento en la infraestructura de búsqueda subyacente. Otras características de Sysdig no se impactan. Estamos investigando activamente el alcance del impacto y proporcionaremos otra actualización tan pronto como se disponga de más información.

2. 2 de julio de 2026 a las 1:29 UTCidentified

   Hemos identificado la causa de la cuestión que afecta a la función de presentación de informes de gestión de vulnerabilidades y estamos viendo mejoras. Procesamiento se ha reanudado y los mensajes de resultados de la exploración ya no se están perdiendo. Sin embargo, los clientes pueden seguir experimentando retrasos en los datos de vulnerabilidad que aparecen en VM Reporting mientras procesamos el atraso de los resultados de la exploración apagada. Trabajamos activamente para restaurar el procesamiento normal y proporcionaremos otra actualización a medida que continúe el progreso.

3. 2 de julio de 2026 a las 20:16 UTCmonitoring

   Se han aplicado con éxito medidas de mitigación y se ha resuelto la cuestión que causa retrasos en la presentación de informes sobre gestión de vulnerabilidades. Estamos monitoreando la recuperación ya que se procesa el atraso restante de los resultados de la exploración. Los clientes pueden seguir experimentando actualizaciones retrasadas hasta que el atraso se haya aclarado completamente. No se produce nueva pérdida de datos.

4. 3 de julio de 2026 a las 5:38 UTCresolved

   Este incidente ha sido resuelto.

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

1. 23 de junio de 2026 a las 23:17 UTCidentified

   We are currently investigating an issue in the US2 region where users are unable to open the Vulnerability 360 drawer from the Vulnerability Finding page for KubeWorkload resources. Our engineering team has successfully identified the root cause and is actively working on a fix to deploy as soon as possible. We apologize for the inconvenience and will provide further updates here.

2. 24 de junio de 2026 a las 0:28 UTCidentified

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

3. 24 de junio de 2026 a las 1:46 UTCmonitoring

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

4. 24 de junio de 2026 a las 4:26 UTCmonitoring

   The fix is working as expected and we're actively monitoring until full recovery.

5. 24 de junio de 2026 a las 13:58 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary.

6. 24 de junio de 2026 a las 17:41 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary

7. 24 de junio de 2026 a las 17:42 UTCresolved

   This incident has been resolved.

1. 23 de junio de 2026 a las 14:50 UTCinvestigating

   We are currently experiencing a delay in processing mass data exports. No data has been lost, and all exports will be sent as soon as the issue is resolved.

2. 23 de junio de 2026 a las 16:07 UTCinvestigating

   We are continuing to investigate the issue.

3. 23 de junio de 2026 a las 16:16 UTCidentified

   We are continuing to investigate the issue.

4. 24 de junio de 2026 a las 0:04 UTCidentified

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

5. 24 de junio de 2026 a las 1:20 UTCmonitoring

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

6. 24 de junio de 2026 a las 4:38 UTCmonitoring

   The fix is working as expected and we're actively monitoring until full recovery.

7. 24 de junio de 2026 a las 13:59 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary.

8. 25 de junio de 2026 a las 12:02 UTCmonitoring

   We're actively monitoring the recovery and will provide further updates as necessary

9. 25 de junio de 2026 a las 16:14 UTCresolved

   This incident has been resolved.

1. 16 de junio de 2026 a las 12:13 UTCinvestigating

   We’ve detected an issue in our processing systems and are actively investigating. We suspect this may be causing delays in Vulnerability Management (VM) data updates, meaning the latest scan findings could take longer than usual to appear. Scans are continuing to run. We’re working to confirm the extent of the impact and will post an update as soon as we know more.

2. 16 de junio de 2026 a las 13:53 UTCidentified

   We have identified the root cause and issued a fix, we are already recovering and we are processing the backlog of data pending to be processed. We will post updates here once we have more information about the recovery path

3. 16 de junio de 2026 a las 15:24 UTCmonitoring

   The data process it's recovering all new Scans should work fine, we might still some gaps until all the processes catch up with the queue. We will update here again when all the processes are good.

4. 16 de junio de 2026 a las 18:22 UTCresolved

   All scan processing services have fully recovered. Scan request volumes have returned to normal levels and all queue backlogs have been cleared. New scans are processing as expected with no further gaps anticipated. We will continue to monitor service health. No action is required on your end.

1. 16 de junio de 2026 a las 2:33 UTCidentified

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

2. 16 de junio de 2026 a las 2:42 UTCmonitoring

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

3. 16 de junio de 2026 a las 6:00 UTCmonitoring

   We are continuing to monitor recovery of the system.

4. 16 de junio de 2026 a las 6:22 UTCresolved

   This incident has been resolved.

1. 6 de mayo de 2026 a las 23:08 UTCinvestigating

   We are currently investigating an issue affecting vulnerability scan processing in the US2 (us-east-2) region. Customers may experience delays in scan results appearing in the UI. New scan requests are taking longer to be processed than expected. Our team is actively working to resolve the issue. Further updates will be provided as investigation progresses.

2. 6 de mayo de 2026 a las 23:22 UTCidentified

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

3. 6 de mayo de 2026 a las 23:46 UTCmonitoring

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

4. 7 de mayo de 2026 a las 0:10 UTCresolved

   This incident has been resolved.

1. 27 de abril de 2026 a las 21:11 UTCinvestigating

   We are currently investigating an issue that may affect report generation. In some cases, reports may be created without displaying data.

2. 27 de abril de 2026 a las 22:22 UTCidentified

   We are aware of a potential issue affecting report generation, where reports may occasionally be generated without displaying data. Our engineering team is investigating and working toward a resolution. Updates will be provided as appropriate.

3. 28 de abril de 2026 a las 0:28 UTCmonitoring

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

4. 28 de abril de 2026 a las 2:44 UTCmonitoring

   We are currently monitoring the system to ensure report generation is functioning as expected. Updates will be shared as needed.

5. 28 de abril de 2026 a las 4:12 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 28 de abril de 2026 a las 7:34 UTCresolved

   This incident has been resolved.

1. 9 de abril de 2026 a las 2:08 UTCresolved

   A processing delay in the data ingestion pipeline is currently impacting vulnerability page visibility for US2 customers, with a fix deployed and full recovery expected

1. 9 de abril de 2026 a las 2:04 UTCresolved

   A processing delay in the data ingestion pipeline is currently impacting vulnerability page visibility for US2 customers, with a fix deployed and full recovery expected

1. 3 de abril de 2026 a las 8:31 UTCinvestigating

   We are currently investigating this issue. We will provide updates as more information becomes available.

2. 3 de abril de 2026 a las 8:57 UTCinvestigating

   Agentless Scanning is experiencing delays, with scans stuck in a "Pending" state or not completing within the expected timeframe. We are actively investigating the issue and will provide more updates as necessary.

3. 3 de abril de 2026 a las 11:34 UTCinvestigating

   This issue is still under active investigation. Additional updates will be provided as new information becomes available.

4. 3 de abril de 2026 a las 15:44 UTCinvestigating

   We have applied changes to improve processing of affected cloud accounts, and recovery is in progress. Some scans and related cloud security features may be delayed while this completes. Our teams are closely monitoring the environment to ensure stability.

5. 4 de abril de 2026 a las 7:10 UTCmonitoring

   We have applied changes to improve processing of affected cloud accounts, and recovery is in progress. Some scans and related cloud security features may be delayed while this completes. Our teams are closely monitoring the environment to ensure stability.

6. 4 de abril de 2026 a las 16:19 UTCmonitoring

   Recovery is in progress. Some scans and related cloud security features may be delayed while this completes. Our teams are closely monitoring the environment to ensure stability.

7. 4 de abril de 2026 a las 20:05 UTCmonitoring

   Recovery is progressing, with host scan volumes increasing. We are monitoring closely as the system continues to stabilize.

8. 5 de abril de 2026 a las 0:04 UTCmonitoring

   Recovery continues, with host scan volumes steadily increasing. We are monitoring closely as the system stabilizes

9. 5 de abril de 2026 a las 4:59 UTCmonitoring

   Recovery continues, with host scan volumes steadily increasing. We are closely monitoring as the system stabilizes.

10. 5 de abril de 2026 a las 6:53 UTCresolved

    This incident has been resolved.

1. 26 de marzo de 2026 a las 12:50 UTCresolved

   Sysdig has become aware of an alerting issue in the cloud platform, which may cause some customers to experience alerts being triggered incorrectly or not on time, or gaps in populated graphs. The rest of Sysdig's features are functioning. The issue was solved at 12.18pm UTC

1. 17 de febrero de 2026 a las 9:47 UTCinvestigating

   We are currently investigating the issue

2. 17 de febrero de 2026 a las 11:58 UTCidentified

   The issues has been identified and the team is working on a fix

3. 17 de febrero de 2026 a las 17:35 UTCidentified

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

4. 17 de febrero de 2026 a las 21:57 UTCmonitoring

   We have deployed a fix to address the issue causing incorrect policy data in Compliance and Inventory. Systems are stable, and we are actively monitoring. Correct data is expected to progressively converge across affected areas within the next 24 hours as processing completes. We will provide further updates if needed

5. 18 de febrero de 2026 a las 7:03 UTCinvestigating

   The previously deployed fix did not work as expected. While data briefly corrected after new scans, subsequent sync cycles are causing policies and controls to be removed again. We are actively investigating the issue.

6. 18 de febrero de 2026 a las 9:42 UTCidentified

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

7. 18 de febrero de 2026 a las 17:12 UTCmonitoring

   The new fix has been deployed, and we are observing policy data being correctly recovered across affected environments. The incident status has been moved to Monitoring while we continue validating stability.

8. 18 de febrero de 2026 a las 21:55 UTCmonitoring

   The previously deployed fix continues to operate as expected, and we are observing policy and control data recovering normally. Systems remain stable, and we are actively monitoring to ensure consistency and sustained correctness of Compliance and Inventory data. We will provide further updates if necessary.

9. 19 de febrero de 2026 a las 0:21 UTCmonitoring

   The previously deployed corrective fix continues to perform as expected, and we are observing policy, control, and requirement data recovering normally. Systems remain stable, and we have not observed any signs of regression. Due to the normal scan lifecycle, Compliance and Inventory data will progressively converge as background processing completes. We are actively monitoring the situation and will provide further updates if necessary.

10. 19 de febrero de 2026 a las 8:58 UTCmonitoring

    Compliance and Inventory data is recovering as expected. We are actively monitoring the situation and will provide further updates if necessary.

11. 19 de febrero de 2026 a las 19:53 UTCmonitoring

    Compliance and Inventory data continue to recover for the vast majority of customers. Systems remain stable, and no regression has been detected. Some customers may still observe partial data or temporary inconsistencies while background processing completes and results converge. We are actively monitoring the situation and will provide further updates if necessary.

12. 20 de febrero de 2026 a las 1:05 UTCmonitoring

    Platform performance remains healthy, and Compliance and Inventory data continue to converge as expected. No regression has been detected. Some customers may still observe partial or delayed data while background processing completes. We will provide further updates if necessary.

13. 20 de febrero de 2026 a las 10:36 UTCmonitoring

    We are still monitoring as some customers may still observe partial or delayed data while background processing completes. Platform performance remains healthy, and Compliance and Inventory data continue to converge. We will provide further updates if necessary.

14. 20 de febrero de 2026 a las 15:55 UTCresolved

    This incident has been resolved.

1. 15 de enero de 2026 a las 9:07 UTCmonitoring

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

2. 15 de enero de 2026 a las 10:14 UTCresolved

   This incident has been resolved.

1. 13 de enero de 2026 a las 15:21 UTCinvestigating

   We are currently investigating this issue.

2. 13 de enero de 2026 a las 17:13 UTCidentified

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

3. 13 de enero de 2026 a las 18:40 UTCmonitoring

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

4. 13 de enero de 2026 a las 20:30 UTCresolved

   This incident has been resolved.

1. 17 de diciembre de 2025 a las 14:37 UTCresolved

   We suffered a momentary disservice in the functionality of visualizing Attack Path due to a data migration, we have addressed the issue and the functionality is back online

1. 1 de diciembre de 2025 a las 18:42 UTCinvestigating

   Cloud log ingestion coming from workloads in us-east-1 at AWS are not being ingested by Sysdig. Our specialists are currently working with AWS to resolve the issue.

2. 2 de diciembre de 2025 a las 18:39 UTCidentified

   Our engineering teams have successfully identified the root cause of the failure that is preventing logs from being ingested by Sysdig. Resolution Underway: We are currently working directly with AWS specialists on the resolution steps required to restore the functionality.

3. 3 de diciembre de 2025 a las 17:19 UTCidentified

   We have collaborated with AWS to resolve the issue that was preventing logs from being ingested via EventBridge. Log ingestion has now resumed, and we have started processing the backlog of events.

4. 4 de diciembre de 2025 a las 19:48 UTCmonitoring

   Log ingestion is functional. We are currently processing the accumulated event backlog.

5. 10 de diciembre de 2025 a las 16:56 UTCresolved

   Our monitoring confirms that log ingestion is functioning as expected and no further delays or drops are occurring. We are now closing the incident.