Is GitGuardian down?

We will be performing scheduled database maintenance on Jun 4, 2026 from 9:00 to 9:30 CET on EU platform tenant. During this window, you may experience: No access to the dashboard Delayed secret scanning results— scans will be queued and processed once maintenance is complete Delayed event processing— security events may take longer than usual to appear in your dashboard No data will be lost. All scans and events will be processed automatically after the maintenance window. We apologize for any inconvenience and appreciate your patience.

Maintenance is done. All services are back to normal operational mode.

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.

We will be performing scheduled database maintenance on May 22, 2026 from 11:00 to 11:15 CET (09:00–09:15 UTC) on EU platform tenant. During this window, you may experience: No access to the dashboard Delayed secret scanning results— scans will be queued and processed once maintenance is complete Delayed event processing— security events may take longer than usual to appear in your dashboard No data will be lost. All scans and events will be processed automatically after the maintenance window. We apologize for any inconvenience and appreciate your patience.

We are continuing to work on a fix for this issue.

Maintenance is over.

We are currently investigating an issue where some customers may experience intermittent spikes of slowness when processing check runs. Our team is actively monitoring the situation and working on a fix. We will provide updates as the situation progresses. We apologise for the inconvenience.

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.