dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
1473
Menos
join:2011-01-27

Menos

Member

Latency to WoW server sucks...tracert inside

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.0.1
2 8 ms 9 ms 9 ms
3 14 ms 14 ms 11 ms
4 7 ms 10 ms 16 ms
5 14 ms 13 ms 12 ms ae1_2120-bdr04-tor.teksavvy.com [69.196.136.68]

6 126 ms 13 ms 282 ms ix-0-0-2-0.tcore1.TNK-Toronto.as6453.net [64.86.
33.21]
7 225 ms 283 ms 27 ms if-2-2.tcore2.TNK-Toronto.as6453.net [64.86.33.9
0]
8 377 ms 32 ms 28 ms if-8-2.tcore1.CT8-Chicago.as6453.net [66.110.48.
2]
9 26 ms 25 ms 24 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
1]

10 38 ms 39 ms 41 ms 64.86.79.42
11 41 ms 45 ms 46 ms cr2.cgcil.ip.att.net [12.122.132.198]
12 41 ms 69 ms 60 ms cr1.n54ny.ip.att.net [12.122.1.1]
13 37 ms 38 ms 39 ms gar1.nw2nj.ip.att.net [12.122.131.81]
14 37 ms 36 ms 37 ms 12-122-254-210.attens.net [12.122.254.210]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Um...its 5PM in the afternoon and not even during peak hours.

digiwth
join:2012-09-21
SmartRG SR808ac
Asus RT-AC86
SmartRG SR505N

digiwth

Member

Might be a local problem, did a traceroute to that IP and worse was 38ms to last jump that responds to ICMP (12.122.251.10), 0% loss.

traceroute to 63.240.104.93 (63.240.104.93), 30 hops max, 38 byte packets
 1  206.248.154.104 (206.248.154.104)  6.961 ms  7.057 ms  7.600 ms
 2  ae2_2110-bdr03-tor.teksavvy.com (69.196.136.41)  6.662 ms  6.368 ms  82.872 ms
 3  ix-5-1-0-0.tcore2.TNK-Toronto.as6453.net (63.243.172.9)  7.734 ms  6.228 ms  6.178 ms
 4  if-8-2.tcore1.CT8-Chicago.as6453.net (66.110.48.2)  20.511 ms  24.553 ms  18.434 ms
 5  if-22-2.tcore2.CT8-Chicago.as6453.net (64.86.79.1)  18.697 ms  19.163 ms  21.054 ms
 6  64.86.79.42 (64.86.79.42)  29.670 ms  27.234 ms  23.322 ms
 7  cr2.cgcil.ip.att.net (12.122.132.198)  41.003 ms  40.007 ms  39.827 ms
 8  cr1.n54ny.ip.att.net (12.122.1.1)  39.104 ms  37.695 ms  40.059 ms
 9  gar1.nw2nj.ip.att.net (12.122.131.81)  36.127 ms  36.019 ms  36.147 ms
10  12.122.251.10 (12.122.251.10)  38.012 ms  38.351 ms  38.679 ms
 

RizzleQ
Cunningham's Law Enthusiast
Premium Member
join:2006-01-12
Windsor, ON
Ubiquiti UDM-Pro
Ubiquiti U6-LR

RizzleQ to Menos

Premium Member

to Menos
Tracing route to 63.240.104.93 over a maximum of 30 hops
 
  1    <1 ms    <1 ms    <1 ms  router [192.168.1.1]
  2     7 ms     7 ms     7 ms  10.195.236.1
  3    14 ms    15 ms    14 ms  192-171-63-10.cpe.pppoe.ca [192.171.63.10]
  4    18 ms    17 ms    16 ms  192-171-63-9.cpe.pppoe.ca [192.171.63.9]
  5    17 ms    15 ms    27 ms  ae2_2555-bdr01-tor.teksavvy.com [206.248.142.195]
  6    15 ms    15 ms    15 ms  ae3_2120-bdr03-tor.teksavvy.com [69.196.136.74]
  7    26 ms    15 ms    15 ms  ix-5-1-0-0.tcore2.TNK-Toronto.as6453.net [63.243.172.9]
  8    26 ms    25 ms    25 ms  if-8-2.tcore1.CT8-Chicago.as6453.net [66.110.48.2]
  9    28 ms    34 ms    34 ms  if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.1]
 10    29 ms    27 ms    27 ms  64.86.79.42
 11    47 ms    47 ms    47 ms  cr2.cgcil.ip.att.net [12.122.132.198]
 12    44 ms    43 ms    47 ms  cr1.n54ny.ip.att.net [12.122.1.1]
 13    43 ms    42 ms    43 ms  gar1.nw2nj.ip.att.net [12.122.131.81]
 14    46 ms    45 ms    45 ms  12.122.251.10
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *     ^C
 

jmck
formerly 'shaded'
join:2010-10-02
Ottawa, ON

1 recommendation

jmck to Menos

Member

to Menos
the lines in bold aren't actually a problem since the ones after are low where you get 39-41ms to Chicago. sadly Blizzard/ATT block pings to their networks so there's no real way to tell what your latency is other than in game. what does it say in game?

Napsterbater
Meh
MVM
join:2002-12-28
Milledgeville, GA
(Software) OPNsense
Ubiquiti UniFi UAP-AC-PRO

Napsterbater

MVM

said by jmck:

the lines in bold aren't actually a problem since the ones after are low where you get 39-41ms to Chicago. sadly Blizzard/ATT block pings to their networks so there's no real way to tell what your latency is other than in game. what does it say in game?

Exactly, trace is clean to ATT, must be their problem. But they hide that so they can blame it on others.
resa1983
Premium Member
join:2008-03-10
North York, ON

resa1983 to Menos

Premium Member

to Menos
Could try the lookingglass..
»us-looking-glass.battle.net/

Menos: What latency are you seeing in-game, home & world?
Menos
join:2011-01-27

Menos

Member

My latency before this mornings "maintenance" is usually around 45/50 home/world ms, and 67/70 ms during peek hours. Its spiking to anywhere from 110-523 home/world and it happens quite randomly.

Used the looking glass site. the results

PING 135.23.91.88 (135.23.91.88) 56(84) bytes of data.
64 bytes from 135.23.91.88: icmp_seq=1 ttl=47 time=45.4 ms
64 bytes from 135.23.91.88: icmp_seq=2 ttl=47 time=41.1 ms
64 bytes from 135.23.91.88: icmp_seq=3 ttl=47 time=41.7 ms
64 bytes from 135.23.91.88: icmp_seq=4 ttl=47 time=40.3 ms

--- 135.23.91.88 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3039ms
rtt min/avg/max/mdev = 40.303/42.165/45.474/1.980 ms

traceroute to 135.23.91.88 (135.23.91.88), 15 hops max, 60 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

traceroute to 135.23.91.88 (135.23.91.88), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.810 ms 0.835 ms 0.907 ms
2 * * *
3 206.18.96.209 (206.18.96.209) 0.337 ms 0.409 ms 0.475 ms
4 63.240.130.185 (63.240.130.185) 0.516 ms 0.610 ms 0.692 ms
5 12.122.251.13 (12.122.251.13) 1.913 ms 1.922 ms 1.934 ms
6 cr1.cgcil.ip.att.net (12.122.99.22) 4.874 ms 4.556 ms 4.503 ms
7 ggr4.cgcil.ip.att.net (12.122.133.33) 3.340 ms 3.307 ms 3.203 ms
8 ae3.chi11.ip4.gtt.net (173.241.128.29) 2.272 ms 2.283 ms 2.305 ms
9 xe-11-0-0.tor10.ip4.gtt.net (141.136.105.214) 22.681 ms 22.770 ms 22.780 ms
10 tek-savvy-solutions-gw.ip4.gtt.net (173.205.58.186) 28.641 ms 28.564 ms 28.519 ms
11 ae2_2140-bdr02-tor.teksavvy.com (69.196.136.130) 28.996 ms 28.948 ms 28.945 ms
12 greensboro-rcable-poi.teksavvy.com (198.48.243.178) 34.861 ms 43.729 ms 69.175 ms
13 * * *
14 135-23-91-88.cpe.pppoe.ca (135.23.91.88) 42.252 ms 42.074 ms 41.141 ms

HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.6 0.6 0.4 1.0 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 206.18.96.209 0.0% 10 0.4 0.6 0.3 1.9 0.5
4. 63.240.130.185 0.0% 10 0.4 0.8 0.3 4.3 1.2
5. 12.122.251.13 0.0% 10 48.6 11.5 1.9 48.6 16.3
6. cr1.cgcil.ip.att.net 0.0% 10 3.4 4.4 2.6 5.6 1.0
7. ggr4.cgcil.ip.att.net 0.0% 10 6.8 5.3 2.9 11.9 2.7
8. ae3.chi11.ip4.gtt.net 0.0% 10 2.3 2.7 2.3 5.8 1.1
9. xe-11-0-0.tor10.ip4.gtt.net 0.0% 10 23.1 23.9 22.7 32.6 3.1
10. tek-savvy-solutions-gw.ip4.gtt.net 0.0% 10 32.3 29.5 28.5 32.3 1.3
11. ae2_2140-bdr02-tor.teksavvy.com 0.0% 10 30.6 29.6 28.9 30.6 0.7
12. greensboro-rcable-poi.teksavvy.com 0.0% 10 36.2 37.7 32.3 51.9 7.1
13. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14. 135-23-91-88.cpe.pppoe.ca 0.0% 10 41.2 42.5 40.1 50.9 3.1

jmck
formerly 'shaded'
join:2010-10-02
Ottawa, ON

jmck

Member

if looking glass isn't showing any network issue and shows a clean route then it's likely server issues (CPU load) causing it.

have you tried another WoW server to see if the issue remains?

Napsterbater
Meh
MVM
join:2002-12-28
Milledgeville, GA

Napsterbater to Menos

MVM

to Menos
That looks, probably a server issue, or internal network issue.
Menos
join:2011-01-27

Menos

Member

All the servers my characters are on seem to be affected.

Leathal
Premium Member
join:2002-02-09
Richmond Hill, ON

Leathal to Menos

Premium Member

to Menos
Blizzard receives it's share of network attacks, it could be that it's being attacked, or was.