Outage in Semgrep
Managed Scans: full project scans being associated with HEAD instead of the default branch name
Resolved MinorIncident Report
We are currently investigating an issue where full project scans in Managed Scans are being associated with HEAD rather than the name of the default branch. This issue started around 16:00 UTC on May 19 and may result in unexpected new findings notifications, and some findings not being closed as expected.
Trusted by 1,000+ teams
Never miss outages in third-party dependencies
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
RESOLVED
5 days ago - at 05/20/2026 02:52AM
This incident has been resolved.
IDENTIFIED
5 days ago - at 05/20/2026 02:08AM
We have identified the issue and are working on a resolution.
INVESTIGATING
5 days ago - at 05/20/2026 01:18AM
We are currently investigating an issue where full project scans in Managed Scans are being associated with HEAD rather than the name of the default branch. This issue started around 16:00 UTC on May 19 and may result in unexpected new findings notifications, and some findings not being closed as expected.
Latest Semgrep outages
Logins are failing for users via GitHub auth - 5 days ago
Scheduling delays for Semgrep Managed Scanning (SMS) - 5 days ago
A small subset of users are unable to login - 26 days ago
Scans failing to start - about 1 month ago
Never miss outages in third-party dependencies
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
