Regarding Reports on Recent Connection Problems with the NA Data Center

[KonaKai]

COX in South Cali/Orange County

Tracing route to dyn-209-2-229-9.dyn.columbia.edu [209.2.229.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 11 ms 11 ms ip68-4-13-52.oc.oc.cox.net [68.4.13.52]
4 9 ms 9 ms 9 ms ip68-4-11-2.oc.oc.cox.net [68.4.11.2]
5 9 ms 11 ms 10 ms 68.1.1.167
6 10 ms 16 ms 12 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 16 ms 19 ms 18 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 25 ms 22 ms 20 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 26 ms 23 ms 26 ms ae-2.r00.lsanca07.us.bb.gin.ntt.net [129.250.3.238]
10 11 ms 13 ms 9 ms be3025.ccr41.lax04.atlas.cogentco.com [154.54.9.29]
11 11 ms 10 ms 11 ms be3271.ccr41.lax01.atlas.cogentco.com [154.54.42.101]
12 22 ms 22 ms 22 ms be2931.ccr31.phx01.atlas.cogentco.com [154.54.44.85]
13 30 ms 30 ms 30 ms be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]
14 47 ms 47 ms 47 ms be2928.ccr42.iah01.atlas.cogentco.com [154.54.30.161]
15 61 ms 63 ms 61 ms be2690.ccr42.atl01.atlas.cogentco.com [154.54.28.129]
16 73 ms 71 ms 72 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
17 78 ms 78 ms 84 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
18 78 ms 78 ms 78 ms be2897.rcr24.jfk01.atlas.cogentco.com [154.54.84.214]
19 122 ms 78 ms 78 ms 38.122.8.210
20 81 ms 77 ms 77 ms cc-core-1-x-nyser32-gw-1.net.columbia.edu [128.59.255.5]
21 78 ms 76 ms 76 ms cc-wlan-1-x-cc-core-1.net.columbia.edu [128.59.255.78]
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

ping 209.2.229.9

Pinging 209.2.229.9 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.2.229.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping 209.2.229.9

Pinging 209.2.229.9 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 209.2.229.9:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58
Reply from 8.8.8.8: bytes=32 time=11ms TTL=58
Reply from 8.8.8.8: bytes=32 time=10ms TTL=58

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 11ms, Average = 10ms

UPDATE: Think I fixed it? Went to my ISP FAQ and did a simple ip refresh. pinging and tracert working after several tests.

tracert 209.2.229.9

Tracing route to dyn-209-2-229-9.dyn.columbia.edu [209.2.229.9]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 10 ms 8 ms 9 ms ip68-4-13-52.oc.oc.cox.net [68.4.13.52]
4 8 ms 9 ms 7 ms ip68-4-11-2.oc.oc.cox.net [68.4.11.2]
5 10 ms 11 ms 10 ms 68.1.1.167
6 19 ms 16 ms 9 ms ae-7.a00.lsanca20.us.bb.gin.ntt.net [129.250.194.165]
7 22 ms 21 ms 23 ms ae-3.r01.lsanca20.us.bb.gin.ntt.net [129.250.2.233]
8 22 ms 21 ms 23 ms ae-8.r23.lsanca07.us.bb.gin.ntt.net [129.250.6.48]
9 27 ms 27 ms 34 ms ae-2.r00.lsanca07.us.bb.gin.ntt.net [129.250.3.238] 10 11 ms 9 ms 9 ms be3025.ccr41.lax04.atlas.cogentco.com [154.54.9.29]
11 11 ms 11 ms 11 ms be3271.ccr41.lax01.atlas.cogentco.com [154.54.42.101]
12 22 ms 22 ms 25 ms be2931.ccr31.phx01.atlas.cogentco.com [154.54.44.85]
13 32 ms 33 ms 47 ms be2929.ccr21.elp01.atlas.cogentco.com [154.54.42.66]
14 47 ms 47 ms 46 ms be2928.ccr42.iah01.atlas.cogentco.com [154.54.30.161]
15 66 ms 60 ms 61 ms be2690.ccr42.atl01.atlas.cogentco.com [154.54.28.129] 16 71 ms 74 ms 72 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
17 77 ms 78 ms 79 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
18 78 ms 79 ms 80 ms be2897.rcr24.jfk01.atlas.cogentco.com [154.54.84.214]
19 77 ms 78 ms 77 ms 38.122.8.210
20 78 ms 79 ms 77 ms cc-core-1-x-nyser32-gw-1.net.columbia.edu [128.59.255.5]
21 78 ms 77 ms 78 ms cc-wlan-1-x-cc-core-1.net.columbia.edu [128.59.255.78]
22 168 ms 101 ms 101 ms dyn-209-2-229-9.dyn.columbia.edu [209.2.229.9]

Trace complete.

ping 209.2.229.9

Pinging 209.2.229.9 with 32 bytes of data:
Reply from 209.2.229.9: bytes=32 time=189ms TTL=18
Reply from 209.2.229.9: bytes=32 time=109ms TTL=18
Reply from 209.2.229.9: bytes=32 time=129ms TTL=18
Reply from 209.2.229.9: bytes=32 time=153ms TTL=18

Ping statistics for 209.2.229.9:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 189ms, Average = 145ms