Semgrep: Scans are degraded or delayed
Affected components: Managed ScansScans and CI/CDsemgrep.dev - Managed Scanssemgrep.dev - Scans and CI/CD
Timeline of updates
- identified
The issue has been identified and a fix is being implemented.
- 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.
First version captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
002ff6b1edd9096c…Version 2 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6813ee56719b1d12…
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-28 19:16 UTC, resolved after 2.4 h, 2 update(s); edited after publishing.
- Title
- Scans are degraded or delayed
- Vendor
- Semgrep
- Date
- URL
- https://rewindex.com/company/semgrep/incidents/rz315h1h99xq
Semgrep profileRecent Semgrep incidentsAll outages on October 28, 2026Semgrep in October 2026MarkdownJSON