GitGuardian experienced a minor incident on August 11, 2026 affecting Secret Detection - Scan Check Run and Secret Detection - Scan Check Run, lasting 2d 20h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 11, 2026, 05:38 PM UTC
Status: Investigating We are aware of delays affecting check runs and GitHub Actions checks for some customers. Our team is actively working on it. We'll post another update as soon as we have more information. Affected components Secret Detection - Scan Check Run (Degraded performance)
- investigating Aug 11, 2026, 07:39 PM UTC
Status: Investigating We are continuing to investigate delays affecting check runs and GitHub Actions checks for customers. The root cause hasn't been confirmed yet, but we've applied mitigations to reduce load on our systems. We're closely monitoring the situation and will share another update as soon as we have more information. Affected components Secret Detection - Scan Check Run (Degraded performance)
- monitoring Aug 12, 2026, 07:24 AM UTC
Status: Monitoring Service has returned to normal levels and we're no longer seeing degradation. Our engineering team has applied mitigations and continues to investigate the underlying cause to prevent recurrence. We're closely monitoring the situation and will update this page as needed. Affected components Secret Detection - Scan Check Run (Operational)
- resolved Aug 14, 2026, 01:46 PM UTC
Status: Resolved This incident is now resolved. Following fixes deployed by our team, we have not observed further performance degradation, and metrics have been stable since. Affected components Secret Detection - Scan Check Run (Operational)