Sysdig US-West-2 Outage History

Sysdig US-West-2 is up right now

Sysdig US-West-2 had 27 outages in the last 2 years totaling 702h 57m of downtime — averaging 1.1 incidents per month.

There were 27 Sysdig US-West-2 outages since October 7, 2025 totaling 702h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status-us2.sysdig.com

Minor October 6, 2026

Sysdig Cloud Platform Alerting Degradation

Detected by Pingoru
Oct 06, 2026, 12:47 PM UTC
Resolved
Oct 06, 2026, 01:10 PM UTC
Duration
23m
Affected: Sysdig Monitor
Timeline · 3 updates
  1. investigating Oct 06, 2026, 12:47 PM UTC

    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. We are investigating the issue and will post updates on this page.

  2. identified Oct 06, 2026, 01:03 PM UTC

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

  3. resolved Oct 06, 2026, 01:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 2, 2026

Cost Advisor degradation

Detected by Pingoru
Oct 02, 2026, 09:21 AM UTC
Resolved
Oct 02, 2026, 10:37 AM UTC
Duration
1h 15m
Affected: Sysdig Monitor
Timeline · 3 updates
  1. investigating Oct 02, 2026, 09:21 AM UTC

    Customers can observe Cost Advisor data to be missing for Azure clusters. We are currently investigating the issue.

  2. identified Oct 02, 2026, 09:32 AM UTC

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

  3. resolved Oct 02, 2026, 10:37 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 30, 2026

degradation in the processing of CSPM scans

Detected by Pingoru
Sep 30, 2026, 07:44 PM UTC
Resolved
Oct 01, 2026, 09:25 AM UTC
Duration
13h 41m
Affected: Sysdig Secure
Timeline · 3 updates
  1. investigating Sep 30, 2026, 07:44 PM UTC

    We are experiencing some degradation in the processing of CSPM scans, which may result in inconsistencies on the Inventory and Compliance Findings pages. We are actively working on a fix to restore CSPM data to normal and expect to provide an update in the coming hours.

  2. monitoring Oct 01, 2026, 01:00 AM UTC

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

  3. resolved Oct 01, 2026, 09:25 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 28, 2026

Vulnerability data ingestion delay impacting Vulnerability Overview, Findings and Reporting

Detected by Pingoru
Sep 28, 2026, 10:17 AM UTC
Resolved
Sep 28, 2026, 01:44 PM UTC
Duration
3h 27m
Affected: Sysdig Secure
Timeline · 3 updates
  1. investigating Sep 28, 2026, 10:17 AM UTC

    We are currently investigating this issue.

  2. monitoring Sep 28, 2026, 01:01 PM UTC

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

  3. resolved Sep 28, 2026, 01:44 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 11, 2026

Customer may experience missing cloud resources in Inventory

Detected by Pingoru
Sep 11, 2026, 11:12 AM UTC
Resolved
Sep 11, 2026, 05:19 PM UTC
Duration
6h 6m
Affected: Sysdig Secure
Timeline · 6 updates
  1. investigating Sep 11, 2026, 11:12 AM UTC

    We are currently investigating this issue.

  2. investigating Sep 11, 2026, 12:05 PM UTC

    We are continuing to investigate this issue.

  3. identified Sep 11, 2026, 01:34 PM UTC

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

  4. identified Sep 11, 2026, 04:05 PM UTC

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

  5. monitoring Sep 11, 2026, 04:55 PM UTC

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

  6. resolved Sep 11, 2026, 05:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 14, 2026

KSPM Scan Degradation

Detected by Pingoru
Aug 14, 2026, 07:11 PM UTC
Resolved
Aug 17, 2026, 07:48 PM UTC
Duration
3d
Affected: Sysdig Secure
Timeline · 4 updates
  1. identified Aug 14, 2026, 07:12 PM UTC

    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. monitoring Aug 14, 2026, 10:04 PM UTC

    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. monitoring Aug 17, 2026, 04:17 PM UTC

    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. resolved Aug 17, 2026, 07:48 PM UTC

    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.

Read the full incident report →

Major August 4, 2026

Delay in detection of policy events

Detected by Pingoru
Aug 04, 2026, 09:17 AM UTC
Resolved
Aug 04, 2026, 09:48 AM UTC
Duration
31m
Affected: Sysdig Secure
Timeline · 3 updates
  1. investigating Aug 04, 2026, 09:17 AM UTC

    Customers may observe delays and/or misses in stateful detection policy events. We are currently investigating the issue.

  2. monitoring Aug 04, 2026, 09:28 AM UTC

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

  3. resolved Aug 04, 2026, 09:48 AM UTC

    This incident has been resolved.

Read the full incident report →

Major August 3, 2026

Customers may experience issues in CSPM scans

Detected by Pingoru
Aug 03, 2026, 09:36 AM UTC
Resolved
Aug 03, 2026, 10:30 AM UTC
Duration
54m
Affected: Sysdig Secure
Timeline · 3 updates
  1. investigating Aug 03, 2026, 09:36 AM UTC

    We are currently investigating the issue

  2. resolved Aug 03, 2026, 10:30 AM UTC

    This incident has been resolved.

  3. postmortem Aug 03, 2026, 03:59 PM UTC

    During this incident, CSPM services were unable to process scans due to a service startup failure due to connectivity issues to an external provider. As a result, scan jobs queued up and were not processed for the duration of the outage. After the affected services have been restored, the backlog of pending scans is expected to drain automatically, with normal scanning functionality resuming progressively.

Read the full incident report →

Minor July 3, 2026

Delay in Vulnerability Scan

Detected by Pingoru
Jul 03, 2026, 02:30 AM UTC
Resolved
Jul 03, 2026, 11:16 AM UTC
Duration
8h 46m
Affected: Sysdig SecureSysdig Data Ingestion
Timeline · 6 updates
  1. investigating Jul 03, 2026, 06:01 AM UTC

    We are currently investigating this issue.

  2. identified Jul 03, 2026, 06:01 AM UTC

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

  3. identified Jul 03, 2026, 06:03 AM UTC

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

  4. identified Jul 03, 2026, 10:24 AM UTC

    We have a fix in place we are working on processing the backlog of data and verifying that the fix it's correct.

  5. monitoring Jul 03, 2026, 10:56 AM UTC

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

  6. resolved Jul 03, 2026, 11:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 2, 2026

Vulnerability Management Reporting Experiencing Processing Issues

Detected by Pingoru
Jul 02, 2026, 06:55 AM UTC
Resolved
Jul 02, 2026, 06:00 PM UTC
Duration
11h 4m
Affected: Sysdig Secure
Timeline · 4 updates
  1. investigating Jul 01, 2026, 11:29 PM UTC

    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.

  2. identified Jul 02, 2026, 01:29 AM UTC

    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.

  3. monitoring Jul 02, 2026, 08:16 PM UTC

    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.

  4. resolved Jul 03, 2026, 05:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 23, 2026

KubeWorkload Vulnerability 360 Drawer Issue

Detected by Pingoru
Jun 23, 2026, 11:17 PM UTC
Resolved
Jun 24, 2026, 05:42 PM UTC
Duration
18h 25m
Affected: Sysdig Secure
Timeline · 8 updates
  1. identified Jun 23, 2026, 11:17 PM UTC

    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. identified Jun 24, 2026, 12:28 AM UTC

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

  3. monitoring Jun 24, 2026, 01:46 AM UTC

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

  4. monitoring Jun 24, 2026, 04:26 AM UTC

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

  5. monitoring Jun 24, 2026, 09:48 AM UTC

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

  6. monitoring Jun 24, 2026, 01:58 PM UTC

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

  7. monitoring Jun 24, 2026, 05:41 PM UTC

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

  8. resolved Jun 24, 2026, 05:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 16, 2026

Investigating potential delay in Vulnerability Management updates

Detected by Pingoru
Jun 16, 2026, 12:13 PM UTC
Resolved
Jun 16, 2026, 06:22 PM UTC
Duration
6h 9m
Affected: Sysdig Data Ingestion
Timeline · 4 updates
  1. investigating Jun 16, 2026, 12:13 PM UTC

    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. identified Jun 16, 2026, 01:53 PM UTC

    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. monitoring Jun 16, 2026, 03:24 PM UTC

    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. resolved Jun 16, 2026, 06:22 PM UTC

    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.

Read the full incident report →

Minor June 16, 2026

Vulnerability data ingestion delay impacting Vulnerability Overview and Findings

Detected by Pingoru
Jun 16, 2026, 02:33 AM UTC
Resolved
Jun 16, 2026, 06:22 AM UTC
Duration
3h 48m
Affected: Sysdig SecureSysdig Data Ingestion
Timeline · 4 updates
  1. identified Jun 16, 2026, 02:33 AM UTC

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

  2. monitoring Jun 16, 2026, 02:42 AM UTC

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

  3. monitoring Jun 16, 2026, 06:00 AM UTC

    We are continuing to monitor recovery of the system.

  4. resolved Jun 16, 2026, 06:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 6, 2026

Delay in Vulnerability Scan Results — US2 Region

Detected by Pingoru
May 06, 2026, 11:08 PM UTC
Resolved
May 07, 2026, 12:10 AM UTC
Duration
1h 1m
Affected: Sysdig Secure
Timeline · 4 updates
  1. investigating May 06, 2026, 11:08 PM UTC

    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. identified May 06, 2026, 11:22 PM UTC

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

  3. monitoring May 06, 2026, 11:46 PM UTC

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

  4. resolved May 07, 2026, 12:10 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 27, 2026

Report Generation Degradation

Detected by Pingoru
Apr 27, 2026, 09:11 PM UTC
Resolved
Apr 28, 2026, 07:34 AM UTC
Duration
10h 23m
Affected: Sysdig Secure
Timeline · 6 updates
  1. investigating Apr 27, 2026, 09:11 PM UTC

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

  2. identified Apr 27, 2026, 10:22 PM UTC

    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. monitoring Apr 28, 2026, 12:28 AM UTC

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

  4. monitoring Apr 28, 2026, 02:44 AM UTC

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

  5. monitoring Apr 28, 2026, 04:12 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Apr 28, 2026, 07:34 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor January 15, 2026

Partial Impact in Cost Metric Ingestion

Detected by Pingoru
Jan 15, 2026, 09:07 AM UTC
Resolved
Jan 15, 2026, 10:14 AM UTC
Duration
1h 6m
Affected: Sysdig Data Ingestion
Timeline · 2 updates
  1. monitoring Jan 15, 2026, 09:07 AM UTC

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

  2. resolved Jan 15, 2026, 10:14 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 13, 2026

Some AWS account CIEM scans are failing, impacting the freshness of CIEM insights

Detected by Pingoru
Jan 13, 2026, 03:21 PM UTC
Resolved
Jan 13, 2026, 08:30 PM UTC
Duration
5h 9m
Affected: Sysdig Secure
Timeline · 4 updates
  1. investigating Jan 13, 2026, 03:21 PM UTC

    We are currently investigating this issue.

  2. identified Jan 13, 2026, 05:13 PM UTC

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

  3. monitoring Jan 13, 2026, 06:40 PM UTC

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

  4. resolved Jan 13, 2026, 08:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 17, 2025

Attack Path visualization was down

Detected by Pingoru
Dec 17, 2025, 02:00 PM UTC
Resolved
Dec 17, 2025, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 17, 2025, 02:37 PM UTC

    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

Read the full incident report →

Minor December 1, 2025

Cloud Log Ingestion Failure from AWS us-east-1 workloads

Detected by Pingoru
Dec 01, 2025, 06:42 PM UTC
Resolved
Dec 10, 2025, 04:56 PM UTC
Duration
8d 22h
Affected: Sysdig Data Ingestion
Timeline · 5 updates
  1. investigating Dec 01, 2025, 06:42 PM UTC

    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. identified Dec 02, 2025, 06:39 PM UTC

    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. identified Dec 03, 2025, 05:19 PM UTC

    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. monitoring Dec 04, 2025, 07:48 PM UTC

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

  5. resolved Dec 10, 2025, 04:56 PM UTC

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

Read the full incident report →

Minor November 29, 2025

Delays in detection of policy events

Detected by Pingoru
Nov 29, 2025, 06:15 PM UTC
Resolved
Nov 30, 2025, 12:39 PM UTC
Duration
18h 23m
Affected: Sysdig Secure
Timeline · 3 updates
  1. investigating Nov 29, 2025, 06:15 PM UTC

    Customers may observe delays and/or misses in stateful detection policy events. The issue has been acknowledged, and our team is working to restore normal performance

  2. monitoring Nov 29, 2025, 06:37 PM UTC

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

  3. resolved Nov 30, 2025, 01:06 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Azure Cloud Metrics Unavailable

Detected by Pingoru
Oct 29, 2025, 08:00 PM UTC
Resolved
Oct 29, 2025, 10:29 PM UTC
Duration
2h 29m
Affected: Sysdig Data Ingestion
Timeline · 3 updates
  1. investigating Oct 29, 2025, 09:34 PM UTC

    We are currently investigating an issue causing Cloud Metrics in Azure to be unavailable due to upstream service failures at Microsoft Azure.

  2. investigating Oct 29, 2025, 09:35 PM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 29, 2025, 10:29 PM UTC

    Upon further investigation, the unavailability alert was triggered by a single customer integration that was manually disabled at 19:56 UTC. No broader customer impact has been observed, and Azure services continue to recover as expected. This incident is now considered a false positive alert, and Cloud Metrics functionality remains healthy for all active integrations. We will continue to monitor Azure’s recovery progress, but no active degradation is present on our side.

Read the full incident report →