Semgrep change history

Semgrep reported a major Login/SSO outage causing intermittent semgrep.dev login failures for GitHub and GitLab users, who could see an "unrecoverable error" after clicking Continue. It started at 2026-10-05 16:00 UTC and lasted 14 min, resolving at 2026-10-05 16:14 UTC after a fix was rolled out.

Semgrep reported a major outage preventing Managed Scans and CI scans from completing because findings could not upload, alongside web UI access issues. It started at 2026-09-22 19:24 UTC and resolved at 2026-09-22 19:37 UTC, lasting 12 min. Engineering initiated a rollback and confirmed all products operational.

Semgrep reported a major outage starting 2026-09-04 23:13 UTC: an incomplete 1.176.1 patch release prevented PyPI installations from using Pro Engine. It recommended installing 1.175.1 or 1.176.0 temporarily. Resolved at 2026-09-04 23:38 UTC after 24 min, Pro Engine could again be installed and used normally with Semgrep 1.176.1 via PyPI.

Semgrep reported a major degradation of SMS Managed Scans starting 2026-09-03 21:35 UTC, lasting 1 h 10 min and resolving at 2026-09-03 22:45 UTC. The vendor attributed the disruption to an AWS STS outage in us-west-2 and confirmed full recovery of all Semgrep products at resolution.

Semgrep reported a critical incident affecting Dashboard and Scans and CI/CD, starting 2026-08-25 19:21 UTC and lasting 2 h 40 min. A bad release caused widespread platform failures; rollback restored stability, and a successful release fully resolved the issue at 2026-08-25 22:01 UTC.

Semgrep reported a major incident affecting Managed Scans: lockfileless scans failed for certain deployments from 2026-08-12 18:16 UTC until resolution at 2026-08-12 21:03 UTC, lasting 2 h 46 min. A fix was rolled out by 2026-08-12 20:23 UTC, restoring scans; no specific root cause was disclosed.

Customers with custom SSO configurations could not log in to Semgrep and saw 504 Gateway Timeout errors. The major-impact incident started at 2026-07-16 09:38 UTC and was resolved at 2026-07-16 12:46 UTC, lasting 3 h 7 min. Semgrep stated that the third-party vendor resolved it.

Semgrep reported a major incident causing widespread exit code 7 scan failures in Managed Scans and Scans and CI/CD from 2026-06-25 21:32 UTC to 2026-06-25 22:27 UTC (55 min). A bad AI skills rules release caused the failures; Semgrep removed "skills.behavioral.skill-destructive-commands.skill-destructive-commands" and confirmed scans were running normally.

Semgrep reported a major outage affecting GitHub-auth logins starting 2026-05-20 17:34 UTC; SSO logins were unaffected. A fix was rolled out at 17:49 UTC, restoring logins, and the incident was resolved at 2026-05-20 18:18 UTC after 44 min.

Semgrep reported major scheduling delays in Semgrep Managed Scanning (SMS), with some scans failing to execute. Recorded start: 2026-05-19 18:54 UTC, with reported onset approximately 18:30 UTC; resolved: 2026-05-19 21:33 UTC; duration: 2 h 38 min. After a system change was deployed, scheduling queues and scan success rates began recovering.

Semgrep reported a major outage: scans failed to start from 14:35 to 14:52 UTC. The vendor said it mitigated the issue and scans were starting normally. The incident is marked resolved, but its recorded start (2026-04-24 16:37 UTC) and resolution (2026-04-24 12:30 UTC) conflict; computed duration is unknown.

Semgrep reported a critical outage affecting Managed Scans and CI scans because of a problem generating configurations for new scans. The recorded window was 2026-04-22 18:14 UTC–18:35 UTC (21 min), though Semgrep reported onset around 17:30 UTC. Semgrep took action and confirmed resolution; users with pending scans were advised to push a new commit to retry.

Semgrep reported a major outage affecting some users’ logins, managed scan starts, and CI scan result processing from 2026-04-20 20:37 UTC to 2026-04-21 00:29 UTC, lasting 3 h 51 min. Semgrep identified backend issues without detailing the cause; scans and logins were processing normally at resolution.

Semgrep reported a major incident affecting Managed Scans: some jobs failed, primarily diff scans used for PR/MR checks. The incident ran from 2026-03-13 18:10 UTC to 2026-03-13 19:48 UTC (1 h 37 min), though errors began rising at 2026-03-13 04:30 UTC. Semgrep increased resources for affected projects; customers could push a new commit to trigger a new scan.

Semgrep reported a major outage affecting repository scans and GitHub pull request checks: some customers saw scans not starting or checks not appearing. It started at 2026-03-06 12:04 UTC and was resolved at 2026-03-06 16:18 UTC, lasting 4 h 14 min. A fix was rolled out, and scans returned to normal operation.

Semgrep reported a critical AppSec Platform login-page outage affecting Login/SSO; existing sessions remained operative. It started at 2026-03-03 19:23 UTC and was resolved at 2026-03-03 20:05 UTC, lasting 41 min. A fix restored page loading at 19:42 UTC; login and other platform functions were normal at resolution.