# Semgrep change history Filter: kind=all. Query: `?kind=notable|all|pages|pricing|trust|legal|incident|incident_edit|incident_deleted|incident_update&history=&page=N`. Company profile: [Semgrep](https://rewindex.com/company/semgrep.md) ## Changes by kind | Kind | Changes | Notable | Latest (UTC) | | --- | --- | --- | --- | | Major incident | 18 | 18 | 2026-10-05 16:00 UTC | ## Timeline | When (UTC) | Kind | Change | Label | Summary | | --- | --- | --- | --- | --- | | 2026-10-05 16:00 UTC | Major incident | [Major incident: Intermittent login failures on semgrep.dev](https://rewindex.com/change/i6f327a9ef68684.md) | outage | 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. | | 2026-09-22 19:24 UTC | Major incident | [Major incident: Interruption to Scans and Accessing Web App](https://rewindex.com/change/ifd047f8ad12b7f.md) | outage | 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. | | 2026-09-04 23:13 UTC | Major incident | [Major incident: Incomplete Semgrep 1.176.1 release: PyPI installs cannot use Pro Engine](https://rewindex.com/change/i102fa2112daceb.md) | outage | 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. | | 2026-09-03 21:35 UTC | Major incident | [Major incident: SMS Scans Degraded](https://rewindex.com/change/ia6e4848e5083cc.md) | degradation | 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. | | 2026-08-25 19:21 UTC | Major incident | [Critical incident: Widespread errors on Semgrep AppSec Platform](https://rewindex.com/change/i13e5ee3558c7bb.md) | outage | 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. | | 2026-08-12 18:16 UTC | Major incident | [Major incident: Lockfileless scans failing for certain deployments](https://rewindex.com/change/if504fe72a93608.md) | outage | 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. | | 2026-07-16 09:38 UTC | Major incident | [Major incident: Custom SSO Login Issues](https://rewindex.com/change/ib0114258cbd9fe.md) | outage | 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. | | 2026-06-25 21:32 UTC | Major incident | [Major incident: Scan failures with exit code 7 due to invalid rule](https://rewindex.com/change/i2f8b9a4919a0ab.md) | outage | 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. | | 2026-05-20 17:34 UTC | Major incident | [Major incident: Logins are failing for users via GitHub auth](https://rewindex.com/change/i3de15037cd3916.md) | outage | 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. | | 2026-05-19 18:54 UTC | Major incident | [Major incident: Scheduling delays for Semgrep Managed Scanning (SMS)](https://rewindex.com/change/i3ee4d94f6fbdf6.md) | degradation | 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. | | 2026-04-24 16:37 UTC | Major incident | [Major incident: Failure to start scans from 14:35 to 14:52 UTC](https://rewindex.com/change/i87b6637ea99683.md) | outage | 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. | | 2026-04-22 18:14 UTC | Major incident | [Critical incident: Scans failing to start](https://rewindex.com/change/i6e8524e9190e39.md) | outage | 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. | | 2026-04-20 20:37 UTC | Major incident | [Major incident: Login and scans are failing for some users](https://rewindex.com/change/i88faa45f0c126c.md) | outage | 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. | | 2026-03-13 18:10 UTC | Major incident | [Major incident: Elevated errors on managed diff scans](https://rewindex.com/change/ia04ebd74d9a351.md) | outage | 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. | | 2026-03-06 12:04 UTC | Major incident | [Major incident: Investigating issues with pull request checks and repository scans](https://rewindex.com/change/i4decac4bf27e84.md) | outage | 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. | | 2026-03-03 19:23 UTC | Major incident | [Critical incident: Semgrep AppSec Platform login page is not working](https://rewindex.com/change/i9f5208a36d3315.md) | outage | 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. | | 2026-01-09 17:02 UTC | Major incident | [Major incident: Degraded scan performance in CI and Semgrep Managed Scans](https://rewindex.com/change/i6f617eb09e26dd.md) | degradation | Semgrep reported major scan performance degradation in CI and Semgrep Managed Scans from 2026-01-09 17:02 UTC to 2026-01-09 23:27 UTC, lasting 6 h 25 min. Semgrep implemented several changes and reported recovery; at resolution, the system was stable and scans were executing normally. | | 2026-01-08 10:40 UTC | Major incident | [Major incident: Some CI Scans are not completing successfully](https://rewindex.com/change/ic0ac35b2f3f01e.md) | degradation | Semgrep reported a major CI scan degradation starting 2026-01-08 10:40 UTC: some scans failed to complete or took a long time, getting stuck at "Uploading scan results" or "Finalizing scan". A fix was implemented at 12:11 UTC, and the incident was resolved at 2026-01-08 13:36 UTC after 2 h 56 min. | --- Canonical: https://rewindex.com/company/semgrep/changes · Markdown: https://rewindex.com/company/semgrep/changes.md · JSON: https://rewindex.com/api/v1/companies/semgrep/changes · Generated 2026-10-18T00:36:58.403Z