GitGuardian incident

Performance Issues Affecting GitGuardian Services

Major Resolved View vendor source →

GitGuardian experienced a major incident on September 11, 2025 affecting Dashboard and Secrets Detection API, lasting 2h 42m. The incident has been resolved; the full update timeline is below.

Started
Sep 11, 2025, 04:31 PM UTC
Resolved
Sep 11, 2025, 07:14 PM UTC
Duration
2h 42m
Detected by Pingoru
Sep 11, 2025, 04:31 PM UTC

Affected components

DashboardSecrets Detection API

Update timeline

  1. investigating Sep 11, 2025, 05:31 PM UTC

    We are currently experiencing performance issues affecting multiple GitGuardian services. Our engineering team is actively investigating and working to resolve these issues as quickly as possible. Current Impact: - Dashboard may load slowly or fail to load intermittently - Public API response times are degraded, which may cause slower performance in ggshield and other integrations - Real-time event processing is experiencing delays, resulting in delayed incident notifications What we're doing: Our engineering team has been alerted and is actively investigating the root cause. We will provide updates as significant developments occur. We apologize for any inconvenience this may cause and appreciate your patience as we work to restore full service performance.

  2. investigating Sep 11, 2025, 05:46 PM UTC

    Some GitHub check-runs may be failing, leading to blocked PRs

  3. investigating Sep 11, 2025, 05:47 PM UTC

    We are continuing to investigate this issue.

  4. identified Sep 11, 2025, 05:49 PM UTC

    The issue has been identified and we are taking remedial actions.

  5. monitoring Sep 11, 2025, 06:17 PM UTC

    We have successfully implemented a resolution that has restored normal operations for the majority of affected services. Service Status: Dashboard: Performance has been fully restored across all regions Public API: Response times have returned to baseline levels Check-runs: Processing has resumed normal operational parameters Real-time scanning: Experiencing residual delays; remediation in progress Next Steps: Our engineering team is actively addressing the remaining performance impact on real-time scanning services.

  6. monitoring Sep 11, 2025, 06:23 PM UTC

    We are continuing to monitor our services as they return to normal operations. Notice: Some check runs may have failed due to timeout errors during the incident. These can be safely restarted manually and should now complete successfully. We will provide a final update once monitoring confirms no further delays on real-time scanning services.

  7. resolved Sep 11, 2025, 07:14 PM UTC

    All GitGuardian services have been fully restored and are operating normally. Real-time scanning has returned to normal service levels, and our monitoring confirms stable performance across all components. We implemented mitigation measures to address the immediate symptoms while continuing to investigate the underlying root cause. What Happened: A database performance issue caused automatic removal of GitGuardian cloud integrations, specifically affecting Jira Cloud and Confluence Cloud installations. Impact: - Jira Cloud integrations: Both scanning sources and notification integrations were uninstalled - Confluence Cloud integrations: Source scanning integrations were uninstalled - Service availability: Real-time monitoring and GitGuardian features are currently unavailable for affected installations Resolution option: Customers can reinstall integrations to immediately restore functionality Current Status: - We are compiling a comprehensive list of all impacted customers - Our customer support team will proactively reach out to affected customers with detailed guidance Important: While reinstallation is possible now, there remains a small risk of recurrence until we fully resolve the root cause. Additional proactive monitoring has been implemented to prevent future occurrences. Next Steps: - Complete root cause analysis and full postmortem documentation - Notify all customers once the underlying issue is definitively resolved - Customers may choose to wait for our all-clear notification before reinstalling We sincerely apologize for this disruption and will keep you updated as our investigation progresses.