Network Latency result

Forums › New Zealand Broadband › Network Latency result

kellogs

3 posts

Wannabe Geek

# 99583 22-Mar-2012 11:03

Dear Geekzone members,

We are a managed hosting company based in Singapore and one of our customer in NZ has feedback to us that they are experiencing slowness when accessing the content from New Zealand.

I am sincerely requesting for your help to traceroute to our IP and post the result here - please indicate which is your ISP.

IP address 103.29.106.4

Thank you very much for your help and it is very much appreciated.

1 | 2

19282 posts

Uber Geek
Inactive user

# 598586 22-Mar-2012 11:08

What ISP / Plan is your New Zealand customer on?

Maybe the traffic is gettng shaped / managed

cisconz

cisconz
1220 posts

Uber Geek

Trusted

Lifetime subscriber

# 598591 22-Mar-2012 11:26

From Actrix Wireless in Auckland

Tracing route to 10g-adn-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

2 8 ms 4 ms 3 ms 203.96.xxx.xxx
3 15 ms 15 ms 14 ms wn-sum-2-bclisn.connections.net.nz [202.49.152.136]
4 23 ms 30 ms 22 ms 192.168.100.37
5 * * * Request timed out.
6 160 ms 186 ms 154 ms 203.167.233.9
7 153 ms 155 ms 155 ms i-7-0-0.hptw-core01.bi.reach.com [202.84.219.125]
8 174 ms 177 ms 173 ms i-0-0-4-1.sydo-core02.bx.reach.com [202.84.142.149]
9 173 ms 171 ms 172 ms i-0-3-2-0.sydo-core01.bi.reach.com [202.84.220.190]
10 237 ms 237 ms 235 ms i-0-0-1.pthp-core01.bi.reach.com [202.84.144.193]
11 251 ms 266 ms 252 ms i-3-3-2.6ntp-core01.bx.reach.com [202.84.141.86]
12 283 ms 282 ms 282 ms i-0-3-0-0.6ntp02.bi.reach.com [202.84.243.82]
13 278 ms 281 ms 285 ms 10g-adn-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

From Telecom ADSL in Auckland

2 1 ms 14 ms 1 ms 219-89-51-1.dialup.xtra.co.nz [219.89.51.1]
3 * 146 ms 154 ms mdr-fid-int.akbr5.global-gateway.net.nz [202.37.244.222]
4 1 ms 15 ms 6 ms ae4-10.akbr5.global-gateway.net.nz [202.37.244.221]
5 1 ms 14 ms 1 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
6 3 ms 19 ms 6 ms xe6-0-0.sgbr1.global-gateway.net.nz [202.50.232.10]
7 18 ms 3 ms 6 ms xe2-0-0-2.sgbr2.global-gateway.net.nz [202.50.232.246]
8 3 ms 17 ms 5 ms pccw-global.sgbr2.global-gateway.net.nz [202.50.238.194]
9 18 ms 30 ms 30 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126.173.149]
10 30 ms 17 ms 30 ms 10G-ADN-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

From Actrix Fibre in Wellington

Tracing route to 10g-adn-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

2 2 ms 1 ms 1 ms 203.96.xxx.xxx
3 2 ms 2 ms 1 ms 202.49.152.197
4 6 ms 4 ms 5 ms 192.168.100.33
5 * * * Request timed out.
6 138 ms 139 ms 142 ms 203.167.233.9
7 140 ms 137 ms 138 ms i-7-0-0.hptw-core01.bi.reach.com [202.84.219.125]
8 160 ms 159 ms 159 ms i-0-0-4-0.sydo-core02.bx.reach.com [202.84.142.153]
9 160 ms 159 ms 161 ms i-0-3-2-0.sydo-core01.bi.reach.com [202.84.220.190]
10 219 ms 218 ms 220 ms i-3-2.pthp-core01.bi.reach.com [202.84.249.193]
11 238 ms 238 ms 238 ms i-2-1-0.6ntp-core01.bx.reach.com [202.84.141.74]
12 280 ms 271 ms 268 ms i-0-3-0-0.6ntp02.bi.reach.com [202.84.243.82]
13 268 ms 267 ms 273 ms 10g-adn-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

From Kordia Fibre in Auckland

Tracing route to 10g-adn-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 124.157.xxx.xxx
2 1 ms 1 ms 1 ms 124.157.xxx.xxx
3 1 ms 1 ms 1 ms 124.157.114.6
4 1 ms 1 ms 1 ms kordia.cre2.nct.odyssey.net.nz [121.99.12.20]
5 25 ms 25 ms 25 ms p17746.syd.equinix.com [202.167.228.93]
6 25 ms 26 ms 27 ms 202.167.228.80
7 129 ms 131 ms 133 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126.173.149]
8 128 ms 129 ms 129 ms 10g-adn-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

Hmmmm

kellogs

3 posts

Wannabe Geek

# 598592 22-Mar-2012 11:29

johnr: What ISP / Plan is your New Zealand customer on?

Maybe the traffic is gettng shaped / managed

Good Morning Johnr,

Customer is on Orcon.

May I know which are the 3 biggest ISP in NZ?

Thank you.

Regards,
Edy

kellogs

3 posts

Wannabe Geek

# 598593 22-Mar-2012 11:30

Awesome information cisconz! Thank you very much :)

freitasm

BDFL - Memuneh
64625 posts

Uber Geek

Administrator

Trusted

Geekzone

Lifetime subscriber

# 598657 22-Mar-2012 13:58

From TelstraClear cable, 100Mbps, Wellington:

Tracing route to 10G-ADN-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

1 2 * * * Request timed out.
3 9 ms 9 ms 9 ms lo0.internet.ivpn.pe25.telstraclear.net [218.101.61.124]
4 18 ms 19 ms 20 ms ie2-g-0-0-0.telstraclear.net [203.98.50.2]
5 18 ms 19 ms 20 ms ge-0-2-0-1.xcore1.acld.telstraclear.net [203.98.50.251]
6 19 ms 18 ms 19 ms 203.167.233.9
7 20 ms 19 ms 19 ms i-7-0-0.hptw-core01.bi.reach.com [202.84.219.125]
8 44 ms 43 ms 43 ms i-0-0-4-1.sydo-core02.bx.reach.com [202.84.142.149]
9 44 ms 43 ms 64 ms i-0-3-2-0.sydo-core01.bi.reach.com [202.84.220.190]
10 100 ms 97 ms 99 ms i-3-2.pthp-core01.bi.reach.com [202.84.249.193]
11 145 ms 145 ms 145 ms i-6-2.6ntp-core01.bx.reach.com [202.84.141.166]
12 149 ms 151 ms 150 ms i-0-3-0-0.6ntp02.bi.reach.com [202.84.243.82]
13 148 ms 147 ms 146 ms 10G-ADN-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

Orcon you say? Things to note:

1.Orcon has unbundled DSL services (their own gear in exchanges) and wholesale connections
2.If customs is connected to a cabinet but Orcon provisioned the connection to the unbundled service, they will suffer of mid-span injection. This is, unfortunately, quite common with Orcon connections.

To solve (2) the customer will need to find it he's connected to a cabinet and what type of service Orcon is providing. Note a wholesale service costs a bit more since a third party is involved (Chorus).

My technology disclosure | Digital Transformation | Enterprise Content Management | Customer Relationship Management | Data Insights, Business Intelligence and Advanced Analytics

Beccara

1124 posts

Uber Geek

# 598697 22-Mar-2012 15:00

Look at the trace's, Somethings going on inside reach thats causing a 140ms difference between the traces here. Ignoring the Telecom ADSL trace which shows 30ms.

Kordia shows 130ms, Telstra shows 150ms, Actrix shows 270ms and I'm showing 220ms from one provider and 140ms on another.

6 29 ms 28 ms 27 ms 202.167.228.80
7 227 ms 228 ms 233 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126.173.149]

Seems to be a bit of a problem hop. It looks like either you or your hosting company needs to talk to whoever sells your transit or handles the reach peering to see whats going on

Most problems are the result of previous solutions...

All comment's I make are my own personal opinion and do not in any way, shape or form reflect the views of current or former employers unless specifically stated

Zeon

3493 posts

Uber Geek

Trusted

# 598722 22-Mar-2012 16:07

It looks like your upstream, Reach has some issues. Orcon interconnects with Reach at Equinix Sydney. It's about 28ms from Auckland to Sydney anhd this is all orcon's Odyssey network so very quick. Reach may have some issues with their connection into Equinix Sydney such as overloading (Equinix are major peering points all around the world).

Orcon Fibre:

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

C:\Users\jonathan.spence>tracert 103.29.106.4

Tracing route to 10g-adn-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms oceanus.power-business.co.nz [10.2.253.1]
2 2 ms 4 ms 3 ms 60.234.23.1
3 2 ms 1 ms 2 ms 121.99.12.0
4 26 ms 26 ms 25 ms p17746.syd.equinix.com [202.167.228.93]
5 26 ms 26 ms 25 ms 202.167.228.80
6 261 ms 258 ms 258 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126
.173.149]
7 223 ms 223 ms 223 ms 10g-adn-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

C:\Users\jonathan.spence>

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

C:\Users\jonathan.spence>ping 103.29.106.4

Pinging 103.29.106.4 with 32 bytes of data:
Reply from 103.29.106.4: bytes=32 time=228ms TTL=245
Reply from 103.29.106.4: bytes=32 time=223ms TTL=245
Reply from 103.29.106.4: bytes=32 time=224ms TTL=245
Reply from 103.29.106.4: bytes=32 time=223ms TTL=245

Ping statistics for 103.29.106.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 223ms, Maximum = 228ms, Average = 224ms

C:\Users\jonathan.spence>

Speedtest 2019-10-14

DjShadow

3002 posts

Uber Geek

Trusted

# 598743 22-Mar-2012 17:12

From Hamilton - Slingshot - ADSL2+ non-interleaved connection:

Tracing route to 10G-ADN-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.0.1]
2 10 ms 11 ms 11 ms 202.180.81.30
3 9 ms 9 ms 9 ms p85.pool-82.callplus.net.nz [202.180.82.85]
4 9 ms 10 ms 9 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
5 10 ms 9 ms 10 ms xe-0-0-0-4061.cpcak2-r1.tranzpeer.net [101.98.1.
82]
6 35 ms 34 ms 34 ms ae2-0.cpcsy1-r1.tranzpeer.net [101.98.1.90]
7 36 ms 34 ms 37 ms 202.167.228.80
8 262 ms 265 ms 263 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126
.173.149]
9 262 ms 263 ms 262 ms 10G-ADN-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

Ragnor

8033 posts

Uber Geek

Trusted

# 598758 22-Mar-2012 17:49

kellogs:

May I know which are the 3 biggest ISP in NZ?

For residential internet market share, I think it would be:

Telecom > Telstraclear > Vodafone > Orcon

Business is a lot harder to estimate.

pieeta

3 posts

Wannabe Geek

# 598763 22-Mar-2012 17:57

I am getting some pretty horrible packet loss from my home connection (Vodafone ADSL down town Wellington)
2. my.router 0.0% 168 0.7 0.6 0.6 0.8 0.0
3. be2-100.bras1wtc.wlg.vf.net.nz 1.8% 168 20.3 63.3 16.4 608.0 153.3
4. 203.109.129.114 1.2% 168 16.8 16.6 15.8 19.5 0.4
5. gi0-2-0-3.ppnzwtc02.wlg.vf.net.nz 0.0% 168 16.8 16.4 15.5 25.2 0.7
6. ip-145.199.31.114.VOCUS.net.au 0.0% 168 153.5 153.3 152.6 154.5 0.3
7. 10gigabitethernet8-3.core1.sjc2.he.net 0.0% 168 153.7 155.1 151.9 174.8 3.7
8. ???
9. i-0-2-1-0.eqnx-core01.bi.reach.com 7.2% 167 182.9 183.0 181.3 214.0 3.9
10. i-2-2.siko-core01.bx.reach.com 0.0% 167 252.1 251.0 250.0 254.2 0.6
11. i-3-2-1.hkhh-core01.bx.reach.com 0.6% 167 249.7 249.9 249.0 251.4 0.5
12. i-3-0-2.istt-core01.bx.reach.com 99.4% 167 259.1 259.1 259.1 259.1 0.0
13. unknown.net.reach.com 99.4% 167 262.6 262.6 262.6 262.6 0.0
14. 10G-ADN-103-29-106-4.solone.net 88.0% 167 260.4 260.9 259.9 266.9 1.5

CityLink fiber has no issues ( Also down town Wellington):

2. 113.197.96.33 0.0% 11 4.6 4.4 3.9 5.4 0.5
3. 113.197.99.32 0.0% 11 16.3 16.5 15.8 20.0 1.3
4. 113.197.99.33 0.0% 11 15.8 20.2 15.8 53.3 11.1
5. vibe-international.snap.net.nz 0.0% 11 15.9 16.4 15.8 18.8 0.8
6. 111-69-27-65.core.snap.net.nz 0.0% 11 16.4 17.5 16.1 27.1 3.2
7. 203.167.233.9 0.0% 10 16.6 16.8 16.5 17.1 0.2
8. i-7-0-0.hptw-core01.bi.reach.com 0.0% 10 17.1 17.1 16.4 18.5 0.7
9. i-0-0-4-0.sydo-core02.bx.reach.c 0.0% 10 40.9 41.1 40.7 41.5 0.3
10. i-0-3-2-0.sydo-core01.bi.reach.c 0.0% 10 41.9 41.5 41.0 42.5 0.5
11. i-0-0-1.pthp-core01.bi.reach.com 0.0% 10 96.2 96.1 95.8 97.0 0.4
12. i-2-1-0.6ntp-core01.bx.reach.com 0.0% 10 143.8 143.7 143.3 144.0 0.3
13. i-0-3-0-0.6ntp02.bi.reach.com 0.0% 10 146.5 146.1 145.0 147.4 0.8
14. 10G-ADN-103-29-106-4.solone.net 0.0% 10 143.8 143.9 143.7 144.0 0.1

mercutio

1387 posts

Uber Geek

# 598801 22-Mar-2012 19:07

Beccara: Look at the trace's, Somethings going on inside reach thats causing a 140ms difference between the traces here. Ignoring the Telecom ADSL trace which shows 30ms.

Kordia shows 130ms, Telstra shows 150ms, Actrix shows 270ms and I'm showing 220ms from one provider and 140ms on another.

6 29 ms 28 ms 27 ms 202.167.228.80
7 227 ms 228 ms 233 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126.173.149]

Seems to be a bit of a problem hop. It looks like either you or your hosting company needs to talk to whoever sells your transit or handles the reach peering to see whats going on

the telecom adsl trace is obviously inaccurate. maybe some kind of timing issue.

pretty much i'd say the pings are good - except for vocus on the outbound path and whoever actrix are using on the inbound path.

i've noticed with starcraft which is hosted in singapore that there is a huge variety in how quickly people can download new maps. like 2degrees 3g is faster than some australian providers.

there can be quite a lot of instances of routing through the US - especially if hurricance electric are involved.

like if you go to http://lg.he.net and trace from the hurricane electric singapore node chances are it'll route through the US giving 300msec+ latency.

Athlonite

1828 posts

Uber Geek
Inactive user

# 598823 22-Mar-2012 20:08

From Napier on Orcon via telecom wholesale

3 36 ms 38 ms 37 ms xe-1-0-0.cre1.nct.orcon.net.nz [121.98.9.13]
4 39 ms 37 ms 38 ms 121.99.12.0
5 62 ms 61 ms 62 ms p17746.syd.equinix.com [202.167.228.93]
6 63 ms * 61 ms 202.167.228.80
7 265 ms 263 ms 263 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126.173.149]
8 292 ms 291 ms 292 ms 10G-ADN-103-29-106-4.solone.net [103.29.106.4]

it would appear that this is the problem area i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126.173.149] with an 260+ ms ping

techmeister

310 posts

Ultimate Geek

# 600002 26-Mar-2012 07:51

Slingshot unlimited

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

C:\Users\User 1>tracert 103.29.106.4

Tracing route to 10G-ADN-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 3 ms 3 ms 2 ms 192.168.0.1
3 16 ms 16 ms 15 ms cpiak1-l9-G-internet.tranzpeer.net [202.180.81.3
2]
4 74 ms 16 ms 19 ms vlan93-cpcak3-e1.tranzpeer.net [202.180.76.68]
5 17 ms 17 ms 16 ms vlan7-cpcak3-s1.tranzpeer.net [202.180.81.49]
6 17 ms 16 ms 17 ms xe-0-0-0-4061.cpcak2-r1.tranzpeer.net [101.98.1.
82]
7 41 ms 42 ms 41 ms ae2-0.cpcsy1-r1.tranzpeer.net [101.98.1.90]
8 42 ms 42 ms 42 ms 202.167.228.80
9 269 ms 268 ms 268 ms i-0-1-0-0-3001-peer.6ntp02.pr.reach.com [202.126
.173.149]
10 268 ms 268 ms 268 ms 10G-ADN-103-29-106-4.solone.net [103.29.106.4]

Trace complete.

C:\Users\User 1>

WrEK

82 posts

Master Geek

# 600082 26-Mar-2012 10:13

Orcon

Napster

202 posts

Master Geek

# 600527 27-Mar-2012 00:41

Through Snap VDSL.

Dead after 6th hop. Wonder whats causing that.

Tracing route to 10G-ADN-103-29-106-4.solone.net [103.29.106.4]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms READYSHARE [192.168.1.1]
2    <1 ms    <1 ms    <1 ms 192.168.178.1
3    38 ms    50 ms    51 ms 16.17.69.111.static.snap.net.nz [111.69.17.16]
4    32 ms    33 ms    32 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]

5    32 ms    33 ms    33 ms 111-69-27-65.core.snap.net.nz [111.69.27.65]
6    33 ms    33 ms    33 ms 203.167.233.10
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.
10     *        *        *     Request timed out.

1 | 2