# Semgrep: Scans failing to start

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2026-04-22 18:14 UTC · Resolved: 2026-04-22 18:35 UTC · Duration: 22 min
- Updates: 2 · Affected components: Scans and CI/CD, semgrep.dev - Scans and CI/CD, Managed Scans, semgrep.dev - Managed Scans
- [Vendor status page: https://stspg.io/q80z4ftw0fxg](https://stspg.io/q80z4ftw0fxg)
- [Company: Semgrep](https://rewindex.com/company/semgrep.md)

## 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, sol)_
## Timeline of updates

- **monitoring** 2026-04-22 18:14 UTC: 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.
- **resolved** 2026-04-22 18:35 UTC: This incident has been resolved.

## Rewindex changes for this incident

- 2026-04-22 18:14 UTC: [Critical incident: Scans failing to start](https://rewindex.com/change/i6e8524e9190e39.md)


---
Canonical: https://rewindex.com/company/semgrep/incidents/y2mmpz3jyky0 · Markdown: https://rewindex.com/company/semgrep/incidents/y2mmpz3jyky0.md · JSON: https://rewindex.com/api/v1/companies/semgrep/incidents/y2mmpz3jyky0 · Generated 2026-10-18T10:42:19.382Z