We are experiencing diffculties on webmail.gandi.net.

Our teams are currently working on it.

UPDATE: Situation is back to normal since 17h30 (CET)

We apologise for any incovenience.

Some Gandimail equipment has an incident. Consultation of mailbox on a subset of our equipement is slow. 

Our team is working on fixing the issue.

Update 2014-02-16 09:34 (CET) : beginning of the incident

Update 2014-02-16 10:00 (CET) : our team resolve the technical problem.

A maintenance on our gandimail platform this will be held on 15/02/2014 from 7:00 p.m. to 0:00 UTC. 

.Disturbances may occur during this maintenance (lack of access to mail.gandi.net in IMAP/POP3).

Please accept our apologies for the inconvenience

Periodically, we have to do some things to the mail servers to keep them running smoothly. This is one of those ocasions, so tonight from 22h00 to 23h00 UTC, we will be working on the mail. 

We are not expecting any customer impact due to this maintenance, but we feel it is important to let our customers know what we are doing, just in case. 

An emergency maintenance will occur on the webmail tonight between 23:00 UTC and 1:00 UTC. Disconnections may happen. Please accept our apologies for the inconvenience.

0:18 UTC: Maintenance work successfully completed.

We will be doing maintenance on our webmail during the afternoon and evening of December 17, in order to update the Roundcube webmail version for all email users.

Between 15:00 and 19:00 Pacific time, webmail will not be accessible. Email delivery and email client access will continue normally.

We apologize for the inconvenience, and look forward to bringing you an updated version of our webmail client.

Update 2013-12-17 19:15 PST: The maintenance is complete.

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.

We will be performing major network upgrades to our backbone network in Paris during the night of 23-24 March 2013.  

The purpose of this work is to replace our current (aging) backbone network routers with newer generation equipment allowing for increased capacity, performance and resilience.  During this time, all Gandi services in Paris will experience brief periods of network unavailability and/or instability as the migration proceeds.

This activity will not impact the individual Gandi services themselves, but rather only the network connectivity between the internet and those services.  As a result, there will be no need for hosting customers to restart their IaaS or PaaS servers/instances.  Services in our Baltimore datacentre will not be directly affected by this maintenance, but some periods of routing instability and reconvergence may be experienced, though these will be far less prevalent than for the Paris services.

This migration will commence at 01:30 CET (00:30 GMT) on Sunday 24 March 2013, and we estimate between 10 and 15 minutes of major network outage during the initial migration, followed by a number of brief periods of network instability during the remainder of the migration.  The entire migration activity should last approximately 90 minutes, but no more than two hours.

Operations will be ended at 05:00 AM CET (04:00 AM GMT).

We apologise in advance for any inconvenience this may cause.

EDIT 03:08 AM CET : maintenance ended