Not server related, but it could be related to the routing issues Comcast has been having lately and what we have been trying to get fixed.
Trace to you
===========
traceroute 24.22.254.211
traceroute to 24.22.254.211 (24.22.254.211), 30 hops max, 40 byte packets
1 206.16.60.33 (206.16.60.33) 0.631 ms 0.529 ms 0.475 ms
2 mdf1-gsr12-1-gig-1-1.dal1.attens.net (63.241.192.201) 0.286 ms 0.309 ms 0.253 ms
3 gar5.dlstx.ip.att.net (12.122.255.225) 1.532 ms 1.168 ms 1.113 ms
4 cr1.dlstx.ip.att.net (12.122.139.6) 1.453 ms 1.362 ms 1.323 ms
5 ggr3.dlstx.ip.att.net (12.122.139.25) 1.445 ms 1.210 ms 1.175 ms
6 * * *
7 cr1-pos-0-0-3-0.losangeles.savvis.net (204.70.192.249) 34.171 ms 34.989 ms 34.242 ms
8 er2-tengig-2-1.lay.savvis.net (204.70.198.6) 33.836 ms 33.894 ms 33.829 ms
9 208.172.41.162 (208.172.41.162) 34.604 ms 34.816 ms 34.491 ms
10 pos-0-15-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.85) 47.449 ms 47.124 ms 47.171 ms
11 pos-0-15-0-0-cr01.portland.or.ibone.comcast.net (68.86.85.198) 59.801 ms 59.440 ms 59.469 ms
12 pos-0-14-0-0-ar01.burien.wa.seattle.comcast.net (68.86.90.222) 64.138 ms 63.776 ms 63.706 ms
13 be-40-ar01.seattle.wa.seattle.comcast.net (68.85.240.94) 64.601 ms 64.120 ms 63.904 ms
14 te-5-1-ur02.ferndale.wa.seattle.comcast.net (68.86.96.106) 66.757 ms 67.125 ms 67.093 ms
15 te-5-3-ur01.ferndale.wa.seattle.comcast.net (68.86.96.109) 66.792 ms 66.811 ms 66.814 ms
16 te-9-3-ur01.burlington.wa.seattle.comcast.net (68.86.96.114) 68.003 ms 67.875 ms 67.899 ms
17 ge-3-0-0-ten02.burlington.wa.seattle.comcast.net (68.86.113.178) 67.685 ms 67.754 ms 67.701 ms
18 c-24-22-254-211.hsd1.wa.comcast.net (24.22.254.211) 83.840 ms 75.284 ms 76.057 ms
19 * * *
20 * * *
21 *^C
Seems there are issues in the Savvis network. Hop #6 is a Savvis router.
