LockSelf Outage History

LockSelf is up right now

Pingoru has recorded 45 incidents for LockSelf: 16 in the last 12 months and 1 in the last 90 days.

Source: lockself.statuspage.io

45incidents recorded
16last 12 months
1last 90 days
6 hourstypical duration
Incidents per month
036AprMayJunJulAugSepOctNov0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov0%
Pingoru began tracking LockSelf in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202653 of 744 (0%)
June 2026645 of 720 (6%)
July 202610 of 744 (0%)
August 202611 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 744 (0%)
November 202600 of 1 (0%)

Incidents, newest first

Minor August 5, 2026 Indisponibilité de service 1h 18m LockSelf Cloud Public

Started Aug 05, 2026, 01:23 PM UTC· resolved Aug 05, 2026, 02:41 PM UTC

  1. investigating Aug 05, 2026, 01:23 PM UTC

    We are currently investigating this issue.

  2. monitoring Aug 05, 2026, 02:40 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 05, 2026, 02:41 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 30, 2026 Problème d'accès via certains réseaux 23h 54m LockSelf Cloud Privé - Région eu-west-2, LockSelf Cloud Privé - Région SecNumCloud

Started Jul 30, 2026, 12:41 PM UTC· resolved Jul 31, 2026, 12:35 PM UTC

  1. investigating Jul 30, 2026, 12:41 PM UTC

    Nous avons identifié un incident affectant l'accès au service depuis certains réseaux. Nos équipes travaillent actuellement à en déterminer l'origine. Nous revenons vers vous dès que nous avons plus d'informations.

  2. investigating Jul 30, 2026, 02:04 PM UTC

    Si vous disposez d'une connectivité redondante (double fibre, multi-WAN, SD-WAN, ou tout autre lien de secours (4G/5G par exemple)) le fait de basculer sur le lien alternatif permet généralement de contourner le problème, l'incident ne touchant que certains réseaux. En parallèle, nous poursuivons nos investigations afin de déterminer l'origine du problème.

  3. resolved Jul 31, 2026, 12:35 PM UTC

    Les perturbations réseau qui affectaient l'accès au service chez certains opérateurs sont terminées. Le service est de nouveau pleinement accessible. Nous reviendrons prochainement vers vous avec des éléments plus détaillés sur l'origine de ces perturbations

Read the full incident report →

Minor June 30, 2026 Service Degradation 50m LockSelf Cloud Public

Started Jun 30, 2026, 12:48 PM UTC· resolved Jun 30, 2026, 01:38 PM UTC

  1. investigating Jun 30, 2026, 12:48 PM UTC

    We have identified degraded response times on our public cloud platform. Our teams are currently investigating the root cause of this slowdown. We will update this page as soon as more information becomes available.

  2. monitoring Jun 30, 2026, 01:07 PM UTC

    The root cause of the degraded response times has been identified and a fix has been applied. Performance has returned to normal. We are continuing to monitor the service to confirm stability before closing this incident.

  3. monitoring Jun 30, 2026, 01:20 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 30, 2026, 01:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 24, 2026 Indisponibilité de service - Région SecNumCloud 19h 26m LockSelf Cloud Privé - Région SecNumCloud

Started Jun 24, 2026, 07:43 PM UTC· resolved Jun 25, 2026, 03:10 PM UTC

  1. investigating Jun 24, 2026, 07:43 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 24, 2026, 07:47 PM UTC

    A new incident has occurred on our SecNumCloud zone. The issue appears to originate from our infrastructure provider, Outscale. We are awaiting their response and analysis. Our disaster recovery procedures (DRP) are being activated on this zone as well. We will share an update as soon as we have more information. Thank you for your patience.

  3. investigating Jun 24, 2026, 08:09 PM UTC

    We currently have no update from our infrastructure provider, Outscale, regarding the ongoing incidents on both the SecNumCloud and eu-west-2 regions. No communication has been received at this time. Our disaster recovery procedures (DRP) remain active on both zones while we await their response. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we have more information. Thank you for your continued patience.

  4. investigating Jun 24, 2026, 08:30 PM UTC

    We still have no new information from our infrastructure provider, Outscale. Our disaster recovery procedures (DRP) remain active on both zones. Our teams are continuing to monitor the situation closely. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we have more information. Thank you for your continued patience.

  5. investigating Jun 24, 2026, 08:58 PM UTC

    We still have no new information from Outscale. Our disaster recovery procedures (DRP) remain fully active. Our teams are on standby and monitoring the situation continuously. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we hear from them. Thank you for your continued patience.

  6. investigating Jun 24, 2026, 09:22 PM UTC

    We still have no new information from Outscale. The incident remains ongoing on both zones. Our disaster recovery procedures (DRP) remain fully active. Our teams are continuing to monitor the situation. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we hear from them. Thank you for your continued patience.

  7. investigating Jun 24, 2026, 09:47 PM UTC

    Outscale has reported improvements on this region. We are waiting for further confirmation before switching our instances back from DRP mode to production. We will keep you informed of any progress. You can follow Outscale's incident status here: https://status.outscale.com Thank you for your continued patience. We will provide a new update as soon as the situation evolves.

  8. monitoring Jun 24, 2026, 10:08 PM UTC

    We are pleased to inform you that all customers on the SecNumCloud region have been successfully switched back to their production instances. Our teams are actively monitoring the situation to ensure full stability. You can follow Outscale's incident status here: https://status.outscale.com We will provide a new update as soon as the situation evolves. Thank you for your continued patience.

  9. resolved Jun 25, 2026, 03:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 24, 2026 Indisponibilité de service - Région eu-west-2 21h 14m LockSelf Cloud Privé - Région eu-west-2

Started Jun 24, 2026, 05:55 PM UTC· resolved Jun 25, 2026, 03:10 PM UTC

  1. investigating Jun 24, 2026, 05:55 PM UTC

    We are currently investigating this issue.

  2. investigating Jun 24, 2026, 06:05 PM UTC

    We are currently experiencing production issues caused by a scheduled maintenance operation conducted by our infrastructure provider, Outscale. Their teams are actively investigating the situation on their end. In the meantime, we have activated our disaster recovery procedures (DRP) to mitigate the impact as much as possible. We will keep you updated as soon as we receive further information from Outscale. We apologize for the inconvenience and thank you for your patience.

  3. investigating Jun 24, 2026, 06:24 PM UTC

    We still have no update from our infrastructure provider, Outscale, regarding the ongoing maintenance and its impact on our services. On our end, our disaster recovery procedures (DRP) are being progressively activated. We are doing everything we can to restore normal service as quickly as possible. We will share a new update as soon as we have more information. Thank you for your continued patience.

  4. identified Jun 24, 2026, 06:43 PM UTC

    Our infrastructure provider, Outscale, has officially declared an incident on their side. No additional information is available at this time — their investigation is still ongoing. On our end, our disaster recovery procedures (DRP) are continuing to be progressively deployed. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we have more information. Thank you for your continued patience.

  5. identified Jun 24, 2026, 07:04 PM UTC

    Outscale has provided a first update at 9:02 PM UTC+1. Their teams are still actively working on resolving the incident. No ETA has been communicated at this time. Our disaster recovery procedures (DRP) remain active on our end. You can follow Outscale's incident status here: https://status.outscale.com We will keep you updated as the situation evolves. Thank you for your patience.

  6. identified Jun 24, 2026, 07:23 PM UTC

    No new update from Outscale at this time. Their teams are continuing to investigate and work towards resolving the incident. Our disaster recovery procedures (DRP) remain active on our end while we await further information. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we hear from them. Thank you for your continued patience.

  7. identified Jun 24, 2026, 07:48 PM UTC

    No update from Outscale regarding the incident on the eu-west-2 region at this time. Their teams are still working on resolving the issue. Our disaster recovery procedures (DRP) remain active on our end. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we hear from them. Thank you for your continued patience.

  8. identified Jun 24, 2026, 08:09 PM UTC

    We currently have no update from our infrastructure provider, Outscale, regarding the ongoing incidents on both the SecNumCloud and eu-west-2 regions. No communication has been received at this time. Our disaster recovery procedures (DRP) remain active on both zones while we await their response. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we have more information. Thank you for your continued patience.

  9. identified Jun 24, 2026, 08:30 PM UTC

    We still have no new information from our infrastructure provider, Outscale. Our disaster recovery procedures (DRP) remain active on both zones. Our teams are continuing to monitor the situation closely. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we have more information. Thank you for your continued patience.

  10. identified Jun 24, 2026, 08:58 PM UTC

    We still have no new information from Outscale. Our disaster recovery procedures (DRP) remain fully active. Our teams are on standby and monitoring the situation continuously. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we hear from them. Thank you for your continued patience.

  11. identified Jun 24, 2026, 09:22 PM UTC

    We still have no new information from Outscale. The incident remains ongoing on both zones. Our disaster recovery procedures (DRP) remain fully active. Our teams are continuing to monitor the situation. You can follow Outscale's incident status here: https://status.outscale.com We will share a new update as soon as we hear from them. Thank you for your continued patience.

  12. identified Jun 24, 2026, 09:47 PM UTC

    No new information from Outscale on this region at this time. Our DRP remains fully active. We will come back to you as soon as we have more information. You can follow Outscale's incident status here: https://status.outscale.com Thank you for your continued patience. We will provide a new update as soon as the situation evolves.

  13. identified Jun 24, 2026, 09:54 PM UTC

    Outscale has provided an update. The incident appears to be related to environmental conditions within their infrastructure. Their teams are actively working to resolve the situation. Our DRP remains fully active. We will come back to you as soon as we have more information. You can follow Outscale's incident status here: https://status.outscale.com Thank you for your continued patience. We will provide a new update as soon as the situation evolves.

  14. identified Jun 24, 2026, 10:31 PM UTC

    No new information from Outscale on the eu-west-2 region at this time. The incident remains ongoing. Our DRP stays fully active. You can follow Outscale's incident status here: https://status.outscale.com We will come back to you as soon as we have more information. Thank you for your continued patience.

  15. identified Jun 24, 2026, 10:31 PM UTC

    No new information from Outscale on the eu-west-2 region at this time. The incident remains ongoing. Our DRP stays fully active. You can follow Outscale's incident status here: https://status.outscale.com We will come back to you as soon as we have more information. Thank you for your continued patience.

  16. identified Jun 24, 2026, 11:02 PM UTC

    Outscale has provided an update. They have successfully stabilized the impacted point of presence within the data center. Network and backbone services have been restarted and stabilized. Their teams are now working on restoring storage systems on the affected physical resources. Our DRP remains fully active while we await full restoration. We will come back to you as soon as we have more information. You can follow Outscale's incident status here: https://status.outscale.com Thank you for your continued patience. We will provide a new update as soon as the situation evolves.

  17. identified Jun 24, 2026, 11:47 PM UTC

    No new information from Outscale at this time. Their teams are continuing to work on restoring storage systems on the affected infrastructure. Our DRP remains fully active. We will come back to you as soon as we have more information. You can follow Outscale's incident status here: https://status.outscale.com Thank you for your continued patience. We will provide a new update as soon as the situation evolves.

  18. identified Jun 25, 2026, 12:21 AM UTC

    We still have no new information from Outscale. The incident remains ongoing. Our DRP stays fully active while we await further updates. You can follow Outscale's incident status here: https://status.outscale.com We will come back to you as soon as we have more information. Thank you for your continued patience.

  19. monitoring Jun 25, 2026, 12:46 AM UTC

    Outscale has successfully restored part of the affected storage infrastructure. Their teams are continuing to work on restoring the remaining storage systems and will provide updates as they progress. On our end, we are progressively switching our DRP environments back to production. We will come back to you as soon as we have more information. You can follow Outscale's incident status here: https://status.outscale.com Thank you for your continued patience. We will provide a new update as soon as the situation evolves.

  20. monitoring Jun 25, 2026, 01:00 AM UTC

    Outscale has fully restored the affected storage infrastructure. Pending operations related to the orchestrator have also been processed. Their teams are now working on restoring compute services ahead of a full API restoration and return to normal operations. On our end, we are continuing to switch our environments back to production. You can follow Outscale's incident status here: https://status.outscale.com Thank you for your continued patience. We will provide a new update as soon as the situation evolves.

  21. monitoring Jun 25, 2026, 01:50 AM UTC

    Outscale has fully restored the API services, which are now operational. Their teams are completing the final recovery actions. On our end, we are switching back to production environments as our servers come back up and are confirmed stable. You can follow Outscale's incident status here: https://status.outscale.com We will provide a final update once all environments are fully restored. Thank you for your continued patience.

  22. monitoring Jun 25, 2026, 02:51 AM UTC

    Outscale has confirmed that the incident affecting the eu-west-2 region has been resolved. As part of the recovery process, all virtual machines impacted by the incident have been marked as stopped and can now be safely restarted. On our end, not all production servers are back up yet. We are switching back from DRP to production environments progressively, as each server is confirmed operational by Outscale. You can follow Outscale's incident status here: https://status.outscale.com We will provide a final update once all our environments are fully restored. Thank you for your continued patience.

  23. resolved Jun 25, 2026, 03:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 11, 2026 Indisponibilité de service 1h 15m LockSelf Cloud Public

Started Jun 11, 2026, 05:57 AM UTC· resolved Jun 11, 2026, 07:13 AM UTC

  1. investigating Jun 11, 2026, 05:57 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 11, 2026, 06:50 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 11, 2026, 07:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 2, 2026 Indisponibilité de service 21h 51m LockSelf Cloud Privé - Région eu-west-2

Started Jun 02, 2026, 11:31 AM UTC· resolved Jun 03, 2026, 09:22 AM UTC

  1. investigating Jun 02, 2026, 11:59 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 02, 2026, 12:12 PM UTC

    L'ensemble des instances de secours pour les environnements impactés ont été deployés.

  3. identified Jun 02, 2026, 02:38 PM UTC

    Un incident chez notre hébergeur de production nous a amené à déployer les environnements de secours. Le service est opérationnel et sera rebasculé sur les instances de production dès la fin de l'incident. Les modifications effectuées sur les environnements de secours ne seront pas répercutées sur les environnements de production à la fin de l'incident.

  4. monitoring Jun 03, 2026, 12:22 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Jun 03, 2026, 09:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 28, 2026 Indisponibilité de service 19m LockSelf Cloud Public

Started May 28, 2026, 03:51 PM UTC· resolved May 28, 2026, 04:10 PM UTC

  1. investigating May 28, 2026, 03:51 PM UTC

    We are currently investigating this issue.

  2. monitoring May 28, 2026, 04:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 28, 2026, 04:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 26, 2026 Indisponibilité de service 5m LockSelf Cloud Public

Started May 26, 2026, 08:24 AM UTC· resolved May 26, 2026, 08:30 AM UTC

  1. investigating May 26, 2026, 08:24 AM UTC

    We are currently investigating this issue.

  2. investigating May 26, 2026, 08:25 AM UTC

    We are continuing to investigate this issue.

  3. monitoring May 26, 2026, 08:27 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 26, 2026, 08:30 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical May 22, 2026 Indisponibilité de service 11m LockSelf Cloud Public

Started May 22, 2026, 09:12 AM UTC· resolved May 22, 2026, 09:24 AM UTC

  1. investigating May 22, 2026, 09:12 AM UTC

    We are currently investigating this issue.

  2. identified May 22, 2026, 09:17 AM UTC

    Incident majeur chez notre fournisseur d'infrastructure Scaleway.

  3. resolved May 22, 2026, 09:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 21, 2026 Problème d'accès à LockSelf pour certains clients 19m LockSelf Cloud Privé - Région eu-west-2

Started May 21, 2026, 04:14 PM UTC· resolved May 21, 2026, 04:34 PM UTC

  1. investigating May 21, 2026, 04:14 PM UTC

    We are currently investigating this issue.

  2. monitoring May 21, 2026, 04:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 21, 2026, 04:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor May 4, 2026 Indisponibilité de service 1h 37m LockSelf Cloud Public

Started May 04, 2026, 12:43 PM UTC· resolved May 04, 2026, 02:21 PM UTC

  1. investigating May 04, 2026, 12:43 PM UTC

    We are currently investigating this issue.

  2. monitoring May 04, 2026, 02:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring May 04, 2026, 02:15 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 04, 2026, 02:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical January 29, 2026 Indisponibilité de service 1h 16m LockSelf Cloud Privé - Région SecNumCloud

Started Jan 29, 2026, 10:42 AM UTC· resolved Jan 29, 2026, 11:58 AM UTC

  1. investigating Jan 29, 2026, 10:42 AM UTC

    Un incident est survenu sur certains environnements Cloud Privé. Nous étudions actuellement ce problème.

  2. monitoring Jan 29, 2026, 11:01 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jan 29, 2026, 11:04 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jan 29, 2026, 11:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 8, 2025 Dégradation des fonctionnalités nécessitants l'envoi d'un email 21m LockSelf Cloud Public

Started Dec 08, 2025, 08:54 AM UTC· resolved Dec 08, 2025, 09:15 AM UTC

  1. investigating Dec 08, 2025, 08:54 AM UTC

    We are currently investigating this issue.

  2. monitoring Dec 08, 2025, 09:06 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 08, 2025, 09:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 2, 2025 Problème d'accès à LockSelf pour certains clients 3h 5m LockSelf Cloud Privé - Région eu-west-2

Started Dec 02, 2025, 05:59 PM UTC· resolved Dec 02, 2025, 09:04 PM UTC

  1. investigating Dec 02, 2025, 05:59 PM UTC

    We are currently investigating this issue.

  2. resolved Dec 02, 2025, 09:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 23, 2025 Erreur lors d'action générant un envoie d'email 10h 20m LockSelf Cloud Public, LockSelf Cloud Privé - Région eu-west-2

Started Oct 23, 2025, 12:34 PM UTC· resolved Oct 23, 2025, 10:54 PM UTC

  1. investigating Oct 23, 2025, 12:34 PM UTC

    L'ensemble des clients de notre offre cloud public ainsi que les clients cloud privés avec l'option SMTP ou l'option lockself-cloud sont impactés.

  2. identified Oct 23, 2025, 12:36 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Oct 23, 2025, 10:54 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 21, 2025 Problème d'accès à LockSelf pour certains clients 24m LockSelf Cloud Privé - Région SecNumCloud

Started Oct 21, 2025, 04:15 PM UTC· resolved Oct 21, 2025, 04:39 PM UTC

  1. investigating Oct 21, 2025, 04:15 PM UTC

    We are currently investigating this issue.

  2. resolved Oct 21, 2025, 04:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 25, 2025 Problème d'accès à LockSelf pour certains clients 30m LockSelf Cloud Privé - Région eu-west-2

Started Sep 25, 2025, 01:50 PM UTC· resolved Sep 25, 2025, 02:20 PM UTC

  1. investigating Sep 25, 2025, 01:50 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 25, 2025, 02:08 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Sep 25, 2025, 02:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Sep 25, 2025, 02:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 28, 2025 Problème d'accès à LockSelf 2h 10m LockSelf Cloud Public

Started Aug 28, 2025, 03:32 PM UTC· resolved Aug 28, 2025, 05:43 PM UTC

  1. investigating Aug 28, 2025, 03:32 PM UTC

    We are currently investigating this issue.

  2. identified Aug 28, 2025, 03:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 28, 2025, 04:23 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 28, 2025, 05:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2025 Ralentissement sur le Cloud Public 35m LockSelf Cloud Public

Started Aug 21, 2025, 07:57 AM UTC· resolved Aug 21, 2025, 08:32 AM UTC

  1. investigating Aug 21, 2025, 07:57 AM UTC

    Des ralentissements sont actuellement en cours sur notre offre d'hébergement Cloud Public.

  2. monitoring Aug 21, 2025, 08:15 AM UTC

    Un fix a été implémenté, nous n'observons plus de ralentissement. Nous continuons le monitoring pour s'assurer de la bonne disponibilité du Cloud Public.

  3. resolved Aug 21, 2025, 08:32 AM UTC

    Nous n'observons plus de ralentissement.

Read the full incident report →

Minor July 28, 2025 Dégradation des fonctionnalités liées aux fichiers 21h 59m LockSelf Cloud Privé - Région eu-west-2, LockSelf Cloud Privé - Région SecNumCloud

Started Jul 28, 2025, 11:00 AM UTC· resolved Jul 29, 2025, 09:00 AM UTC

  1. investigating Jul 28, 2025, 11:00 AM UTC

    Notre fournisseur Outscale rencontre des dégradations de son service OOS. Les fonctionnalités de LockTransfer et LockFiles peuvent être impactées. Il est possible de suivre l'avancée de la résolution de l'incident sur: https://status.outscale.com/incidents/cv0b5vtxq2jv .

  2. monitoring Jul 28, 2025, 11:40 AM UTC

    Notre fournisseur Outscale a identifié et corrigé l'incident rencontré sur son service OOS.

  3. resolved Jul 29, 2025, 09:00 AM UTC

    Notre fournisseur Outscale a cloturé l'incident.

Read the full incident report →

Major May 12, 2025 Consultation de mots de passe 2h 6m LockSelf Cloud Public

Started May 12, 2025, 09:02 PM UTC· resolved May 12, 2025, 11:08 PM UTC

  1. investigating May 12, 2025, 09:02 PM UTC

    Un incident est en cours rendant impossible la consultation de mots de passe. Le problème est identifié et nos équipes sont en cours de résolution.

  2. resolved May 12, 2025, 11:08 PM UTC

    L'incident est terminé.

Read the full incident report →

Major April 7, 2025 Problème d'accès à LockSelf pour certains utilisateurs 8h 39m LockSelf Cloud Privé - Région eu-west-2

Started Apr 07, 2025, 02:16 PM UTC· resolved Apr 07, 2025, 10:55 PM UTC

  1. investigating Apr 07, 2025, 02:16 PM UTC

    Un problème d'accès aux serveurs LockSelf pour certains utilisateurs est en cours sur la zone eu-west-2. Nos équipes sont en relation avec les équipes de notre hébergeur Outscale afin de déterminer la cause du problème.

  2. investigating Apr 07, 2025, 03:09 PM UTC

    Nous restons en étroite collaboration avec les équipes d'Outscale afin de rétablir le service. Suivi des investigations : https://status.outscale.com/

  3. investigating Apr 07, 2025, 04:12 PM UTC

    Les investigations sont toujours en cours par les équipes Outscale. Suivi des investigations : https://status.outscale.com/

  4. monitoring Apr 07, 2025, 08:07 PM UTC

    Les équipes d'Outscale ont identifié et semblent avoir résolu le problème. Nous continuons le monitoring pour s'assurer de la bonne disponibilité des environnements impactés.

  5. resolved Apr 07, 2025, 10:55 PM UTC

    L'incident a été résolu par notre hébergeur Outscale. Nos équipes ont vérifié que tous les environnements LockSelf impactés sont bien rétablis.

Read the full incident report →

Major March 10, 2025 Problème d'accès à LockSelf 1h 30m LockSelf Cloud Public

Started Mar 10, 2025, 04:12 PM UTC· resolved Mar 10, 2025, 05:42 PM UTC

  1. identified Mar 10, 2025, 04:12 PM UTC

    Un incident lié à une instabilité réseau chez notre fournisseur d'infrastructure est en cours chez notre fournisseur : https://status.scaleway.com/incidents/162zw5zd9x8r

  2. monitoring Mar 10, 2025, 05:22 PM UTC

    Un incident lié à une instabilité réseau chez notre fournisseur d'infrastructure est en cours chez notre fournisseur : https://status.scaleway.com/incidents/162zw5zd9x8r

  3. resolved Mar 10, 2025, 05:42 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 5, 2025 Ralentissement sur le Cloud Public 19m LockSelf Cloud Public

Started Feb 05, 2025, 09:33 AM UTC· resolved Feb 05, 2025, 09:52 AM UTC

  1. investigating Feb 05, 2025, 09:33 AM UTC

    Des ralentissements sont actuellement en cours sur notre offre d'hébergement Cloud Public.

  2. monitoring Feb 05, 2025, 09:37 AM UTC

    Un correctif a été implémenté et est en cours de vérification. Nous n'observons plus de ralentissement.

  3. resolved Feb 05, 2025, 09:52 AM UTC

    L'incident est résolu.

Read the full incident report →