53 Seomonitor incidents · Temmuz 2025 — official updates, affected components, duration and resolution details.
AIO alıntı verileri Mobile için işlenmesine neden olan gecikmelere neden olan bir sorunu tespit ettik ve bir düzeltme uygulandı. Şu anda düzeltmeyi ve işleme kuyruğunu izliyoruz.
This incident has been solved and no data was lost.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Şu anda sihirbaz sırasında mevcut olmayan birincil cihaz olarak Mobile seçme seçeneği haline getiren bir sorunu tespit ettik ve düzeltme üzerinde çalışıyoruz.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
Şu anda günlük rütbeleri işlemede gecikmeler yaşıyoruz ve sırayla Viabil Puanlarını hesaplamaktayız. Nedeni araştırıyoruz ve en kısa sürede bir güncelleme sağlayacaktır.
Bu sorun için bir düzeltme üzerinde çalışmaya devam ediyoruz.
Resmî olay güncellemesinden otomatik olarak çevrilmiştir.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We are currently experiencing delays in processing the daily ranks and, in turn, calculating the Visibility Scores. We're investigating the cause and will provide an update as soon as possible.
This incident has been resolved. We're now back to the regular processing pace, and no data was lost.
We have identified an outage at our data storage provider affecting our servers, causing downtime across the platform. We are working on finding a solution until it's fixed on their side as well.
The systems are now back to normal functioning parameters, but we are still monitoring for any side effects.
This incident has been resolved. No data was lost.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We're currently experiencing an issue that delays article generation in the Content Writer section. We identified the root cause and are working on the fix.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.
We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.
This incident has been resolved.