Elevated errors on managed diff scans
Incident Lifecycle
Incident Timeline
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.
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.
Mar 13, 2026 at 7:25 PM UTC
Identified
We have identified the cause of the problem and are working on a fix.
Mar 13, 2026 at 6:55 PM UTC
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.
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.
Mar 13, 2026 at 6:15 PM UTC
Investigating
Errors started Mar 12 at 21:30 PST and have been increasing since then.
Mar 13, 2026 at 6:10 PM UTC
Was your business affected by this Semgrep outage?
Set up instant alerts for Semgrep, be the first to know about outages via email, Slack, Teams, or Discord.