High Latency related to Battlegroup?

(Locked)

90 Blood Elf Priest
12985
I've noticed all of the high latency threads and the trace routes. One thing I've noticed after server hopping and checking latency is that I only lag on realms of certain battle groups. I play on Burning Blade, which I lag terribly on. I then checked my other servers - Korgath, Destromath, Bonechewer - I did NOT lag on these. All of these are different battle groups. I then logged into Burning Legion, same battle group as Burning Blade, and I DO lag on that server. I then checked Lothar, which is a different battlegroup than all of the above mentioned, but someone posted that they are lagging on it. I AM lagging on this one as well.

I know nothing about how this all works, but it seems that certain connections are having connectivity issues with specific battle.net servers. Are all servers on the same battlegroup hosted by the same server? Are we just having communication issues with specific servers?

All I know is I really wish this could be resolved...my guild is now clearing normal mode instead of being able to work on H Amber-Shaper because I am not there to heal. This is very very frustrating and depressing that I'm holding the guild back and its not in my control to fix. Help! :-(
90 Orc Hunter
11440
/sign
/rage
90 Blood Elf Priest
10090
Lag severely on Bleeding Hollow, not on Executus or Sen'jin.

Connecting from AZ.
90 Blood Elf Priest
12985
I'm also connecting from AZ. Chandler, AZ. Cox Communication Cable.

Lag started for me a few days ago, not sure exactly, but became high enough so I couldn't raid efficiently about 24 hours ago.
Edited by Aisllyn on 1/10/2013 8:00 PM PST
100 Tauren Druid
20770
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.
90 Undead Mage
10480
I'm also connecting from AZ. Chandler, AZ. Cox Communication Cable.

Lag started for me a few days ago, not sure exactly, but became high enough so I couldn't raid efficiently about 24 hours ago.


Im Scottsdale, AZ with Cox. Start yesterday for me. Today its be unplayable for a good majority of the time.

Mostly during PM hours.

Perhaps its IP related with Cox routing to Blizz servers or whatever?
Edited by Aycheff on 1/10/2013 8:15 PM PST
90 Tauren Druid
6595
01/10/2013 07:59 PMPosted by Aisllyn
I'm also connecting from AZ. Chandler, AZ. Cox Communication Cable.


This is also my city and isp. Lag started about 2 days ago for me, now its just unplayable.
90 Undead Mage
10480
Lets all go raid Cox.

On real note, what can we do to fix it?
90 Blood Elf Priest
12985


On real note, what can we do to fix it?


Tech support response would be nice :-/
100 Tauren Druid
20770
01/10/2013 08:27 PMPosted by Aycheff
Lets all go raid Cox.


Not sure it's just cox that is at fault. I blame AT&T personally...


Tracing route to 206.18.99.53 over a maximum of 30 hops

1 1 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 5 ms 4 ms 4 ms 217.32.143.41
3 5 ms 5 ms 5 ms 217.32.143.94
4 6 ms 6 ms 6 ms 212.140.206.130
5 6 ms 7 ms 6 ms 31.55.165.225
6 6 ms 6 ms 6 ms 31.55.165.109
7 6 ms 6 ms 6 ms acc2-10GigE-1-2-0.mr.21cn-ipp.bt.net [109.159.25
0.198]
8 17 ms 15 ms 15 ms core2-te0-13-0-0.ealing.ukcore.bt.net [109.159.2
50.139]
9 14 ms 14 ms 15 ms transit1-xe9-0-0.ealing.ukcore.bt.net [62.6.200.
189]
10 21 ms 14 ms 14 ms t2c3-xe-10-0-0.uk-eal.eu.bt.net [166.49.168.1]
11 14 ms 20 ms * tengigabitethernet8-4.ar7.lon3.gblx.net [64.215.
25.245]
12 111 ms 112 ms 111 ms 192.205.32.125
13 * * * Request timed out.
14 109 ms 109 ms 109 ms gar3.cgcil.ip.att.net [12.122.132.213]
15 110 ms 110 ms 110 ms 12.122.251.22
16 284 ms 207 ms 211 ms 63.240.130.214


That's the traceroute for me.
90 Gnome Monk
9145
mesa, az...same issue, cox said its on blizzards end with the att hops, nothing they can do...
90 Blood Elf Priest
14860
Same issue, same ISP, same area. I've got a tracert to Illidan from last Tuesday (before the issue started) and yesterday (when the issue started for me). Not going to post them, but I have them if tech support wants them.
phoenix, az....cox cable, both dethecus and alleria are unplayable, rampage battlegroup. All battlegroups mentioned as unplayable so far reside in the Chicago datacenter
90 Blood Elf Priest
12985
I hate cox a lot more than I hate AT&T or Blizz, so I still blame Cox. Afterall....they seem to be the only ones having issues connecting smoothly with Blizz/AT&T, no one else in my raid has any lag issues.
90 Blood Elf Priest
10090
Its ATT/Cogent and isolated to Chicago datacenter.
90 Blood Elf Priest
14860
01/10/2013 08:45 PMPosted by Buffzplz
Its ATT/Cogent and isolated to Chicago datacenter.


This definitely seems to be the case.
90 Troll Shaman
9375
Also Cox, in Sierra Vista, just posted my own thread, then read this one.
85 Draenei Priest
6970
40St. and Thunderbird, North Phoenix. Same issue. FML, no raiding tonight.
90 Blood Elf Priest
10090
Interesting addition. Guildie also in AZ has CenturyLink DSL and has 0 lag issues, so CenturyLink must route differently than Cox in AZ.
100 Tauren Druid
20770
Interesting addition. Guildie also in AZ has CenturyLink DSL and has 0 lag issues, so CenturyLink must route differently than Cox in AZ.


I use BT in the united kingdom and I'm hitting the lag from whatever servers are causing this so yeah probably. It might just be rng who gets routed through what though.
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)

Reported!

[Close]