I doubt WOW can fix it. Seeing similar from a different network:
Tracing route to 74.125.204.147 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms koyomi.aosake.net [192.168.102.1]
2 24 ms 20 ms 21 ms 173-228-7-1.dsl.static.fusionbroadband.com [173.228.7.1]
3 20 ms 21 ms 21 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 35 ms 32 ms 32 ms ae2.cr2.lsatca11.sonic.net [50.0.79.178]
5 20 ms 21 ms 21 ms 50.ae4.gw.pao1.sonic.net [142.254.58.158]
6 21 ms 21 ms 21 ms ae2.0.gw.equinix-sj.sonic.net [50.0.2.14]
7 21 ms 21 ms 21 ms eqixsj-google-gige.google.com [206.223.116.21]
8 83 ms 21 ms 22 ms 216.239.49.168
9 157 ms 157 ms 156 ms 209.85.246.253
10 29 ms 29 ms 30 ms 64.233.174.204
11 126 ms 143 ms 126 ms 209.85.242.88
12 156 ms 156 ms 156 ms 209.85.255.39
13 156 ms 156 ms 156 ms 209.85.249.75
14 * * * Request timed out.
15 155 ms 156 ms 156 ms 74.125.204.147
Trace complete.