Gitguardian kesinti geçmişi

1. 16 Ekim 2026 16:05 UTCresolved

   Durum: Çözülmüş Karar Onaylandı. Etkilenen bileşenler Sır Tespit API (Operational)

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 8 Ekim 2026 07:07 UTCresolved

   Durum: Çözülen Sistem normal işlemlere geri döndü. Etkilenen bileşenler Webhooks (Operasyonel) Gizli Tespit - Scan Check Run (Operasyonel)

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 18 Ağustos 2026 11:34 UTCresolved

   Durum: Yeniden çözülmemiş Re. Veritabanı optimizasyonlarını takip edin ve gürültülü arka plan işlerinden yük azaltın, daha fazla performans bozulması gözlemlenmedi. Ölçümlerin dağıtımından bu yana ölçümler stabildir. Etkilenen bileşenler Gizli Tespit - Scan Check Run (Operational)

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 14 Ağustos 2026 13:46 UTCresolved

   Durum: Yeniden çözülmemiş Bu olay şimdi çözüldü. Ekibimiz tarafından dağıtılan düzeltmeler sonrasında, daha fazla performans bozulmasını gözlemledik ve metrikler o zamandan beri stabildi. Etkilenen bileşenler Gizli Tespit - Scan Check Run (Operational)

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 16 Temmuz 2026 23:18 UTCidentified

   Şu anda halk ingestion boru hattımızda bozulan performansı yaşıyoruz. Bu, GitHub API'sinin devam eden bir kesintiye uğramasına neden oluyor ve GitHub kendi durumu sayfasında kabul etti. Ekibimiz durumu aktif olarak izliyor. Çünkü kök nedeni GitHub'un tarafında, karar API'lerini geri yüklemesine bağlıdır. Boru hattımız otomatik olarak bir kez GitHub kurtarıyor ve durum geliştikçe daha fazla güncelleme sağlayacağız.

2. 17 Temmuz 2026 00:05 UTCmonitoring

   GitHub API'lerini restore etmeye başladı ve halk ingestion hattımız geri dönüyor. Real-time event ingestion ve retrieval yeniden yapılır. Tam kurtarmayı doğrulamak ve boru hattının normal olarak işlenmesini sağlamak için durumu izlemeye devam ediyoruz. Olay tamamen çözüldüğü bir son güncelleme sağlayacağız.

3. 17 Temmuz 2026 00:15 UTCresolved

   GitHub API'lerini restore etti ve halk ingestion hattımız tamamen iyileşti. Real-time event ingestion ve retrieval normal olarak tekrar çalışıyor. Bu olay bir upstream GitHub API'nin kesintisine neden oldu ve şimdi çözüldü. Sabrınız için teşekkür ederiz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 16 Temmuz 2026 10:34 UTCmonitoring

   Şu anda bazı müşterilerin işlem kontrolü çalışırken yavaşlık artışlarını deneyimleyebileceği bir sorunu araştırıyoruz. Takımımız bir düzeltme yaptı ve durumu aktif olarak izliyor. Durum ilerledikçe güncellemeler vereceğiz. Rahatlık için özür dileriz.

2. 16 Temmuz 2026 11:39 UTCresolved

   Düzeltme başarıyla yapıldı ve durum normale geri dönmeliydi. Rahatlık için özür dilerim.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 31 Mayıs 2026 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 Mayıs 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 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 Haziran 2026 13:24 UTCresolved

   This incident has been resolved.

1. 9 Haziran 2026 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 Haziran 2026 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 Haziran 2026 13:24 UTCresolved

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

1. 9 Haziran 2026 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 Haziran 2026 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 Haziran 2026 13:24 UTCresolved

   This incident has been resolved.

1. 9 Haziran 2026 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 Haziran 2026 13:24 UTCidentified

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

3. 9 Haziran 2026 13:24 UTCresolved

   This incident has been resolved.

1. 9 Haziran 2026 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 Haziran 2026 13:24 UTCresolved

   This incident has been resolved.

2. 9 Haziran 2026 13:24 UTCmonitoring

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

3. 9 Haziran 2026 13:24 UTCinvestigating

   Start of the issue.

1. 9 Haziran 2026 13:24 UTCinvestigating

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

2. 9 Haziran 2026 13:24 UTCresolved

   The incident has been resolved at 9h10 CEST.

1. 9 Haziran 2026 13:24 UTCresolved

   The incident has been resolved.

2. 9 Haziran 2026 13:24 UTCinvestigating

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