The pace is accelerating for new generic top-level domain (gTLD) releases. In case you haven't heard, the Donuts registry is offering 7 new extensions for sunrise right now:

Another batch of 7 is queued up for December 10, at 8am Pacific time:

Add to this list the gTLDs .menu and شبكة (aka .shabaka, or "web" in Arabic), depending on whether we get the data we need from the registry in time. 


December 11 is a good day for gTLDs too, with the Sunrise of .tattoo and .sexy. Should be interesting, but where is .nice? 


We are working on getting .kiwi ready for  December 16, and will notify you here about others as the information becomes available. Stay tuned!

Simple Hosting instances located in our Baltimore data center only may be currently experiencing issues. Our technical staff is investigating the issue. Please do not perform any operations on your instance in the meantime.

This post will be updated as the situation evolves.

Update 00:51:20 CET:

A member of our technical staff is currently onsite in Baltimore to address the problem.

Update 01:35:13 CET:

The issue has been resolved. Services should be now operating normally.

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

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

The incident of November 11th is part of a series of incidents over the past few weeks caused by the gateway units, which provide Internet access for the Simple Hosting instances.
The Simple Hosting platform has experienced a number of different issues, principally with the gateway equipment, which seems to be the weakest link in the architecture. It is suject to:
  • HSRP instability causing short interruptions in connectivity,
  • Saturation of NAT translation tables as a result of a number of factors, including DDoS and Customer Activity, 
  • High CPU usage under certain conditions.
What will Gandi do to fix the situation, replace this gateway and improve the Simple Hosting product ?
  • Replace the network equipment which provides the gateway to Internet for the Simple Hosting product with more powerful appliances, and greater numbers of units (scaling). The new units will better handle the current load and will support the growth of Simple Hosting instances in the near future,
  • Set up a deeper level of monitoring to better detect technical problems,
  • Implement advanced monitoring to detect abuse from specific instances and enable quicker reaction from our technical team for handling these abuses before they impact the quality of services for all other customers.
We apologise for the inconvenience, and please be assured that our teams are endeavouring to correct these issues in the shortest possible time.

We experienced a hardware fault on routing equipment on the simple hosting platform.
Below is a chronology of the various events:
- 20:06 UTC : CPU load on the equipment shows significant increase.
- 20:06 UTC : Equipment is running at 100% CPU for no apparent reason, and has failed to respond to commands.
- 20:08 UTC : We made the decision to migrate to secondary equipment.
- 20:08 UTC : The secondary equipement exhibits the same symptoms as the primary, so traffic was not transferred.
- 20:09 UTC : Debugging underway as to ascertain the cause of the problem.
- 20:26 UTC : Migration to the now-stabilised secondary equipment.
- 20:27 UTC : Service returned to nominal operation.
- 22:42 UTC : Following this incident, there was a secondary effect on DNS resolution; the Simple Hosting instances failing to resolve DNS since 20:06 UTC.  the problem is now resolved.
- The network equipment used for the Gateways for this service are visibly showing signs of weakness.  An in-depth analysis of the anomaly and behaviour of the primary unit is underway (likely due to a memory fault).  We are currently running on the secondary gateway for the moment.

This year, as you probably know, will see the arrival of the first set of new top-level domain name (TLD) extensions. Over 500 new registries are forming, which collectively will service over 1500 of these additional extensions. This huge expansion in the name space of domains will not be possible without creating some branding conflicts, and this is where the Trademark Clearinghouse (TMCH) comes in. 


What is the TMCH?

The Trademark Clearinghouse is an institution that provides centralized brand management.

ICANN has anticipated the need for a single point of contact for all trade and service mark registrations, and has created the TMCH for this purpose. It is managed by IBM, who is taking care of the technical side, and Deloitte, who will handle the validation of registered trademarks. Together, they will enable the the holders of valid, registered trademarks to gain priority in the registration of domains that are comprised of these marks. Companies registering with TMCH can defensively register domains (during the sunrise period for a given TLD) or be notified of registrations that match registered trademarks during the 90-day window following the sunrise.


Who can register a trademark?

Domain names containing registered trademarks can be registered any natural or legal person with proven rights to a given brand, either regional, national or international. We have found that there are limitations to the use of a trademark as a domain name, however. For example, brands containing a period (.) or special marks can't be parsed by the DNS system and will not be accepted. Spaces and other punctuation marks included in a brand may be replaced by a dash, and if the mark contains the @ or & characters they can be translated into the language corresponding to the jurisdiction of the brand (e.g. "at" and "and" in English).


How can Gandi help?

Gandi Corporate Services can manage the registration of your mark, and send you any alerts you may get.

If you want to become a Gandi Corporate Services customer, you can! To use the TMCH service, just subscribe for a one-year term by sending your request to or


Once you are subscribed, we will help you register your trademarks in the TMCH and monitor alerts regarding potential infringing registrations. Our prices for this service are as follows:


  • Registration of a brand for one year: $250 (including the $145 fee assessed by TMCH), and $250 for renewal (which is useful in protecting your mark for as-yet-unreleased extensions).
  • Registration of a brand for three years: $690 (including the $435 TMCH fee)
  • Registration of a brand for five years: $1090 (including $725 TMCH fee)


ICANN estimates that the first extensions will be openly available by June, so a 3-year or even 5-year registration makes sense, especially considering that the rate of introduction may be as high as 1000 new extensions a year. We offer volume pricing for large customers.


If you are interested in our offer or want specific details, please contact us at

Our database system will have a maintenance tonight.
Therefore all update of the DNS zones updates will be delayed betweeen 00:00 CEST and 02:00 CEST.
We apologize for the inconvenience.

A network unit currently encountered an issue.


Our technical team is on  site and analyzing the issue.


They will do the necessary maintenance operations in the next minutes.

This issue was resolved by the network team within minutes of this message being posted. 

Page   1 2 346 47 4872 73 74
Change the news ticker size