Changes / Semgrep / Elevated errors on managed diff scans

Semgrep: Major incident: Elevated errors on managed diff scans

Summary

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 diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 92%)Changed Detected Source: stspg.io

What changed

AddedTitle#1
Before: not present
After: Elevated errors on managed diff scans
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-03-13 18:10 UTC
AddedResolved time#5
Before: not present
After: 2026-03-13 19:48 UTC
AddedAffected components#6
Before: not present
After: Managed Scans, semgrep.dev - Managed Scans
AddedUpdateinvestigating#7
Before: not present
After: Errors started Mar 12 at 21:30 PST and have been increasing since then.
AddedUpdateinvestigating#8
Before: not present
After: 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.
AddedUpdateidentified#9
Before: not present
After: We have identified the cause of the problem and are working on a fix.
AddedUpdatemonitoring#10
Before: not present
After: 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.
AddedUpdateresolved#11
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)ChangeKind
Major incident: Elevated errors on managed diff scans (this change)
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.
Major incident

All Semgrep changes → · Semgrep profile · Markdown · JSON