High Latency related to Battlegroup?

(Locked)

90 Undead Mage
10480
*whistle whistle* waiting for blue post.

I like how they respond to topics without given information, but here we give them a plethora of info yet they can't respond to us. :\
100 Tauren Druid
20515
I was just waiting for the traces to finish on my computer ..

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Home-PC [192.168.1.68]
1 BTHomeHub.home [192.168.1.254]
2 217.32.143.41
3 217.32.143.110
4 212.140.206.130
5 31.55.165.225
6 31.55.165.109
7 acc2-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.228]
8 core2-te0-12-0-4.ealing.ukcore.bt.net [109.159.250.135]
9 transit1-xe9-0-0.ealing.ukcore.bt.net [62.6.200.189]
10 t2c3-xe-9-2-0.uk-eal.eu.bt.net [166.49.168.25]
11 tengigabitethernet3-3.ar7.lon3.gblx.net [64.215.25.1]
12 att-1-ar2.CHI2.gblx.net [64.208.110.146]
13 cr2.cgcil.ip.att.net [12.122.132.158]
14 gar3.cgcil.ip.att.net [12.122.132.213]
15 12.122.251.50
16 63.240.130.214
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Home-pc [192.168.1.68]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% BTHomeHub.home [192.168.1.254]
0/ 100 = 0% |
2 4ms 0/ 100 = 0% 0/ 100 = 0% 217.32.143.41
0/ 100 = 0% |
3 13ms 0/ 100 = 0% 0/ 100 = 0% 217.32.143.110
0/ 100 = 0% |
4 6ms 0/ 100 = 0% 0/ 100 = 0% 212.140.206.130
0/ 100 = 0% |
5 6ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.225
0/ 100 = 0% |
6 6ms 0/ 100 = 0% 0/ 100 = 0% 31.55.165.109
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% acc2-10GigE-9-2-0.mr.21cn-ipp.bt.net [109.159.250.228]
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% core2-te0-12-0-4.ealing.ukcore.bt.net [109.159.250.135]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% transit1-xe9-0-0.ealing.ukcore.bt.net [62.6.200.189]
0/ 100 = 0% |
10 18ms 0/ 100 = 0% 0/ 100 = 0% t2c3-xe-9-2-0.uk-eal.eu.bt.net [166.49.168.25]
0/ 100 = 0% |
11 27ms 0/ 100 = 0% 0/ 100 = 0% tengigabitethernet3-3.ar7.lon3.gblx.net [64.215.25.1]
0/ 100 = 0% |
12 107ms 0/ 100 = 0% 0/ 100 = 0% att-1-ar2.CHI2.gblx.net [64.208.110.146]
100/ 100 =100% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.132.158]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att.net [12.122.132.213]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214


Now I'm aware of the local packet loss as that came up as an issue about an hour ago with downed lines in a flood hit area down south.... of the UK. But the ATT ones? I have no clue what is happening with them.

Edit: I also note the local issue isn't affecting the internet at large given I have been connecting everywhere today so fast my computer can't keep up.. Except when I try to connect to Burning Blade in the chicago datacentre.
Edited by Velnrak on 1/11/2013 11:33 AM PST
Support Forum Agent
There seems to be an issue with players from Arizona, but there are outliers as well. We're looking for this info:

1) Realm
2) City and State
3) ISP (Internet Service Provider)
4) A trace route and pathping

After you paste the traces into a post, highlight everything, and hit the "pre" button (It says "Code Blocks" when you hover your mouse over it). That'll make the information much more readable.

Thanks very much for the info, and I apologize for not getting to this thread earlier.
________________________________________________
Monday - Friday, 8 am - 5 pm PST
90 Human Paladin
12160
I am going to wait until peak time before attaching the required info. While the problem persists at all times, it is minimal at best before about 4/5 PM MST.
100 Tauren Druid
20515
1) Realm
2) City and State
3) ISP (Internet Service Provider)
4) A trace route and pathping


Burning Blade

Lancaster, England, United Kingdom

British telecom

Already posted pathping and traceroute in the thread.
Support Forum Agent
I'm connecting to burning blade in vindication, and I'm getting high latency all of a sudden... my housemate connected to cenarian circle isn't getting any lag outside of the normal...

So something is going wonky somewhere in the tubes...

I doubt Blizz can do anything though.... granted both of us are connecting from the UK but still that discrepancy on the same network is weird.

Your pathping looks good, Waraila. Is your housemate seeing high latency on Burning Blade too? When you log on Cenarian Circle, is the latency normal?
________________________________________________
Monday - Friday, 8 am - 5 pm PST
100 Tauren Druid
20515
01/11/2013 11:37 AMPosted by Velnrak
Your pathping looks good, Waraila. Is your housemate seeing high latency on Burning Blade too? When you log on Cenarian Circle, is the latency normal?


yes to both. Which is strange... if it was our end then latency would be high across the board but it is not. And CC servers are further away <.< which is baffling.

i'm currently waiting on livechat with BT to make absolutely sure it's nothing my end but if it was we shouldn't see the discrepancy between the two datacentres.
Edited by Waraila on 1/11/2013 11:41 AM PST
90 Blood Elf Death Knight
13290
Realms: Skullcrusher, Azshara, Bleeding Hollow (all realms on Chicago-based battlegroups)
EDIT: getting 200-500ms on these servers, 20-30 on non-Chicago realms like Korgath.
Tempe, AZ
ISP: COX
I can't get a full pathping - it stops at 1 hop even when running CMD prompts as admin (maybe firewall?); I'm not tech savvy enough to figure that out.

Trace route:

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 172.21.0.80
4 16 ms 11 ms 11 ms 70.169.73.90
5 11 ms 8 ms 9 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 22 ms 21 ms 23 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 21 ms 29 ms 21 ms te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
8 22 ms 21 ms 21 ms te0-2-0-2.mpd22.lax01.atlas.cogentco.com [154.54.30.197]
9 58 ms 59 ms 57 ms te0-2-0-3.mpd22.iah01.atlas.cogentco.com [154.54.45.9]
10 62 ms 67 ms 63 ms te0-0-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.25.221]
11 74 ms 75 ms 73 ms te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
12 86 ms 85 ms 86 ms te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.4.34]
13 85 ms 88 ms 85 ms te0-1-0-7.ccr22.ord03.atlas.cogentco.com [154.54.1.98]
14 97 ms 99 ms 100 ms 192.205.37.177
15 97 ms 99 ms 97 ms cr1.cgcil.ip.att.net [12.122.84.54]
16 137 ms 104 ms 97 ms gar3.cgcil.ip.att.net [12.122.132.213]
17 96 ms 97 ms 99 ms 12.122.251.50
18 95 ms 97 ms 96 ms 63.240.130.214
19 * * * Request timed out.
Edited by Jingdi on 1/11/2013 11:51 AM PST
90 Human Warrior
7725
I live in Avondale, Arizona. I am having the same issue everyone else is having. It is during peak time, my latency can go up to 300+ especially in battlegrounds.

My abilities have a 1 to 2 second delay. Its very upsetting =(.

Realm: Tichondrius
City / State: Avondale, Arizona
ISP: Cox

Trace Route:

Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 11 ms 11 ms 8 ms 10.144.0.1
3 10 ms 8 ms 12 ms wsip-184-178-205-32.ph.ph.cox.net [184.178.205.32]
4 29 ms 10 ms 12 ms 70.169.75.86
5 20 ms 13 ms 15 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
6 * * * Request timed out.
7 22 ms 21 ms 22 ms te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
8 53 ms 63 ms 61 ms 192.205.37.157
9 64 ms 57 ms 67 ms cr2.la2ca.ip.att.net [12.122.84.218]
10 65 ms 164 ms 113 ms gar20.la2ca.ip.att.net [12.122.128.181]
11 62 ms 58 ms 57 ms 12-122-254-234.attens.net [12.122.254.234]
12 59 ms 68 ms 57 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
13 * * * Request timed out.
14 * * * Request timed out.
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.


Path Ping:

Tracing route to 12.129.254.192 over a maximum of 30 hops

0 Banixx-PC [192.168.1.12]
1 192.168.1.1
2 10.144.0.1
3 wsip-184-178-205-32.ph.ph.cox.net [184.178.205.32]
4 70.169.75.86
5 mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
6 langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
8 192.205.37.157
9 cr2.la2ca.ip.att.net [12.122.84.218]
10 gar29.la2ca.ip.att.net [12.122.129.241]
11 12.122.251.190
12 206.16.68.46
13 * * *
Computing statistics for 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Banixx-PC [192.168.1.12]
0/ 100 = 0% |
1 1ms 1/ 100 = 1% 1/ 100 = 1% 192.168.1.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 10.144.0.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% wsip-184-178-205-32.ph.ph.cox.net [184.178.205.32]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% 70.169.75.86
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
0/ 100 = 0% |
6 29ms 0/ 100 = 0% 0/ 100 = 0% langbprj02-ae2.rd.la.cox.net [68.1.1.19]
0/ 100 = 0% |
7 24ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
2/ 100 = 2% |
8 67ms 2/ 100 = 2% 0/ 100 = 0% 192.205.37.157
98/ 100 = 98% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.84.218]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 206.16.68.46

Trace complete.


If a blue could respond to this question that would be great! My question is with this compiled information will you be able to contact ATT or Cogentco (whoever is responsible for this, or even Cox?) to try to get this resolved. I contacted my ISP and they said everything is fine, they dont even understand what I am talking about which is frustrating. They wont do anything for me.
Edited by Velnrak on 1/11/2013 12:19 PM PST
90 Undead Mage
10480
There seems to be an issue with players from Arizona, but there are outliers as well. We're looking for this info:

1) Realm
2) City and State
3) ISP (Internet Service Provider)
4) A [url="http://us.battle.net/support/en/article/performing-a-traceroute?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS"]trace route[/url] and [url="https://us.battle.net/support/en/article/running-a-pathping-test?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS"]pathping[/url]

After you paste the traces into a post, highlight everything, and hit the "pre" button (It says "Code Blocks" when you hover your mouse over it). That'll make the information much more readable.

Thanks very much for the info, and I apologize for not getting to this thread earlier.
________________________________________________
Monday - Friday, 8 am - 5 pm PST


Lag seems fine right now, its usually during peak hours. Here is my info now, I'll post later as well during peak.

1) Arthas
2) Tempe, Arizona
3) Cox Communications
4) Trace & Path


Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms TIMD [192.168.1.1]
2 8 ms 8 ms 12 ms 10.35.64.1
3 8 ms 10 ms 9 ms 172.21.0.96
4 18 ms 23 ms 11 ms 70.169.73.90
5 9 ms 12 ms 8 ms 70.169.75.153
6 23 ms 22 ms 41 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 37 ms 21 ms 22 ms te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 25 ms 23 ms 22 ms te0-3-0-5.ccr22.lax01.atlas.cogentco.com [154.54.44.133]
9 58 ms 59 ms 58 ms te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
10 64 ms 63 ms 73 ms te0-3-0-5.ccr22.dfw01.atlas.cogentco.com [154.54.24.26]
11 73 ms 73 ms 73 ms te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
12 84 ms 91 ms 86 ms te0-3-0-7.ccr22.ord01.atlas.cogentco.com [154.54.84.78]
13 86 ms 86 ms 85 ms te0-5-0-7.ccr22.ord03.atlas.cogentco.com [154.54.44.166]
14 98 ms 96 ms 99 ms 192.205.37.173
15 97 ms 99 ms 100 ms cr1.cgcil.ip.att.net [12.122.84.54]
16 96 ms 97 ms 172 ms gar3.cgcil.ip.att.net [12.122.132.213]
17 105 ms 99 ms 102 ms 12.122.251.50
18 97 ms 99 ms 100 ms 63.240.130.210
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 * *



Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Patrick-PC.ph.cox.net [192.168.1.132]
1 TIMD [192.168.1.1]
2 10.35.64.1
3 172.21.0.96
4 70.169.73.90
5 70.169.75.153
6 langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 te0-2-0-2.ccr22.lax01.atlas.cogentco.com [154.54.29.201]
9 te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
10 te0-3-0-5.ccr22.dfw01.atlas.cogentco.com [154.54.24.26]
11 te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
12 te0-3-0-7.ccr22.ord01.atlas.cogentco.com [154.54.84.78]
13 te0-5-0-7.ccr22.ord03.atlas.cogentco.com [154.54.44.166]
14 192.205.37.173
15 cr2.cgcil.ip.att.net [12.122.84.94]
16 gar3.cgcil.ip.att.net [12.122.132.213]
17 12.122.251.50
18 63.240.130.210
19 * * *
Computing statistics for 450 seconds...
85 Tauren Warrior
5940
The lag begin at 2pm est hour. Was 35-45 ms noe 100 ms+ and sometime arround 200+ Now I have random lag spike.

Zul'Jin
Canada East
AEI internet (DSL)

Détermination de l'itinéraire vers 63.240.161.189 avec un maximum de 30 sauts.

1 <1 ms <1 ms <1 ms 192.168.2.1

2 10 ms 10 ms 9 ms lns001.lo-0.aei.net [204.19.206.30]

3 9 ms 9 ms 9 ms coreB.ge-3.6.aei.net [204.19.207.5]

4 10 ms 10 ms 9 ms gateway.synapse.net [199.84.54.1]

5 9 ms 9 ms 9 ms 206.123.6.1

6 9 ms 10 ms 10 ms gi1-1.ccr01.ymq03.atlas.cogentco.com [38.122.102.1]

7 10 ms 10 ms 11 ms te0-3-0-0.ccr22.ymq02.atlas.cogentco.com [154.54.0.13]

8 17 ms 17 ms 17 ms te0-3-0-5.ccr21.yyz02.atlas.cogentco.com [154.54.43.221]

9 31 ms 31 ms 31 ms te0-5-0-2.ccr21.ord01.atlas.cogentco.com [154.54.6.154]

10 32 ms 32 ms 32 ms te0-6-0-6.ccr22.ord03.atlas.cogentco.com [154.54.29.18]

11 45 ms 45 ms 46 ms 192.205.37.177

12 52 ms 51 ms 48 ms cr2.cgcil.ip.att.net [12.122.84.94]

13 44 ms 137 ms * gar3.cgcil.ip.att.net [12.122.132.213]

14 46 ms * * 12.122.251.22

15 46 ms 49 ms 179 ms 63.240.130.214

16 * * * Délai d'attente de la demande dépassé.

17 * * * Délai d'attente de la demande dépassé.

18 * * * Délai d'attente de la demande dépassé.

19 * * * Délai d'attente de la demande dépassé.

20 * * * Délai d'attente de la demande dépassé.

21 * * * Délai d'attente de la demande dépassé.

22 * * * Délai d'attente de la demande dépassé.

23 * * * Délai d'attente de la demande dépassé.

24 * * * Délai d'attente de la demande dépassé.

25 * * * Délai d'attente de la demande dépassé.

26 * * * Délai d'attente de la demande dépassé.

Détermination de l'itinéraire vers 63.240.161.189 avec un maximum de 30 sauts.

0 pl [192.168.2.100]

1 192.168.2.1

2 lns001.lo-0.aei.net [204.19.206.30]

3 coreB.ge-3.6.aei.net [204.19.207.5]

4 gateway.synapse.net [199.84.54.1]

5 206.123.6.1

6 gi1-1.ccr01.ymq03.atlas.cogentco.com [38.122.102.1]

7 te0-3-0-0.ccr22.ymq02.atlas.cogentco.com [154.54.0.13]

8 te0-3-0-5.ccr21.yyz02.atlas.cogentco.com [154.54.43.221]

9 te0-5-0-2.ccr21.ord01.atlas.cogentco.com [154.54.6.154]

10 te0-6-0-6.ccr22.ord03.atlas.cogentco.com [154.54.29.18]

11 192.205.37.177

12 cr1.cgcil.ip.att.net [12.122.84.54]

13 gar2.clboh.ip.att.net [12.122.133.197]

14 12.122.251.50

15 63.240.130.214

16 * * *

Traitement des statistiques pendant 400 secondes...

Source vers ici Ce noud/lien

Saut RTT Perdu/Envoyé = Perdu/Envoyé = Adresse

0 pl [192.168.2.100]

0/ 100 = 0% |

1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.2.1

0/ 100 = 0% |

2 11ms 0/ 100 = 0% 0/ 100 = 0% lns001.lo-0.aei.net [204.19.206.30]

0/ 100 = 0% |

3 11ms 0/ 100 = 0% 0/ 100 = 0% coreB.ge-3.6.aei.net [204.19.207.5]

0/ 100 = 0% |

4 10ms 0/ 100 = 0% 0/ 100 = 0% gateway.synapse.net [199.84.54.1]

0/ 100 = 0% |

5 11ms 0/ 100 = 0% 0/ 100 = 0% 206.123.6.1

0/ 100 = 0% |

6 33ms 0/ 100 = 0% 0/ 100 = 0% gi1-1.ccr01.ymq03.atlas.cogentco.com [38.122.102.1]

0/ 100 = 0% |

7 11ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-0.ccr22.ymq02.atlas.cogentco.com [154.54.0.13]

0/ 100 = 0% |

8 18ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-5.ccr21.yyz02.atlas.cogentco.com [154.54.43.221]

0/ 100 = 0% |

9 32ms 0/ 100 = 0% 0/ 100 = 0% te0-5-0-2.ccr21.ord01.atlas.cogentco.com [154.54.6.154]

0/ 100 = 0% |

10 33ms 0/ 100 = 0% 0/ 100 = 0% te0-6-0-6.ccr22.ord03.atlas.cogentco.com [154.54.29.18]

7/ 100 = 7% |

11 48ms 7/ 100 = 7% 0/ 100 = 0% 192.205.37.177

93/ 100 = 93% |

12 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.84.54]

0/ 100 = 0% |

13 --- 100/ 100 =100% 0/ 100 = 0% gar2.clboh.ip.att.net [12.122.133.197]

0/ 100 = 0% |

14 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50

0/ 100 = 0% |

15 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214

0/ 100 = 0% |

16 --- 100/ 100 =100% 0/ 100 = 0% pl [0.0.0.0]

Itinéraire déterminé.
Edited by Milennos on 1/11/2013 1:54 PM PST
90 Tauren Death Knight
10720
1) Illidan-US
2) Phoenix, Arizona
3) COX

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.146.192.1
3 10 ms 8 ms 9 ms 68.2.8.17
4 12 ms 11 ms 11 ms 70.169.75.84
5 10 ms 9 ms 9 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 20 ms 21 ms 21 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 22 ms 23 ms 21 ms te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 22 ms 21 ms 21 ms 154.54.88.194
9 58 ms 60 ms 59 ms te0-1-0-3.ccr22.iah01.atlas.cogentco.com [154.54.44.253]
10 64 ms 63 ms 66 ms te0-3-0-5.ccr22.dfw01.atlas.cogentco.com [154.54.24.26]
11 73 ms 71 ms 73 ms te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
12 88 ms 84 ms 85 ms te0-3-0-2.ccr22.ord01.atlas.cogentco.com [154.54.6.213]
13 88 ms 85 ms 88 ms te0-5-0-3.ccr22.ord03.atlas.cogentco.com [154.54.43.234]
14 96 ms * 96 ms 192.205.37.177
15 98 ms 103 ms 98 ms cr2.cgcil.ip.att.net [12.122.84.94]
16 97 ms 97 ms 96 ms gar3.cgcil.ip.att.net [12.122.132.213]
17 98 ms 98 ms 98 ms 12.122.251.50
18 99 ms 98 ms 98 ms 63.240.130.214
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.


Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Home-PC [192.168.1.2]
1 192.168.1.1
2 10.146.192.1
3 68.2.8.17
4 70.169.75.84
5 chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 * langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 te0-2-0-2.mpd22.lax01.atlas.cogentco.com [154.54.30.197]
9 te0-2-0-3.mpd22.iah01.atlas.cogentco.com [154.54.45.9]
10 te0-3-0-2.ccr22.dfw01.atlas.cogentco.com [154.54.0.202]
11 te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
12 te0-3-0-2.ccr22.ord01.atlas.cogentco.com [154.54.6.213]
13 te0-5-0-3.ccr22.ord03.atlas.cogentco.com [154.54.43.234]
14 192.205.37.177
15 cr2.cgcil.ip.att.net [12.122.84.94]
16 gar3.cgcil.ip.att.net [12.122.132.213]
17 12.122.251.50
18 * 63.240.130.214
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Home-PC [192.168.1.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 10.146.192.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 68.2.8.17
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% 70.169.75.84
0/ 100 = 0% |
5 13ms 0/ 100 = 0% 0/ 100 = 0% chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
0/ 100 = 0% |
6 27ms 0/ 100 = 0% 0/ 100 = 0% langbprj02-ae2.rd.la.cox.net [68.1.1.19]
0/ 100 = 0% |
7 23ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
0/ 100 = 0% |
8 23ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-2.mpd22.lax01.atlas.cogentco.com [154.54.30.197]
0/ 100 = 0% |
9 58ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-3.mpd22.iah01.atlas.cogentco.com [154.54.45.9]
0/ 100 = 0% |
10 64ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-2.ccr22.dfw01.atlas.cogentco.com [154.54.0.202]
0/ 100 = 0% |
11 74ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
0/ 100 = 0% |
12 86ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-2.ccr22.ord01.atlas.cogentco.com [154.54.6.213]
0/ 100 = 0% |
13 86ms 0/ 100 = 0% 0/ 100 = 0% te0-5-0-3.ccr22.ord03.atlas.cogentco.com [154.54.43.234]
3/ 100 = 3% |
14 102ms 3/ 100 = 3% 0/ 100 = 0% 192.205.37.177
97/ 100 = 97% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.84.94]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att.net [12.122.132.213]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214

Trace complete.
Edited by Velnrak on 1/11/2013 12:24 PM PST
100 Tauren Druid
20515
One thing I do have to point out Velnrak is that this issue can be very intermittent. Last night I was fine for 10 -30 mins, then all of a sudden latency would spike so high it would d/c me mid raid and then stay that way for a while, or a few seconds, or 4 minutes or 15 etc. Right now, the latency is fine, but I have seen it spike randomly and usually at the worst possible times.

(I swear your server connections are sentient in some way, they always choose the worst times to .. well get worse)
90 Blood Elf Paladin
10340
+1 Waraila. I'm in Mississippi and have the same issue jumping from cogentco to att
100 Pandaren Priest
9605
1) Shattered Hand-US
2) Vancouver, BC Canada
3) Telus

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.254
2 29 ms 25 ms 25 ms 10.144.48.1
3 42 ms 26 ms 26 ms 208.181.241.222
4 26 ms 26 ms 27 ms 209.121.72.251
5 * * * Request timed out.
6 31 ms 31 ms 67 ms MTLXPQVVBR02.core.tac.net [204.225.245.137]
7 30 ms 29 ms 31 ms te7-4.ccr02.sea02.atlas.cogentco.com [154.54.10.45]
8 29 ms 29 ms 29 ms te2-7.ccr02.sea01.atlas.cogentco.com [154.54.85.181]
9 50 ms 51 ms 52 ms te0-0-0-4.ccr21.slc01.atlas.cogentco.com [154.54.5.34]
10 * 62 ms * te8-2.ccr02.den01.atlas.cogentco.com [154.54.82.230]
11 74 ms 73 ms 74 ms te0-2-0-7.ccr22.mci01.atlas.cogentco.com [154.54.82.214]
12 86 ms 85 ms 85 ms te0-3-0-7.ccr21.ord01.atlas.cogentco.com [154.54.84.74]
13 98 ms 101 ms 91 ms te0-5-0-1.ccr22.ord03.atlas.cogentco.com [154.54.43.230]
14 99 ms 99 ms 99 ms 192.205.37.177
15 105 ms 100 ms 101 ms cr1.cgcil.ip.att.net [12.122.84.54]
16 99 ms 97 ms 100 ms gar2.clboh.ip.att.net [12.122.133.197]
17 * 103 ms 102 ms 12.122.251.22
18 102 ms 101 ms 100 ms 63.240.130.210
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.

racing route to 63.240.161.189 over a maximum of 30 hops

0 Razada [192.168.1.69]
1 192.168.1.254
2 10.144.48.1
3 208.181.241.222
4 209.121.72.251
5 154.11.22.114
6 MTLXPQVVBR02.core.tac.net [204.225.245.137]
7 te7-4.ccr02.sea02.atlas.cogentco.com [154.54.10.45]
8 te2-7.ccr02.sea01.atlas.cogentco.com [154.54.85.181]
9 te0-0-0-4.ccr21.slc01.atlas.cogentco.com [154.54.5.34]
10 te8-2.ccr01.den01.atlas.cogentco.com [154.54.82.222]
11 te0-2-0-7.ccr21.mci01.atlas.cogentco.com [154.54.82.206]
12 te0-3-0-7.ccr21.ord01.atlas.cogentco.com [154.54.84.74]
13 154.54.43.230
14 192.205.37.177
15 cr2.cgcil.ip.att.net [12.122.84.94]
16 gar2.clboh.ip.att.net [12.122.133.197]
17 12.122.251.50
18 63.240.130.210
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Razada [192.168.1.69]
0/ 100 = 0% |
1 4ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254
0/ 100 = 0% |
2 27ms 0/ 100 = 0% 0/ 100 = 0% 10.144.48.1
0/ 100 = 0% |
3 28ms 0/ 100 = 0% 0/ 100 = 0% 208.181.241.222
0/ 100 = 0% |
4 27ms 0/ 100 = 0% 0/ 100 = 0% 209.121.72.251
0/ 100 = 0% |
5 28ms 0/ 100 = 0% 0/ 100 = 0% 154.11.22.114
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% MTLXPQVVBR02.core.tac.net [204.225.245.137]
0/ 100 = 0% |
7 71ms 0/ 100 = 0% 0/ 100 = 0% te7-4.ccr02.sea02.atlas.cogentco.com [154.54.10.45]
0/ 100 = 0% |
8 85ms 0/ 100 = 0% 0/ 100 = 0% te2-7.ccr02.sea01.atlas.cogentco.com [154.54.85.181]
0/ 100 = 0% |
9 53ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-4.ccr21.slc01.atlas.cogentco.com [154.54.5.34]
0/ 100 = 0% |
10 121ms 1/ 100 = 1% 1/ 100 = 1% te8-2.ccr01.den01.atlas.cogentco.com [154.54.82.222]
0/ 100 = 0% |
11 75ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-7.ccr21.mci01.atlas.cogentco.com [154.54.82.206]
0/ 100 = 0% |
12 87ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-7.ccr21.ord01.atlas.cogentco.com [154.54.84.74]
0/ 100 = 0% |
13 88ms 0/ 100 = 0% 0/ 100 = 0% te0-5-0-1.ccr22.ord03.atlas.cogentco.com [154.54.43.230]
7/ 100 = 7% |
14 103ms 7/ 100 = 7% 0/ 100 = 0% 192.205.37.177
93/ 100 = 93% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.84.94]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar2.clboh.ip.att.net [12.122.133.197]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.210

Trace complete.


This issue started for the first time on Jan 9th. Before i had never had any issues with latency. It seems to be the worst around 7pm - 12pm server

Edit* When i log on to a different server not located in the same region i do not have the latency issues..............
Edited by Razaz on 1/11/2013 1:01 PM PST
90 Blood Elf Priest
12985
There seems to be an issue with players from Arizona, but there are outliers as well. We're looking for this info:

1) Realm
2) City and State
3) ISP (Internet Service Provider)
4) A [url="http://us.battle.net/support/en/article/performing-a-traceroute?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS"]trace route[/url] and [url="https://us.battle.net/support/en/article/running-a-pathping-test?utm_source=internal&utm_medium=support_forums&utm_campaign=BlizzardCS"]pathping[/url]

After you paste the traces into a post, highlight everything, and hit the "pre" button (It says "Code Blocks" when you hover your mouse over it). That'll make the information much more readable.

Thanks very much for the info, and I apologize for not getting to this thread earlier.
________________________________________________
Monday - Friday, 8 am - 5 pm PST


Thank you for looking at this!

1) Burning Legion
2) Chandler, AZ
3) Cox Communication
4a) Trace Route:

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.0.1
2 13 ms 25 ms 26 ms 10.39.0.1
3 12 ms 16 ms 13 ms 172.21.0.116
4 28 ms 23 ms 26 ms 70.169.73.90
5 13 ms 14 ms 20 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 27 ms 24 ms 28 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 * * 73 ms te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
8 33 ms 35 ms 34 ms te0-2-0-6.ccr22.lax01.atlas.cogentco.com [154.54.82.153]
9 86 ms 73 ms 70 ms te0-2-0-5.mpd22.iah01.atlas.cogentco.com [154.54.0.250]
10 85 ms 85 ms 67 ms te0-1-0-2.ccr22.dfw01.atlas.cogentco.com [154.54.5.129]
11 80 ms 82 ms 81 ms te0-3-0-2.ccr22.mci01.atlas.cogentco.com [154.54.25.210]
12 111 ms 108 ms 89 ms te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.4.34]
13 105 ms 97 ms 92 ms te0-6-0-1.ccr22.ord03.atlas.cogentco.com [154.54.6.210]
14 102 ms 126 ms 109 ms 192.205.37.177
15 111 ms 109 ms 106 ms cr2.cgcil.ip.att.net [12.122.84.94]
16 98 ms * * gar2.clboh.ip.att.net [12.122.133.197]
17 110 ms 102 ms 111 ms 12.122.251.50
18 101 ms 103 ms 98 ms 63.240.130.210
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.


4b) Pathping:

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Penguin-PC.ph.cox.net [192.168.0.102]
1 192.168.0.1
2 10.39.0.1
3 172.21.0.116
4 70.169.73.90
5 chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
8 te0-1-0-1.mpd22.lax01.atlas.cogentco.com [154.54.3.9]
9 te0-1-0-6.ccr22.iah01.atlas.cogentco.com [66.28.4.237]
10 te0-2-0-6.ccr22.dfw01.atlas.cogentco.com [154.54.25.213]
11 te0-3-0-2.ccr22.mci01.atlas.cogentco.com [154.54.25.210]
12 te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.4.34]
13 te0-6-0-1.ccr22.ord03.atlas.cogentco.com [154.54.6.210]
14 192.205.37.177
15 cr1.cgcil.ip.att.net [12.122.84.54]
16 gar2.clboh.ip.att.net [12.122.133.197]
17 * 12.122.251.50
18 63.240.130.210
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Penguin-PC.ph.cox.net [192.168.0.102]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% 10.39.0.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 172.21.0.116
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% 70.169.73.90
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
0/ 100 = 0% |
6 28ms 0/ 100 = 0% 0/ 100 = 0% langbprj02-ae2.rd.la.cox.net [68.1.1.19]
0/ 100 = 0% |
7 22ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
0/ 100 = 0% |
8 23ms 0/ 100 = 0% 0/ 100 = 0% te0-1-0-1.mpd22.lax01.atlas.cogentco.com [154.54.3.9]
0/ 100 = 0% |
9 59ms 0/ 100 = 0% 0/ 100 = 0% te0-1-0-6.ccr22.iah01.atlas.cogentco.com [66.28.4.237]
0/ 100 = 0% |
10 67ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-6.ccr22.dfw01.atlas.cogentco.com [154.54.25.213]
0/ 100 = 0% |
11 73ms 1/ 100 = 1% 1/ 100 = 1% te0-3-0-2.ccr22.mci01.atlas.cogentco.com [154.54.25.210]
0/ 100 = 0% |
12 86ms 0/ 100 = 0% 0/ 100 = 0% te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.4.34]
0/ 100 = 0% |
13 87ms 0/ 100 = 0% 0/ 100 = 0% te0-6-0-1.ccr22.ord03.atlas.cogentco.com [154.54.6.210]
7/ 100 = 7% |
14 101ms 7/ 100 = 7% 0/ 100 = 0% 192.205.37.177
93/ 100 = 93% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.84.54]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar2.clboh.ip.att.net [12.122.133.197]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.210

Trace complete.


I want to note that I have the same issues on my laptop as I do on my boyfriends computer on the same connection. I have also bypassed the router and plugged the desktop directly into the modem - same issues. I then went to my parents house about 7 miles away, who also use Cox, and had the same issues there.

And as I stated in my OP, I only seem to lag on some servers and not others. I have tried a few. I have 300-1500 ms on the following servers: Burning Blade, Burning Legion, Lothar. I have less than 100ms on the following servers: Bonechewer, Destromath, and Korgath.
Edited by Aisllyn on 1/11/2013 1:58 PM PST
90 Pandaren Monk
10150
Thank you for looking at this!

1) Stormrage
2) Tucson, AZ
3) Cox Communication
4a) Trace Route:

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 2 ms 1 ms 1 ms 192.168.1.1
2 12 ms 8 ms 11 ms 10.37.28.1
3 11 ms 9 ms 10 ms 70.169.77.160
4 25 ms 23 ms 23 ms 70.169.73.60
5 16 ms 15 ms 14 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 26 ms 26 ms * langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 44 ms 25 ms 34 ms te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
8 26 ms 28 ms 28 ms te0-0-0-2.mpd22.lax01.atlas.cogentco.com [154.54.6.229]
9 64 ms 61 ms 65 ms te0-0-0-5.mpd22.iah01.atlas.cogentco.com [154.54.0.242]
10 66 ms 67 ms 66 ms te0-2-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.25.97]
11 79 ms 85 ms 77 ms te0-3-0-6.ccr22.mci01.atlas.cogentco.com [154.54.46.209]
12 92 ms 89 ms 90 ms te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.4.34]
13 89 ms 89 ms 91 ms te0-5-0-7.ccr22.ord03.atlas.cogentco.com [154.54.44.166]
14 117 ms 104 ms 100 ms 192.205.37.177
15 128 ms 117 ms 105 ms cr1.cgcil.ip.att.net [12.122.84.54]
16 104 ms 112 ms 101 ms gar2.clboh.ip.att.net [12.122.133.197]
17 107 ms 101 ms 102 ms 12.122.251.50
18 101 ms 100 ms 102 ms 63.240.130.210
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.


Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Joseph-PC [192.168.1.2]
1 192.168.1.1
2 10.37.28.1
3 70.169.77.160
4 70.169.73.60
5 chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 * langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
8 te0-2-0-2.mpd22.lax01.atlas.cogentco.com [154.54.30.197]
9 te0-0-0-5.mpd22.iah01.atlas.cogentco.com [154.54.0.242]
10 te0-2-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.25.97]
11 te0-3-0-6.ccr22.mci01.atlas.cogentco.com [154.54.46.209]
12 te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.4.34]
13 te0-5-0-7.ccr22.ord03.atlas.cogentco.com [154.54.44.166]
14 192.205.37.177
15 cr2.cgcil.ip.att.net [12.122.84.94]
16 gar3.cgcil.ip.att.net [12.122.132.213]
17 12.122.251.50
18 63.240.130.210
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Joseph-PC [192.168.1.2]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% 10.37.28.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% 70.169.77.160
0/ 100 = 0% |
4 22ms 0/ 100 = 0% 0/ 100 = 0% 70.169.73.60
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
0/ 100 = 0% |
6 31ms 0/ 100 = 0% 0/ 100 = 0% langbprj02-ae2.rd.la.cox.net [68.1.1.19]
0/ 100 = 0% |
7 26ms 0/ 100 = 0% 0/ 100 = 0% te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
0/ 100 = 0% |
8 26ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-2.mpd22.lax01.atlas.cogentco.com [154.54.30.197]
0/ 100 = 0% |
9 61ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-5.mpd22.iah01.atlas.cogentco.com [154.54.0.242]
0/ 100 = 0% |
10 69ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.25.97]
0/ 100 = 0% |
11 79ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-6.ccr22.mci01.atlas.cogentco.com [154.54.46.209]
0/ 100 = 0% |
12 89ms 0/ 100 = 0% 0/ 100 = 0% te0-4-0-3.ccr22.ord01.atlas.cogentco.com [66.28.4.34]
0/ 100 = 0% |
13 90ms 0/ 100 = 0% 0/ 100 = 0% te0-5-0-7.ccr22.ord03.atlas.cogentco.com [154.54.44.166]
8/ 100 = 8% |
14 105ms 8/ 100 = 8% 0/ 100 = 0% 192.205.37.177
92/ 100 = 92% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.84.94]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att.net [12.122.132.213]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.210

Trace complete.


Have tried the other remedies like everyone else. Thanks again for looking this over for all of us.
Edited by Velnrak on 1/11/2013 1:52 PM PST
Support Forum Agent
Thank you for posting everything I've asked for so far. Our network administrators are investigating and I'll keep you advised as I get updates.
________________________________________________
Monday - Friday, 8 am - 5 pm PST
90 Blood Elf Priest
12985
Thanks much Velnrak! Hope things get sorted out quick. :-(
90 Pandaren Hunter
12795
Same issue as everyone else, although I am nowhere near Arizona... sudden spike in world latency over the last week (after playing for years at <30ms home+world).

I play on Stormreaver, but experience the same problem on Dunemaul.

I live in Niagara Falls, Ontario (Canada)

My ISP is Cogeco.

Both tracert and pathping seem to be unable to get past a certain IP and time out after hop 9.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 11 ms 7 ms 7 ms 10.75.128.1
2 9 ms 16 ms 8 ms 10.75.128.1
3 10 ms 11 ms 11 ms d226-9-93.home.cgocable.net [24.226.9.93]
4 12 ms 10 ms 10 ms 67.69.228.101
5 23 ms 22 ms 23 ms bx5-chicagodt_xe3-1-0-0.net.bell.ca [64.230.186.246]
6 24 ms 26 ms 23 ms 12.249.212.9
7 26 ms 27 ms 23 ms 12.122.251.14
8 25 ms 26 ms 24 ms 63.240.130.206
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
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.


Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Acheron [192.168.0.105]
1 10.75.128.1
2 10.75.128.1
3 d226-9-93.home.cgocable.net [24.226.9.93]
4 67.69.228.101
5 bx5-chicagodt_xe0-1-0_0 [64.230.186.255]
6 12.249.212.9
7 12.122.251.18
8 63.240.130.206
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Acheron [192.168.0.105]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 10.75.128.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.75.128.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% d226-9-93.home.cgocable.net [24.226.9.93]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% 67.69.228.101
100/ 100 =100% |
5 --- 100/ 100 =100% 0/ 100 = 0% bx5-chicagodt_xe0-1-0_0 [64.230.186.255]
0/ 100 = 0% |
6 --- 100/ 100 =100% 0/ 100 = 0% 12.249.212.9
0/ 100 = 0% |
7 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.18
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.206

Trace complete.
Edited by Mintak on 1/11/2013 2:02 PM PST
This topic is locked.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]