Semgrep: Possibly Delayed Scans
Affected components: AWS - AWS ec2-us-west-2AWS ec2-us-west-2Managed Scanssemgrep.dev - Managed Scans
Timeline of updates
- identified
We are observing an AWS EC2 failure in at least one region. We are observing that we have sufficient capacity to handle current load, and will post an update once more to report.
- monitoring
We are beginning to observe recovery. We will continue monitoring.
- resolved
We have observed full recovery of affected systems.
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 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.
First version captured
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
77f1dec4e7653152…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
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-11-06 23:46 UTC, resolved after 1.1 h, 3 update(s); edited after publishing.
- Title
- Possibly Delayed Scans
- Vendor
- Semgrep
- Date
- URL
- https://rewindex.com/company/semgrep/incidents/m1sq3l6yd4n5
Semgrep profileRecent Semgrep incidentsAll outages on November 6, 2026Semgrep in November 2026MarkdownJSON