Latency Issues - Phoenix, Arizona - Cox Cable

Technical Support
Prev 1 2 3 4 7 Next
You go from "knowing" that they fixed it, to speculating that they fixed it, then to a theory. Crazy.


Mine is actually fixed but only when I am on the actual Frostmane server. When I go into an instance, my home stays the same .. about 25 .. and my world goes up.. 150. My ISP routed me around cognetco .. my theory was if it was fixed for other people that they did the same.
I am having this problem with Comcast as my ISP. After extensive tech support from Blizz and from Comcast. We have traced the problem to AT&T. This is not the first time this has happened. In fact, earlier this year, the very IP address I'm having problems with, and it looks like many of you are being routed through the same hub, was causing people to not be able to connect at all.

Blizz has instructed me to pester my ISP more to get them to work with AT&T and/or create a thread and if the thread gets enough attention of people with the same problem, then they can take all the evidence to AT&T for us and work with them.

This thread already exists, so I will be adding to it for now and requesting a sticky, and I have notified Blizz tech support about this thread directly as well.

Pleas post pathping tests in addition to the traceroutes, hopefully we'll get this worked out together.

1 11ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 48ms 0/ 100 = 0% 0/ 100 = 0% 96.120.0.5
0/ 100 = 0% |
3 38ms 1/ 100 = 1% 1/ 100 = 1% te-9-1-ur02.lascruces.nm.albuq.comcast.net [69.139.177.5]
0/ 100 = 0% |
4 39ms 1/ 100 = 1% 1/ 100 = 1% te-0-1-0-1-ar04.albuquerque.nm.albuq.comcast.net [68.85.65.9]
0/ 100 = 0% |
5 59ms 1/ 100 = 1% 1/ 100 = 1% te-0-0-0-4-cr01.losangeles.ca.ibone.comcast.net [68.86.90.9]
0/ 100 = 0% |
6 96ms 0/ 100 = 0% 0/ 100 = 0% pos-0-3-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.87.210]
0/ 100 = 0% |
7 78ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.25
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.128.98]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.29]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.30.26]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.31.86]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar18.cgcil.ip.att.net [12.122.99.21]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.18
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.202

Trace complete.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 10.0.0.1
2 12 ms 13 ms 5 ms 96.120.0.5
3 8 ms 7 ms 8 ms te-9-1-ur02.lascruces.nm.albuq.comcast.net [69.139.177.5]
4 12 ms 20 ms 14 ms te-0-1-0-1-ar04.albuquerque.nm.albuq.comcast.net [68.85.65.9]
5 33 ms 31 ms 36 ms te-0-0-0-4-cr01.losangeles.ca.ibone.comcast.net [68.86.90.9]
6 38 ms 34 ms 39 ms pos-0-3-0-0-pe01.600wseventh.ca.ibone.comcast.net [68.86.87.210]
7 39 ms 34 ms 35 ms 192.205.37.25
8 65 ms 62 ms 63 ms cr1.la2ca.ip.att.net [12.122.128.98]
9 67 ms 67 ms 65 ms cr1.slkut.ip.att.net [12.122.30.29]
10 77 ms 71 ms 71 ms cr2.dvmco.ip.att.net [12.122.30.26]
11 65 ms 67 ms 67 ms cr1.cgcil.ip.att.net [12.122.31.86]
12 72 ms 71 ms 74 ms gar18.cgcil.ip.att.net [12.122.99.21]
13 64 ms 62 ms 63 ms 12.122.251.18
14 * 72 ms 75 ms 63.240.130.202
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.
Good news everyone. Tech support just gave me a response saying that they'll look closer into this thread and it will likely get a blue post and hopefully a sticky. Try redirecting other people here too if they are having problems with a traceroute/pathtping including att.net in it.

Here's the quote from tech support: "Thanks for submitting your pathping information to that thread! It's Sunday, so a blue post reaction to that thread might be a tad slow (they mostly work mon-fri shifts). The more reports we'll get, the better!

We might not get a blue post on it today, but very early tomorrow. I'm emailing information on this to a higher up to make sure there's extra visibility on it though!"
I am with ATT and am having huge latency issues. I don't know how to post a traceroute but it has gotten to the point where game play is impossible with world latency on Shadow Council in the 1300s.

I have done all the deleting WTF, Cache, Interface also. No help.
Wereknight, you should post a pathping as described here: https://us.battle.net/support/en/article/running-a-pathping-test
Good news everyone. Tech support just gave me a response saying that they'll look closer into this thread and it will likely get a blue post and hopefully a sticky. Try redirecting other people here too if they are having problems with a traceroute/pathtping including att.net in it.

Here's the quote from tech support: "Thanks for submitting your pathping information to that thread! It's Sunday, so a blue post reaction to that thread might be a tad slow (they mostly work mon-fri shifts). The more reports we'll get, the better!

We might not get a blue post on it today, but very early tomorrow. I'm emailing information on this to a higher up to make sure there's extra visibility on it though!"


Is there anything else I could personally do to help get this stuff fixed. I am having these problems as well, along with my forum avatar and server not showing up? what the hell?
So these are my results

PathPing
Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Tanner-PC [192.168.1.2]
1 192.168.1.1
2 10.128.16.1
3 172.21.1.62
4 72.215.229.22
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-0-0-32.ccr23.lax05.atlas.cogentco.com [38.104.84.13]
8 be2179.ccr22.lax01.atlas.cogentco.com [154.54.41.81]
9 be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
10 be2146.ccr22.dfw01.atlas.cogentco.com [154.54.25.242]
11 be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.54]
12 192.205.36.221
13 cr1.dlstx.ip.att.net [12.122.139.18]
14 cr1.phmaz.ip.att.net [12.122.28.182]
15 12.123.158.5
16 12-122-254-218.attens.net [12.122.254.218]
17 mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
18 * * *
Computing statistics for 425 seconds...

Trace Route

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 10 ms 14 ms 10.128.16.1
3 11 ms 8 ms 13 ms 172.21.1.62
4 13 ms 17 ms 13 ms 72.215.229.22
5 9 ms 11 ms 11 ms mcdldsrj01-ae2.0.rd.ph.cox.net [70.169.76.225]
6 25 ms 22 ms 31 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 24 ms 25 ms 31 ms te0-0-0-32.ccr23.lax05.atlas.cogentco.com [38.104.84.13]
8 23 ms 25 ms 22 ms be2181.mpd21.lax01.atlas.cogentco.com [154.54.41.113]
9 58 ms 63 ms 61 ms be2067.mpd21.iah01.atlas.cogentco.com [154.54.7.161]
10 63 ms 67 ms 65 ms be2144.ccr21.dfw01.atlas.cogentco.com [154.54.25.106]
11 67 ms 72 ms 65 ms be2031.ccr21.dfw03.atlas.cogentco.com [154.54.7.46]
12 107 ms * 111 ms 192.205.36.221
13 * 105 ms 107 ms cr1.dlstx.ip.att.net [12.122.139.18]
14 103 ms 105 ms 103 ms cr1.phmaz.ip.att.net [12.122.28.182]
15 104 ms 106 ms 103 ms 12.123.158.5
16 101 ms 105 ms 103 ms 12-122-254-218.attens.net [12.122.254.218]
17 102 ms 109 ms 107 ms mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
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.
Is there anything else I could personally do to help get this stuff fixed. I am having these problems as well, along with my forum avatar and server not showing up? what the hell?


Pester the tar out of your ISP, attack from both sides. Technically it's their job to make sure you have reliable internet, but when Blizz gets enough complaints on this they can take the evidence and pester as well.
Pathping
Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Kyle-PC.ftrdhcpuser.net [192.168.1.4]
1 myrouter.home [192.168.1.1]
2 static-50-46-224-1.evrt.wa.frontiernet.net [50.46.224.1]
3 50.34.2.173
4 ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.101]
5 ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.126]
6 12.249.36.33
7 cr81.st0wa.ip.att.net [12.122.111.10]
8 cr82.st0wa.ip.att.net [12.122.5.150]
9 cr2.ptdor.ip.att.net [12.122.5.230]
10 cr1.ptdor.ip.att.net [12.122.30.141]
11 cr1.sffca.ip.att.net [12.122.30.146]
12 cr1.la2ca.ip.att.net [12.122.3.122]
13 gar20.la2ca.ip.att.net [12.122.128.181]
14 12-122-254-238.attens.net [12.122.254.238]
15 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Kyle-PC.ftrdhcpuser.net [192.168.1.4]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% myrouter.home [192.168.1.1]
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% static-50-46-224-1.evrt.wa.frontiernet.net [50.46.224.1]
0/ 100 = 0% |
3 78ms 0/ 100 = 0% 0/ 100 = 0% 50.34.2.173
0/ 100 = 0% |
4 76ms 0/ 100 = 0% 0/ 100 = 0% ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.101]
0/ 100 = 0% |
5 47ms 0/ 100 = 0% 0/ 100 = 0% ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.126]
0/ 100 = 0% |
6 20ms 0/ 100 = 0% 0/ 100 = 0% 12.249.36.33
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr81.st0wa.ip.att.net [12.122.111.10]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr82.st0wa.ip.att.net [12.122.5.150]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.ptdor.ip.att.net [12.122.5.230]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.ptdor.ip.att.net [12.122.30.141]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.sffca.ip.att.net [12.122.30.146]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.3.122]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.

Trace Route

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms myrouter.home [192.168.1.1]
2 4 ms 4 ms 18 ms static-50-46-224-1.evrt.wa.frontiernet.net [50.46.224.1]
3 7 ms 8 ms 9 ms 50.34.2.173
4 13 ms 10 ms 9 ms ae3---0.cor02.sttl.wa.frontiernet.net [74.40.1.101]
5 10 ms 14 ms 18 ms ae1---0.cbr01.sttl.wa.frontiernet.net [74.40.5.126]
6 57 ms 49 ms 24 ms 12.249.36.33
7 46 ms 43 ms 43 ms cr81.st0wa.ip.att.net [12.122.111.10]
8 51 ms 46 ms 48 ms cr82.st0wa.ip.att.net [12.122.5.150]
9 48 ms 46 ms 49 ms cr2.ptdor.ip.att.net [12.122.5.230]
10 45 ms 47 ms 43 ms cr1.ptdor.ip.att.net [12.122.30.141]
11 45 ms 44 ms 48 ms cr1.sffca.ip.att.net [12.122.30.146]
12 49 ms 50 ms 47 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 43 ms 42 ms 43 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 43 ms 43 ms 44 ms 12-122-254-238.attens.net [12.122.254.238]
15 43 ms 43 ms 43 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
25/24 home/world MS since yesterday morning until as i'm typing this. Safe to say they fixed my latency issue. Hopefully the rest of you still experiencing this get some relief, because it sure does feel good hovering around 20 ms :)
I have always had around 30 latency, however for the last 3-4 weeks now it stays around 100-130 going down to about 70 in the dead of night. I have my own thread on this that has been getting no attention from the blues so I am posting here as well. The issue appears to somewhere in between my ISP and blizzard servers. If the only time I can que competitive arena with my latency is in the dead of night I might as well cancel my subscription. I have plenty more pathping's/tracerts if needed.
http://us.battle.net/wow/en/forum/topic/10787138996?page=2#21

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Scott-PC [192.168.1.74]
1 192.168.1.254
2 10.194.48.1
3 209.115.198.117
4 209.115.198.105
5 * edtnab02ca01.bb.telus.com [154.11.94.228]
6 chcgildtgr00.bb.telus.com [154.11.11.34]
7 d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181]
8 ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221]
9 192.205.32.193
10 cr2.cgcil.ip.att.net [12.122.132.198]
11 gar6.ipsin.ip.att.net [12.122.132.241]
12 12.122.251.18
13 63.240.130.202
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Scott-PC [192.168.1.74]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.254
0/ 100 = 0% |
2 1ms 0/ 100 = 0% 0/ 100 = 0% 10.194.48.1
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 209.115.198.117
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 209.115.198.105
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% edtnab02ca01.bb.telus.com [154.11.94.228]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% chcgildtgr00.bb.telus.com [154.11.11.34]
0/ 100 = 0% |
7 62ms 0/ 100 = 0% 0/ 100 = 0% d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181]
0/ 100 = 0% |
8 50ms 0/ 100 = 0% 0/ 100 = 0% ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221]
1/ 100 = 1% |
9 106ms 1/ 100 = 1% 0/ 100 = 0% 192.205.32.193
99/ 100 = 99% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.132.198]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% gar6.ipsin.ip.att.net [12.122.132.241]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.18
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.202

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 2 ms 1 ms 1 ms 10.194.48.1
3 1 ms 1 ms 1 ms 209.115.198.117
4 2 ms 2 ms 2 ms 209.115.198.105
5 3 ms 2 ms 1 ms edtnab02ca01.bb.telus.com [154.11.94.228]
6 44 ms 47 ms 44 ms chcgildtgr00.bb.telus.com [154.11.11.34]
7 60 ms 60 ms 62 ms d1-3-1-0-7.r04.chcgil09.us.bb.gin.ntt.net [128.242.186.181]
8 59 ms 58 ms 58 ms ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221]
9 111 ms 104 ms 105 ms 192.205.32.193
10 111 ms 99 ms 107 ms cr2.cgcil.ip.att.net [12.122.132.198]
11 100 ms 100 ms 98 ms gar6.ipsin.ip.att.net [12.122.132.241]
12 108 ms 110 ms 243 ms 12.122.251.18
13 108 ms 100 ms 108 ms 63.240.130.202
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.
On Junchuri's request, just copy and pasting my ping tests and stuff from yesterday. I apologise if I'm breaking any posting ToS by copy and pasting this.

Hey what's up everybody,

I've been getting really cumbersome latency for the past few weeks or so during peak-hour times. Before they were occurring, my ms would only be about 50 ms higher during the peak hours but now they're something like 200-300 points higher.

It does tend to subside around 6pm my time (which is around midnight in some parts of the US I believe?) and it does however only seems to affect my world MS, as seen in the screen shot below:

http://imgur.com/QgjlBIl

Any help would be appreciated!

Tracer Route


Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 1 ms 1 ms RTA1025W.home [192.168.1.1]
2 30 ms 29 ms 29 ms 10.20.21.89
3 30 ms 29 ms 36 ms syd-sot-ken-csw1-ten-4-4.tpgi.com.au [203.29.135.165]
4 32 ms 31 ms 30 ms syd-sot-ken-crs2-Te-0-6-0-8.tpgi.com.au [202.7.214.165]
5 226 ms 224 ms 227 ms te0-0-0-19.ccr22.lax04.atlas.cogentco.com [38.104.210.53]
6 223 ms 225 ms 230 ms be2022.mpd22.lax01.atlas.cogentco.com [154.54.88.1]
7 260 ms 264 ms 266 ms be2068.mpd22.iah01.atlas.cogentco.com [154.54.7.157]
8 267 ms 274 ms 270 ms be2147.ccr22.dfw01.atlas.cogentco.com [154.54.27.18]
9 274 ms 278 ms 277 ms be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.54]
10 309 ms 311 ms 307 ms 192.205.36.221
11 292 ms 288 ms 292 ms cr2.dlstx.ip.att.net [12.122.138.18]
12 293 ms * 292 ms cr2.la2ca.ip.att.net [12.122.28.178]
13 355 ms 292 ms 288 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 301 ms 289 ms 294 ms 12-122-254-234.attens.net [12.122.254.234]
15 293 ms 290 ms 289 ms 12.129.193.254
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.209.68 over a maximum of 30 hops

0 hahhah.home [192.168.1.3]
1 RTA1025W.home [192.168.1.1]
2 10.20.21.89
3 syd-sot-ken-csw1-ten-4-4.tpgi.com.au [203.29.135.165]
4 syd-sot-ken-crs2-Te-0-6-0-8.tpgi.com.au [202.7.214.165]
5 te0-0-0-19.ccr22.lax04.atlas.cogentco.com [38.104.210.53]
6 be2020.ccr22.lax01.atlas.cogentco.com [154.54.88.17]
7 be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
8 be2146.ccr22.dfw01.atlas.cogentco.com [154.54.25.242]
9 be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.54]
10 192.205.36.221
11 cr2.dlstx.ip.att.net [12.122.138.18]
12 cr2.la2ca.ip.att.net [12.122.28.178]
13 gar29.la2ca.ip.att.net [12.122.129.241]
14 12-122-254-234.attens.net [12.122.254.234]
15 12.129.193.254
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 hahhah.home [192.168.1.3]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% RTA1025W.home [192.168.1.1]
0/ 100 = 0% |
2 33ms 0/ 100 = 0% 0/ 100 = 0% 10.20.21.89
0/ 100 = 0% |
3 37ms 0/ 100 = 0% 0/ 100 = 0% syd-sot-ken-csw1-ten-4-4.tpgi.com.au [203.29.135.165]
0/ 100 = 0% |
4 38ms 0/ 100 = 0% 0/ 100 = 0% syd-sot-ken-crs2-Te-0-6-0-8.tpgi.com.au [202.7.214.165]
0/ 100 = 0% |
5 226ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-19.ccr22.lax04.atlas.cogentco.com [38.104.210.53]
0/ 100 = 0% |
6 226ms 0/ 100 = 0% 0/ 100 = 0% be2020.ccr22.lax01.atlas.cogentco.com [154.54.88.17]
0/ 100 = 0% |
7 263ms 0/ 100 = 0% 0/ 100 = 0% be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
0/ 100 = 0% |
8 287ms 0/ 100 = 0% 0/ 100 = 0% be2146.ccr22.dfw01.atlas.cogentco.com [154.54.25.242]
0/ 100 = 0% |
9 271ms 0/ 100 = 0% 0/ 100 = 0% be2032.ccr21.dfw03.atlas.cogentco.com [154.54.6.54]
5/ 100 = 5% |
10 315ms 5/ 100 = 5% 0/ 100 = 0% 192.205.36.221
95/ 100 = 95% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.122.138.18]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 12.129.193.254

Trace complete.

Still having the same problems. used to be around 30MS still sitting around 100+ today.
bump...

I'm starting to get real frustrated with blizz here, tell me they'll do something and it doesn't happen, hope they're stupidly busy with this right now.

Open tickets and pester ISPs. Just ran another pathping and it looks the same.
Bump
Still having problems here
Their answer is : Contact your ISP. Well, guess what, multiple ISPs are having problems. It must be all of them, right? Jesus, this is like talking to a 2 year old. In fact, my girlfriend's 4 year old is smarter, and probably could come up with a better response, than this.
Having massive latency problems since Friday 13th December.
Bump submitted a ticket and I recommend everyone do the same nothing will get fixed until it be comes a big enough problem

Edit: Pretty much was just told to pester my ISP which so far has done nothing.
BUMP, told to phone ISP as well.
I have completely uninstalled and reinstalled about a week ago (left addons off) and still have the d/c issues. All of my drivers are up to date as well so that's not the issue. I've tried every troubleshooting advice listed to no avail. I even Spent $300 on a new router and hardwired it. The issues seems to be bliz servers from what I can tell. Here is the pathping I ran showing 100% data loss at bliz's AT&T servers.

Tracing route to 63.240.161.189 over a maximum of 30 hops


1 router.asus.com [192.168.1.1]
2 bdl1.eas-ubr2.atw-eas.pa.cable.rcn.net [10.48.192.1]
3 bvi4.aggr1.phdl.pa.rcn.net [208.59.252.2]
4 te-3-1.car2.Philadelphia1.Level3.net [4.78.154.89]
5 ae-3-3.bar1.Philadelphia1.Level3.net [4.69.153.97]
6 ae-6-6.ebr1.NewYork1.Level3.net [4.69.133.170]
7 ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
8 ae-1-60.edge3.NewYork1.Level3.net [4.69.155.17]
9 att-level3.newyork1.level3.net [4.68.63.142]
10 cr1.n54ny.ip.att.net [12.122.131.102]
11 cr2.cgcil.ip.att.net [12.122.1.2]
12 gar6.ipsin.ip.att.net [12.122.132.241]
13 12.122.251.14
14 63.240.130.206
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.asus.com [192.168.1.1]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% bdl1.eas-ubr2.atw-eas.pa.cable.rcn.net [10.48.192.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% bvi4.aggr1.phdl.pa.rcn.net [208.59.252.2]
0/ 100 = 0% |
4 23ms 0/ 100 = 0% 0/ 100 = 0% te-3-1.car2.Philadelphia1.Level3.net [4.78.154.89]
0/ 100 = 0% |
5 12ms 0/ 100 = 0% 0/ 100 = 0% ae-3-3.bar1.Philadelphia1.Level3.net [4.69.153.97]
0/ 100 = 0% |
6 13ms 0/ 100 = 0% 0/ 100 = 0% ae-6-6.ebr1.NewYork1.Level3.net [4.69.133.170]
0/ 100 = 0% |
7 13ms 0/ 100 = 0% 0/ 100 = 0% ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
0/ 100 = 0% |
8 15ms 0/ 100 = 0% 0/ 100 = 0% ae-1-60.edge3.NewYork1.Level3.net [4.69.155.17]
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% att-level3.newyork1.level3.net [4.68.63.142]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.131.102]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar6.ipsin.ip.att.net [12.122.132.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.14
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.206

Trace complete.

Join the Conversation

Return to Forum