High pings to Spark/Bigpipe IPs

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › High pings to Spark/Bigpipe IPs

Threarah

45 posts

Geek
+1 received by user: 20

#248183 13-Mar-2019 15:45

I've just noticed that I seem to be getting quite high latency to some(?) Spark IPs:

Tracing route to 122-61-211-xxx-adsl.sparkbb.co.nz [122.61.211.xxx]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms xxxxxxxxxxxxxxxxxxx
2     1 ms     1 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    18 ms    18 ms    18 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4   151 ms   150 ms   150 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5   153 ms   153 ms   155 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.33]
6     *        *      151 ms mdr-ip24-dom.msc.global-gateway.net.nz [122.56.116.10]
7   170 ms   164 ms   165 ms 122-61-208-1-adsl.sparkbb.co.nz [122.61.208.1]
8   171 ms   171 ms   172 ms 122-61-211-xxx-adsl.sparkbb.co.nz [122.61.211.xxx]

That's going from Christchurch (2degrees 200/20 UFB) to Darfield (Bigpipe ADSL), but even if it's going the long way via Auckland its still rather high. Here's what it looks like going the other way:

traceroute to 151.210.219.xxx (151.210.219.xxx), 30 hops max, 38 byte packets
1 125-239-11-1-adsl.sparkbb.co.nz (125.239.11.1) 10.081 ms 9.936 ms 10.908 ms
2 * * *
3 ae8-10.akbr6.global-gateway.net.nz (122.56.116.5) 24.274 ms 24.817 ms 24.730 ms
4 ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 24.649 ms 23.801 ms 24.166 ms
5 ae10-10.tkbr12.global-gateway.net.nz (202.50.232.29) 25.157 ms xe-7-0-3.sjbr3.global-gateway.net.nz (203.96.120.134) 149.604 ms xe7-0-8-10.sjbr3.global-gateway.net.nz (122.56.127.14) 149.204 ms
6 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 149.207 ms 149.310 ms xe-0-0-7-3.sjbr3.global-gateway.net.nz (202.50.232.18) 149.311 ms
7 ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25) 155.646 ms 153.093 ms 153.144 ms
8 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 153.254 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net (129.250.4.119) 155.006 ms ae0.pabr5.global-gateway.net.nz (203.96.120.74) 162.946 ms
9 ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41) 160.822 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 150.010 ms ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41) 157.757 ms
10 ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 150.410 ms xe-0-0-24-3.a00.snjsca04.us.ce.gin.ntt.net (129.250.200.102) 153.347 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net (129.250.4.119) 160.546 ms
11 ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 155.557 ms 155.833 ms *
12 151.210.219.xxx (151.210.219.xxx) 171.133 ms 179.767 ms

I get a similar result to spark.co.nz itself:

Tracing route to spark.co.nz [146.171.248.36]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms xxxxxxxxxxxxxx
2     1 ms     1 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    26 ms    26 ms    25 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4   151 ms   151 ms   150 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5   153 ms   153 ms   160 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.33]
6   147 ms   146 ms   146 ms spark-sdn-ak1-dom.akcr11.global-gateway.net.nz [203.96.65.198]
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.

I don't suppose anyone else is getting funky results to similar IPs - say from 2degrees to 122.61.211.xxx ? I'll likely throw their support an email either this evening or tomorrow, and some more tracerts wouldn't go amiss when I do so.

1 | 2

meow
13579 posts

Uber Geek
+1 received by user: 10910

Moderator

ID Verified

Trusted

Lifetime subscriber

#2197368 13-Mar-2019 15:49

The main Spark domain doesn't have ICMP (Ping) turned on. I've just tested a few IP's I manage and they're all fine (30ms).

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.

Threarah

45 posts

Geek
+1 received by user: 20

#2197382 13-Mar-2019 16:03

michaelmurfy:

The main Spark domain doesn't have ICMP (Ping) turned on. I've just tested a few IP's I manage and they're all fine (30ms).

It was more the jump from 25ms to 150ms on the 4th hop when going to spark.co.nz - the same thing happens going to Darfield - rather than the later requests not responding. Thanks for the quick tests though - were any done from Christchurch?

michaelmurfy

meow
13579 posts

Uber Geek
+1 received by user: 10910

Moderator

ID Verified

Trusted

Lifetime subscriber

#2197390 13-Mar-2019 16:09

@Threarah as has been pointed out many times before on Traceroutes ping is not prioritised by the routers along the way so it is normal to see that. Also spark.co.nz doesn't have ICMP (ping) enabled so it wouldn't work.

Really nothing to see here - totally normal and nothing at all wrong with it.

dfnt

1553 posts

Uber Geek
+1 received by user: 1036

Trusted

Lifetime subscriber

#2197393 13-Mar-2019 16:14

Isn't that routing via America hence the high latency @michaelmurfy?

Probably because Spark don't peer openly etc

Threarah

45 posts

Geek
+1 received by user: 20

#2197394 13-Mar-2019 16:18

michaelmurfy:

@Threarah as has been pointed out many times before on Traceroutes ping is not prioritised by the routers along the way so it is normal to see that. Also spark.co.nz doesn't have ICMP (ping) enabled so it wouldn't work.

Really nothing to see here - totally normal and nothing at all wrong with it.

Regardless of the traceroute results, pinging 170ms from Christchurch to Darfield seems a bit excessive, no? It was previously 30-50ms. It's almost as if its recently started taking an extended scenic route.

michaelmurfy

meow
13579 posts

Uber Geek
+1 received by user: 10910

Moderator

ID Verified

Trusted

Lifetime subscriber

#2197395 13-Mar-2019 16:20

dfnt:

Isn't that routing via America hence the high latency @michaelmurfy?

Probably because Spark don't peer openly etc

I did notice that. I suspect the reason is because Spark don't play well with others in terms of peering. I know a few ISP's are pulling out from their paid peering agreement with Spark as it is costing them more than what it costs for international bandwidth.

I am going to likely get spoken to by the Spark guys here but really if latency is important between 2 sites then either have them both on Spark or them both on any ISP except Spark and Vodafone.

Mighty Ape

Shop now at Mighty Ape (affiliate link).

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#2197398 13-Mar-2019 16:23

michaelmurfy:

if latency is important between 2 sites then either have them both on Spark or them both on any ISP except Spark and Vodafone.

Yea if you need lowest possible latency between sites look at a hosted WAN solution perhaps.

If this is about self-hosted game servers (or similar), then it just is what it is.

michaelmurfy

meow
13579 posts

Uber Geek
+1 received by user: 10910

Moderator

ID Verified

Trusted

Lifetime subscriber

#2197400 13-Mar-2019 16:25

Threarah:

Regardless of the traceroute results, pinging 170ms from Christchurch to Darfield seems a bit excessive, no? It was previously 30-50ms. It's almost as if its recently started taking an extended scenic route.

Yes - this is sounding more and more like "lets send traffic via overseas to Spark as it costs us too much to send directly". Not saying it is, but it has happened to several providers now. Spark really need to get with the times in regards to playing nice with others.

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2197419 13-Mar-2019 16:58

Threarah:

I've just noticed that I seem to be getting quite high latency to some(?) Spark IPs:

Tracing route to 122-61-211-xxx-adsl.sparkbb.co.nz [122.61.211.xxx]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms xxxxxxxxxxxxxxxxxxx
2     1 ms     1 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    18 ms    18 ms    18 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4   151 ms   150 ms   150 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5   153 ms   153 ms   155 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.33]
6     *        *      151 ms mdr-ip24-dom.msc.global-gateway.net.nz [122.56.116.10]
7   170 ms   164 ms   165 ms 122-61-208-1-adsl.sparkbb.co.nz [122.61.208.1]
8   171 ms   171 ms   172 ms 122-61-211-xxx-adsl.sparkbb.co.nz [122.61.211.xxx]

That's going from Christchurch (2degrees 200/20 UFB) to Darfield (Bigpipe ADSL), but even if it's going the long way via Auckland its still rather high. Here's what it looks like going the other way:

traceroute to 151.210.219.xxx (151.210.219.xxx), 30 hops max, 38 byte packets
1 125-239-11-1-adsl.sparkbb.co.nz (125.239.11.1) 10.081 ms 9.936 ms 10.908 ms
2 * * *
3 ae8-10.akbr6.global-gateway.net.nz (122.56.116.5) 24.274 ms 24.817 ms 24.730 ms
4 ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 24.649 ms 23.801 ms 24.166 ms
5 ae10-10.tkbr12.global-gateway.net.nz (202.50.232.29) 25.157 ms xe-7-0-3.sjbr3.global-gateway.net.nz (203.96.120.134) 149.604 ms xe7-0-8-10.sjbr3.global-gateway.net.nz (122.56.127.14) 149.204 ms
6 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 149.207 ms 149.310 ms xe-0-0-7-3.sjbr3.global-gateway.net.nz (202.50.232.18) 149.311 ms
7 ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25) 155.646 ms 153.093 ms 153.144 ms
8 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 153.254 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net (129.250.4.119) 155.006 ms ae0.pabr5.global-gateway.net.nz (203.96.120.74) 162.946 ms
9 ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41) 160.822 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 150.010 ms ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41) 157.757 ms
10 ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 150.410 ms xe-0-0-24-3.a00.snjsca04.us.ce.gin.ntt.net (129.250.200.102) 153.347 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net (129.250.4.119) 160.546 ms
11 ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 155.557 ms 155.833 ms *
12 151.210.219.xxx (151.210.219.xxx) 171.133 ms 179.767 ms

I get a similar result to spark.co.nz itself:

Tracing route to spark.co.nz [146.171.248.36]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms xxxxxxxxxxxxxx
2     1 ms     1 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    26 ms    26 ms    25 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4   151 ms   151 ms   150 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5   153 ms   153 ms   160 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.33]
6   147 ms   146 ms   146 ms spark-sdn-ak1-dom.akcr11.global-gateway.net.nz [203.96.65.198]
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.

I don't suppose anyone else is getting funky results to similar IPs - say from 2degrees to 122.61.211.xxx ? I'll likely throw their support an email either this evening or tomorrow, and some more tracerts wouldn't go amiss when I do so.

Hiya,

I'm not seeing the same type of responses, see results below from within 2D core and from my connection at home.

Within 2d (We peer with Spark via GGI Domestic in Auckland)

C:\Users\nick.mackechnie>tracert 146.171.248.36

Tracing route to 146.171.248.36 over a maximum of 30 hops

1    20 ms     1 ms     1 ms 10.221.10.252
2     2 ms     2 ms     1 ms 10.69.0.5
3     7 ms    <1 ms    <1 ms 244.60.69.111.static.snap.net.nz [111.69.60.244]
4    <1 ms    <1 ms    <1 ms 64.62.69.111.static.snap.net.nz [111.69.62.64]
5    <1 ms     5 ms    <1 ms 65.62.69.111.static.snap.net.nz [111.69.62.65]
6     *        2 ms     1 ms 208.55.69.111.static.snap.net.nz [111.69.55.208]
7    18 ms    18 ms    18 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
8    32 ms    21 ms    19 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
9    18 ms    18 ms    18 ms ae9-44.akcr11.global-gateway.net.nz [122.56.127.209]
10    19 ms    21 ms    18 ms spark-sdn-ak1-dom.akcr11.global-gateway.net.nz [203.96.65.198]
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.

Via home

C:\Users\administrator.THENET>tracert 146.171.248.36

Tracing route to 146.171.248.36 over a maximum of 30 hops

1     1 ms     1 ms     1 ms thenet01.thenet.gen.nz [192.168.0.1]
2     2 ms     2 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    19 ms    20 ms    19 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4    19 ms    19 ms    24 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5    21 ms    22 ms    21 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.
33]
6    21 ms    20 ms    21 ms spark-sdn-ak1-dom.akcr11.global-gateway.net.nz [
203.96.65.198]
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9 ^C

Are you able to provide other specific IP's for us to test to?

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

Threarah

45 posts

Geek
+1 received by user: 20

#2197430 13-Mar-2019 17:12

NickMack:

Threarah:

I've just noticed that I seem to be getting quite high latency to some(?) Spark IPs:

Tracing route to 122-61-211-xxx-adsl.sparkbb.co.nz [122.61.211.xxx]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms xxxxxxxxxxxxxxxxxxx
2     1 ms     1 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    18 ms    18 ms    18 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4   151 ms   150 ms   150 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5   153 ms   153 ms   155 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.33]
6     *        *      151 ms mdr-ip24-dom.msc.global-gateway.net.nz [122.56.116.10]
7   170 ms   164 ms   165 ms 122-61-208-1-adsl.sparkbb.co.nz [122.61.208.1]
8   171 ms   171 ms   172 ms 122-61-211-xxx-adsl.sparkbb.co.nz [122.61.211.xxx]

That's going from Christchurch (2degrees 200/20 UFB) to Darfield (Bigpipe ADSL), but even if it's going the long way via Auckland its still rather high. Here's what it looks like going the other way:

traceroute to 151.210.219.xxx (151.210.219.xxx), 30 hops max, 38 byte packets
1 125-239-11-1-adsl.sparkbb.co.nz (125.239.11.1) 10.081 ms 9.936 ms 10.908 ms
2 * * *
3 ae8-10.akbr6.global-gateway.net.nz (122.56.116.5) 24.274 ms 24.817 ms 24.730 ms
4 ae7-2.akbr7.global-gateway.net.nz (122.56.119.53) 24.649 ms 23.801 ms 24.166 ms
5 ae10-10.tkbr12.global-gateway.net.nz (202.50.232.29) 25.157 ms xe-7-0-3.sjbr3.global-gateway.net.nz (203.96.120.134) 149.604 ms xe7-0-8-10.sjbr3.global-gateway.net.nz (122.56.127.14) 149.204 ms
6 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 149.207 ms 149.310 ms xe-0-0-7-3.sjbr3.global-gateway.net.nz (202.50.232.18) 149.311 ms
7 ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25) 155.646 ms 153.093 ms 153.144 ms
8 ae0.pabr5.global-gateway.net.nz (203.96.120.74) 153.254 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net (129.250.4.119) 155.006 ms ae0.pabr5.global-gateway.net.nz (203.96.120.74) 162.946 ms
9 ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41) 160.822 ms ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 150.010 ms ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41) 157.757 ms
10 ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 150.410 ms xe-0-0-24-3.a00.snjsca04.us.ce.gin.ntt.net (129.250.200.102) 153.347 ms ae-15.r02.snjsca04.us.bb.gin.ntt.net (129.250.4.119) 160.546 ms
11 ae-2.a00.snjsca04.us.bb.gin.ntt.net (129.250.3.58) 155.557 ms 155.833 ms *
12 151.210.219.xxx (151.210.219.xxx) 171.133 ms 179.767 ms

I get a similar result to spark.co.nz itself:

Tracing route to spark.co.nz [146.171.248.36]
over a maximum of 30 hops:

1    <1 ms    <1 ms    <1 ms xxxxxxxxxxxxxx
2     1 ms     1 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    26 ms    26 ms    25 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4   151 ms   151 ms   150 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5   153 ms   153 ms   160 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.33]
6   147 ms   146 ms   146 ms spark-sdn-ak1-dom.akcr11.global-gateway.net.nz [203.96.65.198]
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9     *        *        *     Request timed out.

I don't suppose anyone else is getting funky results to similar IPs - say from 2degrees to 122.61.211.xxx ? I'll likely throw their support an email either this evening or tomorrow, and some more tracerts wouldn't go amiss when I do so.

Hiya,

I'm not seeing the same type of responses, see results below from within 2D core and from my connection at home.

Within 2d (We peer with Spark via GGI Domestic in Auckland)

C:\Users\nick.mackechnie>tracert 146.171.248.36

Tracing route to 146.171.248.36 over a maximum of 30 hops

1    20 ms     1 ms     1 ms 10.221.10.252
2     2 ms     2 ms     1 ms 10.69.0.5
3     7 ms    <1 ms    <1 ms 244.60.69.111.static.snap.net.nz [111.69.60.244]
4    <1 ms    <1 ms    <1 ms 64.62.69.111.static.snap.net.nz [111.69.62.64]
5    <1 ms     5 ms    <1 ms 65.62.69.111.static.snap.net.nz [111.69.62.65]
6     *        2 ms     1 ms 208.55.69.111.static.snap.net.nz [111.69.55.208]
7    18 ms    18 ms    18 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
8    32 ms    21 ms    19 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
9    18 ms    18 ms    18 ms ae9-44.akcr11.global-gateway.net.nz [122.56.127.209]
10    19 ms    21 ms    18 ms spark-sdn-ak1-dom.akcr11.global-gateway.net.nz [203.96.65.198]
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.

Via home

C:\Users\administrator.THENET>tracert 146.171.248.36

Tracing route to 146.171.248.36 over a maximum of 30 hops

1     1 ms     1 ms     1 ms thenet01.thenet.gen.nz [192.168.0.1]
2     2 ms     2 ms     1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3    19 ms    20 ms    19 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4    19 ms    19 ms    24 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5    21 ms    22 ms    21 ms ae9-42.akcr11.global-gateway.net.nz [122.56.127.
33]
6    21 ms    20 ms    21 ms spark-sdn-ak1-dom.akcr11.global-gateway.net.nz [
203.96.65.198]
7     *        *        *     Request timed out.
8     *        *        *     Request timed out.
9 ^C

Are you able to provide other specific IP's for us to test to?

Nick.

I'll PM you the specific IP address of the Darfield connection, however pinging anything in the 122.61.211.xxx range (that responds) seems to come back with similar results (170ms-190ms) with similar traceroutes showing the spike on the 4th hop.

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2198009 14-Mar-2019 14:09

Update - 14/03/19

Hi All,

It would appear like there is a routing issue with the 151.210.128.0/17 range based on our investigation, we have raised this issue to Spark in investigate. Once we have a response, I will provide an update on this issue.

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

Lego

Shop now for Lego sets and other gifts (affiliate link).

Threarah

45 posts

Geek
+1 received by user: 20

#2198044 14-Mar-2019 14:39

NickMack:

Update - 14/03/19

Hi All,

It would appear like there is a routing issue with the 151.210.128.0/17 range based on our investigation, we have raised this issue to Spark in investigate. Once we have a response, I will provide an update on this issue.

Nick.

Cheers for looking into this Nick. It's much appreciated.

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2198046 14-Mar-2019 14:40

Threarah:

NickMack:

Update - 14/03/19

Hi All,

It would appear like there is a routing issue with the 151.210.128.0/17 range based on our investigation, we have raised this issue to Spark in investigate. Once we have a response, I will provide an update on this issue.

Nick.

Cheers for looking into this Nick. It's much appreciated.

All good.... Craft beer fixes most things :-)

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

NickMack

977 posts

Ultimate Geek
+1 received by user: 831

Trusted

In memoriam

Lifetime subscriber

#2198189 14-Mar-2019 19:25

Threarah:

NickMack:

Update - 14/03/19

Hi All,

It would appear like there is a routing issue with the 151.210.128.0/17 range based on our investigation, we have raised this issue to Spark in investigate. Once we have a response, I will provide an update on this issue.

Nick.

Cheers for looking into this Nick. It's much appreciated.

Ticket logged with Spark to update their prefixes.

Nick.

https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz

Threarah

45 posts

Geek
+1 received by user: 20

#2198392 15-Mar-2019 08:55

Well that was quick:

Tracing route to 122-61-205-xxx-adsl.sparkbb.co.nz [122.61.205.xxx]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms xxxxxxxx
2 2 ms 2 ms 1 ms 12.7.69.111.static.snap.net.nz [111.69.7.12]
3 19 ms 19 ms 19 ms 38.27.69.111.static.snap.net.nz [111.69.27.38]
4 24 ms 18 ms 21 ms 39.27.69.111.static.snap.net.nz [111.69.27.39]
5 21 ms 19 ms 19 ms ae9-44.akcr11.global-gateway.net.nz [122.56.127.209]
6 20 ms 19 ms 20 ms mdr-ip24-dom.msc.global-gateway.net.nz [122.56.116.10]
7 43 ms 41 ms 43 ms 122-61-200-1-adsl.sparkbb.co.nz [122.61.200.1]
8 45 ms 44 ms 45 ms 122-61-205-xxx-adsl.sparkbb.co.nz [122.61.205.xxx]

Thanks again Nick and the rest of the team at 2degrees for sorting this out 👍

1 | 2