Past couple of days I've had random outages of my dedicated. Pingdom was alerting me but it would come back in a few minutes and I wasn't in front of a computer able to test. It went out again and I did some tracerts. I got some weird results I've never seen before.
From my office, while unable to load the site:
Once it came back:
From VZ31-WA while down:
And once back up:
Seems like a routing problem or is the server just going unresponsive? Server load after it comes back is nothing out of the ordinary.
From my office, while unable to load the site:
Code:
C:\Users\Mike>tracert cfffit.com
Tracing route to cfffit.com [209.236.126.155]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.100.1
2 151 ms 8 ms 68 ms 10.112.0.1
3 7 ms 7 ms 8 ms 100.127.64.74
4 145 ms 14 ms 10 ms wsip-70-166-189-128.ph.ph.cox.net [70.166.189.128]
5 23 ms 29 ms 43 ms langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
6 22 ms 23 ms 23 ms ae20.mpr1.lax12.us.zip.zayo.com [64.125.13.97]
7 31 ms 22 ms 23 ms ae10.cr1.lax112.us.zip.zayo.com [64.125.26.6]
8 41 ms 46 ms 41 ms ae27.cs1.lax112.us.eth.zayo.com [64.125.30.184]
9 42 ms 41 ms 57 ms ae3.cs1.dfw2.us.eth.zayo.com [64.125.29.52]
10 42 ms 41 ms 43 ms ae27.cr1.dfw2.us.zip.zayo.com [64.125.30.181]
11 42 ms 41 ms 41 ms ae11.er1.dfw2.us.zip.zayo.com [64.125.20.66]
12 41 ms 41 ms 41 ms ae8.er2.dfw2.us.zip.zayo.com [64.125.29.122]
13 43 ms 41 ms 41 ms 64.124.196.226.t00876-01.above.net [64.124.196.226]
14 43 ms 50 ms 50 ms Jcore4.0.dal.colo4.com [206.123.64.218]
15 43 ms 43 ms 46 ms 72.249.128.110
16 * * * Request timed out.
17 * * * Request timed out.
18 * 162 ms * host2.cfffit.com [209.236.126.155]
19 157 ms * * host2.cfffit.com [209.236.126.155]
20 * * * Request timed out.
21 * 155 ms 157 ms host2.cfffit.com [209.236.126.155]
Trace complete.Once it came back:
Code:
C:\Users\Mike>tracert cfffit.com
Tracing route to cfffit.com [209.236.126.155]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.100.1
2 7 ms 13 ms 7 ms 10.112.0.1
3 7 ms 9 ms 7 ms 100.127.64.74
4 9 ms 9 ms 9 ms wsip-70-166-189-128.ph.ph.cox.net [70.166.189.128]
5 23 ms 22 ms 33 ms langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
6 * 23 ms 30 ms ae20.mpr1.lax12.us.zip.zayo.com [64.125.13.97]
7 24 ms 25 ms 23 ms ae10.cr1.lax112.us.zip.zayo.com [64.125.26.6]
8 68 ms 41 ms 41 ms ae27.cs1.lax112.us.eth.zayo.com [64.125.30.184]
9 45 ms 46 ms 42 ms ae3.cs1.dfw2.us.eth.zayo.com [64.125.29.52]
10 40 ms 41 ms 42 ms ae27.cr1.dfw2.us.zip.zayo.com [64.125.30.181]
11 40 ms 42 ms 44 ms ae11.er1.dfw2.us.zip.zayo.com [64.125.20.66]
12 41 ms 41 ms 41 ms ae8.er2.dfw2.us.zip.zayo.com [64.125.29.122]
13 41 ms 41 ms 43 ms 64.124.196.226.t00876-01.above.net [64.124.196.226]
14 48 ms 42 ms 41 ms Jcore4.0.dal.colo4.com [206.123.64.218]
15 41 ms 43 ms 41 ms 72.249.128.110
16 55 ms 56 ms 58 ms host2.cfffit.com [209.236.126.155]
Trace complete.From VZ31-WA while down:
Code:
[~]# tracert cfffit.com
traceroute to cfffit.com (209.236.126.155), 30 hops max, 40 byte packets
1 vz31-wa.privatesystems.net (199.193.177.31) 0.106 ms 0.023 ms 0.020 ms
2 216.211.135.114 (216.211.135.114) 0.679 ms 0.678 ms 0.703 ms
3 te2-3.sea-cor00.sea.tierpoint.com (173.240.48.6) 0.496 ms 0.550 ms 0.601 ms
4 216.182.84.146 (216.182.84.146) 3.002 ms 2.992 ms 3.007 ms
5 * * *
6 * * *
7 ae-102-102.ebr2.Seattle1.Level3.net (4.69.206.186) 40.298 ms 40.285 ms 40.311 ms
8 ae-2-2.ebr2.Denver1.Level3.net (4.69.132.54) 41.272 ms 41.234 ms 41.221 ms
9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 40.886 ms 40.816 ms 40.812 ms
10 ae-2-2.ebr2.Dallas1.Level3.net (4.69.132.106) 41.295 ms 41.288 ms 41.324 ms
11 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 40.606 ms 40.545 ms 40.583 ms
12 * * *
13 COLO4-DALLA.ear1.Dallas1.Level3.net (8.9.232.74) 41.326 ms 41.287 ms 41.313 ms
14 Jcore4.0.dal.colo4.com (206.123.64.218) 42.264 ms 41.980 ms 44.930 ms
15 72.249.128.162 (72.249.128.162) 41.125 ms 41.097 ms 41.111 ms
16 * * *
17 * * *
18 * host2.cfffit.com (209.236.126.155) 142.081 ms *And once back up:
Code:
[~]# tracert cfffit.com
traceroute to cfffit.com (209.236.126.155), 30 hops max, 40 byte packets
1 vz31-wa.privatesystems.net (199.193.177.31) 0.051 ms 0.023 ms 0.020 ms
2 216.211.135.114 (216.211.135.114) 0.504 ms 0.531 ms 0.560 ms
3 te2-3.sea-cor00.sea.tierpoint.com (173.240.48.6) 0.343 ms 0.492 ms 0.484 ms
4 216.182.84.146 (216.182.84.146) 2.934 ms 2.928 ms 2.920 ms
5 * * *
6 * * *
7 ae-102-102.ebr2.Seattle1.Level3.net (4.69.206.186) 40.298 ms 40.278 ms 40.278 ms
8 ae-2-2.ebr2.Denver1.Level3.net (4.69.132.54) 41.295 ms 41.280 ms 41.265 ms
9 ae-1-100.ebr1.Denver1.Level3.net (4.69.151.181) 49.534 ms 47.283 ms 47.246 ms
10 ae-2-2.ebr2.Dallas1.Level3.net (4.69.132.106) 41.303 ms 41.317 ms 41.277 ms
11 ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153) 41.190 ms 40.487 ms 40.605 ms
12 * * *
13 COLO4-DALLA.ear1.Dallas1.Level3.net (8.9.232.74) 41.286 ms 41.299 ms 41.413 ms
14 Jcore4.0.dal.colo4.com (206.123.64.218) 42.101 ms 42.084 ms 42.162 ms
15 72.249.128.162 (72.249.128.162) 41.138 ms 60.526 ms 60.496 ms
16 host2.cfffit.com (209.236.126.155) 42.063 ms 42.053 ms 41.984 msSeems like a routing problem or is the server just going unresponsive? Server load after it comes back is nothing out of the ordinary.
