Since the servers have changed I and my visitors are having random periods were we cannot access site. It just says The connection to the server was reset while the page was loading. I cannot access via mine or the x10 hosting domain so heres my results when site is inaccessible,
Ping my domain
Pinging ovgyclan.com [74.86.116.190] with 32 bytes of data:
Reply from 74.86.116.190: bytes=32 time=163ms TTL=49
Reply from 74.86.116.190: bytes=32 time=137ms TTL=49
Reply from 74.86.116.190: bytes=32 time=142ms TTL=49
Reply from 74.86.116.190: bytes=32 time=140ms TTL=49
Ping statistics for 74.86.116.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 137ms, Maximum = 163ms, Average = 145ms
ping ovgyclan.x10hosting.com
Pinging ovgyclan.com [74.86.116.190] with 32 bytes of data:
Reply from 74.86.116.190: bytes=32 time=163ms TTL=49
Reply from 74.86.116.190: bytes=32 time=137ms TTL=49
Reply from 74.86.116.190: bytes=32 time=142ms TTL=49
Reply from 74.86.116.190: bytes=32 time=140ms TTL=49
Ping statistics for 74.86.116.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 137ms, Maximum = 163ms, Average = 145ms
ping cossacks server
Tracing route to x10hosting [74.86.116.190]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 8 ms 10.249.148.1
3 35 ms 10 ms 12 ms nott-t2cam2-b-v614.inet.ntl.com [82.13.48.197]
4 8 ms 9 ms 9 ms nott-t3core-1b-ge-111-0.inet.ntl.com [195.182.17
5.145]
5 10 ms 10 ms 10 ms nth-bb-b-so-020-0.inet.ntl.com [213.105.174.173]
6 18 ms 12 ms 15 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
7 15 ms 16 ms 14 ms 195.50.91.69
8 14 ms 17 ms 19 ms ae-32-52.ebr2.London1.Level3.net [4.68.116.62]
9 85 ms 108 ms 105 ms ae-4.ebr1.NewYork1.Level3.net [4.69.132.109]
10 87 ms 91 ms 87 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
11 84 ms 87 ms 90 ms ae-93-93.ebr3.NewYork1.Level3.net [4.69.134.109]
12 96 ms 89 ms 89 ms ae-3.ebr3.Washington1.Level3.net [4.69.132.89]
13 97 ms 126 ms 109 ms ae-63-63.csw1.Washington1.Level3.net [4.69.134.1
62]
14 90 ms 92 ms 90 ms ae-61-61.ebr1.Washington1.Level3.net [4.69.134.1
29]
15 118 ms 108 ms 124 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
16 123 ms 124 ms 161 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
17 125 ms 140 ms 143 ms ae-73-73.csw2.Dallas1.Level3.net [4.69.136.158]
18 125 ms 141 ms 151 ms ae-2-79.edge3.Dallas1.Level3.net [4.68.19.72]
19 142 ms 139 ms 168 ms te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
20 151 ms 139 ms 138 ms po55.fcr03.dal01.dallas-datacenter.com [66.228.1
18.182]
21 138 ms 137 ms 138 ms x10hosting [74.86.116.190]
Trace complete.
Hope this info is helpfull to you guys as this problem is becoming rather annoying.
Ping my domain
Pinging ovgyclan.com [74.86.116.190] with 32 bytes of data:
Reply from 74.86.116.190: bytes=32 time=163ms TTL=49
Reply from 74.86.116.190: bytes=32 time=137ms TTL=49
Reply from 74.86.116.190: bytes=32 time=142ms TTL=49
Reply from 74.86.116.190: bytes=32 time=140ms TTL=49
Ping statistics for 74.86.116.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 137ms, Maximum = 163ms, Average = 145ms
ping ovgyclan.x10hosting.com
Pinging ovgyclan.com [74.86.116.190] with 32 bytes of data:
Reply from 74.86.116.190: bytes=32 time=163ms TTL=49
Reply from 74.86.116.190: bytes=32 time=137ms TTL=49
Reply from 74.86.116.190: bytes=32 time=142ms TTL=49
Reply from 74.86.116.190: bytes=32 time=140ms TTL=49
Ping statistics for 74.86.116.190:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 137ms, Maximum = 163ms, Average = 145ms
ping cossacks server
Tracing route to x10hosting [74.86.116.190]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 8 ms 10.249.148.1
3 35 ms 10 ms 12 ms nott-t2cam2-b-v614.inet.ntl.com [82.13.48.197]
4 8 ms 9 ms 9 ms nott-t3core-1b-ge-111-0.inet.ntl.com [195.182.17
5.145]
5 10 ms 10 ms 10 ms nth-bb-b-so-020-0.inet.ntl.com [213.105.174.173]
6 18 ms 12 ms 15 ms pop-bb-a-so-100-0.inet.ntl.com [213.105.172.14]
7 15 ms 16 ms 14 ms 195.50.91.69
8 14 ms 17 ms 19 ms ae-32-52.ebr2.London1.Level3.net [4.68.116.62]
9 85 ms 108 ms 105 ms ae-4.ebr1.NewYork1.Level3.net [4.69.132.109]
10 87 ms 91 ms 87 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]
11 84 ms 87 ms 90 ms ae-93-93.ebr3.NewYork1.Level3.net [4.69.134.109]
12 96 ms 89 ms 89 ms ae-3.ebr3.Washington1.Level3.net [4.69.132.89]
13 97 ms 126 ms 109 ms ae-63-63.csw1.Washington1.Level3.net [4.69.134.1
62]
14 90 ms 92 ms 90 ms ae-61-61.ebr1.Washington1.Level3.net [4.69.134.1
29]
15 118 ms 108 ms 124 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
16 123 ms 124 ms 161 ms ae-7.ebr3.Dallas1.Level3.net [4.69.134.21]
17 125 ms 140 ms 143 ms ae-73-73.csw2.Dallas1.Level3.net [4.69.136.158]
18 125 ms 141 ms 151 ms ae-2-79.edge3.Dallas1.Level3.net [4.68.19.72]
19 142 ms 139 ms 168 ms te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
20 151 ms 139 ms 138 ms po55.fcr03.dal01.dallas-datacenter.com [66.228.1
18.182]
21 138 ms 137 ms 138 ms x10hosting [74.86.116.190]
Trace complete.
Hope this info is helpfull to you guys as this problem is becoming rather annoying.
Last edited: