57 recorded Seomonitor incidents since July 2025, with official updates, affected components, duration and resolution information.
Our systems signalled an uptick in keyword rank drops since September 25, which we are currently investigating. During the investigation, the data will be unavailable from this date onwards.
We identified the root cause and implemented a solution that we're currently monitoring.
This incident has been closed. No data was lost.
We identified an issue causing delays in writing the AIO data. While we're working on the fix, users might experience temporary drops or fluctuations in AIO for the current day.
This incident has been resolved. No data was lost.
We are currently experiencing delays in processing the daily ranks, which are also affecting the Visibility Score calculation. We're investigating the cause and will provide an update as soon as possible.
This incident has been resolved.
We are currently experiencing delays in processing the daily ranks for both devices, which are also affecting the Visibility Score calculation. We're investigating the cause and will provide an update as soon as possible.
The issue is currently affecting only the Mobile. We are continuing to work on the fix.
This incident has been resolved. No data was lost.
We identified an issue causing delays in processing AIO citation data for Mobile and have implemented a fix. We are currently monitoring the fix and the processing queue.
This incident has been solved and no data was lost.
We identified an issue that's currently making the option to select Mobile as the primary device unavailable during the Wizard, and we are working on the fix.
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.
We are continuing to work on a fix for this issue.
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 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.
