Diablo 3 Unplayable Latency (on MWeb)

S

smashinashin

Member
Joined
Jun 25, 2014
Messages
10
Reaction score
0
For the past several days now I've been getting some unplayable latency in Diablo 3 (NA). The issues I've experienced have been restricted completely to playing Diablo 3. There have been some minor issues with connecting to Battle.net, but those don't tend to affect me for very long. I can play World of Warcraft (NA), Battlefield 4(local and international for testing purposes), League of Legends(NA), with no problem.

I can start to play Diablo 3 and it will work fine for a while, but eventually every time a fight begins, I lag out until I die. Everything resumes as normal until I revive and start to fight again. The latency usually then gets so bad that I lag out completely and disconnect.

I've done a pathping and tracert via the Battle.net instructions; both have shown no issues anywhere along the way that I can see through casual observation. This has happened to me in the past, and I've been unable to play Diablo 3 for weeks/months at a time. The problems just "clear up" at some point, and I'm able to play again for a while.

Is anyone else having issues like this, or is there anyone that can advise me on this issue?

EDIT
This problem is intermittent on an hourly basis. It's generally unplayable but it does have moments of clarity.
 
Last edited:
Get a free account from axxis and test again. See if that changes anything. Check for CRC errors on router. Reset router for about 15 minutes and switch on again. Port reset from telkom.
 
Hey Anamech, thanks for responding.

I've never heard of, and can't seem to find Axxes offering free international ADSL. That'd be great though, could you perhaps help me out with a link or more info?

I started with a D-Link router, switched to a backup Belkin, and as of Sunday bought a new Netgear router. MWeb has reset our ports already.
 
Some other people have also been having latency issues.
See what happens if you connect to EU?
 
I'm not sure. I haven't tried that because I don't have any characters on the EU side. Most of my friends are from and/or play on the NA side. I also currently have plans to immigrate to the states within the next 7ish months. But I'll give it a test to see what happens.
 
smashinashin said:
For the past several days now I've been getting some unplayable latency in Diablo 3 (NA). The issues I've experienced have been restricted completely to playing Diablo 3. There have been some minor issues with connecting to Battle.net, but those don't tend to affect me for very long. I can play World of Warcraft (NA), Battlefield 4(local and international for testing purposes), League of Legends(NA), with no problem.

I can start to play Diablo 3 and it will work fine for a while, but eventually every time a fight begins, I lag out until I die. Everything resumes as normal until I revive and start to fight again. The latency usually then gets so bad that I lag out completely and disconnect.

I've done a pathping and tracert via the Battle.net instructions; both have shown no issues anywhere along the way that I can see through casual observation. This has happened to me in the past, and I've been unable to play Diablo 3 for weeks/months at a time. The problems just "clear up" at some point, and I'm able to play again for a while.

Is anyone else having issues like this, or is there anyone that can advise me on this issue?

EDIT
This problem is intermittent on an hourly basis. It's generally unplayable but it does have moments of clarity.
Click to expand...


Hi smashinashin

You have spoken with an ADSL consultant and had the port refreshed and bought different routers and having issues mostly with Battlefield and here and there with others.

What was/is your tracert results?

If the account & line is/was found fine have you checked in with our Dedicated Gaming admins on our Gaming site/forum?

http://www.mweb.co.za/games/Home.aspx
 
Hey MWEB Guy,

Sorry if I wasn't clear before, but the ONLY game I'm having problems with is Diablo 3.

The tracert results: When playing NA servers, we normally get a stable 360 ping.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 8 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
3 10 ms 9 ms 10 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 11 ms 11 ms 11 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 205 ms 208 ms 206 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
6 211 ms 211 ms 212 ms ldn-b5-link.telia.net [62.115.13.13]
7 204 ms 204 ms 254 ms ldn-bb1-link.telia.net [80.91.247.91]
8 279 ms 279 ms 279 ms ash-bb3-link.telia.net [80.91.246.68]
9 278 ms 277 ms 277 ms ash-b2-link.telia.net [213.155.133.221]
10 289 ms 288 ms 287 ms 192.205.33.25
11 353 ms 356 ms 355 ms cr82.wshdc.ip.att.net [12.122.135.102]
12 363 ms 365 ms 363 ms cr2.wswdc.ip.att.net [12.122.134.94]
13 352 ms 354 ms 355 ms cr1.cgcil.ip.att.net [12.122.18.21]
14 365 ms 366 ms 363 ms cr2.dvmco.ip.att.net [12.122.31.85]
15 346 ms 347 ms 347 ms cr1.slkut.ip.att.net [12.122.30.25]
16 357 ms 359 ms 360 ms cr2.la2ca.ip.att.net [12.122.30.30]
17 410 ms 364 ms 363 ms gar5.lsrca.ip.att.net [12.122.85.33]
18 356 ms 355 ms 355 ms 12-122-254-226.attens.net [12.122.254.226]
19 362 ms 363 ms 362 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
20 353 ms 353 ms 352 ms 12.129.248.118
21 355 ms 355 ms 355 ms 12.129.209.68

Trace complete.

Pathping results: Note: The 100% loss at node 11-20 is normal for Blizzard's servers as stated by Blizzard's pathping guide.

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
0/ 100 = 0% |
5 199ms 0/ 100 = 0% 0/ 100 = 0% be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
0/ 100 = 0% |
6 214ms 0/ 100 = 0% 0/ 100 = 0% ldn-b5-link.telia.net [62.115.13.13]
0/ 100 = 0% |
7 204ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb1-link.telia.net [80.91.247.91]
0/ 100 = 0% |
8 282ms 0/ 100 = 0% 0/ 100 = 0% ash-bb3-link.telia.net [80.91.246.68]
0/ 100 = 0% |
9 282ms 0/ 100 = 0% 0/ 100 = 0% ash-b2-link.telia.net [213.155.133.221]
0/ 100 = 0% |
10 281ms 0/ 100 = 0% 0/ 100 = 0% 192.205.33.25
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr82.wshdc.ip.att.net [12.122.135.102]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% cr2.wswdc.ip.att.net [12.122.134.94]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
17 --- 100/ 100 =100% 100/ 100 =100% gar5.lsrca.ip.att.net [12.122.85.33]
0/ 100 = 0% |
18 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-226.attens.net [12.122.254.226]
0/ 100 = 0% |
19 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
0/ 100 = 0% |
20 --- 100/ 100 =100% 100/ 100 =100% 12.129.248.118
0/ 100 = 0% |
21 355ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.

I'll post in the forums there and see what I can find. I will update this forum with any non-MWeb relevant information.

I'm still open to suggestions that anyone might have.

Thanks for your time.
 
smashinashin said:
Hey MWEB Guy,

Sorry if I wasn't clear before, but the ONLY game I'm having problems with is Diablo 3.

The tracert results: When playing NA servers, we normally get a stable 360 ping.

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 8 ms 8 ms 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
3 10 ms 9 ms 10 ms 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
4 11 ms 11 ms 11 ms 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
5 205 ms 208 ms 206 ms be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
6 211 ms 211 ms 212 ms ldn-b5-link.telia.net [62.115.13.13]
7 204 ms 204 ms 254 ms ldn-bb1-link.telia.net [80.91.247.91]
8 279 ms 279 ms 279 ms ash-bb3-link.telia.net [80.91.246.68]
9 278 ms 277 ms 277 ms ash-b2-link.telia.net [213.155.133.221]
10 289 ms 288 ms 287 ms 192.205.33.25
11 353 ms 356 ms 355 ms cr82.wshdc.ip.att.net [12.122.135.102]
12 363 ms 365 ms 363 ms cr2.wswdc.ip.att.net [12.122.134.94]
13 352 ms 354 ms 355 ms cr1.cgcil.ip.att.net [12.122.18.21]
14 365 ms 366 ms 363 ms cr2.dvmco.ip.att.net [12.122.31.85]
15 346 ms 347 ms 347 ms cr1.slkut.ip.att.net [12.122.30.25]
16 357 ms 359 ms 360 ms cr2.la2ca.ip.att.net [12.122.30.30]
17 410 ms 364 ms 363 ms gar5.lsrca.ip.att.net [12.122.85.33]
18 356 ms 355 ms 355 ms 12-122-254-226.attens.net [12.122.254.226]
19 362 ms 363 ms 362 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
20 353 ms 353 ms 352 ms 12.129.248.118
21 355 ms 355 ms 355 ms 12.129.209.68

Trace complete.

Pathping results: Note: The 100% loss at node 11-20 is normal for Blizzard's servers as stated by Blizzard's pathping guide.

0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 10ms 0/ 100 = 0% 0/ 100 = 0% 41-133-124-1.dsl.mweb.co.za [41.133.124.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% 197-82-5-250.dbn.mweb.co.za [197.82.5.250]
0/ 100 = 0% |
4 11ms 0/ 100 = 0% 0/ 100 = 0% 197-82-2-3.dbn.mweb.co.za [197.82.2.3]
0/ 100 = 0% |
5 199ms 0/ 100 = 0% 0/ 100 = 0% be-3-777-thd-up-1.mweb.co.za [176.67.177.131]
0/ 100 = 0% |
6 214ms 0/ 100 = 0% 0/ 100 = 0% ldn-b5-link.telia.net [62.115.13.13]
0/ 100 = 0% |
7 204ms 0/ 100 = 0% 0/ 100 = 0% ldn-bb1-link.telia.net [80.91.247.91]
0/ 100 = 0% |
8 282ms 0/ 100 = 0% 0/ 100 = 0% ash-bb3-link.telia.net [80.91.246.68]
0/ 100 = 0% |
9 282ms 0/ 100 = 0% 0/ 100 = 0% ash-b2-link.telia.net [213.155.133.221]
0/ 100 = 0% |
10 281ms 0/ 100 = 0% 0/ 100 = 0% 192.205.33.25
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr82.wshdc.ip.att.net [12.122.135.102]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% cr2.wswdc.ip.att.net [12.122.134.94]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% cr2.dvmco.ip.att.net [12.122.31.85]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
17 --- 100/ 100 =100% 100/ 100 =100% gar5.lsrca.ip.att.net [12.122.85.33]
0/ 100 = 0% |
18 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-226.attens.net [12.122.254.226]
0/ 100 = 0% |
19 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]
0/ 100 = 0% |
20 --- 100/ 100 =100% 100/ 100 =100% 12.129.248.118
0/ 100 = 0% |
21 355ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.

I'll post in the forums there and see what I can find. I will update this forum with any non-MWeb relevant information.

I'm still open to suggestions that anyone might have.

Thanks for your time.
Click to expand...


Hi smashinashin

You have then check in with our Gaming team?
 
Yes, I've posted there and have been talking to someone about the issue. Thanks MWeb Guy.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X