On Tuesday, 7 October, we experienced a series of serious incidents affecting some of the storage units in our Parisian datacenter. These incidents caused two interruptions in service for some of our customers, affecting both Simple Hosting instances and IaaS servers.

The combined effect of these interruptions represents the most serious hosting outage we've had in three years.

First and foremost, we want to apologize. We understand how disruptive this was for many of you, and we want to make it right.

In accordance with our Service Level Agreement, we will be issuing compensation to those whose services were unavailable.

Here's what happened:

On Tuesday, October 7, shortly before 8:00 p.m. Paris time (11:00 a.m. PDT), a storage unit in our Parisian datacenter housing a part of the disks of our IaaS servers and Simple Hosting instances became unresponsive.

At 8:00 p.m., after ruling out the most likely causes, we made the decision to switch to the backup equipment.

At 9:00 p.m., after one hour of importing data, the operation was interrupted, leading to a lengthy investigation that resulted in eventually falling back to the original storage unit. Our team, having determined the culprit to be the caching equipment, proceeded to change the disk of the write journal.

At 2:00 a.m., the storage unit whose disk had been replaced was rebooted.

Between 3:00 and 5:30 a.m., the recovery from a 6-hour outage caused a heavy overload, both on the network level and on the storage unit itself. The storage unit became unresponsive, and we were forced to restart the VMs in waves.

At 8:30 a.m., all the VMs and instances were once again functional, with a few exceptions which were handled manually.

We inspected our other storage units that were using the same model of disk, replacing one of them as a precaution.

At 12:30 p.m., we began investigating some slight misbehavior exhibited by the storage unit whose drive we had replaced as a precaution.

At 3:50 p.m., three virtual disks and a dozen VMs became unresponsive. We investigated and identified the cause, and proceeded to update the storage unit while our engineers worked on the fix.

Unfortunately, this update caused an unexpected automatic reboot, causing another interruption for the other Simple Hosting instances and IaaS servers on that storage unit.

By 4:15 p.m., all Simple Hosting instances were functional again, but there were problems remounting IaaS disks. By 5:30 p.m., 80% of the disks were accessible again, with the rest following by 5:45 p.m.

This latter incident lasted about two hours (4:00 to 6:00 p.m.). During this time, all hosting operations (creating, starting, or stopping servers) were queued.

Due to the large number of queued operations, it took until 7:30 p.m. for all of them to complete.

These incidents have seriously impacted the quality of our service, and for this we are truly sorry. We have already begun taking steps to minimize the consequences of such incidents in the future, and are working on tools to more accurately predict the risk of such hardware failures.

We are also working on a customer-facing tool for incident tracking which will be announced in the coming days. 

Thank you for using Gandi, and please accept our sincere apologies. If you have any questions, please do not hesitate to contact us.

The Gandi team






Usage statistics for CPU, disk (read/write) and network activity will be unavailable for several weeks for stability reasons.

Originally, our statistics tool was intended for IaaS servers. It was then adapted for use on instances, but the visualizations have not been entirely accurate. In fact, they weren't accurate at all. For this reason, usage statistics will no longer be available.

Over the last few months, our technical team has been working on a new system, which will replace the ones that have been present on PaaS/Simple Hosting and IaaS/VPS. These stats will be more detailed and precise in representing the real resource consumption on the instance. The new tool will also be considerably prettier, and we'll be able to build additional features on top of it.

The new statistics system will be released for PaaS instances in a few weeks. The IaaS version for VPS will follow shortly thereafter.


It's now possible to use GeoIP on Simple Hosting instances and on the Web Accelerator.

To do so, just obtain the 'X-Country-Code' from the HTTP header. The value returned will be a country code in the form 'EN', 'FR', 'US', 'GB', and so on, as defined by ISO 3166.

This functionality is useful for multilingual websites, because it allows you to adapt the language the site will be served in based on the country your visitor is located in.

The country code is determined based on a visitor's IP address. Bother IPv4 and IPv6 addresses are supported, and this feature is now available on all Gandi's datacenters.

For more information about using GeoIP on Gandi's Simple Hosting platform, see our support wiki.


As you probably know, RIPE, the organization in charge of delegating IP addresses in Europe, ended the distribution of new IPv4 blocks about a year ago.

The IPv6 protocol was developed in anticipation of this shortage, caused by an exponential increase in internet-connected internet-connected devices. Unfortunately, not all operators and manufacturers have followed recommended standards, and so not all the world's users will be ready for a full transition to IPv6 for several more years.

Due to this situation, the market value of IPv4 addresses is rising, and this is reflected in our prices.

But it's not your fault that certain providers haven't kept up with the rest of us, and so we don't think you should have to bear the consequences if you don't need to. This is why we are now allowing customers to run servers with no IPv4 addresses at all, which will lower your server costs by around 17%.

Anyone whose server doesn't require accessibility by everyone on the internet can benefit from this option (if you're just using a server for your own backup purposes, and your ISP supports IPv6, for example).

To create an IPv6-only sever, just deactivate the IPv4 option in the web form during the server creation. If you're using our hosting API, set the ip_version to 6 in the hosting.vm.create() method.

For more information on the technical aspects and advantages of our new boot procedure, check out our post at gandikitchen.net.

Update: We're on HackerNews! Join the discussion.



For our IaaS customers, we've added a nice little feature that allows you to let others give you credit, or to buy credit for other users.

We implemented this feature with three use cases in mind:

  • Many of the open source projects hosted by us can ask for support in the form of credits to help run their Gandi server
  • Sites hosting communities (games, cultural associations, non-profits, etc.), and would like to ask their members for credits
  • Small entrepreneurs who run servers for their customers can now ask their customers to pay directly for their servers
The system works by simply telling Gandi where the credit resources you order should be sent. Or, you can use a link with a Gandi account handle on your site, like this:
https://www.gandi.net/credit/buy?handle=XX123-GANDI


Page 1 2 3 4 5 6
Change the news ticker size