Semgrep: Incident updated: Possibly Delayed Scans

Incident updateNormal progress (rule, 100%)Changed 2026-11-07 00:13 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

~~identified~~

monitoring

AddedUpdatemonitoring2026-11-07 00:09 UTC#2

not present

We are beginning to observe recovery. We will continue monitoring.

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 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.

Nov 6
Before captured 23:53 UTC
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on Nov 7, 00:44 UTC. Record hash 77f1dec4e7653152…
Download proof

Rewindex captured a newer version after the last checkpoint; the next run (00:41 UTC) commits it.

History of this incident

TodaySaturday, November 7Sat, Nov 7

2 incident changes

Normal progress
01:04Incident
Incident updatePossibly Delayed Scans
Normal progress
00:13Incident
Incident updatePossibly Delayed Scansthis change

Cite this

Incident updated: Possibly Delayed Scans on Semgrep’s status page, changed 2026-11-07 00:13 UTC (change 1 of 2).

Title: Incident updated: Possibly Delayed Scans
Vendor: Semgrep
Date: 2026-11-07 00:13 UTC
URL: https://rewindex.com/change/rc27ba2b99ef0e5

All Semgrep changes Semgrep profile Markdown JSON