Historial de interrupciones de Seomonitor

1. July 29, 2026 at 12:40 PM UTCmonitoring

   Identificamos un problema causando retrasos en el procesamiento de datos de citación AIO para Mobile y hemos implementado una solución. Actualmente estamos monitoreando la solución y la cola de procesamiento.

2. August 4, 2026 at 9:46 AM UTCresolved

   This incident has been solved and no data was lost.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 4:51 PM UTCidentified

   Identificamos un problema que está haciendo la opción de seleccionar Mobile como el dispositivo primario no disponible durante el Asistente, y estamos trabajando en la solución.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 2:03 PM UTCidentified

   Actualmente estamos experimentando retrasos en el procesamiento de las filas diarias y, a su vez, calculando las puntuaciones de visibilidad. Estamos investigando la causa y proporcionaremos una actualización lo antes posible.

2. July 28, 2026 at 7:28 AM UTCidentified

   Seguimos trabajando para solucionar este problema.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 7, 2026 at 1:43 PM 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. July 7, 2026 at 1:58 PM UTCresolved

   This incident has been resolved.

1. July 6, 2026 at 7:06 AM 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. July 7, 2026 at 9:24 AM UTCresolved

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

1. June 27, 2026 at 6:59 PM 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. June 27, 2026 at 8:15 PM UTCmonitoring

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

3. June 29, 2026 at 7:55 AM UTCresolved

   This incident has been resolved. No data was lost.

1. June 18, 2026 at 2:27 PM 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. June 18, 2026 at 2:32 PM UTCresolved

   This incident has been resolved.

1. June 17, 2026 at 11:05 AM 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. June 17, 2026 at 11:15 AM UTCresolved

   This incident has been resolved.

1. June 15, 2026 at 4:07 PM 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. June 15, 2026 at 4:17 PM UTCresolved

   This incident has been resolved.

1. June 15, 2026 at 3:34 PM 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. June 15, 2026 at 3:49 PM UTCresolved

   This incident has been resolved.

1. June 15, 2026 at 2:13 PM 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. June 15, 2026 at 2:27 PM UTCresolved

   This incident has been resolved.

1. June 15, 2026 at 1:32 PM 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. June 15, 2026 at 1:37 PM UTCresolved

   This incident has been resolved.

1. June 11, 2026 at 8:09 AM 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. June 11, 2026 at 8:56 AM UTCresolved

   This incident has been resolved.

1. June 10, 2026 at 4:47 PM 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. June 10, 2026 at 5:12 PM UTCresolved

   This incident has been resolved.

1. May 13, 2026 at 2:22 PM 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. May 13, 2026 at 2:27 PM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 8:26 PM 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. May 12, 2026 at 8:36 PM UTCresolved

   This incident has been resolved.

1. May 12, 2026 at 2:13 PM 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. May 12, 2026 at 2:23 PM UTCresolved

   This incident has been resolved.

1. May 11, 2026 at 4:59 PM 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. May 11, 2026 at 5:04 PM UTCresolved

   This incident has been resolved.

1. May 11, 2026 at 4:21 PM 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. May 11, 2026 at 4:41 PM UTCresolved

   This incident has been resolved.

1. May 11, 2026 at 2:22 PM 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. May 11, 2026 at 2:32 PM UTCresolved

   This incident has been resolved.