Changes / Semgrep / Scans failing to start
Semgrep: Critical incident: Scans failing to start
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 diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Scans failing to start
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-04-22 18:14 UTC
Before: not present
After: 2026-04-22 18:35 UTC
Before: not present
After: Managed Scans, Scans and CI/CD, semgrep.dev - Managed Scans, semgrep.dev - Scans and CI/CD
Before: not present
After: 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.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Scans failing to start (this change) 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. | Major incident |