53 Seomonitor incidents · julio de 2025 — official updates, affected components, duration and resolution details.
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.
Este incidente ha sido resuelto y no se perdieron datos.
Traducido automáticamente desde la actualización oficial del incidente.
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.
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.
Seguimos trabajando en una solución para esta cuestión.
Traducido automáticamente desde la actualización oficial del incidente.
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.