Historial de interrupciones de Sysdig Us East 1

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

   Hemos identificado un problema que causa fallos intermitentes de la exploración de KSPM en todas las regiones. Algunos escaneos se completan con éxito, mientras que otros no. Como resultado, los datos de postura y cumplimiento de Kubernetes pueden ser incompletos o no disponibles para algunos clientes. Hemos identificado la causa y estamos implementando activamente una solución. Proporcionaremos otra actualización a medida que continúe el progreso.

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:28 UTCresolved

   This incident has been resolved.

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

1. 5 de julio de 2026 a las 20:45 UTCinvestigating

   We are investigating an issue impacting the processing of Posture and Compliance data. Customers may experience delays in new Posture and Compliance results appearing in dashboards and reports. Previously collected data remains available. We are actively investigating the issue and working to restore normal processing. We will provide another update as more information becomes available.

2. 5 de julio de 2026 a las 23:54 UTCmonitoring

   We have deployed a fix and processing of Posture and Compliance data has resumed successfully. New Posture and Compliance results are now being processed and should appear normally in dashboards and reports. We are continuing to monitor the service to ensure processing remains stable and will provide another update as appropriate.

3. 6 de julio de 2026 a las 9:33 UTCresolved

   This incident has been resolved.

1. 26 de marzo de 2026 a las 12:49 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. 18 de marzo de 2026 a las 20:14 UTCinvestigating

   We are currently investigating an issue affecting the Risk feature, which is currently unavailable. Our team is working to resolve the issue and will provide updates as soon as more information becomes available.

2. 18 de marzo de 2026 a las 20:53 UTCresolved

   The issue affecting the Risk feature has been resolved. We are continuing to monitor to ensure stability.

1. 10 de marzo de 2026 a las 6:23 UTCinvestigating

   We are currently investigating the issue.

2. 10 de marzo de 2026 a las 6:42 UTCinvestigating

   Sysdig has become aware of an alerting issue which may cause customers to not receive triggered alerts since alert notifications are being dropped. We are actively investigating the issue and will post further updates.

3. 10 de marzo de 2026 a las 6:55 UTCmonitoring

   A fix has been implemented and alerting is functional again. We are actively monitoring the situation to ensure continued stability.

4. 10 de marzo de 2026 a las 7:29 UTCresolved

   This incident has been resolved.

1. 17 de febrero de 2026 a las 9:48 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:56 UTCmonitoring

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

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

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

7. 18 de febrero de 2026 a las 9:41 UTCidentified

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

8. 18 de febrero de 2026 a las 17:11 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.

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

10. 19 de febrero de 2026 a las 0:20 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.

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

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

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

14. 20 de febrero de 2026 a las 10:34 UTCmonitoring

    We are continuing to monitor for any further issues.

15. 20 de febrero de 2026 a las 10:35 UTCresolved

    This incident has been resolved.

1. 6 de febrero de 2026 a las 8:08 UTCinvestigating

   We are currently investigating this issue.

2. 6 de febrero de 2026 a las 8:29 UTCmonitoring

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

3. 6 de febrero de 2026 a las 8:34 UTCresolved

   This incident has been resolved.

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

   We are currently investigating this issue.

2. 13 de enero de 2026 a las 17:12 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. 7 de enero de 2026 a las 9:54 UTCidentified

   VM Overview and Threats Overview pages are not showing data in dashboards. Our team has identified the issue and is actively working on a fix.

2. 7 de enero de 2026 a las 10:17 UTCresolved

   This incident has been resolved.

1. 17 de diciembre de 2025 a las 14:36 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:40 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:17 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:46 UTCmonitoring

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

5. 10 de diciembre de 2025 a las 16:54 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.

1. 13 de noviembre de 2025 a las 0:19 UTCinvestigating

   We are experiencing problems with login to secure. We have identified the problem and are working on a fix.

2. 13 de noviembre de 2025 a las 0:26 UTCidentified

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

3. 13 de noviembre de 2025 a las 1:34 UTCmonitoring

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

4. 13 de noviembre de 2025 a las 2:24 UTCresolved

   This incident has been resolved.

1. 20 de octubre de 2025 a las 15:46 UTCresolved

   from 7:30am to 9:30am UTC because of a problem with our upstream cloud provider

1. 3 de octubre de 2025 a las 15:00 UTCinvestigating

   We have identified an issue causing delays in risk updates. Customers may experience degraded performance with automated risk-related operations. Our team is actively deploying a fix and we will provide updates as recovery progresses.

2. 3 de octubre de 2025 a las 15:05 UTCidentified

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

3. 3 de octubre de 2025 a las 16:27 UTCmonitoring

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

4. 3 de octubre de 2025 a las 16:29 UTCresolved

   This incident has been resolved.

1. 22 de septiembre de 2025 a las 15:31 UTCidentified

   We are currently experiencing degraded performance with alert calculations and dashboards because of delayed metrics ingestion. Our team has identified the issue and is actively working on a fix.

2. 22 de septiembre de 2025 a las 16:45 UTCresolved

   This incident has been resolved.

1. 29 de agosto de 2025 a las 1:11 UTCinvestigating

   We are currently investigating this issue.

2. 29 de agosto de 2025 a las 2:08 UTCresolved

   Detection notifications were sent once and will not reoccur.

1. 17 de julio de 2025 a las 4:08 UTCidentified

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

2. 17 de julio de 2025 a las 4:32 UTCmonitoring

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

3. 17 de julio de 2025 a las 4:50 UTCresolved

   This incident has been resolved.

1. 15 de julio de 2025 a las 19:39 UTCidentified

   Resource Type: Image drawer not available under “Inventory” in Sysdig Secure, we are currently working on a fix

2. 16 de julio de 2025 a las 0:44 UTCresolved

   This incident has been resolved.

1. 23 de junio de 2025 a las 8:55 UTCidentified

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

2. 23 de junio de 2025 a las 11:45 UTCresolved

   This incident has been resolved.

1. 13 de junio de 2025 a las 16:07 UTCinvestigating

   Sysdig has become aware of a data ingestion issue, which may cause some customers to experience gaps in populated graphs, network timeouts while communicating with the cloud platform, or alerts triggered incorrectly. The rest of Sysdig's features are functioning. We are investigating the issue and will post updates on this page.

2. 13 de junio de 2025 a las 16:07 UTCidentified

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

3. 13 de junio de 2025 a las 16:08 UTCidentified

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

4. 13 de junio de 2025 a las 16:45 UTCmonitoring

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

5. 13 de junio de 2025 a las 17:23 UTCresolved

   This incident has been resolved.