So I have been away from Wow for quite some time. Just recently noted there there were posting saying the latency problem to US wow server have improved.
Low and behold, I updated my wow installation and logged into my starter account and checked out the latency. it is at 220ms+/- 50ms
That is way better then the 500ms+/+500ms, I had when I left wow like 2-3 years ago.
So I did some digging and did tracert and pathping, to some server in US. Result as follow.
QUOTE
Tracing route to 12.129.255.32 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 7 ms 7 ms 219.93.218.177
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
1 <1 ms <1 ms <1 ms 192.168.1.254
2 7 ms 7 ms 7 ms 219.93.218.177
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
QUOTE
Tracing route to 12.129.254.206 over a maximum of 30 hops
0 Simpleton-PC [192.168.1.135]
1 192.168.1.254
2 219.93.218.177
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Simpleton-PC [192.168.1.135]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254
72/ 100 = 72% |
2 10ms 72/ 100 = 72% 0/ 100 = 0% 219.93.218.177
Trace complete.
0 Simpleton-PC [192.168.1.135]
1 192.168.1.254
2 219.93.218.177
3 * * *
Computing statistics for 50 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Simpleton-PC [192.168.1.135]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254
72/ 100 = 72% |
2 10ms 72/ 100 = 72% 0/ 100 = 0% 219.93.218.177
Trace complete.
So I was curious how come the hop stops at 219.93.218.177
Is that tm's new toy that is now routing our traffic?
Just some thing to talk about I guess.
Cant wait to sign up for more subscription.
Woot
Skywardsword
edit:
So there was this lightning storm when I first tested it. So I shut down my modem/pc to prevent damage.
Anyhow now I am back up and doing some more test.
My router also have traceroute, apparently it works.
QUOTE
Traceroute to 12.129.254.206 (timer gran. 10 ms)...
30 hops max, 56 byte packets
1 219.93.218.177 0 ms 10 ms 10 ms
2 175.144.89.53 0 ms 10 ms 10 ms
3 10.55.192.49 210 ms 10.55.192.55 210 ms 10.55.192.0 210 ms
4 12.248.108.5 210 ms 210 ms 210 ms
5 12.122.104.50 220 ms 220 ms 220 ms
6 12.122.1.145 220 ms 220 ms 220 ms
7 12.122.128.181 280 ms 220 ms 220 ms
8 12.122.254.234 220 ms 210 ms 12.122.254.238 220 ms
9 12.129.193.250 220 ms 220 ms 12.129.193.254 220 ms
However, I am suspicious as my pathping shows that I am losing 70% packets. plus the below I cant do pingtest's packet lost...30 hops max, 56 byte packets
1 219.93.218.177 0 ms 10 ms 10 ms
2 175.144.89.53 0 ms 10 ms 10 ms
3 10.55.192.49 210 ms 10.55.192.55 210 ms 10.55.192.0 210 ms
4 12.248.108.5 210 ms 210 ms 210 ms
5 12.122.104.50 220 ms 220 ms 220 ms
6 12.122.1.145 220 ms 220 ms 220 ms
7 12.122.128.181 280 ms 220 ms 220 ms
8 12.122.254.234 220 ms 210 ms 12.122.254.238 220 ms
9 12.129.193.250 220 ms 220 ms 12.129.193.254 220 ms

what is going on...
so this is whats going on! I was using firefox with noscript blocking the testing server, therefore the packet lost testing couldnt proceed.
I do have a A line.

This post has been edited by skywardsword: Mar 21 2012, 08:07 PM
Mar 21 2012, 05:55 PM, updated 14y ago
Quote
0.0129sec
0.42
5 queries
GZIP Disabled