Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


bradstewart

4338 posts

Uber Geek
+1 received by user: 166

Retired Mod
Trusted
Lifetime subscriber

#143010 31-Mar-2014 22:08
Send private message

Lately the connection to Battle.net on Snap in the evenings has been terrible. Multiple disconnects, horrible latency and often I can't connect at all including tonight.

This doesn't seem to be affecting anyone else I play with in NZ on other ISPs.

Everything else is working perfectly fine for me, Battle.net is the only thing having issues.

Tracert as follows. Something looks broken.

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    21 ms    21 ms    22 ms  205.9.69.111.static.snap.net.nz [111.69.9.205]
  3    21 ms    20 ms    21 ms  204.9.69.111.static.snap.net.nz [111.69.9.204]
  4     *        *        *     Request timed out.
  5    48 ms    39 ms    46 ms  32.27.69.111.static.snap.net.nz [111.69.27.32]
  6    39 ms    40 ms    39 ms  33.27.69.111.static.snap.net.nz [111.69.27.33]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9   200 ms     *      165 ms  xe7-0-1-10.lebr7.global-gateway.net.nz [202.50.232.162]
 10     *        *      195 ms  ae3-10.sjbr3.global-gateway.net.nz [122.56.127.25]
 11   169 ms   169 ms   169 ms  ae0.pabr5.global-gateway.net.nz [203.96.120.74]
 12   206 ms   205 ms   206 ms  xe-0-0-0-1.r06.plalca01.us.bb.gin.ntt.net [140.174.21.17]
 13   205 ms   205 ms   206 ms  ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
 14   180 ms   178 ms   177 ms  192.205.37.57
 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.


Create new topic
vexxxboy
4336 posts

Uber Geek
+1 received by user: 2072


  #1016279 31-Mar-2014 23:00
Send private message

i tried it and i timed out on the 5th and at the end it's telling me Destination host unreachable, so it's not just you.  Snap VDSL.




Common sense is not as common as you think.




hio77
'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified
Trusted
Lizard Networks
Subscriber

  #1016284 31-Mar-2014 23:08
Send private message

my connection to bnet has been solid (aside from the issue presented in the other thread. but then bnet isnt to blame for that.)


never notice any lag there..




#include <std_disclaimer>

 

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


bonkas
315 posts

Ultimate Geek
+1 received by user: 12


  #1016331 1-Apr-2014 08:48
Send private message

Are you guys still having issues with this?

Im going to try get on tonight.







Lias
5655 posts

Uber Geek
+1 received by user: 3978

ID Verified
Trusted
Lifetime subscriber

  #1016414 1-Apr-2014 10:25
Send private message

Snap VDSL ChCh:

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.178.1]
2 20 ms 20 ms 20 ms 111-69-1-254.core.snap.net.nz [111.69.1.254]
3 20 ms 20 ms 19 ms 32.54.69.111.static.snap.net.nz [111.69.54.32]
4 45 ms 34 ms 34 ms 32.27.69.111.static.snap.net.nz [111.69.27.32]
5 34 ms 33 ms 37 ms 33.27.69.111.static.snap.net.nz [111.69.27.33]
6 * * * Request timed out.
7 34 ms 34 ms 35 ms ae1-10.tkbr12.global-gateway.net.nz [202.50.232.37]
8 191 ms 190 ms * xe7-0-1-10.lebr7.global-gateway.net.nz [202.50.232.162]
9 167 ms 197 ms 197 ms ae3-10.sjbr3.global-gateway.net.nz [122.56.127.25]
10 190 ms 190 ms 190 ms ae0.pabr5.global-gateway.net.nz [203.96.120.74]
11 200 ms 200 ms 201 ms xe-0-0-0-1.r06.plalca01.us.bb.gin.ntt.net [140.174.21.17]
12 169 ms 169 ms 170 ms ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
13 206 ms 205 ms 209 ms 192.205.37.57
14 207 ms 207 ms 206 ms cr1.sffca.ip.att.net [12.122.114.30]
15 203 ms 214 ms 204 ms cr1.la2ca.ip.att.net [12.122.3.122]
16 170 ms 178 ms 170 ms gar20.la2ca.ip.att.net [12.122.128.181]
17 205 ms 204 ms 205 ms 12-122-254-234.attens.net [12.122.254.234]
18 238 ms 202 ms 202 ms 206.16.68.46
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.

Snap Fibre ChCh:

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 1 ms 2 ms 3 ms 172.20.147.1
2 <1 ms <1 ms <1 ms 172.16.15.73
3 <1 ms <1 ms <1 ms 165.84.107.5
4 1 ms 1 ms 1 ms juniper-4350-internet-gateway.cpit.network [165.84.106.1]
5 1 ms <1 ms 1 ms 185.114.124.202.static.snap.net.nz [202.124.114.185]
6 32 ms 15 ms 15 ms 32.27.69.111.static.snap.net.nz [111.69.27.32]
7 15 ms 15 ms 15 ms 33.27.69.111.static.snap.net.nz [111.69.27.33]
8 15 ms 15 ms 15 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.213]
9 18 ms 15 ms 16 ms ae1-10.tkbr12.global-gateway.net.nz [202.50.232.37]
10 171 ms 139 ms 171 ms xe2-0-1.lebr7.global-gateway.net.nz [203.96.120.142]
11 144 ms 148 ms 178 ms ae3-10.sjbr3.global-gateway.net.nz [122.56.127.25]
12 180 ms 179 ms 179 ms ae0.pabr5.global-gateway.net.nz [203.96.120.74]
13 181 ms 180 ms 180 ms xe-0-0-0-1.r06.plalca01.us.bb.gin.ntt.net [140.174.21.17]
14 149 ms 149 ms 149 ms ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
15 184 ms 186 ms 183 ms 192.205.37.57
16 184 ms 183 ms 183 ms cr1.sffca.ip.att.net [12.122.114.30]
17 189 ms 187 ms 187 ms cr1.la2ca.ip.att.net [12.122.3.122]
18 182 ms 182 ms 276 ms gar20.la2ca.ip.att.net [12.122.128.181]
19 194 ms 784 ms 203 ms 12-122-254-238.attens.net [12.122.254.238]
20 194 ms 183 ms 275 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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.

BigPipe DSL Kapiti

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 2 ms 1 ms <1 ms 192.168.0.254
2 24 ms 23 ms 23 ms 100.64.0.1
3 23 ms 23 ms 23 ms 10.1.2.2
4 24 ms 24 ms 24 ms 203.96.123.101
5 23 ms 23 ms 23 ms g7-2-8-201.akbr6.global-gateway.net.nz [122.56.118.65]
6 * 22 ms 23 ms ae5-2.akbr7.global-gateway.net.nz [210.55.202.213]
7 24 ms 24 ms 23 ms ae1-10.tkbr12.global-gateway.net.nz [202.50.232.37]
8 179 ms 147 ms 148 ms xe7-0-1-10.lebr7.global-gateway.net.nz [202.50.232.162]
9 187 ms 187 ms 178 ms ae3-10.sjbr3.global-gateway.net.nz [122.56.127.25]
10 151 ms 152 ms 151 ms ae0.pabr5.global-gateway.net.nz [203.96.120.74]
11 180 ms 181 ms 179 ms xe-0-0-0-1.r06.plalca01.us.bb.gin.ntt.net [140.174.21.17]
12 157 ms 157 ms 159 ms ae-4.r07.snjsca04.us.bb.gin.ntt.net [129.250.4.119]
13 165 ms 168 ms 162 ms 192.205.37.57
14 196 ms 194 ms 196 ms cr1.sffca.ip.att.net [12.122.114.30]
15 167 ms 163 ms 164 ms cr1.la2ca.ip.att.net [12.122.3.122]
16 159 ms 161 ms 159 ms gar20.la2ca.ip.att.net [12.122.128.181]
17 194 ms 191 ms 191 ms 12-122-254-238.attens.net [12.122.254.238]
18 192 ms 191 ms 192 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.






I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup. Opinions are my own and not the views of my employer.


Quinny
926 posts

Ultimate Geek
+1 received by user: 208

Trusted

  #1016548 1-Apr-2014 13:22
Send private message

Been fine for me on UFB in Chch with Snap. Just moved from TelstraCable which has gone so downhill. Ping is up (150 to 180). No in game issues and watched all my Telstra buddies DC in game on Sunday with me just fine. The request timeout in trace above is normal as this is where it hits Blizzard and is blocked. Sorry cant help more than that.

D1NZ
194 posts

Master Geek
+1 received by user: 14


  #1018061 3-Apr-2014 20:00
Send private message

I am on UFB in Chch with Snap also, haven't noticed any issues with ping in fact my ping in D3 dropped from 160~180ms down to 40~60ms.
From what I have heard is that Diablo 3 had new server up and running in Sydney/Australia for Aussie and New Zealand players.




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






 
 
 

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.
hio77
'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified
Trusted
Lizard Networks
Subscriber

  #1018090 3-Apr-2014 20:28
Send private message

D1NZ: I am on UFB in Chch with Snap also, haven't noticed any issues with ping in fact my ping in D3 dropped from 160~180ms down to 40~60ms.
From what I have heard is that Diablo 3 had new server up and running in Sydney/Australia for Aussie and New Zealand players.


that latency would line up pretty well with it being in sydney..




#include <std_disclaimer>

 

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


Ragnor
8279 posts

Uber Geek
+1 received by user: 585

Trusted

  #1018155 3-Apr-2014 22:33
Send private message

Nothing wrong with those tracerts not all servers/hops respond to icmp (tracert, ping etc), in fact blizzard's network doesn't on purpose.

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.