rewindex

CompaniesSemgrepIncidents

Semgrep: Newly reported scan results not being processed (CI and Semgrep Managed Scans)

MinorStatus: resolvedStarted Resolved (42 min)3 updatesstspg.io (opens in new tab)

Affected components: Scans and CI/CDsemgrep.dev - Scans and CI/CDManaged Scanssemgrep.dev - Managed Scans

Timeline of updates

  1. investigating

    We are currently investigating an issue with scan results not being processed. You may see scan jobs appear to hang or time out at the stage of reporting findings to the platform.

  2. investigating

    We have rolled out a fix and are seeing scan results processing resume. We are monitoring the system for stability.

  3. resolved

    This issue has been resolved, and the system is now processing scans normally.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Semgrep, started 2026-02-24 22:38 UTC, resolved after 42 min, 3 update(s).

Title
Newly reported scan results not being processed (CI and Semgrep Managed Scans)
Vendor
Semgrep
Date
URL
https://rewindex.com/company/semgrep/incidents/svcvj6rfgctr

Semgrep profileRecent Semgrep incidentsAll outages on February 24, 2026Semgrep in February 2026MarkdownJSON