53 Seomonitor incidents · Juli 2025 — official updates, affected components, duration and resolution details.
Wir haben ein Problem festgestellt, das zu Verzögerungen bei der Verarbeitung von AIO-Zitatdaten für Mobile führt, und einen Fix implementiert. Wir überwachen derzeit den Fix und die Verarbeitungswarteschlange.
This incident has been solved and no data was lost.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir haben ein Problem festgestellt, das derzeit die Option, Mobile als primäres Gerät auszuwählen, während des Wizards nicht verfügbar macht, und wir arbeiten an der Korrektur.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir erleben derzeit Verzögerungen bei der Verarbeitung der täglichen Ränge und der Berechnung der Sichtbarkeitswerte. Wir untersuchen die Ursache und werden so schnell wie möglich ein Update bereitstellen.
Wir arbeiten weiter an einer Lösung für dieses Problem.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
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.