- Detected by Pingoru
- Jul 09, 2026, 10:32 AM UTC
- Resolved
- Jul 09, 2026, 12:35 PM UTC
- Duration
- 2h 3m
Affected: Search engine, members directories, members management
Timeline · 3 updates
-
investigating Jul 09, 2026, 10:32 AM UTC
A la suite d'une opération de maintenance programmée qui était censée être invisible pour les utilisateurs, les moteurs de recherche et annuaires ne sont plus accessibles sur la plateforme. Nous avons identifié le problème et le corrigeons au plus vite. --- Following a scheduled maintenance operation that was intended to be invisible to users, search engines and directories are no longer accessible on the platform. We have identified the problem and are fixing it as quickly as possible.
-
identified Jul 09, 2026, 10:36 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jul 09, 2026, 12:35 PM UTC
L'incident est résolu. --- The incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 07, 2026, 03:41 PM UTC
- Resolved
- Jul 07, 2026, 06:02 PM UTC
- Duration
- 2h 20m
Affected: Main applicationAPI
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Jun 23, 2026, 12:25 PM UTC
- Resolved
- Jun 23, 2026, 08:44 PM UTC
- Duration
- 8h 19m
Affected: Main application
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- May 13, 2026, 06:41 AM UTC
- Resolved
- May 13, 2026, 06:56 AM UTC
- Duration
- 15m
Affected: File storage
Timeline · 2 updates
-
investigating May 13, 2026, 06:41 AM UTC
We are currently investigating this issue.
-
resolved May 13, 2026, 06:56 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 12, 2026, 02:49 PM UTC
- Resolved
- May 12, 2026, 03:27 PM UTC
- Duration
- 37m
Affected: File storageWhaller 365 (document editor)Discussions
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Apr 29, 2026, 04:33 AM UTC
- Resolved
- Apr 29, 2026, 05:40 AM UTC
- Duration
- 1h 7m
Affected: Whaller 365 (document editor)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 06:35 AM UTC
- Resolved
- Apr 28, 2026, 07:41 AM UTC
- Duration
- 1h 5m
Affected: Whaller 365 (document editor)
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Nov 24, 2025, 08:36 AM UTC
- Resolved
- Nov 24, 2025, 08:15 PM UTC
- Duration
- 11h 38m
Affected: Whaller 365 (document editor)
Timeline · 2 updates
-
identified Nov 24, 2025, 08:36 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Nov 24, 2025, 08:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 21, 2025, 07:56 AM UTC
- Resolved
- Nov 21, 2025, 08:30 AM UTC
- Duration
- 34m
Affected: Main applicationAPI
Timeline · 4 updates
-
investigating Nov 21, 2025, 07:56 AM UTC
Nous rencontrons actuellement des difficultés techniques affectant l'authentification et la navigation sur la plateforme. Nos équipes techniques travaillent activement à la résolution de ce problème. Nous vous tiendrons informés de l'avancement et vous présenterons nos excuses pour la gêne occasionnée.
-
identified Nov 21, 2025, 08:23 AM UTC
Nous avons identifié le problème qui est lié aux serveurs de bases de données, nous corrigeons le problème.
-
monitoring Nov 21, 2025, 08:24 AM UTC
Le service est revenu à la normale, nous surveillons les services et nous vous ferons part d'un post mortem détaillé.
-
resolved Nov 21, 2025, 08:30 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2025, 08:30 AM UTC
- Resolved
- Nov 12, 2025, 11:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Nov 13, 2025, 08:30 AM UTC
Suite à une panne technique sur un disque hébergeant des données chez notre hébergeur, les accès à des fichiers ont pu être perturbés pour certains utilisateurs. L'incident a été résolu une fois le disque remis en service. L'incident chez notre hébergeur est disponible ici : https://hosted-private-cloud.status-ovhcloud.com/incidents/9j5l7jt7zgx8
Read the full incident report →
- Detected by Pingoru
- Nov 04, 2025, 10:52 AM UTC
- Resolved
- Nov 04, 2025, 09:00 AM UTC
- Duration
- —
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2025, 07:35 AM UTC
- Resolved
- Sep 18, 2025, 09:45 AM UTC
- Duration
- 2h 10m
Affected: Search engine, members directories, members management
Timeline · 2 updates
-
identified Sep 18, 2025, 07:35 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Sep 18, 2025, 09:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2025, 08:00 AM UTC
- Resolved
- Sep 01, 2025, 08:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 01, 2025, 04:20 PM UTC
Le 1er septembre 2025 entre 10:12 et 10:39, les utilisateurs d’une marque blanche hébergée sur Whaller ont pu connaître des problèmes d’authentification. Cela était lié à une indisponibilité du service de connexion suite à une perte de liaison avec notre cluster de données. Une fois la liaison rétablie, le service de connexion était de nouveau fonctionnel.
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2025, 04:09 PM UTC
- Resolved
- Aug 20, 2025, 01:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 20, 2025, 04:09 PM UTC
Afin d'ajouter une couche supplémentaire de sécurité sur l'authentification via SSO, nous avons effectué une mise à jour de l'application. Une erreur de configuration a rendu indisponible l'authentification pendant 30 minutes de 15:00 à 15:30, heure à laquelle nous avons déployé un correctif.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 07:49 AM UTC
- Resolved
- Aug 19, 2025, 12:53 PM UTC
- Duration
- 5h 3m
Affected: Search engine, members directories, members management
Timeline · 2 updates
-
identified Aug 19, 2025, 07:49 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Aug 19, 2025, 12:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2025, 10:35 AM UTC
- Resolved
- Jul 18, 2025, 10:48 AM UTC
- Duration
- 13m
Affected: Main application
Timeline · 2 updates
-
identified Jul 18, 2025, 10:35 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved Jul 18, 2025, 10:48 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2025, 08:09 AM UTC
- Resolved
- Jun 19, 2025, 08:49 AM UTC
- Duration
- 39m
Affected: Push server
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Jun 02, 2025, 03:07 PM UTC
- Resolved
- Jun 02, 2025, 02:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 02, 2025, 03:07 PM UTC
Certaines pages ont été inaccessibles pendant quelques instants suite à une modification de la configuration des notifications. Vous pouvez maintenant choisir si vous désirez recevoir le son des notifications du service Discussions.
Read the full incident report →
- Detected by Pingoru
- May 23, 2025, 10:20 AM UTC
- Resolved
- May 23, 2025, 11:00 AM UTC
- Duration
- 39m
Affected: Discussions
Timeline · 2 updates
-
identified May 23, 2025, 10:20 AM UTC
The issue has been identified and a fix is being implemented.
-
resolved May 23, 2025, 11:00 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 20, 2025, 08:30 AM UTC
- Resolved
- May 20, 2025, 12:07 PM UTC
- Duration
- 3h 36m
Affected: Discussions
Timeline · 4 updates
-
identified May 20, 2025, 08:30 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring May 20, 2025, 10:21 AM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring May 20, 2025, 11:59 AM UTC
We are continuing to monitor for any further issues.
-
resolved May 20, 2025, 12:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 09, 2025, 01:58 PM UTC
- Resolved
- May 09, 2025, 09:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved May 09, 2025, 01:58 PM UTC
La plateforme a été inaccessible quelques instants suite à une indisponibilité de notre cluster de données. L'équipe technique a résolu rapidement cette inaccessibilité.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 09:08 AM UTC
- Resolved
- Apr 23, 2025, 09:21 AM UTC
- Duration
- 12m
Affected: Discussions
Timeline · 2 updates
-
identified Apr 23, 2025, 09:08 AM UTC
Le module de messagerie instantanée est momentanément indisponible. Nous ajoutons des ressources aux machines concernées. Le service sera rétabli d'ici quelques minutes.
-
resolved Apr 23, 2025, 09:21 AM UTC
Le services "Discussions" est à nouveau disponible. Merci de votre compréhension.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 07:33 AM UTC
- Resolved
- Apr 23, 2025, 06:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 23, 2025, 07:33 AM UTC
Certains utilisateurs ont pu avoir des problèmes d'accès à Whaller, suite à une défaillance technique de notre hébergement. -- Ce ticket sera complété au fur et à mesure de nos investigations
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 06:53 AM UTC
- Resolved
- Apr 23, 2025, 06:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 23, 2025, 06:53 AM UTC
Nous subissons actuellement un incident sur le service principal de Whaller. La cause est identifiée et nos équipes sont en train de tout faire pour rétablir la situation.
Read the full incident report →
- Detected by Pingoru
- Mar 24, 2025, 09:33 AM UTC
- Resolved
- Mar 25, 2025, 02:51 PM UTC
- Duration
- 1d 5h
Affected: Discussions
Timeline · 3 updates
-
investigating Mar 24, 2025, 09:33 AM UTC
We are currently investigating this issue.
-
monitoring Mar 24, 2025, 10:31 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 25, 2025, 02:51 PM UTC
This incident has been resolved.
Read the full incident report →