Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0
View the provider incident record →Current answer
Semgrep experienced a minor incident: Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0. ServiceAlert observed recovery on Oct 19, 2026.
Looking for an update now? Check the current status, or follow Semgrep for future changes.
Incident Lifecycle
Affected Components
Scans and CI/CD
Incident Timeline
Monitoring
We have released a fix for this issue and are monitoring to confirm resolution.
Oct 19, 2026 at 11:05 PM UTC
Identified
We have identified the issue and are working on a fix.
Oct 19, 2026 at 9:20 PM UTC
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.
Oct 19, 2026 at 9:00 PM UTC
Was your business affected by this Semgrep outage?
Follow Semgrep and route available status alerts to email or a team channel.