Histórico de interrupções do Seomonitor

1. 29 Gouere 2026 da 12:40 UTCmonitoring

   Identificamos um problema que causa atraso no processamento de dados de citação de AIO para Mobile e implementamos uma correção. Estamos atualmente monitorando a correção e a fila de processamento.

2. 4 Eost 2026 da 09:46 UTCresolved

   This incident has been solved and no data was lost.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 16:51 UTCidentified

   Identificou-se um problema que atualmente está fazendo a opção de selecionar Mobile como o dispositivo primário indisponível durante o Assistente, e estamos trabalhando na correção.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 14:03 UTCidentified

   Atualmente, estamos passando por atrasos no processamento das fileiras diárias e, por sua vez, no cálculo das pontuações de visibilidade. Estamos a investigar a causa e vamos fazer uma actualização o mais depressa possível.

2. 28 Gouere 2026 da 07:28 UTCidentified

   Continuamos trabalhando em uma solução para esse problema.

Traduzido automaticamente da atualização oficial do incidente.

1. 7 Gouere 2026 da 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 Gouere 2026 da 13:58 UTCresolved

   This incident has been resolved.

1. 6 Gouere 2026 da 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 Gouere 2026 da 09:24 UTCresolved

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

1. 27 Mezheven 2026 da 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 Mezheven 2026 da 20:15 UTCmonitoring

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

3. 29 Mezheven 2026 da 07:55 UTCresolved

   This incident has been resolved. No data was lost.

1. 18 Mezheven 2026 da 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 Mezheven 2026 da 14:32 UTCresolved

   This incident has been resolved.

1. 17 Mezheven 2026 da 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 Mezheven 2026 da 11:15 UTCresolved

   This incident has been resolved.

1. 15 Mezheven 2026 da 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 Mezheven 2026 da 16:17 UTCresolved

   This incident has been resolved.

1. 15 Mezheven 2026 da 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 Mezheven 2026 da 15:49 UTCresolved

   This incident has been resolved.

1. 15 Mezheven 2026 da 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 Mezheven 2026 da 14:27 UTCresolved

   This incident has been resolved.

1. 15 Mezheven 2026 da 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 Mezheven 2026 da 13:37 UTCresolved

   This incident has been resolved.

1. 11 Mezheven 2026 da 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 Mezheven 2026 da 08:56 UTCresolved

   This incident has been resolved.

1. 10 Mezheven 2026 da 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 Mezheven 2026 da 17:12 UTCresolved

   This incident has been resolved.

1. 13 Mae 2026 da 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 Mae 2026 da 14:27 UTCresolved

   This incident has been resolved.

1. 12 Mae 2026 da 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 Mae 2026 da 20:36 UTCresolved

   This incident has been resolved.

1. 12 Mae 2026 da 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 Mae 2026 da 14:23 UTCresolved

   This incident has been resolved.

1. 11 Mae 2026 da 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 Mae 2026 da 17:04 UTCresolved

   This incident has been resolved.

1. 11 Mae 2026 da 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 Mae 2026 da 16:41 UTCresolved

   This incident has been resolved.

1. 11 Mae 2026 da 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 Mae 2026 da 14:32 UTCresolved

   This incident has been resolved.