GitGuardian Outage History

Started Oct 16, 2026, 01:10 PM UTC· resolved Oct 16, 2026, 02:05 PM UTC

1. investigating Oct 16, 2026, 01:10 PM UTC

   We are currently experiencing transient email sending errors from our provider. Email sending capabilities are impacted. Other means of notifications are not impacted.

2. monitoring Oct 16, 2026, 02:07 PM UTC

   We identified the reason our email provider prevented some of our email to be sent. We fixed the issue and and we are currently monitoring the situation.

3. resolved Oct 16, 2026, 04:05 PM UTC

   Resolution has been validated.

Read the full incident report →

Started Oct 07, 2026, 04:39 PM UTC· resolved Oct 07, 2026, 05:36 PM UTC

1. investigating Oct 07, 2026, 04:39 PM UTC

   Check-runs are slower than usual and some of them are timing out. Real-time scanning of events is delayed, secrets may appear in your dashboard with a delay up to 2 hours

2. monitoring Oct 07, 2026, 05:36 PM UTC

   No more delays for check runs are expected. We are still processing backlog for real-time.

3. resolved Oct 08, 2026, 07:07 AM UTC

   System is back to normal operations.

Read the full incident report →

Started Aug 18, 2026, 11:11 AM UTC· resolved Aug 18, 2026, 11:34 AM UTC

1. investigating Aug 18, 2026, 11:11 AM UTC

   We've identified renewed performance degradation affecting check run and realtime processing, with some customers experiencing delays of up to approximately 30 minutes. We've identified contributing factors related to database load and have deployed mitigations to reduce impact. We're continuing to investigate further improvements and will share updates as we have more information.

2. resolved Aug 18, 2026, 11:34 AM UTC

   Resolved. Following database query optimizations and reduced load from noisy background jobs, no further performance degradation has been observed. Metrics have been stable since deployment of the fixes.

Read the full incident report →

Started Aug 11, 2026, 05:38 PM UTC· resolved Aug 12, 2026, 07:24 AM UTC

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.

Read the full incident report →

Started Jun 04, 2026, 07:03 AM UTC· resolved Jun 04, 2026, 07:23 AM UTC

1. investigating Jun 04, 2026, 07:03 AM UTC

   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.

2. resolved Jun 04, 2026, 07:23 AM UTC

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

Read the full incident report →

Started May 31, 2026, 10:00 PM UTC· resolved May 31, 2026, 10:00 PM UTC

1. resolved Jun 01, 2026, 11:43 AM UTC

   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.

Read the full incident report →

Started May 22, 2026, 08:36 AM UTC· resolved May 22, 2026, 10:21 AM UTC

1. identified May 22, 2026, 08:36 AM UTC

   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.

2. identified May 22, 2026, 10:21 AM UTC

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

3. resolved May 22, 2026, 10:21 AM UTC

   Maintenance is over.

Read the full incident report →

Started May 21, 2026, 03:41 PM UTC· resolved May 22, 2026, 02:33 PM UTC

1. monitoring May 21, 2026, 03:41 PM UTC

   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.

2. resolved May 22, 2026, 02:33 PM UTC

   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.

Read the full incident report →

Started Apr 15, 2026, 11:04 AM UTC· resolved Apr 15, 2026, 11:04 AM UTC

1. resolved Apr 15, 2026, 12:35 PM UTC

   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.

Read the full incident report →

Started Mar 18, 2026, 09:04 AM UTC· resolved Mar 18, 2026, 09:28 AM UTC

1. monitoring Mar 18, 2026, 09:04 AM UTC

   We identified delay in real-time scanning of public commits since 7:30 AM (UTC). We deployed a fix and the delay is decreasing. At most, the delay was of 1 hour and 45 minutes. No data has been lost.

2. resolved Mar 18, 2026, 09:28 AM UTC

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

Read the full incident report →

Started Mar 12, 2026, 10:10 AM UTC· resolved Mar 12, 2026, 01:41 PM UTC

1. investigating Mar 12, 2026, 10:10 AM UTC

   We are currently investigating this issue.

2. investigating Mar 12, 2026, 11:13 AM UTC

   We are continuing to investigate this issue.

3. resolved Mar 12, 2026, 01:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 12, 2026, 11:40 AM UTC· resolved Feb 12, 2026, 12:48 PM UTC

1. investigating Feb 12, 2026, 11:40 AM UTC

   GitGuardian is investigating reports of performance issues affecting GitGuardian Platform US (Dashboard, Secrets Detection API, Webhooks). Users may experience delays in realtime events processing and slower response times. We are working to resolve this issue. Next update in 10 hours.

2. resolved Feb 12, 2026, 12:48 PM UTC

   Performances issues have been resolved.

Read the full incident report →

Started Feb 11, 2026, 11:40 PM UTC· resolved Feb 11, 2026, 11:40 PM UTC

1. identified Feb 11, 2026, 09:22 PM UTC

   Following an incident on our cloud provider, our explore feature is not available in public monitoring. We monitor the situation and take measures to reduce the impact.

2. identified Feb 11, 2026, 09:56 PM UTC

   We are waiting for updates from our cloud provider on their status page: https://bare-metal-servers.status-ovhcloud.com/incidents/l18zzyfpnxq2

3. monitoring Feb 11, 2026, 10:36 PM UTC

   Cloud provider incident is resolved. Our services are restarting and will then catch up with the real-time. Explore feature is available again but with a delay of 2 hours which should resolve in a few hours.

4. resolved Feb 12, 2026, 07:47 AM UTC

   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.

Read the full incident report →

Started Feb 06, 2026, 04:17 PM UTC· resolved Feb 06, 2026, 06:22 PM UTC

1. investigating Feb 06, 2026, 04:17 PM UTC

   We are currently investigating errors on our webhooks and delays in check-runs evaluation

2. monitoring Feb 06, 2026, 05:31 PM UTC

   We identified and resolved a traffic spike that exceeded our scaling capacity. Scaling parameters have been adjusted to prevent recurrence. - Check-runs: Operating normally with no delays - Webhooks: Restored and under active monitoring We apologize for the disruption and will continue monitoring system performance closely.

3. resolved Feb 06, 2026, 06:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 20, 2026, 11:28 AM UTC· resolved Jan 20, 2026, 11:49 AM UTC

1. monitoring Jan 20, 2026, 11:28 AM UTC

   We experienced a delay of at most 30 minutes in real-time events handling. We implemented a fix and are monitoring the situation.

2. resolved Jan 20, 2026, 11:49 AM UTC

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

Read the full incident report →

Started Jan 19, 2026, 02:30 PM UTC· resolved Jan 19, 2026, 02:30 PM UTC

1. resolved Jan 20, 2026, 08:25 AM UTC

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

Read the full incident report →

Started Jan 14, 2026, 01:00 AM UTC· resolved Jan 14, 2026, 11:43 AM UTC

1. identified Jan 14, 2026, 07:36 AM UTC

   Several components of our platform are experiencing delays and partial outage

2. identified Jan 14, 2026, 07:36 AM UTC

   We are currently investigating a performance issue on our platform. The problem has been identified, we are taking mitigation actions

3. monitoring Jan 14, 2026, 08:34 AM UTC

   A fix has been implemented and the backlog is being handled. We expect real-time to catch up in about an hour.

4. resolved Jan 14, 2026, 11:43 AM UTC

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

Read the full incident report →

Started Dec 15, 2025, 04:48 PM UTC· resolved Dec 15, 2025, 06:04 PM UTC

1. investigating Dec 15, 2025, 04:48 PM UTC

   We are investigating an issue with secrets validity checks on our platform. Some of our validity checks are currently failing for unknown reason. We will keep you updated as our engineers make progress on the issue.

2. identified Dec 15, 2025, 05:39 PM UTC

   The origin of the incident has been identified and we are taking mitigating actions.

3. resolved Dec 15, 2025, 06:04 PM UTC

   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.

Read the full incident report →

Started Nov 19, 2025, 04:31 PM UTC· resolved Nov 19, 2025, 05:30 PM UTC

1. identified Nov 19, 2025, 04:31 PM UTC

   We have identified an issue with the explore feature. Users may encounter failures when running queries. We are currently performing corrective actions to restore full functionality.

2. resolved Nov 19, 2025, 05:30 PM UTC

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

Read the full incident report →

Started Nov 04, 2025, 03:34 PM UTC· resolved Nov 04, 2025, 04:42 PM UTC

1. investigating Nov 04, 2025, 03:34 PM UTC

   GitGuardian is investigating instabilities affecting Realtime Secret Detection on the US Platform. Users may experience failures in realtime event deliveries. All types of incoming events are affected. We are working to resolve this issue. Next update in 10 hours.

2. monitoring Nov 04, 2025, 04:02 PM UTC

   A fix has been implemented and GitGuardian is monitoring the results. Realtime Secret Detection on the US Platform is operating normally. GitGuardian will recover any missed events from the affected period. Next update in 24 hours.

3. resolved Nov 04, 2025, 04:42 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 03, 2025, 02:24 PM UTC· resolved Nov 03, 2025, 05:37 PM UTC

1. investigating Nov 03, 2025, 02:24 PM UTC

   GitGuardian is investigating an issue affecting free tier VCS scans and automatic severity detection on the US platform. Users may experience scans queued but not completing. We are working to resolve this issue. Next update in 10 hours.

2. monitoring Nov 03, 2025, 04:52 PM UTC

   A fix has been implemented for the processing issue affecting both US and EU platforms. During our investigation, we discovered the issue also impacted the EU platform and Public Monitoring features. The async workers are now processing the backlog of queued tasks, including VCS historical scans (free tier and business customers), automatic severity detection, and public monitoring. GitGuardian is monitoring progress as the system catches up with accumulated delays. Next update in 8 hours.

3. resolved Nov 03, 2025, 05:37 PM UTC

   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.

Read the full incident report →

Started Oct 20, 2025, 09:56 AM UTC· resolved Oct 21, 2025, 07:26 AM UTC

1. monitoring Oct 20, 2025, 09:56 AM UTC

   GitGuardian has identified an issue affecting Integrations and Webhooks due to an external AWS infrastructure incident. Users may experience delays in real-time event processing from Jira Cloud, Confluence Cloud, and Slack integrations, as well as webhook delivery delays. Resolution is dependent on AWS addressing their infrastructure issue. Next update in 2 hours.

2. monitoring Oct 20, 2025, 12:46 PM UTC

   GitGuardian services have recovered and Integrations and Webhooks are operating normally. While the underlying AWS infrastructure incident continues, our systems are processing events as expected. Please note that some notifications from Jira Cloud, Confluence Cloud, and Slack integrations may not have been delivered during the affected period. We are monitoring the situation until AWS fully resolves their issue. Next update in 24 hours.

3. monitoring Oct 20, 2025, 04:10 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Oct 21, 2025, 07:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 10, 2025, 08:03 PM UTC· resolved Oct 10, 2025, 10:54 PM UTC

1. investigating Oct 10, 2025, 08:03 PM UTC

   We are currently experiencing delays in historical scan processing for Git repositories. Our team is actively investigating the issue and working to restore normal processing as quickly as possible. We will provide updates as we make progress.

2. investigating Oct 10, 2025, 08:04 PM UTC

   We are continuing to investigate this issue.

3. identified Oct 10, 2025, 09:09 PM UTC

   The issue has been identified and corrective measures are being prepared.

4. monitoring Oct 10, 2025, 09:44 PM UTC

   Historical scan processing for Git repositories has been restored and is actively catching up on the backlog. We are closely monitoring system performance and progress to ensure timely completion. Further updates will be provided as needed.

5. resolved Oct 10, 2025, 10:54 PM UTC

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

Read the full incident report →