[Snap] Horrible ping to battle net

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] Horrible ping to battle net

Kiwiownage

112 posts

Master Geek
+1 received by user: 5

#132378 20-Oct-2013 12:21

Since Friday my latency to all battle net servers has gone up to about 300, any1 else getting this or just me? it's also very spikey.

timmmay

20858 posts

Uber Geek
+1 received by user: 5350

Trusted

Lifetime subscriber

#917696 20-Oct-2013 12:39

Can you post a ping and traceroute

Behodar

11101 posts

Uber Geek
+1 received by user: 6084

Trusted

Lifetime subscriber

#917698 20-Oct-2013 12:46

I'm with Fyx (Maxnet) and my latency is normal, so it's not a widespread issue. Hopefully that helps you track down where the problem is :)

Kiwiownage

112 posts

Master Geek
+1 received by user: 5

#917700 20-Oct-2013 13:06

Tracerts show nothing out of the ordinary... but there's certainly lag happening on my end.

1 2 ms <1 ms 1 ms 192.168.178.1
2 12 ms 14 ms 13 ms 64.37.69.111.static.snap.net.nz [111.69.37.64]
3 12 ms 12 ms 13 ms 80.53.69.111.static.snap.net.nz [111.69.53.80]
4 26 ms 49 ms 21 ms 32.27.69.111.static.snap.net.nz [111.69.27.32]
5 21 ms 28 ms 21 ms 33.27.69.111.static.snap.net.nz [111.69.27.33]
6 27 ms 22 ms 22 ms ae2-6.tkbr12.global-gateway.net.nz [122.56.127.1
7]
7 173 ms 173 ms 175 ms 202.50.232.18
8 181 ms 150 ms 184 ms ae3-10.lebr7.global-gateway.net.nz [122.56.127.2
6]
9 149 ms 150 ms 153 ms ae1-10.lebr6.global-gateway.net.nz [122.56.127.2
1]
10 153 ms 149 ms 148 ms ae51.edge2.LosAngeles9.Level3.net [4.53.230.13]

11 184 ms 182 ms 183 ms vlan80.csw3.LosAngeles1.Level3.net [4.69.144.190
]
12 184 ms 188 ms 185 ms ae-83-83.ebr3.LosAngeles1.Level3.net [4.69.137.4
1]
13 185 ms 191 ms 183 ms ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
14 183 ms 184 ms 181 ms ae-208-3608.bar21.Tustin1.Level3.net [4.69.158.1
26]
15 186 ms 187 ms 184 ms 192.205.37.145
16 155 ms 154 ms 155 ms cr1.la2ca.ip.att.net [12.122.128.102]
17 183 ms 185 ms 182 ms gar20.la2ca.ip.att.net [12.122.128.181]
18 184 ms 186 ms 185 ms 12.122.251.190
19 187 ms 184 ms 182 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]

timmmay

20858 posts

Uber Geek
+1 received by user: 5350

Trusted

Lifetime subscriber

#917708 20-Oct-2013 13:19

Here's mine on TC/Vodafone cable

3 10 ms 11 ms 12 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]
4 29 ms 26 ms 22 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 19 ms 28 ms * ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
6 151 ms 145 ms 146 ms te7-3.ccr01.sjc05.atlas.cogentco.com [38.122.92.105]
7 146 ms 147 ms 157 ms te0-3-0-7.ccr21.sjc01.atlas.cogentco.com [154.54.6.73]
8 172 ms 174 ms 174 ms be2166.mpd21.sfo01.atlas.cogentco.com [154.54.28.69]
9 186 ms 186 ms 184 ms be2134.mpd21.mci01.atlas.cogentco.com [154.54.6.38]
10 202 ms 194 ms 197 ms be2064.ccr21.dfw01.atlas.cogentco.com [154.54.5.218]
11 228 ms 222 ms 221 ms be2031.ccr21.dfw03.atlas.cogentco.com [154.54.7.46]
12 232 ms 247 ms 241 ms 192.205.36.221
13 228 ms 231 ms 220 ms cr2.dlstx.ip.att.net [12.122.138.18]
14 224 ms 238 ms 225 ms cr2.la2ca.ip.att.net [12.122.28.178]
15 221 ms 225 ms 220 ms gar29.la2ca.ip.att.net [12.122.129.241]
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.

At the end it hung, control C wouldn't get it back.

I couldn't ping the last few servers, here's the one closest to the end I could

ping 192.205.37.145

Pinging 192.205.37.145 with 32 bytes of data:
Reply from 192.205.37.145: bytes=32 time=194ms TTL=243
Reply from 192.205.37.145: bytes=32 time=207ms TTL=243
Reply from 192.205.37.145: bytes=32 time=202ms TTL=243
Reply from 192.205.37.145: bytes=32 time=212ms TTL=243

Based on this I'd say you're doing better than Vodafone.

michaelmurfy

meow
13580 posts

Uber Geek
+1 received by user: 10912

Moderator

ID Verified

Trusted

Lifetime subscriber

#917715 20-Oct-2013 13:43

Telecom VDSL:

mmurphy@charmander:~$ ping 192.205.37.145
PING 192.205.37.145 (192.205.37.145) 56(84) bytes of data.
64 bytes from 192.205.37.145: icmp_req=1 ttl=241 time=163 ms
64 bytes from 192.205.37.145: icmp_req=2 ttl=241 time=164 ms
64 bytes from 192.205.37.145: icmp_req=3 ttl=241 time=163 ms
64 bytes from 192.205.37.145: icmp_req=4 ttl=241 time=160 ms
64 bytes from 192.205.37.145: icmp_req=5 ttl=241 time=164 ms
^C
--- 192.205.37.145 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 160.993/163.414/164.904/1.321 ms

It might be your connection, what's your line stats? Also where are you based?

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

Kiwiownage

112 posts

Master Geek
+1 received by user: 5

#917751 20-Oct-2013 14:44

I'm on 100/50 fiber, located in dunedin

Dell

Shop now for Dell laptops and other devices (affiliate link).

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#917754 20-Oct-2013 14:50

snap vdsl, 8ms profile..

Pinging 192.205.37.145 with 32 bytes of data:
Reply from 192.205.37.145: bytes=32 time=187ms TTL=242
Reply from 192.205.37.145: bytes=32 time=190ms TTL=242
Reply from 192.205.37.145: bytes=32 time=197ms TTL=242
Reply from 192.205.37.145: bytes=32 time=188ms TTL=242

looks pretty close to perfect to me

dont have any bnet games on me to test ingame latency however it shouldnt be any different..

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

michaelmurfy

meow
13580 posts

Uber Geek
+1 received by user: 10912

Moderator

ID Verified

Trusted

Lifetime subscriber

#917755 20-Oct-2013 14:51

Kiwiownage: I'm on 100/50 fiber, located in dunedin

Have you tried turning both your router and ONT off and on again?

Kiwiownage

112 posts

Master Geek
+1 received by user: 5

#917758 20-Oct-2013 14:57

michaelmurfy:
Kiwiownage: I'm on 100/50 fiber, located in dunedin

Have you tried turning both your router and ONT off and on again?

haha :D, yes several times.

D1NZ

194 posts

Master Geek
+1 received by user: 14

#918848 20-Oct-2013 21:10

Kiwiownage:
michaelmurfy:
Kiwiownage: I'm on 100/50 fiber, located in dunedin

Have you tried turning both your router and ONT off and on again?

haha :D, yes several times.

I am getting about 60% package lost at hop 7 also ping flicking up and down on the last few hops.

I am on Snap UFB 100/50

I will attach a image of my tracert to battle net

battlenet trace

CPU: Intel Xeon E3-1225 V2 @ 3.20Ghz
RAM: A-data ECC 4GB x 2 1600MHz
SSD: Samsung 840 Pro 120GB
Motherboard: Intel S1200KPR server board mini-ITX
NIC: Intel Ethernet Server Adapter I350-T2

Sounddude

I fix stuff!
1935 posts

Uber Geek
+1 received by user: 640

Trusted

2degrees

Lifetime subscriber

#918854 20-Oct-2013 21:16

Don't be fooled by packet loss in the middle of a traceroute. It means nothing. The important value is the end value.

Routers treat ICMP packets targeted at them as low priority. They also have a lot of filters protecting them.