GitGuardian incident

Delayed check runs

Resolved after 2 days 20 hours, affecting Secret Detection - Scan Check Run and Secret Detection - Scan Check Run, on August 11, 2026.

resolved Aug 14, 2026, 01:46 PM UTC

This incident is now resolved. Following fixes deployed by our team, we have not observed further performance degradation, and metrics have been stable since.

Started
Aug 11, 2026, 05:38 PM UTC
Resolved
Aug 14, 2026, 01:46 PM UTC
Duration
2d 20h
Detected by Pingoru
Aug 11, 2026, 05:38 PM UTC

Affected components

Secret Detection - Scan Check RunSecret Detection - Scan Check Run

Update timeline

  1. investigating Aug 11, 2026, 05:38 PM UTC

    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.

  2. investigating Aug 11, 2026, 07:39 PM UTC

    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.

  3. monitoring Aug 12, 2026, 07:24 AM UTC

    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.

  4. resolved Aug 14, 2026, 01:46 PM UTC

    This incident is now resolved. Following fixes deployed by our team, we have not observed further performance degradation, and metrics have been stable since.

Your product runs on more than GitGuardian

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →