Due to a high load, a storage unit is currently suffering from a high load, so the SimpleHosting is in degraded mode.
Errors may be encountered on some instances during this issue.
Our technical team is currently working on fixing this issue, we will analyze and do the necessary maintenance operations.
Please do not launch any operation like rebooting your instance.
UPDATE 24/07 19h51 : issue is now finished, we will identify and correct a software-related bug.
UPDATE 25/07 11h30 : a new issue has been encoutered on another storage unit, impacting part of our Simplehosting instances on Paris/France datacenter. We work on the issue, will take appropriate actions to identify surely the bug and fix the bug in a sustainable way to avoid contention once the incident is finished.
UPDATE 11h55 : the faulty storage unit has been restarted, please do not launch any operation on your PaaS instance or your IaaS instance (like restart)
UPDATE 12h50 : the situation is now stable, tech team is analyzing and identifying the whole issue to find the potential bugs.
We are currently experiencing a load problem with Gandimail and are working on a solution.
EDIT : Still on going problem, we are on degraded mode.
EDIT : services is back to normal.
EDIT jun 21 05:14 PM CEST : As a result of a problem resulting from excessive load on about 15% of our email storage systems, some customers may have had difficulties accessing their mailbox, or may have experienced delays in delivery of their emails.
On 20 June, we detected an anomaly one some storage units and our teams took steps to stabilise the problem. Unfortunately, these measures were ineffective and resulted in disruption to the webmail service between 14:00 and 16:32.
Between 16:32 and 19:00 only 15% of the storage units showed signs of this anomalous behaviour (connection difficulties or slow delivery). On 21 June, from 9:30, we again began experiencing the issue on certain storage units. We subsequently were able to identify the root cause of the problem and implement the necessary corrective measures. The situation was stabilised around 13:45. There was no loss to any data as a result of this incident.