Spark VDSL High Latency

Forums › Spark New Zealand (including Skinny and BigPipe) › Spark VDSL High Latency

1 | 2 | 3 | 4 | 5 | 6 | 7

yitz

2075 posts

Uber Geek

#2052660 10-Jul-2018 13:33

The "fix" will be for some $$$ to change hands. I'm guessing Telstra have finally realised Spark are no longer associated with AAPT and that they no longer need to maintain any settlement-free peering with them.

So the options would be for Spark to pay Telstra or relinquish peering with them (and reduce diversity options in their Aus domestic connectivity, everything go through NTT).

Linux

11424 posts

Uber Geek

Trusted

Lifetime subscriber

#2052661 10-Jul-2018 13:38

jspk:

noroad:

jspk:

Month later and issue still not fixed and no updates from spark

um, you are not still expecting this to get fixed at this point are you? If its been a month I would suggest its now in the too hard bucket and the case has been quietly closed, after all you do have communication with the end point, its just sub-optimal routing. If you want optimised routing I would suggest picking a service provider with an open peering policy.

Surely this latency/sub-optimal routing is being noticed by others and is something they'd want to fix? Looks pretty bad when other ISP's aren't having this issue.
Do I just have to wait for this to be fixed overseas?
Anyone who had this issue have a workaround for this (vpn etc.)?

Working as designed so NFF

John

sbiddle

30853 posts

Uber Geek

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#2052662 10-Jul-2018 13:39

jspk:

Surely this latency/sub-optimal routing is being noticed by others and is something they'd want to fix? Looks pretty bad when other ISP's aren't having this issue.
Do I just have to wait for this to be fixed overseas?
Anyone who had this issue have a workaround for this (vpn etc.)?

"Sub optimal" routing occurs throughout the Internet - such things happen in NZ where a number of RSPs only Interconnect in Auckland so traffic from say an Invercargill customer to another Invercargill customer has to route via Auckland.

Nothing is broken per se, it's simply how the Internet works. A "fix" for something that's not actually broken won't necessarily happen, especially when changes are probably based around peering and interconnects and obviously revolve around $ rather than anything else.

If you don't like the way traffic is routing you should change providers.

jspk

35 posts

Geek

#2052747 10-Jul-2018 14:51

sbiddle:

jspk:

Surely this latency/sub-optimal routing is being noticed by others and is something they'd want to fix? Looks pretty bad when other ISP's aren't having this issue.
Do I just have to wait for this to be fixed overseas?
Anyone who had this issue have a workaround for this (vpn etc.)?

"Sub optimal" routing occurs throughout the Internet - such things happen in NZ where a number of RSPs only Interconnect in Auckland so traffic from say an Invercargill customer to another Invercargill customer has to route via Auckland.

Nothing is broken per se, it's simply how the Internet works. A "fix" for something that's not actually broken won't necessarily happen, especially when changes are probably based around peering and interconnects and obviously revolve around $ rather than anything else.

If you don't like the way traffic is routing you should change providers.

A lot have mentioned that Spark don't openly peer and is likely the cause (or reason they wont fix this), which ISP offers the best open peering/routing support?

noroad

949 posts

Ultimate Geek

Trusted

#2052772 10-Jul-2018 15:41

A lot have mentioned that Spark don't openly peer and is likely the cause (or reason they wont fix this), which ISP offers the best open peering/routing support?

Most service providers outside of Spark/Vodafone (and sub brands) openly peer.

hashbrown

463 posts

Ultimate Geek

#2052922 10-Jul-2018 21:00

Those saying this can't be fixed without a change in peering need to remember that some of the prefixes are actually fine.

e.g. 125.238.0.0/20 has a reasonable route back from Telstra

1 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.324 ms 0.266 ms 0.239 ms
2 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) 2.485 ms 1.541 ms 2.114 ms
3 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 12.107 ms 12.287 ms 12.858 ms
4 bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93) 12.106 ms 12.289 ms 12.980 ms
5 bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98) 13.106 ms 14.160 ms 12.858 ms
6 i-0-1-0-49.sydp-core04.telstraglobal.net (202.84.223.17) 13.731 ms 14.035 ms 12.606 ms
7 i-0-6-0-0-529-peer.sydp01.pr.telstraglobal.net (134.159.124.221) 14.229 ms 15.782 ms 13.356 ms
8 spark_newzealand-peer.sydp01.pr.telstraglobal.net (134.159.124.222) 12.108 ms 12.252 ms 12.231 ms
9 122.56.119.85 (122.56.119.85) 13.856 ms 12.411 ms 12.483 ms
10 xe0-0-3.tkbr12.global-gateway.net.nz (122.56.119.125) 35.092 ms
11 ae10-10.akbr7.global-gateway.net.nz (202.50.232.30) 35.895 ms
12 ae7-2.akbr6.global-gateway.net.nz (122.56.119.54) 36.395 ms 35.774 ms *

but 115.188.240.0/20 doesn't

1 gigabitethernet3-3.exi1.melbourne.telstra.net (203.50.77.49) 0.269 ms 0.265 ms 0.241 ms
2 bundle-ether3-100.exi-core10.melbourne.telstra.net (203.50.80.1) 0.991 ms 1.415 ms 2.242 ms
3 bundle-ether12.chw-core10.sydney.telstra.net (203.50.11.124) 11.612 ms 12.162 ms 12.983 ms
4 bundle-ether1.oxf-gw11.sydney.telstra.net (203.50.6.93) 12.987 ms 12.162 ms 12.986 ms
5 bundle-ether1.sydo-core03.sydney.reach.com (203.50.13.98) 12.858 ms 12.660 ms 12.983 ms
6 i-0-1-0-17.sydo-core04.bi.telstraglobal.net (202.84.222.62) 12.985 ms
7 i-64.1wlt-core02.telstraglobal.net (202.84.136.209) 155.329 ms
8 i-61.1wlt-core02.telstraglobal.net (202.84.136.157) 160.576 ms
9 i-92.eqla01.bi.telstraglobal.net (202.84.253.82) 160.312 ms
10 206.82.129.90 (206.82.129.90) 152.903 ms 152.832 ms 153.401 ms
11 ae0-10.lebr7.global-gateway.net.nz (202.50.232.41) 158.150 ms 158.201 ms 153.176 ms
12 xe0-0-2.tkbr12.global-gateway.net.nz (202.50.232.161) 153.378 ms
13 xe0-0-1.akbr7.global-gateway.net.nz (203.96.120.193) 157.641 ms
14 122.56.127.54 (122.56.127.54) 163.094 ms *

kiwirock

685 posts

Ultimate Geek

#2055994 13-Jul-2018 22:01

@jspk

I'm with the folks at Bigpipe, so half of the routes you're going through from Spark - so too am I. Funny: the xtra DNS entry on the 2nd HOP says adsl, I'm very much with Fibre.

Unfortunately, the latency to the final destination is much less for me than you. Interestingly enough though, you have lower latency to some of the routes in the middle of my trace route as I'm at the bottom of the country.

It's unfortunate the way your latency is, however it's well upstream of Spark and with routers on other networks.

Tracing route to 203.36.190.7 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms eth6-rb2011ils-in.blahblahblah.blahblah.nz [172.24.24.24]
2 6 ms 3 ms 4 ms 125-236-192-9.adsl.xtra.co.nz [125.236.192.9]
3 * * * Request timed out.
4 24 ms 24 ms 23 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
5 26 ms 23 ms 24 ms ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
6 46 ms 47 ms 47 ms xe0-0-0.sebr3.global-gateway.net.nz [202.50.232.194]
7 46 ms 47 ms 48 ms 122.56.119.86
8 48 ms 47 ms 48 ms ae-17.r20.sydnau02.au.bb.gin.ntt.net [103.13.80.121]
9 47 ms 47 ms 47 ms ae-0.au.sydnau02.au.bb.gin.ntt.net [129.250.9.14]
10 48 ms 47 ms 47 ms 202.68.65.137
11 51 ms 47 ms 47 ms bundle-ether50.chw-edge903.sydney.telstra.net [110.145.238.89]
12 50 ms 47 ms 48 ms bundle-ether2.ken-edge903.sydney.telstra.net [203.50.11.174]
13 49 ms 52 ms 52 ms bundle-ether17.ken-core10.sydney.telstra.net [203.50.11.172]
14 49 ms 47 ms 51 ms tengigabitethernet7-1.stl1.sydney.telstra.net [203.50.20.50]
15 49 ms 47 ms 47 ms telstr1429.lnk.telstra.net [165.228.136.114]
16 * * * Request timed out.
17 51 ms 51 ms 52 ms 203.36.190.7

Trace complete.

Lenovo

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

Talkiet

4792 posts

Uber Geek

Trusted

#2061527 24-Jul-2018 09:46

Some changes have been made last night and the couple of tests I have run that were previously indicating a very scenic route are now significantly more direct. Can you please check and see what the situation is like now?

I'd also be interested if anyone is still observing packet loss at peak times.

Cheers - N

Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.

wratterus

1687 posts

Uber Geek

#2061597 24-Jul-2018 10:49

All good here now. Nice work.

Tracing route to www.telstra.com.au [203.36.190.7]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 56 ms 29 ms 28 ms 69.7.69.111.static.snap.net.nz [111.69.7.69]
3 * * * Request timed out.
4 62 ms 63 ms 62 ms 4.56.69.111.static.snap.net.nz [111.69.56.4]
5 62 ms 70 ms 63 ms 5.56.69.111.static.snap.net.nz [111.69.56.5]
6 77 ms 72 ms 73 ms BE-108.cor02.syd04.nsw.VOCUS.net.au [114.31.192.86]
7 90 ms 86 ms 90 ms bundle-101.bdr01.syd11.nsw.vocus.net.au [114.31.192.83]
8 85 ms 81 ms 85 ms Bundle-Ether12.ken-edge903.sydney.telstra.net [203.27.185.57]
9 88 ms 92 ms 91 ms bundle-ether17.ken-core10.sydney.telstra.net [203.50.11.172]
10 81 ms 82 ms 83 ms tengigabitethernet7-1.stl1.sydney.telstra.net [203.50.20.50]
11 92 ms 89 ms 85 ms telstr1429.lnk.telstra.net [165.228.136.114]
12 * * * Request timed out.
13 66 ms 65 ms 66 ms 203.36.190.7

Spark

Tracing route to www.telstra.com.au [203.36.148.7]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home.gateway.pace.net [192.168.1.254]
2 1 ms 1 ms 1 ms home.gateway.pace.net [192.168.1.254]
3 * * * Request timed out.
4 32 ms 31 ms 31 ms mdr-ip24-int.msc.global-gateway.net.nz [122.56.116.6]
5 31 ms 31 ms 31 ms ae8-10.akbr6.global-gateway.net.nz [122.56.116.5]
6 31 ms 32 ms 31 ms ae2-6.tkbr12.global-gateway.net.nz [122.56.127.17]
7 54 ms 54 ms 54 ms xe7-0-2.sebr3.global-gateway.net.nz [202.50.232.234]
8 55 ms 55 ms 55 ms 122.56.119.86
9 55 ms 54 ms 55 ms ae-17.r20.sydnau02.au.bb.gin.ntt.net [103.13.80.121]
10 55 ms 55 ms 55 ms ae-0.au.sydnau02.au.bb.gin.ntt.net [129.250.9.14]
11 55 ms 66 ms 56 ms 202.68.65.137
12 56 ms 56 ms 55 ms Bundle-Ether50.chw-edge903.sydney.telstra.net [110.145.238.89]
13 55 ms 55 ms 55 ms bundle-ether2.ken-edge903.sydney.telstra.net [203.50.11.174]
14 56 ms 57 ms 57 ms bundle-ether17.ken-core10.sydney.telstra.net [203.50.11.172]
15 68 ms 68 ms 68 ms bundle-ether10.win-core10.melbourne.telstra.net [203.50.11.123]
16 66 ms 66 ms 67 ms tengigabitethernet7-1.win22.melbourne.telstra.net [203.50.80.162]
17 67 ms 67 ms 70 ms telstr745.lnk.telstra.net [139.130.39.114]
18 * * * Request timed out.
19 68 ms 68 ms 68 ms 203.36.148.7

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#2061611 24-Jul-2018 11:04

damn, those paces are still out 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.

wratterus

1687 posts

Uber Geek

#2061614 24-Jul-2018 11:07

hio77:

damn, those paces are still out there!

This one goes hard. :p

This is just an ADSL line that is pretty much solely for testing - that actual modem gets very little use.

hio77

12999 posts

Uber Geek

ID Verified

Trusted

Lizard Networks

#2061617 24-Jul-2018 11:11

wratterus:
hio77:

damn, those paces are still out there!

This one goes hard. :p

This is just an ADSL line that is pretty much solely for testing - that actual modem gets very little use.

I still remember the first one i reset...
What? Wifi isn't turned on out of the box!!

#include <std_disclaimer>

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

1 | 2 | 3 | 4 | 5 | 6 | 7