Störungsverlauf von Gitguardian

1. 16. Oktober 2026 um 16:05 UTCresolved

   Status: Resolved Resolution wurde validiert. Betroffene Komponenten Secrets Detection API (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 8. Oktober 2026 um 07:07 UTCresolved

   Status: Resolved System ist wieder im normalen Betrieb. Betroffene Komponenten Webhooks (Operational) Secret Detection - Scan Check Run (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 18. August 2026 um 11:34 UTCresolved

   Status: gelöst gelöst. Nach Datenbankabfrageoptimierungen und reduzierter Belastung durch verrauschte Hintergrundjobs wurde keine weitere Leistungsminderung beobachtet. Die Metriken sind seit dem Einsatz der Fixes stabil. Betroffene Komponenten Secret Detection - Scan Check Run (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. August 2026 um 13:46 UTCresolved

   Status: gelöst Dieser Vorfall ist nun gelöst. Nach den von unserem Team bereitgestellten Korrekturen haben wir keine weitere Leistungsminderung beobachtet, und die Metriken sind seitdem stabil. Betroffene Komponenten Secret Detection - Scan Check Run (Operational)

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 23:18 UTCidentified

   Wir erleben derzeit eine verschlechterte Leistung in unserer Pipeline zur öffentlichen Aufnahme. Dies wird durch einen anhaltenden Ausfall der GitHub-API verursacht, den GitHub auf seiner eigenen Statusseite bestätigt hat. Unser Team beobachtet die Situation aktiv. Da die Ursache auf GitHubs Seite liegt, hängt die Auflösung davon ab, dass GitHub seine API wiederherstellt. Unsere Pipeline ist so konzipiert, dass sie automatisch wieder aufgenommen wird, sobald sich GitHub erholt hat, und wir werden weitere Updates bereitstellen, wenn sich die Situation entwickelt.

2. 17. Juli 2026 um 00:05 UTCmonitoring

   GitHub hat damit begonnen, seine API wiederherzustellen, und unsere Public Ingestion Pipeline erholt sich. Event Ingestion und Commit Retrieval werden in Echtzeit fortgesetzt. Wir beobachten die Situation weiterhin, um die vollständige Wiederherstellung zu bestätigen und sicherzustellen, dass die Pipeline normal verarbeitet wird. Wir werden ein endgültiges Update bereitstellen, sobald der Vorfall vollständig behoben ist.

3. 17. Juli 2026 um 00:15 UTCresolved

   GitHub hat seine API wiederhergestellt und unsere Public Ingestion Pipeline hat sich vollständig erholt. Event Ingestion und Commit Retrieval in Echtzeit funktionieren wieder normal. Dieser Vorfall wurde durch einen Upstream-GitHub-API-Ausfall verursacht und ist nun behoben. Vielen Dank für Ihre Geduld.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 16. Juli 2026 um 10:34 UTCmonitoring

   Wir untersuchen derzeit ein Problem, bei dem einige Kunden bei der Verarbeitung von Prüfläufen intermittierende Spitzen der Langsamkeit erleben können. Unser Team hat eine Lösung bereitgestellt und überwacht die Situation aktiv. Wir werden Updates bereitstellen, wenn die Situation fortschreitet. Wir entschuldigen uns für die Unannehmlichkeiten.

2. 16. Juli 2026 um 11:39 UTCresolved

   Der Fix wurde erfolgreich eingesetzt und die Situation sollte wieder normal sein. Sorry für die Unannehmlichkeiten.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 31. Mai 2026 um 22:00 UTCresolved

   Status: Resolved 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.

1. 22. Mai 2026 um 14:33 UTCresolved

   Status: Resolved 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. Affected components Secret Detection - Scan Check Run (Operational)

1. 9. Juni 2026 um 13:24 UTCresolved

   Due to an availability issue of github.com Actions APIs (https://www.githubstatus.com/incidents/z3c6q056q332), some check runs have timed out on our side, resulting in a neutral status.

1. 9. Juni 2026 um 13:24 UTCidentified

   We are currently experiencing an incident on GPUB that started around yesterday, 10PM Monday 13th of March. An unexpected activity led to an overload of the queuing system of GPUB. We are deploying a fix to resume processing and catch up with the lag. In terms of data, some events will need to be reprocessed afterward, and we need to assess if some events cannot be processed again.

2. 9. Juni 2026 um 13:24 UTCmonitoring

   The fix has been deployed, the processing has resumed at full speed and the awaiting queue will be processing within the next hour.

3. 9. Juni 2026 um 13:24 UTCresolved

   This incident has been resolved.

1. 9. Juni 2026 um 13:24 UTCresolved

   Following a upgrade operation of a network component, GIM endpoints have been unavailable most of the time during this incident between 09:48 and 10:24 UTC. Fix has been deployed, situation is still under monitoring.

1. 9. Juni 2026 um 13:24 UTCresolved

   During deployment of GIM new version, The app was malfunctioning for a few minutes. The events that failed to evaluate during the incidents have been processed again.

1. 9. Juni 2026 um 13:24 UTCresolved

   We have identified a Network issue on Internal Repositories Monitoring that impacted Hook, Dashboard and API.

1. 9. Juni 2026 um 13:24 UTCresolved

   Following a DNS misconfiguration, GitGuardian Internal Monitoring platform was unavailable for about 20 minutes. Impact: No realtime scan (webhook): - GitHub events from recent GHE instances and Github.com were redelivered after the incident - Other events (BitBucket, GitLab) have been lost but we fully rescanned repositories when possible No API for secrets detection: CI and pre-commit hook failed. Dashboard was unavailable. Impacted entries: - api.gitguardian.com - dashboard.gitguardian.com - hook.gitguardian.com

1. 9. Juni 2026 um 13:24 UTCinvestigating

   Since October 17th, 2022, 12:28am (CEST) we are sending notifications by email for certain incidents already present in your workspace. We are currently investigating this incident.

2. 9. Juni 2026 um 13:24 UTCresolved

   This incident has been resolved.

1. 9. Juni 2026 um 13:24 UTCidentified

   On October 17th 2022, at around 5pm GMT, The queuing system in charge of handling Github Check Runs and Real Time Monitoring accumulated tasks that were slow to process and impacted the whole system. The size of the task queue started increasing for several hours straight, delaying processing for all customers. until it started decreasing again and went back to normal the day after at around 1am GMT, where processing time was back to normal. This event occurred again on October 18th 2022, at around 4pm GMT, but has been detected earlier and have been solved at 5pm GMT. Actions were taken to avoid this issue to happen again: It includes a better monitoring of those queues to improve time to detect an issue. The montoring of processing latencies on a end-user point of view will be improved too. More long terms actions are also planned, including implementing mechanisms to avoid accumulating latency in case of slow tasks accumulations.

2. 9. Juni 2026 um 13:24 UTCidentified

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

3. 9. Juni 2026 um 13:24 UTCresolved

   This incident has been resolved.

1. 9. Juni 2026 um 13:24 UTCresolved

   From Friday 9th Sept 6:30pm UTC to Monday 12th Sept 7:30 UTC, data collectors services were partially down due to an internal error. Github events have been correctly gathered into GitGuardian platform but processing of those events was down. There is no data loss but no alerts have been sent during this period of time. The processing has resumed correctly on Monday 12th Sept 7:30 UTC, the backdata from the week-end is being analyzed and should be caught up around 12pm. Update Monday 12th Sept. 10:25am UTC: Queues processing is slower than expected, ETA for catch up with the lag is postponed to at least to Tuesday morning (UTC), more precise ETA will be communicated when available. Update Monday 12th Sept. 2:05pm UTC: Slowness issues have been solved, queues processing has resumed at normal speed, ETA for catch up with the lag is Monday 12th Sept. 5:00pm UTC

1. 9. Juni 2026 um 13:24 UTCresolved

   This incident has been resolved.

2. 9. Juni 2026 um 13:24 UTCmonitoring

   A fix has been implemented and the systems are getting back to normal progressively.

3. 9. Juni 2026 um 13:24 UTCinvestigating

   Start of the issue.

1. 9. Juni 2026 um 13:24 UTCinvestigating

   We have an issue with our database. We are still evaluating the impact.

2. 9. Juni 2026 um 13:24 UTCresolved

   The incident has been resolved at 9h10 CEST.

1. 9. Juni 2026 um 13:24 UTCresolved

   The incident has been resolved.

2. 9. Juni 2026 um 13:24 UTCinvestigating

   We have detected a spike in errors on some endpoints of GitGuardian Internal Monitoring API. Our teams are investigating.