We noticed that requests to our Whois Service were failing with no or very slow response from our database server. Our investigations suggested that the database query in some cases was taking more than 10 seconds causing the CPU to go as high as 100% at certain intervals (reason for the intermittent response)
The Network Team identified this spike and was able to filter the WHOIS traffic by creating a Security rule. We are now seeing an increased performance and CPU reading is hovering around the 41% mark.
Our development team has currently hot-fixed this issue. On further investigating, there are still a couple of code changes required to fix this permanently.
Kindly bear with us and we shall get back to you with more information shortly.
We're seeing an elevated rate of errors and user reports describing Time Out errors while fetching the whois details. We're currently investigating and working with our Development Team to diagnose and fix this permanently.
The issue with the Whois Lookup service on OrderBox has now resurfaced.
Our development team is currently investigating the same and the issue should be fixed soon.
We are currently experiencing an issue with the WHOIS Lookup Service on OrderBox. Due to this incomplete WHOIS details are being fetched for thin TLDs via both the Web based as well as Port 43 based WHOIS. The following services will be affected in case your WHOIS servers point to OrderBox WHOIS servers:
1. Transfer of any domain name
2. Performing SSL verification while selecting a custom email address
3. WHOIS lookup service on Supersite
Our development team is working to get this issue resolved at the earliest.
Affected Services