Search

Companies / Semgrep / incidents

Semgrep: Scans failing to start

Impact: criticalStatus: resolvedStarted Resolved (22 min)2 updatesSource: stspg.io (opens in new tab)
Summary

Semgrep reported a critical outage affecting Managed Scans and CI scans because of a problem generating configurations for new scans. The recorded window was 2026-04-22 18:14 UTC–18:35 UTC (21 min), though Semgrep reported onset around 17:30 UTC. Semgrep took action and confirmed resolution; users with pending scans were advised to push a new commit to retry.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Scans and CI/CDsemgrep.dev - Scans and CI/CDManaged Scanssemgrep.dev - Managed Scans

Timeline of updates

  1. monitoring

    We have identified a problem in the service that generates the configuration for new scans. This incident began at approximately 17:30 UTC, and it affects both Managed Scans and CI scans. We have taken action and are actively monitoring the system. If you have a scan that is pending, you can push a new commit to cause the scan to retry.

  2. resolved

    This incident has been resolved.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Semgrep profile · Recent Semgrep incidents · Markdown · JSON