Diablo® III

Blizz on Disconnect"its your ISP"Wrong Proof pic inside

They told me to use D3TR and that i'd see it's my isp responsible for "random latency spikes and rubberbanding"

Mmmmk!

here is your D3TR blizz.

http://i10.photobucket.com/albums/a129/mikeglaser/BlizzMSEC_zps9c542308.png

Even if there were east coast centers, we would still have to go through 10+ hops to get there. Ever do a tracert on the useast.battle.net? It's about the same for me and im in chicago. I STILL go through 8+ blizzard servers until i reach my final game IP.

And for those saying, it's at&t or some other ISP not blizzard.. Blizzard has the right to change from what lines they use you know.. didn't you notice my tracert to google? I use megapath as my provider, yet when i connected to Diablo 3 I went through 3 servers of Level3 Communication(ISP), instead of megapath.
Diablo 3:
4 28 ms 124 ms 50 ms ge-3-7.car2.Chicago1.Level3.net [4.71.182.41] Chicago
5 51 ms 27 ms 27 ms ae-31-51.ebr1.Chicago1.Level3.net [4.69.138.30] Chicago
6 26 ms 26 ms 26 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190] Chicago
Then take a look at HOW MANY of their servers i have to hop through!!!
1server 67 ms 67 ms 68 ms cr1.cgcil.ip.att.net [12.122.133.34]
2server 69 ms 68 ms 66 ms cr2.dvmco.ip.att.net [12.122.31.85]
3server 71 ms 71 ms 72 ms cr1.slkut.ip.att.net [12.122.30.25]
4server 72 ms 72 ms 71 ms cr2.la2ca.ip.att.net [12.122.30.30]
5server 68 ms 67 ms 67 ms gar29.la2ca.ip.att.net [12.122.129.241]
6server 67 ms 67 ms 66 ms 12.122.251.190
7server 65 ms 65 ms 65 ms 12.129.193.254

Any website I visit(not just google.com)
3 8 ms 8 ms 18 ms ge-0-1-2-0.chcgilgb-mxc1.bb.megapath.net [155.229.70.57]
4 8 ms 8 ms 42 ms ae0-0.chcgilgb-mxc2.bb.megapath.net [155.229.57.22]
^^^^ this is my ISP (megapath) and their servers here in chicago. But when i connect to diablo3 i go through three level3Comm(isp) servers then through 7 USbattle.net servers... Ridiculous..

And for all those people saying 'Google has the money to support data centers all over" I did a tracert for a BLOG news website whom i guarantee makes way less $$ than blizzard.

Tracing route to drudgereport.com [98.158.27.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms (my IP )
2 9 ms 8 ms 8 ms 64.145.107.1
3 8 ms 8 ms 8 ms 155.229.57.41
4 9 ms 8 ms 10 ms ge-0-1-2-0.chcgilgb-mxc1.bb.megapath.net [155.229.70.57]
5 8 ms 8 ms 11 ms ae0-0.chcgilgb-mxc2.bb.megapath.net [155.229.57.22]
6 68 ms 66 ms 67 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
7 69 ms 67 ms 67 ms ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]
8 69 ms 68 ms 68 ms 8X8-INC.car2.SanJose1.Level3.net [4.28.8.38]
9 69 ms 68 ms 68 ms 98.158.27.203
Trace complete.

Oh look.. EIGHT hops. and i still go through my ISP servers here in chicago. Blizzard needs to fix this crazy hop issue. I shouldn't need to go through SEVEN hops on their servers all taking place on att(which are blizz servers btw, not AT&T) quoted fromBlizzards support section
To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net.


Now for all the people thinking that this is due to not having datacacenters in Central US/East Coast I did tracert for a WoW Server. (i never played WoW, but it's easy to find the servers)
Central WoW Server Fizzcrank(it's in new york but they have it under Central for whatever reason

Tracing route to 199.107.25.29 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 64.145.107.1
3 8 ms 10 ms 8 ms 155.229.57.41
4 126 ms 31 ms 172 ms ge-3-7.car2.Chicago1.Level3.net [4.71.182.41]
5 27 ms 25 ms 26 ms ae-32-52.ebr2.Chicago1.Level3.net [4.69.138.62]
6 27 ms 26 ms 26 ms ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194]
7 26 ms 26 ms 26 ms 4.69.158.157
8 29 ms 27 ms 27 ms 192.205.37.149
[b] 9 33 ms 31 ms 31 ms cr1.cgcil.ip.att.net [12.122.133.34]
10 31 ms 31 ms
Edited by Michael#13785 on 3/26/2013 6:56 AM PDT
Reply Quote
Don't get me wrong, i typically have incredible gameplay. However recently I've been getting random RubberBand issues. The spikes in latency (in my photo) is the reason why, which all occur on Blizzard's servers.
They need to fix it.

I have d3tr running in the background while I play D3.. typically i'm around 60-80msec.. But when i see arrows stop coming out of my crossbow, and see msec go to 250. I hit pause.
I then alt-tab
And i always see spikes on hop 8-15 which are all blizzards servers...
I wait until the latency comes back down and i go back into game and un-pause.. Many times my screen will look like this:

http://i10.photobucket.com/albums/a129/mikeglaser/close1_zpscbcf911b.png
Edited by Michael#13785 on 3/26/2013 6:41 AM PDT
Reply Quote
Quite interesting......

Chi-town Represent!!!
Reply Quote
What would be the incentive for Bliz to fix it? They will make no additional money, if it were corrected. It would likely cost money to correct. It is unlikely to add new players either way. At this late date I doubt many users are leaving over this issue, else they should have left long ago.

I had many problems with lag and even a rare disconnect. I finally got my ISP to come out and test the modem and found it was not set correctly and I was not getting my full bandwidth. With that corrected I have seen no lag and that was using a router. Now I had them move the modem and I direct connect at ~66mb.

I had run traces in the past and was getting 30+ hops as I am in Florida.
Reply Quote
Quite interesting......

Chi-town Represent!!!

+1
Reply Quote
im not sure what all this means, but stick it to the man!
Reply Quote
yeah well... i dunno what'll happen with all this.
Reply Quote
They told me to use D3TR and that i'd see it's my isp responsible for "random latency spikes and rubberbanding"

Mmmmk!

here is your D3TR blizz.

http://i10.photobucket.com/albums/a129/mikeglaser/BlizzMSEC_zps9c542308.png

Even if there were east coast centers, we would still have to go through 10+ hops to get there. Ever do a tracert on the useast.battle.net? It's about the same for me and im in chicago. I STILL go through 8+ blizzard servers until i reach my final game IP.

And for those saying, it's at&t or some other ISP not blizzard.. Blizzard has the right to change from what lines they use you know.. didn't you notice my tracert to google? I use megapath as my provider, yet when i connected to Diablo 3 I went through 3 servers of Level3 Communication(ISP), instead of megapath.
Diablo 3:
4 28 ms 124 ms 50 ms ge-3-7.car2.Chicago1.Level3.net [4.71.182.41] Chicago
5 51 ms 27 ms 27 ms ae-31-51.ebr1.Chicago1.Level3.net [4.69.138.30] Chicago
6 26 ms 26 ms 26 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190] Chicago
Then take a look at HOW MANY of their servers i have to hop through!!!
1server 67 ms 67 ms 68 ms cr1.cgcil.ip.att.net [12.122.133.34]
2server 69 ms 68 ms 66 ms cr2.dvmco.ip.att.net [12.122.31.85]
3server 71 ms 71 ms 72 ms cr1.slkut.ip.att.net [12.122.30.25]
4server 72 ms 72 ms 71 ms cr2.la2ca.ip.att.net [12.122.30.30]
5server 68 ms 67 ms 67 ms gar29.la2ca.ip.att.net [12.122.129.241]
6server 67 ms 67 ms 66 ms 12.122.251.190
7server 65 ms 65 ms 65 ms 12.129.193.254

Any website I visit(not just google.com)
3 8 ms 8 ms 18 ms ge-0-1-2-0.chcgilgb-mxc1.bb.megapath.net [155.229.70.57]
4 8 ms 8 ms 42 ms ae0-0.chcgilgb-mxc2.bb.megapath.net [155.229.57.22]
^^^^ this is my ISP (megapath) and their servers here in chicago. But when i connect to diablo3 i go through three level3Comm(isp) servers then through 7 USbattle.net servers... Ridiculous..

And for all those people saying 'Google has the money to support data centers all over" I did a tracert for a BLOG news website whom i guarantee makes way less $$ than blizzard.

Tracing route to drudgereport.com [98.158.27.203]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms (my IP )
2 9 ms 8 ms 8 ms 64.145.107.1
3 8 ms 8 ms 8 ms 155.229.57.41
4 9 ms 8 ms 10 ms ge-0-1-2-0.chcgilgb-mxc1.bb.megapath.net [155.229.70.57]
5 8 ms 8 ms 11 ms ae0-0.chcgilgb-mxc2.bb.megapath.net [155.229.57.22]
6 68 ms 66 ms 67 ms ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
7 69 ms 67 ms 67 ms ae-3-3.ebr2.SanJose1.Level3.net [4.69.132.57]
8 69 ms 68 ms 68 ms 8X8-INC.car2.SanJose1.Level3.net [4.28.8.38]
9 69 ms 68 ms 68 ms 98.158.27.203
Trace complete.

Oh look.. EIGHT hops. and i still go through my ISP servers here in chicago. Blizzard needs to fix this crazy hop issue. I shouldn't need to go through SEVEN hops on their servers all taking place on att(which are blizz servers btw, not AT&T) quoted fromBlizzards support section
To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net.


Now for all the people thinking that this is due to not having datacacenters in Central US/East Coast I did tracert for a WoW Server. (i never played WoW, but it's easy to find the servers)
Central WoW Server Fizzcrank(it's in new york but they have it under Central for whatever reason

Tracing route to 199.107.25.29 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 64.145.107.1
3 8 ms 10 ms 8 ms 155.229.57.41
4 126 ms 31 ms 172 ms ge-3-7.car2.Chicago1.Level3.net [4.71.182.41]
5 27 ms 25 ms 26 ms ae-32-52.ebr2.Chicago1.Level3.net [4.69.138.62]
6 27 ms 26 ms 26 ms ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194]
7 26 ms 26 ms 26 ms 4.69.158.157
8 29 ms 27 ms 27 ms 192.205.37.149
[b] 9 33 ms 31 ms 31 ms cr1.cgcil.ip.att.net [12.122.133.34]
10 31 ms 31 ms


This guy has a Great point.

What would be the incentive for Bliz to fix it? They will make no additional money, if it were corrected. It would likely cost money to correct. It is unlikely to add new players either way. At this late date I doubt many users are leaving over this issue, else they should have left long ago.

I had many problems with lag and even a rare disconnect. I finally got my ISP to come out and test the modem and found it was not set correctly and I was not getting my full bandwidth. With that corrected I have seen no lag and that was using a router. Now I had them move the modem and I direct connect at ~66mb.

I had run traces in the past and was getting 30+ hops as I am in Florida.


Get your facts straight or go back to WoW !@#$. D3 doesnt like you now %^-*
Reply Quote
03/26/2013 06:06 AMPosted by Michael
Ever do a tracert on the useast.battle.net?

If I understand right (and it's possible I don't), that URL is only for the old-school Battle.net (Diablo, D2, SC1, WC2, WC3, etc.)
Reply Quote
Can you explain this in non-hacker terms for the regular guy so more people read this and understand why its bad from your perspective. Very interesting find though. I feel like more people should see this.
Reply Quote
Diablo 3:
4 28 ms 124 ms 50 ms ge-3-7.car2.Chicago1.Level3.net [4.71.182.41] Chicago
5 51 ms 27 ms 27 ms ae-31-51.ebr1.Chicago1.Level3.net [4.69.138.30] Chicago
6 26 ms 26 ms 26 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190] Chicago
Then take a look at HOW MANY of their servers i have to hop through!!!
1server 67 ms 67 ms 68 ms cr1.cgcil.ip.att.net [12.122.133.34]
2server 69 ms 68 ms 66 ms cr2.dvmco.ip.att.net [12.122.31.85]
3server 71 ms 71 ms 72 ms cr1.slkut.ip.att.net [12.122.30.25]
4server 72 ms 72 ms 71 ms cr2.la2ca.ip.att.net [12.122.30.30]
5server 68 ms 67 ms 67 ms gar29.la2ca.ip.att.net [12.122.129.241]
6server 67 ms 67 ms 66 ms 12.122.251.190
7server 65 ms 65 ms 65 ms 12.129.193.254


Oh look.. EIGHT hops. and i still go through my ISP servers here in chicago. Blizzard needs to fix this crazy hop issue. I shouldn't need to go through SEVEN hops on their servers all taking place on att(which are blizz servers btw, not AT&T) quoted fromBlizzards support section

"To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net."


interesting stuff.
would be nice to see less hops.

i mean look at my tracert.
Tracing route to 12.129.209.68 over a maximum of 20 hops

1 7 ms 8 ms 7 ms [my IP]
2 9 ms 7 ms 7 ms 173-219-234-80-link.sta.suddenlink.net [173.219.234.80]
3 20 ms 26 ms 21 ms 173-219-234-50-link.sta.suddenlink.net [173.219.234.50]
4 10 ms 9 ms 24 ms 173-219-255-235.mid.sta.suddenlink.net [173.219.255.235]
5 10 ms 9 ms 10 ms 173-219-234-32-link.sta.suddenlink.net [173.219.234.32]
6 21 ms 19 ms 19 ms 173-219-247-106-link.sta.suddenlink.net [173.219.247.106]
7 20 ms 21 ms 19 ms 173-219-247-72-link.sta.suddenlink.net [173.219.247.72]
8 36 ms 22 ms 23 ms 173-219-247-68-link.sta.suddenlink.net [173.219.247.68]
9 23 ms 23 ms 26 ms cdm-66-76-30-177.tylrtx.suddenlink.net [66.76.30.177]


10 26 ms 19 ms 19 ms xe-2-3-0.er2.dfw2.us.above.net [64.124.200.181]
11 91 ms 21 ms 20 ms 192.205.36.13

12 87 ms 84 ms 84 ms cr2.dlstx.ip.att.net [12.122.212.14]
13 84 ms 83 ms 87 ms cr2.la2ca.ip.att.net [12.122.28.178]
14 127 ms 174 ms 88 ms gar29.la2ca.ip.att.net [12.122.129.241]
15 62 ms 62 ms 62 ms 12.122.251.190
16 82 ms 182 ms 82 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.

Trace complete.


suddenlink is my provider. [8 hops]
then [2 hops] from some points in between.
then blizzard [5 hops].

im not getting lag or dc's atm. however, whenever i DO get really bad lag it has shown up on the attens server.

even so, looking at my trace you can see it jumps from 20ms to 80ms+ as soon as it hits blizzard. then within their severs there are points where it increases in latency. everytime ive did a trace with really bad lag (500ms-1k+ms) then it didnt show up as anything wrong in the upper portion. normally it shows up on the server that says attens.
Reply Quote
also your first link to the picture died. repost?
Reply Quote
I love how someone reported the OP for this... Why would ANYONE report the OP for this thread? Anyways, you can see a continuation of this topic here:

http://us.battle.net/d3/en/forum/topic/8569389059?page=1#5
Reply Quote

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]