View Single Post
Commander
Join Date: Jun 2012
Posts: 441
# 241
12-10-2012, 01:45 PM
Quote:
Originally Posted by evil70th View Post
I am using Cox Communication and here is my results;

Tracing route to patchserver.crypticstudios.com [208.95.185.41]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms (My IP)
2 * * * Request timed out.
3 6 ms 5 ms 5 ms ip68-6-12-190.sd.sd.cox.net [68.6.12.190]
4 6 ms 6 ms 5 ms elcnsysc01-tec-141.sd.sd.cox.net [68.6.8.58]
5 6 ms 5 ms 5 ms fed1sysc01-gex0901.sd.sd.cox.net [68.6.8.100]
6 23 ms 23 ms 23 ms 68.1.5.129
7 32 ms 32 ms 32 ms dcr2-ge-7-0-0-292.sanfranciscosfo.savvis.net [208.173.170.1]
8 39 ms 33 ms 33 ms cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.70.200.198]
9 72 ms 72 ms 72 ms cr2-bundle-pos-1.newyork.savvis.net [204.70.197.34]
10 70 ms 71 ms 71 ms er1-te-2-1.newyorknyd.savvis.net [204.70.196.70]
11 79 ms 77 ms 76 ms msr1-te-0-3-0-0.bos.savvis.net [206.28.97.205]
12 76 ms 75 ms 76 ms 206.28.97.137
13 176 ms 85 ms 80 ms internap.Boston.savvis.net [208.172.51.230]
14 164 ms 160 ms 166 ms border11.te7-1-bbnet1.bsn.pnap.net [63.251.128.41]

15 77 ms 78 ms 78 ms cryptic-3.border11.bsn.pnap.net [216.52.61.78]
16 77 ms 77 ms 77 ms 208.95.185.41

Trace complete.



The information marked in orange seems to run through the area lewstelamon01 described earlier as running through the area hit by Sandy. I also would like to note that I had no latency issues prior to the season 7 release.

Brian
True, but those numbers aren't completely problematic there, except in hop 14. I'll point out, though, that I'd run several traces over a period of time when I posted that commentary and got wildly variable results...but yes, they were in that zone.
****
Lagging, D/Cing, or rubberbanding? Here's some help.

Current ships: A lot. RTR 15 National Championships....and counting