Erreurs d'envoi de courriel transitoire
Pending
- resolved
Statut: Résolution résolue a été validée. Composants affectés Secrets Détection API (opérationnelle)
Traduit automatiquement depuis la mise à jour officielle de l'incident.
33 Gitguardian incidents · mars 2021 — official updates, affected components, duration and resolution details.
Statut: Résolution résolue a été validée. Composants affectés Secrets Détection API (opérationnelle)
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Statut : Le système résolu est de retour aux opérations normales. Composants affectés Webhooks (opérationnel) Détection secrète - Scan Check Run (opérationnel)
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Statut : résolu résolu. Suite aux optimisations des requêtes de base de données et à la réduction de la charge des tâches de fond bruyantes, aucune dégradation supplémentaire des performances n'a été observée. Les mesures ont été stables depuis le déploiement des correctifs. Composants affectés Détection secrète - Exécution de la vérification (opérationnelle)
Traduit automatiquement depuis la mise à jour officielle de l'incident.
État : résolu Cet incident est maintenant résolu. À la suite des corrections déployées par notre équipe, nous n'avons pas observé d'autres dégradations des performances, et les mesures sont stables depuis. Composants affectés Détection secrète - Exécution de la vérification (opérationnelle)
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous connaissons actuellement des performances dégradées dans notre pipeline public d'ingestion. Ceci est dû à une panne continue de l'API GitHub, que GitHub a reconnu sur sa propre page d'état. Notre équipe surveille activement la situation. Parce que la cause racine est du côté de GitHub, la résolution dépend de la restauration de leur API par GitHub. Notre pipeline est conçu pour reprendre automatiquement une fois GitHub récupéré, et nous fournirons d'autres mises à jour au fur et à mesure que la situation se développera.
GitHub a commencé à restaurer son API, et notre pipeline public d'ingestion se rétablit. L'ingestion d'événements en temps réel et la récupération du commit reprennent. Nous continuons de surveiller la situation afin de confirmer le rétablissement complet et de nous assurer que le pipeline est traité normalement. Nous fournirons une mise à jour finale une fois l'incident complètement résolu.
GitHub a restauré son API, et notre pipeline public d'ingestion a complètement récupéré. L'ingestion d'événements en temps réel et la récupération du commit fonctionnent à nouveau normalement. Cet incident a été causé par une panne d'API en amont de GitHub et est maintenant résolu. Merci de votre patience.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons actuellement sur un problème où certains clients peuvent éprouver des pics intermittents de lenteur lors du contrôle de traitement. Notre équipe a déployé une solution et surveille activement la situation. Nous fournirons des mises à jour à mesure que la situation progresse. Nous nous excusons pour le désagrément.
La correction a été déployée avec succès et la situation devrait être revenue à la normale. Désolé pour le dérangement.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
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.
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)
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.
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.
The fix has been deployed, the processing has resumed at full speed and the awaiting queue will be processing within the next hour.
This incident has been resolved.
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.
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.
We have identified a Network issue on Internal Repositories Monitoring that impacted Hook, Dashboard and API.
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
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.
This incident has been resolved.
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.
We are continuing to work on a fix for this issue.
This incident has been resolved.
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
Traduit automatiquement depuis la mise à jour officielle de l'incident.
This incident has been resolved.
A fix has been implemented and the systems are getting back to normal progressively.
Start of the issue.
We have an issue with our database. We are still evaluating the impact.
The incident has been resolved at 9h10 CEST.
The incident has been resolved.
We have detected a spike in errors on some endpoints of GitGuardian Internal Monitoring API. Our teams are investigating.