rewindex

CompaniesSemgrepIncidents

Semgrep: Delay in findings being updated

MinorStatus: resolvededitedStarted Resolved (43 min)2 updatesstatus.semgrep.dev (opens in new tab)

Affected components: APIDashboardScans and CI/CDsemgrep.dev - APIsemgrep.dev - Dashboardsemgrep.dev - Scans and CI/CD

Timeline of updates

  1. investigating

    Findings processing is delayed, and new findings or updates may take some time to appear. We are currently investigating this issue.

  2. resolved

    This incident has been resolved.

Changes Rewindex caught on this incident

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 these records existed by then and have 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 status.semgrep.dev (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Semgrep, started 2026-10-27 17:25 UTC, resolved after 43 min, 2 update(s); edited after publishing.

Title
Delay in findings being updated
Vendor
Semgrep
Date
URL
https://rewindex.com/company/semgrep/incidents/3h191fp65bdh

Semgrep profileRecent Semgrep incidentsAll outages on October 27, 2026Semgrep in October 2026MarkdownJSON