53 Seomonitor incidents · juli 2025 — official updates, affected components, duration and resolution details.
Vi identificerede et problem forårsager forsinkelser i behandling AIO citation data for Mobile og har gennemført en rettelse. Vi overvåger i øjeblikket fix og behandling kø.
This incident has been solved and no data was lost.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi identificerede et problem, der i øjeblikket gør mulighed for at vælge Mobile som den primære enhed utilgængelig under guiden, og vi arbejder på fix.
Automatisk oversat fra den officielle hændelsesopdatering.
Vi oplever i øjeblikket forsinkelser i behandlingen af de daglige rækker og til gengæld beregning af synlighedsresultaterne. Vi undersøger sagen og vil give en opdatering så hurtigt som muligt.
Vi fortsætter med at arbejde på en løsning på dette problem.
Automatisk oversat fra den officielle hændelsesopdatering.
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.