Companies / Semgrep / incidents
Semgrep: Elevated errors on managed diff scans
Semgrep reported a major incident affecting Managed Scans: some jobs failed, primarily diff scans used for PR/MR checks. The incident ran from 2026-03-13 18:10 UTC to 2026-03-13 19:48 UTC (1 h 37 min), though errors began rising at 2026-03-13 04:30 UTC. Semgrep increased resources for affected projects; customers could push a new commit to trigger a new scan.
Machine-written from the archived incident (Sol). Check the timeline before relying on it.
Affected components: Managed Scanssemgrep.dev - Managed Scans
Timeline of updates
- investigating
Errors started Mar 12 at 21:30 PST and have been increasing since then.
- investigating
We are investigating issues that are causing some Semgrep Managed Scan (SMS) scan jobs to fail. This is primarily affecting diff scans, which are used for checks on PRs and MRs. The error rate began to rise at approximately 21:30PT on Thursday, March 12 (2026-03-13 04:30 UTC). We will share updates as information becomes available.
- identified
We have identified the cause of the problem and are working on a fix.
- monitoring
We’ve assessed that the scan failures are due to insufficient resources allocated to scans in particular projects. In response, we increased the resources available to affected projects. We are actively monitoring scan performance, and we’re seeing errors diminish. If your repository was affected, you can push a new commit to your PR/MR to trigger a new scan. The new scan will run with increased resources.
- resolved
This incident has been resolved.
Rewindex changes for this incident
- Major incident: Elevated errors on managed diff scans 2026-03-13 18:10 UTC
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