Due to a power outage in TH2 (Paris) some operators still experience some difficulties.

For this reason you can experience some difficulties to reach gandi through some networks.

Team are working to mitigate the problem.

Hosting operations are unavailable. Due to this you can't do any modification on your vm

(stop, start, ressources add, etc.)

Please accept our apologies for the inconvenience

We are encountering a paypal payment issue.

Please use if possible another payment method for the moment.

We are working on it.

We are sorry for the inconvenience.

update 10:52 CET: the incident is over, we are handling the blocked payments via this method.

We lost contact with 7 physical machines hosting PaaS/SimpleHosting instances (no impact on IaaS platform when we analyze the behavior).

Our technical team is currently analyzing deeply the issue and will fix it as soon as possible.

One of our technical team members from Luxembourg is on its way to the datacenter.

Update 19h50 : it seems that we lost a network unit (switch). To be confirmed once our system/network administrator is on site.

Update 20h30 : the network unit has been replaced, all is now working again. Postmortem analysis will be done asap.

Due to an equipment failure, simple hosting was in degraded mode form 15:52 to 19:00 CEST.

The failure wasn't detected by our monitoring. Our team will analyse the problem and do the necessary.

Please accept our apologies for the inconvience

There is a new network issue on our platform.

We will analyze and recover as soon as possible. Our technical team was already in the datacenter. It seems related/like to the same issue we got a few hours ago.

Please do not launch any operation in the meantime.

More information to come.

UPDATE : 18H30 : the network unit that has been isolated this morning was the source of this new issue. We apologize for this new issue and the inconvenience you encountered, again.

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.

On going network instabilities, update coming soon.

EDIT : situation back to normal, more information later.

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.

We apologise for any inconvenience caused.