GitGuardian: Delayed check runs
Affected components: Secret Detection - Scan Check Run
Timeline of updates
- investigating
We've identified renewed performance degradation affecting check run and realtime processing, with some customers experiencing delays of up to approximately 30 minutes. We've identified contributing factors related to database load and have deployed mitigations to reduce impact. We're continuing to investigate further improvements and will share updates as we have more information.
- resolved
Resolved. Following database query optimizations and reduced load from noisy background jobs, no further performance degradation has been observed. Metrics have been stable since deployment of the fixes.
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-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
806d4fea2c43f949…
Impact, status and times are the vendor’s own, as last archived. View on status.gitguardian.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitGuardian, started 2026-08-18 11:11 UTC, resolved after 23 min, 2 update(s).
- Title
- Delayed check runs
- Vendor
- GitGuardian
- Date
- URL
- https://rewindex.com/company/gitguardian/incidents/01M0A92QJSZQ9Z22DG4YY6J6QZ
GitGuardian profileRecent GitGuardian incidentsAll outages on August 18, 2026GitGuardian in August 2026MarkdownJSON