[Snap] SNAP performance declining over time?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] SNAP performance declining over time?

1 | 2 | 3 | 4

MattR

224 posts

Master Geek

#1148346 6-Oct-2014 16:29

slingynz:
Can you please post a tracert?

AKL North Shore, VDSL2.

traceroute to login.worldoftanks.asia (92.223.16.65), 30 hops max, 60 byte packets
1 192.168.51.1 (192.168.51.1) 0.177 ms 0.153 ms 0.161 ms
2 229.34.69.111.static.snap.net.nz (111.69.34.229) 4.918 ms 4.908 ms 4.867 ms
3 228.34.69.111.static.snap.net.nz (111.69.34.228) 6.275 ms 6.259 ms 6.246 ms
4 * * *
5 4.56.69.111.static.snap.net.nz (111.69.56.4) 28.899 ms 28.928 ms 29.226 ms
6 5.56.69.111.static.snap.net.nz (111.69.56.5) 29.211 ms 28.729 ms 28.522 ms
7 ten-0-0-0-3.cor03.syd03.nsw.VOCUS.net.au (114.31.192.208) 30.322 ms 29.984 ms 29.962 ms
8 ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au (175.45.72.73) 29.917 ms 28.516 ms 28.498 ms
9 tengigabitethernet8-4.ult2.sydney.telstra.net (139.130.73.105) 28.516 ms 28.636 ms 28.610 ms
10 bundle-ether7-100.ken-core4.sydney.telstra.net (203.50.20.1) 30.366 ms 30.361 ms 30.342 ms
11 bundle-ether19.ken-core10.sydney.telstra.net (203.50.11.129) 32.368 ms 32.581 ms 30.697 ms
12 bundle-ether12.win-core10.melbourne.telstra.net (203.50.11.123) 42.504 ms 42.477 ms 43.220 ms
13 bundle-ether6.fli-core1.adelaide.telstra.net (203.50.11.90) 54.718 ms 54.689 ms 52.165 ms
14 bundle-ether5.wel-core3.perth.telstra.net (203.50.11.19) 80.926 ms 83.152 ms 83.136 ms
15 203.50.9.6 (203.50.9.6) 91.146 ms 91.154 ms 91.166 ms
16 i-0-0-1-0.istt-core02.bx.telstraglobal.net (202.84.141.158) 136.825 ms 135.249 ms 135.224 ms
17 i-0-0-1-0.istt03.bi.telstraglobal.net (202.84.243.94) 132.463 ms i-0-0-0-0.istt03.bi.telstraglobal.net (202.84.243.74) 133.424 ms i-0-0-1-0.istt03.bi.telstraglobal.net (202.84.243.94) 135.441 ms
18 unknown.telstraglobal.net (202.126.128.90) 131.457 ms 131.183 ms 133.197 ms
19 xe-1-1-1.gw401.sg2.ap.equinix.com (27.111.222.107) 135.227 ms 132.650 ms 132.688 ms
20 27.111.214.82 (27.111.214.82) 134.125 ms 135.656 ms 133.945 ms
21 sg2-n5596-fe-1-vl231.wargaming.net (92.223.116.163) 133.949 ms 133.939 ms 132.719 ms
22 sg2-sl-a65.worldoftanks.sg (92.223.16.65) 132.941 ms !X 136.210 ms !X 132.503 ms !X

Lenovo

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

DulceEtDecorumEst

13 posts

Geek

#1148450 6-Oct-2014 18:07

From the wilds of the Wairarapa, cross the Styx and turn left:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\John>tracert worldoftanks.asia

Tracing route to worldoftanks.asia [92.223.16.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 15 ms 15 ms 15 ms 105.37.69.111.static.snap.net.nz [111.69.37.105]

3 16 ms 15 ms 15 ms 104.37.69.111.static.snap.net.nz [111.69.37.104]

4 * * * Request timed out.
5 56 ms 55 ms 55 ms 4.56.69.111.static.snap.net.nz [111.69.56.4]
6 54 ms 54 ms 55 ms 5.56.69.111.static.snap.net.nz [111.69.56.5]
7 56 ms 55 ms 56 ms ten-0-0-0-3.cor03.syd03.nsw.VOCUS.net.au [114.31
.192.208]
8 55 ms 56 ms 55 ms ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.7
2.73]
9 56 ms 55 ms 55 ms tengigabitethernet8-4.ult2.sydney.telstra.net [1
39.130.73.105]
10 60 ms 66 ms 59 ms bundle-ether7-100.ken-core4.sydney.telstra.net [
203.50.20.1]
11 58 ms 58 ms 55 ms bundle-ether19.ken-core10.sydney.telstra.net [20
3.50.11.129]
12 72 ms 69 ms 70 ms bundle-ether12.win-core10.melbourne.telstra.net
[203.50.11.123]
13 86 ms 85 ms 80 ms bundle-ether6.fli-core1.adelaide.telstra.net [20
3.50.11.90]
14 110 ms 107 ms 107 ms bundle-ether5.wel-core3.perth.telstra.net [203.5
0.11.19]
15 106 ms 105 ms 107 ms 203.50.9.6
16 157 ms 157 ms 156 ms i-0-1-4-0.istt-core02.bx.telstraglobal.net [202.
84.141.154]
17 152 ms 153 ms 154 ms i-0-0-0-0.istt03.bi.telstraglobal.net [202.84.24
3.74]
18 155 ms 150 ms 154 ms unknown.telstraglobal.net [202.126.128.90]
19 151 ms 159 ms 152 ms xe-1-1-1.gw401.sg2.ap.equinix.com [27.111.222.10
7]
20 152 ms 153 ms 155 ms 27.111.214.82
21 151 ms 152 ms 151 ms sg2-n5596-fe-1-vl231.wargaming.net [92.223.116.1
63]
22 153 ms 152 ms 159 ms sg2-sl-a133.worldoftanks.sg [92.223.16.133]

Trace complete.

Impressed. Very impressed. Please keep the cattle prod to the hamster :-)

cheers

hio77

'That VDSL Cat'
12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

Subscriber

#1148814 7-Oct-2014 01:49

170~ ms in Auckland, VDSL DLM-1

At a glance, comparing the route ild say the difference between mine and others, looks like the route back is where the "latency jump" is for me now!

great work snap!

Tracing route to sg2-sl-a133.worldoftanks.sg [92.223.16.133]
over a maximum of 30 hops:

1 6 ms 6 ms 6 ms 16.17.69.111.static.snap.net.nz [111.69.17.16]
2 7 ms 6 ms 5 ms 16.17.69.111.static.snap.net.nz [111.69.17.16]
3 5 ms 5 ms 5 ms 54.32.69.111.static.snap.net.nz [111.69.32.54]
4 28 ms 29 ms 28 ms 4.56.69.111.static.snap.net.nz [111.69.56.4]
5 28 ms 28 ms 28 ms 5.56.69.111.static.snap.net.nz [111.69.56.5]
6 29 ms 28 ms 30 ms ten-0-0-0-3.cor03.syd03.nsw.VOCUS.net.au [114.31.192.208]
7 29 ms 29 ms 29 ms ten-1-0-0.bdr03.syd04.nsw.VOCUS.net.au [175.45.72.73]
8 29 ms 28 ms 28 ms tengigabitethernet8-4.ult2.sydney.telstra.net [139.130.73.105]
9 32 ms 30 ms 30 ms bundle-ether7-100.ken-core4.sydney.telstra.net [203.50.20.1]
10 29 ms 30 ms 30 ms bundle-ether19.ken-core10.sydney.telstra.net [203.50.11.129]
11 43 ms 42 ms 42 ms bundle-ether12.win-core10.melbourne.telstra.net[203.50.11.123]
12 52 ms 55 ms 55 ms bundle-ether6.fli-core1.adelaide.telstra.net [203.50.11.90]
13 80 ms 82 ms 82 ms bundle-ether5.wel-core3.perth.telstra.net [203.50.11.19]
14 82 ms 82 ms 84 ms 203.50.9.6
15 129 ms 131 ms 130 ms i-0-0-1-0.istt-core02.bx.telstraglobal.net [202.84.141.158]
16 128 ms 128 ms 128 ms i-0-0-2-0.istt03.bi.telstraglobal.net [202.84.225.238]
17 241 ms 241 ms 241 ms unknown.telstraglobal.net [202.126.128.90]
18 224 ms 224 ms 224 ms xe-1-1-1.gw401.sg2.ap.equinix.com [27.111.222.107]
19 173 ms 173 ms 174 ms 27.111.214.82
20 171 ms 171 ms 172 ms sg2-n5596-fe-1-vl231.wargaming.net [92.223.116.163]
21 174 ms 170 ms 174 ms sg2-sl-a133.worldoftanks.sg [92.223.16.133]

#include <std_disclaimer>

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

DulceEtDecorumEst

13 posts

Geek

#1148823 7-Oct-2014 06:50

Yeah, big ups for SNAP, got past the symptoms and down to fixing the causes, not the easiest of things to do when you are bound up in a bunch of wholesale deals. Real customer service, deserve more customers. Nice.

MattR

224 posts

Master Geek

#1149314 7-Oct-2014 17:32

and back to 170ms again for me. Looks like Wargaming is sending the traffic back to me via Japan :(

hio77

'That VDSL Cat'
12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

Subscriber

#1149329 7-Oct-2014 17:44

MattR: and back to 170ms again for me. Looks like Wargaming is sending the traffic back to me via Japan :(

on the upside, snap have done their part in helping the situation, so if you can convince wargaming to do the same..... you will be set!

#include <std_disclaimer>

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

MattR

224 posts

Master Geek

#1149342 7-Oct-2014 17:57

but that's the thing... I just spent the last two months getting them to fix it, and it's been undone :(

Week 33 is when Wargaming started sending traffic back via Japan.
Week 38 is where Snap started sending traffic to Wargaming via Japan.
Week 39 is where Wargaming 'fixed' the return path to via Perth.
yesterday is when Snap started sending traffic via Perth.
today is when Wargaming->snap is back to via Japan.

hio77

'That VDSL Cat'
12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

Subscriber

#1149346 7-Oct-2014 18:01

unfortunately routing can be a pain.

there is probably a team managing it, and once accidental removal could mean, oh. nope. back to default you go.

Worth pointing out, it was on netgate (Global gateways) side that traffic started going via japan not snaps. Looks like snap have worked with their upstreams to find an effective Path however.

Sounds like wargaming is only temporarily "fixing" it, maybe they are trying new things on their end to avoid the more expensive routing and hoping you accept it as is?

#include <std_disclaimer>

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

MattR

224 posts

Master Geek

#1149374 7-Oct-2014 18:20

I know how routing works. I run my own AS.

It certainly looks that way, I've never had much luck with WG support. And for the amount of money I spend on this game, I'm certainly not going to accept it.

hio77

'That VDSL Cat'
12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

Subscriber

#1149376 7-Oct-2014 18:21

MattR: I know how routing works. I run my own AS.

It certainly looks that way, I've never had much luck with WG support. And for the amount of money I spend on this game, I'm certainly not going to accept it.

did not mean to try to reteach you.

point being, it seems wargaming will need a bit of jumping on their back again!

#include <std_disclaimer>

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

pchs

184 posts

Master Geek

#1149495 7-Oct-2014 21:00

hio77:
MattR: I know how routing works. I run my own AS.

It certainly looks that way, I've never had much luck with WG support. And for the amount of money I spend on this game, I'm certainly not going to accept it.

did not mean to try to reteach you.

point being, it seems wargaming will need a bit of jumping on their back again!

You run your own ASN on a Residential Connection? I assume this is not the case (I doubt Snap would allow you to run BGP on a Residential service) If you did run your ASN then it would be on a Business Service where you would have access to engineers who could probably troubleshoot further.

If the path has been changed back at the remote end there is very little if anything that Snap can do, in all honesty you as end users using the service would have more luck getting World of Tanks to change their route back.

MattR

224 posts

Master Geek

#1149896 8-Oct-2014 12:52

pchs: You run your own ASN on a Residential Connection? I assume this is not the case

Uhh no, for work. Nothing to do with Snap.

If the path has been changed back at the remote end there is very little if anything that Snap can do, in all honesty you as end users using the service would have more luck getting World of Tanks to change their route back.

Yes of course, I have tickets open with WG too. But both sides need to be involved, as the routes in both directions have been far from optimal in the last month or two.

1 | 2 | 3 | 4