GitGuardian Outage History

What happened: From June 1 12:00am UTC to June 1 08:45am UTC, one of the component serving the public monitoring experienced some delays and a growing backlog of unprocessed messages. Impact: No data was lost. The only impact for customers could have been a delay between the detection of a secret and the moment the corresponding incident was created in the customer's dashboard. The problem is now fixed, the faulty component was able to re-start and to process the backlog of messages.

Maintenance is over.

We deployed a fix today that addressed the check run issues. A brief database load increase was observed post-deployment with no impact on check run results. This incident is now resolved.

Between April 14, 2026 at 14:02 UTC and April 15, 2026 at 11:04 UTC, this status page was unavailable due to a misconfiguration on our end. During this period, we were unable to publish incident updates here, and you may not have received your usual notifications for any events that occurred within this window. We sincerely apologize for any confusion this may have caused. We are now backfilling all incidents that took place during this time to ensure the timeline accurately reflects what happened. If you were affected by an incident during this period and have questions, please don't hesitate to reach out to our support team.

Situation is back to normal, all public commits have been processed.

This incident has been resolved.

Performances issues have been resolved.

The incident has been fully mitigated. Root cause: hardware failure in our cloud provider's networking infrastructure. All services have been restored to normal operation.

This incident has been resolved.

We caught up the delay in real-time evaluation. Platform is back to normal operations

We experienced degraded performance on the dashboard and the public API from 10 AM UTC to 2:30 PM UTC. No data was lost.

The incident has been resolved. All real-time scanning is up to date, and check-runs are executed on time.

The incident has been resolved. Validity checks are now behaving as expected. Impact for the end users is limited: no data loss, faulty validity checks are being relaunched.

We have mitigated the issue and systems are back to normal operations

This incident has been resolved.

This incident has been resolved. All delayed tasks have been processed and GitGuardian services are operating normally. The issue affected async task processing on both US and EU platforms, impacting VCS historical scans (free tier and business customers), automatic severity detection, and public monitoring features. A fix was deployed and all queued tasks accumulated during the incident have now been completed.

This incident has been resolved.

Backlog of historical scans has been processed, everything is back to normal.

This incident has been resolved. A database performance optimization process caused automatic removal of some Slack integrations from GitGuardian Platform US. Affected customers will be notified and can reinstall their Slack integrations to restore functionality. All GitGuardian services are operating normally.

The incident is resolved and all systems are back to normal

The issue has been resolved. It was due to a recent update that caused a lot of activity in one of our main data tables. This unexpected surge affected our database performance, causing delays and 10 min of unavailability.

This incident is now resolved. Public monitoring is back to normal and our engineers have fully fixed the component that triggered the issue.

We experimented a DB outage that made the app partially unavailable. Incident was resolved at 12:45.

We experienced a service disruption affecting the GitGuardian Platform US dashboard and API, resulting in 9 minutes of unavailability. This issue occurred during the upgrade of a networking component within our infrastructure, which temporarily prevented the application from resolving the DNS names of various datastores, leading to connectivity failures. We apologize for any inconvenience caused and appreciate your understanding.