Historia awarii Seomonitor

1. 29 lipca 2026 12:40 UTCmonitoring

   Zidentyfikowaliśmy problem powodujący opóźnienia w przetwarzaniu danych AIO cytowanych dla Mobile i wdrożyliśmy rozwiązanie. Obecnie monitorujemy kolejkę poprawek i przetwarzania.

2. 4 sierpnia 2026 09:46 UTCresolved

   This incident has been solved and no data was lost.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 27 lipca 2026 16:51 UTCidentified

   Zidentyfikowaliśmy problem, który obecnie tworzy opcję wyboru Mobile jako podstawowego urządzenia niedostępnego podczas Wizard, i pracujemy nad naprawą.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 27 lipca 2026 14:03 UTCidentified

   Obecnie mamy opóźnienia w przetwarzaniu rankingów dziennych, a z kolei w obliczaniu wyników widoczności. Badamy przyczynę i dostarczymy jak najszybciej nowe informacje.

2. 28 lipca 2026 07:28 UTCidentified

   Kontynuujemy prace nad rozwiązaniem tego problemu.

Automatyczne tłumaczenie oficjalnej aktualizacji incydentu.

1. 7 lipca 2026 13:43 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 7 lipca 2026 13:58 UTCresolved

   This incident has been resolved.

1. 6 lipca 2026 07:06 UTCidentified

   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.

2. 7 lipca 2026 09:24 UTCresolved

   This incident has been resolved. We're now back to the regular processing pace, and no data was lost.

1. 27 czerwca 2026 18:59 UTCidentified

   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.

2. 27 czerwca 2026 20:15 UTCmonitoring

   The systems are now back to normal functioning parameters, but we are still monitoring for any side effects.

3. 29 czerwca 2026 07:55 UTCresolved

   This incident has been resolved. No data was lost.

1. 18 czerwca 2026 14:27 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 18 czerwca 2026 14:32 UTCresolved

   This incident has been resolved.

1. 17 czerwca 2026 11:05 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 17 czerwca 2026 11:15 UTCresolved

   This incident has been resolved.

1. 15 czerwca 2026 16:07 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 15 czerwca 2026 16:17 UTCresolved

   This incident has been resolved.

1. 15 czerwca 2026 15:34 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 15 czerwca 2026 15:49 UTCresolved

   This incident has been resolved.

1. 15 czerwca 2026 14:13 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 15 czerwca 2026 14:27 UTCresolved

   This incident has been resolved.

1. 15 czerwca 2026 13:32 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 15 czerwca 2026 13:37 UTCresolved

   This incident has been resolved.

1. 11 czerwca 2026 08:09 UTCidentified

   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.

2. 11 czerwca 2026 08:56 UTCresolved

   This incident has been resolved.

1. 10 czerwca 2026 16:47 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 10 czerwca 2026 17:12 UTCresolved

   This incident has been resolved.

1. 13 maja 2026 14:22 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 13 maja 2026 14:27 UTCresolved

   This incident has been resolved.

1. 12 maja 2026 20:26 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 12 maja 2026 20:36 UTCresolved

   This incident has been resolved.

1. 12 maja 2026 14:13 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 12 maja 2026 14:23 UTCresolved

   This incident has been resolved.

1. 11 maja 2026 16:59 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 11 maja 2026 17:04 UTCresolved

   This incident has been resolved.

1. 11 maja 2026 16:21 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 11 maja 2026 16:41 UTCresolved

   This incident has been resolved.

1. 11 maja 2026 14:22 UTCidentified

   We have identified an issue causing slow loading times (or downtime) across the platform, coming from an overload on the database entry point.

2. 11 maja 2026 14:32 UTCresolved

   This incident has been resolved.