Semgrep experienced a major incident on March 13, 2026 affecting Managed Scans, lasting 1h 37m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Mar 13, 2026, 06:10 PM UTC
Errors started Mar 12 at 21:30 PST and have been increasing since then.
- investigating Mar 13, 2026, 06:15 PM UTC
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 Mar 13, 2026, 06:55 PM UTC
We have identified the cause of the problem and are working on a fix.
- monitoring Mar 13, 2026, 07:25 PM UTC
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 Mar 13, 2026, 07:48 PM UTC
This incident has been resolved.