Live  /  Semgrep  /  Incident

Semgrep: Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Semgrep · semgrep.devMinor incidentResolved2026-10-19 23:49 UTC
Public — what happened

Summary

Semgrep said that some scans run with version 1.181.0 could not be reported back to the Semgrep AppSec Platform, failing with a 400 error. The problem began around 21:00 UTC on 2026-10-19, and Semgrep initially said it might be connected to how dependencies are resolved dynamically. About twenty minutes later it said it had identified the issue and was working on a fix, and at 23:05 UTC it said a fix had been released and it was monitoring the result. The incident was marked resolved at 23:49 UTC, and Semgrep rated it as minor.

Affected

Scans and CI/CD

As listed on Semgrep’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Semgrep against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Semgrep: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Semgrep report →

More from Semgrep

Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.

The full archive is on the Semgrep status & history page.

Related: Semgrep status & history. SquidGrid is not affiliated with Semgrep.