Sysdig US-West-2 Outage History

Sysdig US-West-2 is up right now

There were 5 Sysdig US-West-2 outages since February 17, 2026 totaling 126h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

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

Notice 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 April 3, 2026

Degraded Performance for Agentless Scanning

Detected by Pingoru
Apr 03, 2026, 05:17 PM UTC
Resolved
Apr 05, 2026, 06:53 AM UTC
Duration
1d 13h
Affected: Sysdig Secure
Timeline · 15 updates
  1. investigating Apr 03, 2026, 08:31 AM UTC

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

  2. investigating Apr 03, 2026, 08:57 AM UTC

    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. investigating Apr 03, 2026, 11:34 AM UTC

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

  4. investigating Apr 03, 2026, 03:44 PM UTC

    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. monitoring Apr 03, 2026, 05:17 PM UTC

    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. monitoring Apr 03, 2026, 11:13 PM UTC

    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.

  7. monitoring Apr 04, 2026, 07:10 AM UTC

    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.

  8. monitoring Apr 04, 2026, 12:20 PM UTC

    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.

  9. monitoring Apr 04, 2026, 04:19 PM UTC

    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.

  10. monitoring Apr 04, 2026, 08:04 PM UTC

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

  11. monitoring Apr 04, 2026, 08:04 PM UTC

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

  12. monitoring Apr 04, 2026, 08:05 PM UTC

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

  13. monitoring Apr 05, 2026, 12:04 AM UTC

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

  14. monitoring Apr 05, 2026, 04:59 AM UTC

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

  15. resolved Apr 05, 2026, 06:53 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 26, 2026

Sysdig Cloud Platform Alerting Degradation

Detected by Pingoru
Mar 26, 2026, 10:30 AM UTC
Resolved
Mar 26, 2026, 10:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 26, 2026, 12:50 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. The issue was solved at 12.18pm UTC

Read the full incident report →

Minor February 17, 2026

Wrong policy data being reflected in compliance and inventory

Detected by Pingoru
Feb 17, 2026, 09:47 AM UTC
Resolved
Feb 20, 2026, 03:55 PM UTC
Duration
3d 6h
Affected: Sysdig Secure
Timeline · 16 updates
  1. investigating Feb 17, 2026, 09:47 AM UTC

    We are currently investigating the issue

  2. identified Feb 17, 2026, 11:58 AM UTC

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

  3. identified Feb 17, 2026, 02:16 PM UTC

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

  4. identified Feb 17, 2026, 04:26 PM UTC

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

  5. identified Feb 17, 2026, 05:35 PM UTC

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

  6. monitoring Feb 17, 2026, 09:57 PM UTC

    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

  7. investigating Feb 18, 2026, 07:03 AM UTC

    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.

  8. identified Feb 18, 2026, 09:42 AM UTC

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

  9. monitoring Feb 18, 2026, 05:12 PM UTC

    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.

  10. monitoring Feb 18, 2026, 09:55 PM UTC

    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.

  11. monitoring Feb 19, 2026, 12:21 AM UTC

    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.

  12. monitoring Feb 19, 2026, 08:58 AM UTC

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

  13. monitoring Feb 19, 2026, 07:53 PM UTC

    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.

  14. monitoring Feb 20, 2026, 01:05 AM UTC

    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.

  15. monitoring Feb 20, 2026, 10:36 AM UTC

    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.

  16. resolved Feb 20, 2026, 03:55 PM UTC

    This incident has been resolved.

Read the full incident report →

Looking to track Sysdig US-West-2 downtime and outages?

Pingoru polls Sysdig US-West-2's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Sysdig US-West-2 reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Sysdig US-West-2 alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Sysdig US-West-2 for free

5 free monitors · No credit card required