Semgrep: Incident updated: Delayed Scans

Incident updateNormal progress (rule, 100%)Changed 2026-10-30 15:33 UTCstatus.semgrep.dev

Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what Semgrep removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1

~~monitoring~~

resolved

AddedResolved time#2

not present

2026-10-30 15:26 UTC

AddedUpdateresolved2026-10-30 15:26 UTC#3

not present

We are seeing full recovery and consider this incident resolved.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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.

Oct 30
Before captured 15:23 UTC
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on Oct 31, 00:42 UTC. Record hash 3073239e145f395f…
Download proof
Oct 30
After captured 15:33 UTC
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on Oct 31, 00:42 UTC. Record hash 47c7bdf43456e248…
Download proof

History of this incident

YesterdayFriday, October 30Fri, Oct 30

2 incident changes

Normal progress
15:33Incident
Incident updateDelayed Scansthis change
Normal progress
15:23Incident
Incident updateDelayed Scans

All Semgrep changes Semgrep profile Markdown JSON