Semgrep incident

Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Minor Resolved View vendor source →

Semgrep experienced a minor incident on October 19, 2026 affecting Scans and CI/CD, lasting 2h 48m. The incident has been resolved; the full update timeline is below.

Started
Oct 19, 2026, 09:00 PM UTC
Resolved
Oct 19, 2026, 11:49 PM UTC
Duration
2h 48m
Detected by Pingoru
Oct 19, 2026, 09:00 PM UTC

Affected components

Scans and CI/CD

Update timeline

  1. investigating Oct 19, 2026, 09:00 PM UTC

    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.

  2. identified Oct 19, 2026, 09:20 PM UTC

    We have identified the issue and are working on a fix.

  3. monitoring Oct 19, 2026, 11:05 PM UTC

    We have released a fix for this issue and are monitoring to confirm resolution.

  4. resolved Oct 19, 2026, 11:49 PM UTC

    This issue has been resolved.