Looking for an update now? Check the current status, or follow Semgrep for future changes.
77.6%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
86.7%
30
4
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0
We have released a fix for this issue and are monitoring to confirm resolution.
identified
We have identified the issue and are working on a fix.
investigating
Some scans with Semgrep 1.181.0 are unable to be successfully reported to the Semgrep AppSec Platform due to a 400 error. The issue may be related to dynamic dependency resolution.
We are currently observing intermittent login failures on semgrep.dev for users signing in with GitHub and GitLab. Affected users may see an "unrecoverable error" page after clicking Continue. Our team has identified the cause and is working on a fix.
Engineering initiated a rollback to fix issues with scans uploading findings preventing successful completion of Managed Scans and CI scans. We are verifying the fix before marking resolved.
identified
We are currently investigating issues with scans uploading findings which prevents the successful completion of scans. Additionally, we are aware of issues accessing the web user interface.
An incomplete patch release of Semgrep 1.176.1 has left installations of this version using PyPI unable to use the Pro Engine.
We recommend explicitly installing version 1.175.1 or 1.176.0 as we work to resolve this issue.
The release has been rolled back and the platform is now stable.
identified
A bad release is causing widespread failures in the Semgrep AppSec Platform.
Legacy Incident Archive
22 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Lockfileless scans failing for certain deployments
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have rolled out a fix, and scans are now working as expected. We are closely monitoring to ensure continued stability.
identified
We've identified the root cause of the issue and are currently working on a fix.
investigating
We are currently investigating this issue.
July 2026
Fragment scanner unavailable to some users
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed. We will continue to monitor our systems to ensure that the issue has been resolved.
identified
We have identified the issue and are actively working on a fix.
investigating
We are currently investigating this issue.
Findings data display lagging behind realtime
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Backfill is continuing and lag has reduced to approximately 1 hour behind realtime. We continue to monitor to ensure progress.
monitoring
Processing of findings data has been delayed since approximately 03:20 UTC and is currently lagging approximately 3 hours behind realtime. The underlying cause has been addressed and we are monitoring to ensure the backlog is processed.
Custom SSO Login Issues
majorSource not attested
Last archived state: resolved
View archived record details
investigating
We're aware of an issue where customers with custom SSO configs are unable to login to Semgrep and are seeing a 504 Gateway Timeout error.
The issue is under investigation
Adding a memory crashes the Memories page in the platform
minorSource not attested
Last archived state: resolved
View archived record details
identified
We've identified the root cause and observed that both creating and editing memories is affected. We are working on a fix for the issue.
investigating
We've observed that when trying to add a new memory, the Memories page crashes, and we are investigating the issue.
June 2026
Scan failures with exit code 7 due to invalid rule
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have removed the problem rule ("skills.behavioral.skill-destructive-commands.skill-destructive-commands") and we are seeing scan behavior recover. We are continuing to monitor for full recovery.
identified
We have observed widespread scan failures relating to a bad release of AI skills rules. We are working to fix the issue.
To prevent the issue in the meantime, you can disable the "skills.behavioral.skill-destructive-commands.skill-destructive-commands" rule in your Semgrep policies.
Delays in scan processing
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
We are currently investigating this issue.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating this issue.
Degraded scan performance in CI and Semgrep Managed Scans
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating an issue causing degraded scan performance in CI and Semgrep Managed Scans, and are actively working to resolve it.
May 2026
Logins are failing for users via GitHub auth
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have rolled out a fix, and logins are now working as expected. We are closely monitoring to ensure continued stability.
identified
We are currently observing login issues using GitHub auth. Our team has identified the issue and is currently working on a fix. SSO logins are working as expected and are not impacted.
Managed Scans: full project scans being associated with HEAD instead of the default branch name
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have deployed the fix and are monitoring.
identified
We have identified the issue and are working on a resolution.
investigating
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.
