Tracing route to www.wgt.com [66.70.125.43] over a maximum of 30 hops:
First 6 steps omitted.
7 16 ms 15 ms 15 ms pos-0-5-0-0-cr01.philadelphia.pa.ibone.comcast.net [68.86.90.13]
8 16 ms 16 ms 16 ms xe-2-1-0-0.was12.ip.tiscali.net [213.200.84.117]
9 88 ms 90 ms 89 ms xe-0-0-0.sjc10.ip.tiscali.net [89.149.187.181]
10 89 ms 90 ms 90 ms datapipe-gw-sjc1.ip.tiscali.net [213.200.84.206]
11 94 ms 199 ms 206 ms vl12.dist1-1.sj2.datapipe.net [66.70.119.27]
12 89 ms 90 ms 99 ms 66.70.125.43
Trace complete.
I'm getting similiar results, although that might mean one of the data centers that routes connections to the WGT has a server down or bottlenecked; something like that.