Unplayable ping...

Q

Qwynbleid

Member
Joined
Jun 25, 2009
Messages
12
Reaction score
0
Recently I have ran into a problem with diablo 3, during the business hours my ping is fine between 200-300 witch is still very playable but after 5 pm(happened just after 6 pm today thou) things deteriorate suddenly, averaging 1k a lot with spikes to 3k, nobody can play with that... sometimes it averages 500 but it still spikes frequently regardless.

Pinging eu.blizzard.com [80.239.186.31] with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.239.186.31:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
and the same with the server itself(80.239.208.193)

Tracing route to 80-239-208-193.customer.teliacarrier.com [80.239.208.193]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 15 ms 15 ms 15 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 17 ms 16 ms 17 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178
.29]
4 17 ms 17 ms 18 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 17 ms 50 ms 16 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 190 ms 189 ms 189 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
7 255 ms 205 ms 206 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.
89]
8 200 ms 200 ms 199 ms 4.69.162.149
9 191 ms 191 ms 191 ms ae-2-52.edge4.Amsterdam1.Level3.net [4.69.139.17
0]
10 192 ms 192 ms 191 ms telia-level3-xe.amsterdam1.Level3.net [213.244.1
65.250]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 *
and it continues timing out. This is on a capped afrihost account(which is unshaped according to them), however the same thing happens on a telkom uncapped account

Tracing route to 80-239-208-193.customer.teliacarrier.com [80.239.208.193]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 17 ms 15 ms 16 ms dsl-145-84-01.telkomadsl.co.za [41.145.84.1]
3 23 ms 22 ms 21 ms 196.43.21.174
4 * * * Request timed out.
5 * * * Request timed out.
6 18 ms 17 ms 17 ms 196.43.10.130
7 17 ms 16 ms 17 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [
196.43.33.5]
8 208 ms 207 ms 207 ms fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.110]
9 274 ms 275 ms 273 ms ffm-b10-link.telia.net [195.12.255.217]
10 296 ms 291 ms 282 ms ffm-bb1-link.telia.net [213.155.134.134]
11 308 ms 428 ms 288 ms hbg-bb1-link.telia.net [213.155.135.139]
12 303 ms 301 ms 308 ms adm-bb3-link.telia.net [80.91.252.42]
13 308 ms 302 ms 284 ms adm-b5-link.telia.net [80.91.253.171]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
and keeps timing out.. so I highly doubt that it is the ISP's at fault which leaves only the adsl line itself, and telkom is as unhelpful as ever.... What do you guys think? I'll do the tracert again during business hours tomorrow and post it here
 
Upstream 512 kbps
Downstream 1024 kbps
SNR Margin (Upstream) 12.0 db
SNR Margin (Downstream) 25.0 db
Line Attenuation (Upstream) 20.0 db
Line Attenuation (Downstream) 37.0 db

Sorry I am rather new at this is that what you mean?
 
It's because you're using the only 2 networks thats NOT meant for gaming. Get MWEBGuy to organize you a trial account and test that

Having said that. Your upload attenuation does seem a lot
 
AcidRaZor said:
It's because you're using the only 2 networks thats NOT meant for gaming. Get MWEBGuy to organize you a trial account and test that

Having said that. Your upload attenuation does seem a lot
Click to expand...

Considering it's fine during the day and not after hours, it's more likely that you're on an oversubscribed exchange.

During the day, everyone's at work so it's fine. After hours, everyone comes home to use their internet.
 
The time outs have nothing to do with your line or ISP.

The time outs are caused by the network device/server not accepting ICMP packets hence you cannot ping it.

Having said that the rest of your tracert looks fine, did you do them while you were experiencing the latency issues?
 
Why paste us traceroutes from two completely different ISP's? That's not going to help us help you in any way I'm afraid. Give us consistent results from different times of the day and we can see properly. Seems like purely an ISP issue on the face of it though
 
Qwynbleid said:
Recently I have ran into a problem with diablo 3, during the business hours my ping is fine between 200-300 witch is still very playable but after 5 pm(happened just after 6 pm today thou) things deteriorate suddenly, averaging 1k a lot with spikes to 3k, nobody can play with that... sometimes it averages 500 but it still spikes frequently regardless.

Pinging eu.blizzard.com [80.239.186.31] with 32 bytes of data
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 80.239.186.31:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
and the same with the server itself(80.239.208.193)

Tracing route to 80-239-208-193.customer.teliacarrier.com [80.239.208.193]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 15 ms 15 ms 15 ms 105-236-9-1-esr-lo.mtnbusiness.co.za [105.236.9.
1]
3 17 ms 16 ms 17 ms ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178
.29]
4 17 ms 17 ms 18 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
5 17 ms 50 ms 16 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
6 190 ms 189 ms 189 ms am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.1
41]
7 255 ms 205 ms 206 ms xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.
89]
8 200 ms 200 ms 199 ms 4.69.162.149
9 191 ms 191 ms 191 ms ae-2-52.edge4.Amsterdam1.Level3.net [4.69.139.17
0]
10 192 ms 192 ms 191 ms telia-level3-xe.amsterdam1.Level3.net [213.244.1
65.250]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 *
and it continues timing out. This is on a capped afrihost account(which is unshaped according to them), however the same thing happens on a telkom uncapped account

Tracing route to 80-239-208-193.customer.teliacarrier.com [80.239.208.193]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.254
2 17 ms 15 ms 16 ms dsl-145-84-01.telkomadsl.co.za [41.145.84.1]
3 23 ms 22 ms 21 ms 196.43.21.174
4 * * * Request timed out.
5 * * * Request timed out.
6 18 ms 17 ms 17 ms 196.43.10.130
7 17 ms 16 ms 17 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [
196.43.33.5]
8 208 ms 207 ms 207 ms fra-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.9.110]
9 274 ms 275 ms 273 ms ffm-b10-link.telia.net [195.12.255.217]
10 296 ms 291 ms 282 ms ffm-bb1-link.telia.net [213.155.134.134]
11 308 ms 428 ms 288 ms hbg-bb1-link.telia.net [213.155.135.139]
12 303 ms 301 ms 308 ms adm-bb3-link.telia.net [80.91.252.42]
13 308 ms 302 ms 284 ms adm-b5-link.telia.net [80.91.253.171]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
and keeps timing out.. so I highly doubt that it is the ISP's at fault which leaves only the adsl line itself, and telkom is as unhelpful as ever.... What do you guys think? I'll do the tracert again during business hours tomorrow and post it here
Click to expand...

Axxess/Afrihost have been terribad for gaming for a while now. Get a new ISP.
 
AcidRaZor said:
It's because you're using the only 2 networks thats NOT meant for gaming. Get MWEBGuy to organize you a trial account and test that

Having said that. Your upload attenuation does seem a lot
Click to expand...

Thank you for the reply, I'll look into trying a different ISP soon.

zolly said:
Considering it's fine during the day and not after hours, it's more likely that you're on an oversubscribed exchange.

During the day, everyone's at work so it's fine. After hours, everyone comes home to use their internet.
Click to expand...

This was my first thought as well but I can only imagine how it will go when almost everyone is on vacation between Christmas and new years, I am hoping this is not the case. Thanks for your input thou.

grim said:
The time outs have nothing to do with your line or ISP.

The time outs are caused by the network device/server not accepting ICMP packets hence you cannot ping it.

Having said that the rest of your tracert looks fine, did you do them while you were experiencing the latency issues?
Click to expand...

A ok thank you for the info, I was not aware of that, yes, the problem is the ping does get short periods of normalcy in between the spikes but that only lasts for a short time making it difficult to say if right at that moment the problem was rearing its head... Perhaps if I connect another monitor so that I can see what the ping is doing and try running it when it starts spiking, I'll try tonight.

fragtion said:
Why paste us traceroutes from two completely different ISP's? That's not going to help us help you in any way I'm afraid. Give us consistent results from different times of the day and we can see properly. Seems like purely an ISP issue on the face of it though
Click to expand...

Thanks for the input, I will make a log of them say every two hours and paste them here later.
 
Qwynbleid said:
A ok thank you for the info, I was not aware of that, yes, the problem is the ping does get short periods of normalcy in between the spikes but that only lasts for a short time making it difficult to say if right at that moment the problem was rearing its head... Perhaps if I connect another monitor so that I can see what the ping is doing and try running it when it starts spiking, I'll try tonight.
Click to expand...

Ping the last hop that responds so that'll be 213.244.165.250

You can leave the ping running by adding -t ie. ping 213.244.165.250 -t

Once you see it spiking run a tracert or even a pathping which will give a clearer indication of which hop is spiking.
 
AcidRaZor said:
It's because you're using the only 2 networks thats NOT meant for gaming. Get MWEBGuy to organize you a trial account and test that

Having said that. Your upload attenuation does seem a lot
Click to expand...

My upload attenuation is higher than my downstream attenuation what would that mean?
SNR Margin downstream 28.5 dB
SNR Margin upstream 12 dB
Line Attenuation downstream 19.5 dB
Line Attenuation upstream 24.0 dB
 
grim said:
Ping the last hop that responds so that'll be 213.244.165.250

You can leave the ping running by adding -t ie. ping 213.244.165.250 -t

Once you see it spiking run a tracert or even a pathping which will give a clearer indication of which hop is spiking.
Click to expand...

Having a 2k ping for a while now the tracerts returns the same as before


Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233] (at 9:40 pm)
over a maximum of 30 hops:

1 7 ms 1 ms <1 ms 192.168.1.254
2 48 ms 31 ms 25 ms dsl-145-84-01.telkomadsl.co.za [41.145.84.1]
3 29 ms 29 ms 30 ms 196.43.21.174
4 * * * Request timed out.
5 * * * Request timed out.
6 31 ms 37 ms 39 ms 196.43.10.130
7 29 ms 29 ms 30 ms rrba-ip-lir-1-gig-2-0-0-201.telkom-ipnet.co.za [
196.43.33.5]
8 269 ms 229 ms 219 ms fra-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.102]
9 299 ms 289 ms 309 ms ffm-b10-link.telia.net [195.12.255.217]
10 299 ms 299 ms 309 ms ffm-bb2-link.telia.net [80.91.251.125]
11 329 ms 339 ms 319 ms hbg-bb2-link.telia.net [80.91.245.120]
12 * 313 ms 326 ms adm-bb4-link.telia.net [80.91.246.236]
13 319 ms 326 ms 322 ms adm-b5-link.telia.net [213.155.132.159]
14 * * * Request timed out.
15 *

With no obvious reason why the ping spikes but then I took your advice and started pinging the last node it hit, I'm losing packets.

Ping statistics for 213.155.132.159:
Packets: Sent = 146, Received = 129, Lost = 17 (11% loss),
Approximate round trip times in milli-seconds:
Minimum = 336ms, Maximum = 461ms, Average = 354ms
and another run for a bit 12% loss.

My PC is connected to the router via a lan cable but to see if the packet loss was between my PC and the router I also ran it for a bit resulting in

Ping statistics for 192.168.1.254:
Packets: Sent = 481, Received = 481, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 10ms, Average = 3ms

So that doesn't seem to be the problem.
Pinging the first IP after my router 41.145.84.1 returns

Ping statistics for 41.145.84.1:
Packets: Sent = 110, Received = 100, Lost = 10 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 39ms, Average = 22ms

This is with
SNR Margin (Upstream) 12.0 db
SNR Margin (Downstream) 25.5 db
Line Attenuation (Upstream) 19.5 db
Line Attenuation (Downstream) 36.5 db
tonight.

The ping to the last node I get is also not the ping I see in game, of course.

I was a bit interested in why the trace can not seem to complete but blizzard does explain this https://us.battle.net/support/en/article/performing-a-traceroute#addresses and it is normal(to their servers that is). What to do now? Seems like it is the line or am I mistaken?

Hype said:
What exchange are you connected to?
Click to expand...

Thanks for your interest, it is one of the arconpark exchanges, the one with location code 428(we have a 016 428 number so thats my gues, 3 exchanges here in total thou according to http://www.broadbandstats.co.za/exchanges/province/Gauteng/district/vereeniging).

Additionally, tonight my ping in-game was 700+, not that I played but yea, that is without any tracert or pinging going on, although that doesn't seem to effect the ping in-game
 
Last edited:
Could be line, could be exchange

The latency and packet loss on the first hop after your router isn't a good sign. It's not ridiculous but could indicate congestion on the exchange side.

Your line stats are pretty good.
 
From the looks of it, exchange congestion. Im having the same issue but in JHB. Log faults for exchange congestion until Telkom hate you. Ideally it would be best if you got a whole host of ppl on your exchange or area to all log faults for congestion. But trying to co ordinate any effort like that in todays age is fairly futile, but if you could manage that .. telkom would wake up.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X