We had some severe lag spikes over the last 5 hours and I once contacted the hosting support about it via web chat about 2 hours ago. I got disconnected in the middle and let it be since the lag was gone by then. What I got out of this was the best way to monitor the lag. So when the lag escalated just now I made the right records and called to the USA support this time to get a reply. While I was on the phone with the support guys I recorded these traceroute figures from my server TO my home provider. So this represents the network inside the provider that should normally reply within a bracket of 2ms, but instead I got this here:
1 ip-184-168-65-251.ip.secureserver.net (184.108.40.206) 220.524 ms 220.521 ms 220.731 ms
2 * * *
3 * * *
4 * * ip-208-109-113-169.ip.secureserver.net (220.127.116.11) 33.251 ms
5 ip-97-74-252-21.ip.secureserver.net (18.104.22.168) 31.845 ms * *
6 * scd-edge-01.inet.qwest.net (22.214.171.124) 31.792 ms *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
The stars mean that the server did not reply in time to the request.
From my home I got some replies within an acceptable 200ms, but again some severe spikes within a 2500ms frame, with 350 being considered severe.
So the support there woke up some technicians and they are working on the issue. I figured waiting until they are done is the best solution.
Given that they are in panic-mode already it does not really help to create a trouble-ticket.
On the good side, the server itself never had any delay so far. It is also very likely that some of the lag that occurred over the recent days was caused by the same issue that godaddy has now, and whatever they have to fix will also fix that.
Also, I have NO idea how long this will take. It’s their lifeblood though I would think they do that fast.