Hi there, been a while

Server went back to 80 ping (boo) for me. Looks like the tracert is in chicago and not San Jose?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\IBM_ADMIN>ping 68.232.172.50
Pinging 68.232.172.50 with 32 bytes of data:
Reply from 68.232.172.50: bytes=32 time=75ms TTL=51
Reply from 68.232.172.50: bytes=32 time=115ms TTL=51
Reply from 68.232.172.50: bytes=32 time=74ms TTL=51
Reply from 68.232.172.50: bytes=32 time=113ms TTL=51
Ping statistics for 68.232.172.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 115ms, Average = 94ms
C:\Users\IBM_ADMIN>tracert 68.232.172.50
Tracing route to 68.232.172.50.choopa.net [68.232.172.50]
over a maximum of 30 hops:
1 1 ms 39 ms 1 ms 192.168.1.1
2 9 ms 44 ms 9 ms x.x.x.x
3 70 ms 8 ms 40 ms te-7-7-ur01.sfgeary.ca.sfba.comcast.net [68.87.196.161]
4 9 ms 42 ms 9 ms 69.139.199.198
5 50 ms 12 ms 43 ms te-1-12-0-13-ar01.sfsutro.ca.sfba.comcast.net [69.139.199.146]
6 14 ms 38 ms 13 ms he-3-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.93.213]
7 63 ms 15 ms 38 ms pos-0-4-0-0-pe01.11greatoaks.ca.ibone.comcast.ne
t [68.86.87.150]
8 15 ms 304 ms 14 ms xe-9-3-0.sjc10.ip4.tinet.net [213.200.80.165]
9 111 ms 72 ms * xe-2-2-3.chi11.ip4.gtt.net [89.149.185.177]
10 280 ms 82 ms * gtt-gw.ip4.gtt.net [77.67.70.166]
11 164 ms 73 ms 118 ms ae1-60g.cr1.ord1.us.nlayer.net [69.31.111.133]
12 76 ms 132 ms 74 ms tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
13 258 ms 76 ms 115 ms 68.232.172.50.choopa.net [68.232.172.50]
Trace complete.
Oh well, it was fun while it lasted

How's your ping Helen?