Connectivity issue with multiple Registries

At around 12:02 GMT, we noticed that the Registry response time was spiking intermittently. This caused an increase in the response time of domain management API calls while the Check Availability calls were timing out intermittently.

Most of these issues were with Verisign Namestore TLDs, Afilias SRS and .GDN TLD. Other TLDs like .com, .net, .org, .info etc were working seamlessly. .GDN Registry confirmed there is some intermittent connectivity issue at their end and Verisign stated that we might be dropping too many connections.

While further debugging, we purged all the Afilias SRS, Verisign NamestoreTLDs and GDN connections. This helped us fix the issue temporarily.

Further investigation revealed that the server making Registry connections had some processes running at the backend which surged the CPU utilization. This was unwanted and post termination everything was back up. 

Kindly revert through support channel in case of any concerns.

The connectivity issue with multiple registries like Verisign, CentralNIC, Uniregistry, etc have been fixed and the check availability is also working.

However we are still monitoring the connections for any further disruptions.

Please reach out to the Support team, in case you face any issues.

We are currently facing connectivity issues with multiple registries such as Verisign, CentralNIC, Uniregistry, etc., due to which you may not be able to complete actions that require registry connections such as domain name registrations, renewals, and transfers. Check availability might also not work for these registries.

We are working with the registries to get this issue resolved at the earliest.

This connectivity issue will have no impact on the resolution/working of your already registered domains.