traceroute to 209.19.5.61 (209.19.5.61), 64 hops max, 44 byte packets
1 216.91.187.34 (216.91.187.34) 0.414 ms 0.328 ms 0.365 ms
2 208.172.1.221 (208.172.1.221) 6.231 ms 6.129 ms 6.159 ms
3 208.172.3.81 (208.172.3.81) 24.551 ms 6.186 ms 6.193 ms
4 dcr1-loopback.Washington.savvis.net (206.24.226.99) 23.122 ms 23.224 ms 23.198 ms
5 cpr1-pos-0-0.VirginiaEquinix.savvis.net (208.173.52.113) 23.599 ms 23.821 ms 23.841 ms
6 208.173.51.142 (208.173.51.142) 23.782 ms 23.623 ms 23.855 ms
7 a5-0-136.border1.rap.atl.transedge.com (216.217.3.169) 36.351 ms 36.473 ms 37.899 ms
8 f0-0.agg1.rap.atl.transedge.com (216.217.3.190) 36.867 ms * 36.821 ms
There is not much we can do about this. It is happening at your ISP. Here is the trace back to your second hop, which we cannot trace to nor ping.
You need to get your ISP involved in this.