Historique des pannes de Seomonitor

1. 29 juillet 2026 à 12:40 UTCmonitoring

   Nous avons identifié un problème causant des retards dans le traitement des données de citation AIO pour Mobile et avons mis en place une correction. Nous surveillons actuellement le correctif et la file d'attente de traitement.

2. 4 août 2026 à 09:46 UTCresolved

   Cet incident a été résolu et aucune donnée n'a été perdue.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 27 juillet 2026 à 16:51 UTCidentified

   Nous avons identifié un problème qui fait actuellement l'option de sélectionner Mobile comme l'appareil principal non disponible pendant le Magicien, et nous travaillons sur la correction.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 27 juillet 2026 à 14:03 UTCidentified

   Nous sommes actuellement confrontés à des retards dans le traitement des grades quotidiens et, à leur tour, dans le calcul des scores de visibilité. Nous enquêtons sur la cause et fournirons une mise à jour dès que possible.

2. 28 juillet 2026 à 07:28 UTCidentified

   Nous continuons de travailler sur une solution à ce problème.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 7 juillet 2026 à 13:43 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. 7 juillet 2026 à 13:58 UTCresolved

   This incident has been resolved.

1. 6 juillet 2026 à 07:06 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. 7 juillet 2026 à 09:24 UTCresolved

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

1. 27 juin 2026 à 18:59 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. 27 juin 2026 à 20:15 UTCmonitoring

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

3. 29 juin 2026 à 07:55 UTCresolved

   This incident has been resolved. No data was lost.

1. 18 juin 2026 à 14:27 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. 18 juin 2026 à 14:32 UTCresolved

   This incident has been resolved.

1. 17 juin 2026 à 11:05 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. 17 juin 2026 à 11:15 UTCresolved

   This incident has been resolved.

1. 15 juin 2026 à 16:07 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. 15 juin 2026 à 16:17 UTCresolved

   This incident has been resolved.

1. 15 juin 2026 à 15:34 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. 15 juin 2026 à 15:49 UTCresolved

   This incident has been resolved.

1. 15 juin 2026 à 14:13 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. 15 juin 2026 à 14:27 UTCresolved

   This incident has been resolved.

1. 15 juin 2026 à 13:32 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. 15 juin 2026 à 13:37 UTCresolved

   This incident has been resolved.

1. 11 juin 2026 à 08:09 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. 11 juin 2026 à 08:56 UTCresolved

   This incident has been resolved.

1. 10 juin 2026 à 16:47 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. 10 juin 2026 à 17:12 UTCresolved

   This incident has been resolved.

1. 13 mai 2026 à 14:22 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. 13 mai 2026 à 14:27 UTCresolved

   This incident has been resolved.

1. 12 mai 2026 à 20:26 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. 12 mai 2026 à 20:36 UTCresolved

   This incident has been resolved.

1. 12 mai 2026 à 14:13 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. 12 mai 2026 à 14:23 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 à 16:59 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. 11 mai 2026 à 17:04 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 à 16:21 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. 11 mai 2026 à 16:41 UTCresolved

   This incident has been resolved.

1. 11 mai 2026 à 14:22 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. 11 mai 2026 à 14:32 UTCresolved

   This incident has been resolved.