All Systems Operational

About This Site

The status of Sysdig running in our US-West-2 region.
Interested in the status of Sysdig running in our AP-South-1 region? Go to https://status-in1.sysdig.com
Interested in the status of Sysdig running in our AP-SouthEast-2 region? Go to https://status-au1.sysdig.com
Interested in the status of Sysdig running in our EU-Central-1 region? Go to https://status-eu1.sysdig.com
Interested in the status of Sysdig running in our US-East-1 region? Go to https://status.sysdigcloud.com
Interested in the status of Sysdig running in our US-West-1 region? Go to https://status-us4.sysdig.com
Interested in the status of Sysdig running in our EU-North-1 region? Go to https://status-eu2.sysdig.com

Sysdig Monitor Operational
90 days ago
100.0 % uptime
Today
Sysdig Secure Operational
90 days ago
98.86 % uptime
Today
Sysdig Data Ingestion Operational
90 days ago
99.94 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Jul 5, 2026

No incidents reported today.

Jul 4, 2026

No incidents reported.

Jul 3, 2026
Resolved - This incident has been resolved.
Jul 3, 11:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 3, 10:56 UTC
Update - We have a fix in place we are working on processing the backlog of data and verifying that the fix it's correct.
Jul 3, 10:24 UTC
Update - We are continuing to work on a fix for this issue.
Jul 3, 06:03 UTC
Identified - The issue has been identified and a fix is being implemented.
Jul 3, 04:30 UTC
Investigating - We are currently investigating this issue.
Jul 3, 02:30 UTC
Jul 2, 2026
Resolved - This incident has been resolved.
Jul 2, 18:00 UTC
Monitoring - Mitigation measures have been successfully implemented and the issue causing delays in Vulnerability Management Reporting has been resolved. We are monitoring the recovery as the remaining backlog of scan results is processed. Customers may continue to experience delayed updates until the backlog has fully cleared. No new data loss is occurring.
Jul 2, 12:35 UTC
Identified - We have identified the cause of the issue impacting the Vulnerability Management Reporting feature and are seeing improvements.
Processing has resumed and scan result messages are no longer being lost. However, customers may continue to experience delays in vulnerability data appearing in VM Reporting while we process the backlog of queued scan results.
We are actively working to restore normal processing and will provide another update as progress continues.

Jul 2, 06:55 UTC
Investigating - We are investigating an issue impacting the Vulnerability Management Reporting feature.
Customers may experience delays and missing vulnerability data in VM Reporting due to an issue affecting the processing of scan results.
Our investigation indicates the issue is related to reduced processing throughput in the underlying search infrastructure. Other Sysdig features are not impacted.
We are actively investigating the scope of the impact and will provide another update as soon as more information becomes available.

Jul 1, 23:29 UTC
Jul 1, 2026
Jun 30, 2026

No incidents reported.

Jun 29, 2026

No incidents reported.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.

Jun 25, 2026
Resolved - This incident has been resolved.
Jun 25, 16:14 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary
Jun 25, 12:02 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary
Jun 25, 07:52 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary
Jun 25, 01:23 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary
Jun 25, 00:22 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary
Jun 24, 19:43 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary
Jun 24, 17:41 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary.
Jun 24, 13:59 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary.
Jun 24, 09:39 UTC
Update - The fix is working as expected and we're actively monitoring until full recovery.
Jun 24, 04:38 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 24, 01:20 UTC
Update - We are continuing to work on a fix for this issue.
Jun 24, 00:04 UTC
Update - We are continuing to work on a fix for this issue.
Jun 23, 23:04 UTC
Identified - We are continuing to work on a fix for this issue.
Jun 23, 22:02 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 23, 20:05 UTC
Update - We are continuing to work on a fix for this issue.
Jun 23, 18:56 UTC
Update - We are continuing to work on a fix for this issue.
Jun 23, 17:55 UTC
Update - We are continuing to work on a fix for this issue.
Jun 23, 16:51 UTC
Identified - We are continuing to investigate the issue.
Jun 23, 16:16 UTC
Update - We are continuing to investigate the issue.
Jun 23, 16:07 UTC
Investigating - 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.
Jun 23, 14:50 UTC
Jun 24, 2026
Resolved - This incident has been resolved.
Jun 24, 17:42 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary
Jun 24, 17:41 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary.
Jun 24, 13:58 UTC
Update - We're actively monitoring the recovery and will provide further updates as necessary.
Jun 24, 09:48 UTC
Update - The fix is working as expected and we're actively monitoring until full recovery.
Jun 24, 04:26 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 24, 01:46 UTC
Update - We are continuing to work on a fix for this issue.
Jun 24, 00:28 UTC
Identified - 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.

Jun 23, 23:17 UTC
Jun 23, 2026
Jun 22, 2026

No incidents reported.

Jun 21, 2026

No incidents reported.