Please advice on this Traceroute Command Result as IP seems blocked

[amitevm]

Hi,

Our domain was not working from last 3 days and Godaddy support was not helpful as usual. We did a traceroute and result seems like Godaddy blocked our domain. Can someone help me in understanding this traceroute result please? It will be very helpful.

Traceroute has started…

traceroute to 104.238.95.102 (104.238.95.102), 64 hops max, 72 byte packets

1  192.168.1.1 (192.168.1.1)  3.185 ms  1.260 ms  1.052 ms

2  abts-mp-dynamic-001.224.70.182.airtelbroadband.in (182.70.224.1)  54.701 ms

    203.101.83.37 (203.101.83.37)  55.339 ms  55.777 ms

3  182.79.146.4 (182.79.146.4)  112.969 ms  112.571 ms  133.060 ms

4  unknown.telstraglobal.net (202.127.73.141)  115.003 ms  116.497 ms  115.207 ms

5  i-92.sgcn-core01.telstraglobal.net (202.84.219.174)  122.858 ms  115.634 ms  116.531 ms

6  i-10551.tlot-core02.telstraglobal.net (202.84.141.17)  278.542 ms  276.461 ms  279.508 ms

7  i-91.tlot02.telstraglobal.net (202.40.149.177)  315.453 ms  292.743 ms  310.203 ms

8  reserved.metro.la.ipv4.godaddy.com (206.223.123.32)  291.484 ms  294.290 ms  424.632 ms

9  * * *

10  * * *

11  * * *

12  * * *

13  * * *

14  * * *

15  * * *

16  * * *

17  *

and this one

Traceroute has started…

traceroute to expertvillagemedia.com (104.238.95.102), 64 hops max, 72 byte packets

1  192.168.1.1 (192.168.1.1)  3.762 ms  1.996 ms  1.109 ms

2  abts-mp-dynamic-001.224.70.182.airtelbroadband.in (182.70.224.1)  55.760 ms

    203.101.83.37 (203.101.83.37)  57.155 ms  54.464 ms

3  182.79.146.4 (182.79.146.4)  115.003 ms  112.779 ms  113.761 ms

4  unknown.telstraglobal.net (202.127.73.141)  114.896 ms  114.948 ms  116.661 ms

5  i-92.sgcn-core01.telstraglobal.net (202.84.219.174)  122.384 ms  116.005 ms  117.513 ms

6  i-10551.tlot-core02.telstraglobal.net (202.84.141.17)  314.354 ms  278.374 ms  278.048 ms

7  i-91.tlot02.telstraglobal.net (202.40.149.177)  335.430 ms  328.087 ms *

8  reserved.metro.la.ipv4.godaddy.com (206.223.123.32)  291.777 ms  335.657 ms  409.969 ms

9  * * *

10  * * 148.72.32.16 (148.72.32.16)  310.780 ms

11  be38.trmc0215-01.ars.mgmt.phx3.gdg (184.168.0.69)  375.754 ms  408.625 ms  299.292 ms

12  ip-208-109-112-121.ip.secureserver.net (208.109.112.121)  299.885 ms  525.754 ms  377.903 ms

13  ip-104-238-95-102.ip.secureserver.net (104.238.95.102)  339.252 ms  408.799 ms  299.233 ms

[PL281]

@amitevm 

Just relying on a TraceRoute isn't the end all be all in trouble shooting something like this.

I want to first off confirm this is a VPS / Dedicated Server

Next - Assuming the answer is yes.... Can you get to WHM either directly or via the GoDaddy control panel for the server

If the answer is yes what URL / port it is using.... if the answer is no - then there is something else going on with your server that GoDaddy will need to look at from the account level

[amitevm]

Thanks for checking this. Yes its a VPS server and I am able to get in to WHM but it works sometimes and sometimes doesnt. At times its very hard to get in to WHM. Godaddy says its not at their end, its an issue at our end. Not sure about port though.

Is there any setting in WHM which can fix this?
One of the Godaddy support guy said our ISP is taking too long in transferring packets so its their issue. We need to contact our ISP and they can fix it.

But how such issue can arise when we havnt touched our server or any setting in dns? Any idea?

[PL281]

@amitevm 

I tried to get to the site and it timed out on getting a secure connection - The server does seem to have just popped up I would try a graceful restart on it / power cycle and see if it fixes it

[amitevm]

No we restarted it many times but it didnt fixed that issue. Godaddy support kept on saying that site is working fine at our end. Any other solution to fix this? 

[PL281 · Accepted solution]

@amitevm 

Ok - so the server is back up and running now - In WHM in the top corner what is the numbers you see in the top right corner (the load averages)

If this is high I would tell you that you need to look at the processes and perhaps you have a script that is running and using up all the processes

Nothing jumps out at me though