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.


View this topic in a long page with up to 500 replies per page Create new topic
1 | 2 | 3 | 4 
3164 posts

Uber Geek

Trusted
Lifetime subscriber

  #2522102 13-Jul-2020 14:21
Send private message quote this post

cbrpilot:

 

Quick update from me here.

 

I believe we have found the issue for both Napier and Kapiti for Bigpipe customers.  Thanks for bringing this to my attention.

 

It would appear that (unknown to us) Chorus seem to take your traffic on a grand tour before it is handed over to our network - and is working as designed from their perspective.  Obviously not ideal and we are exploring options to see if we can avoid this.  Can't make any guarantees at this point but we are working on it!

 

Dave.

 

 

This has made me smile (sort of).

 

Would be interesting to know if all other RSPs are impacted or if this is special to Spark.





and


2214 posts

Uber Geek

Subscriber

  #2522110 13-Jul-2020 14:35
Send private message quote this post

These are my pings from Porirua on Orcon fibre 100/20

 

ping 219.88.188.70

 

Pinging 219.88.188.70 with 32 bytes of data:
Reply from 219.88.188.70: bytes=32 time=22ms TTL=120
Reply from 219.88.188.70: bytes=32 time=22ms TTL=120
Reply from 219.88.188.70: bytes=32 time=22ms TTL=120
Reply from 219.88.188.70: bytes=32 time=23ms TTL=120

 

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

 

ping 219.88.188.134

 

Pinging 219.88.188.134 with 32 bytes of data:
Reply from 219.88.188.134: bytes=32 time=28ms TTL=120
Reply from 219.88.188.134: bytes=32 time=27ms TTL=120
Reply from 219.88.188.134: bytes=32 time=27ms TTL=120
Reply from 219.88.188.134: bytes=32 time=28ms TTL=120

 

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

 

ping 219.88.188.7

 

Pinging 219.88.188.7 with 32 bytes of data:
Reply from 219.88.188.7: bytes=32 time=13ms TTL=120
Reply from 219.88.188.7: bytes=32 time=14ms TTL=120
Reply from 219.88.188.7: bytes=32 time=11ms TTL=120
Reply from 219.88.188.7: bytes=32 time=11ms TTL=120

 

Ping statistics for 219.88.188.7:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 11ms, Maximum = 14ms, Average = 12ms


 
 
 
 


4446 posts

Uber Geek

Trusted

  #2522111 13-Jul-2020 14:39
Send private message quote this post

The server IPs I gave to ping are only really a valid test measure for Spark/Bigpipe/Skinny customers. Other ISPs will be able to see them but are never served from them - so honestly I have never even thought about how optimised paths to them from other ISPs might be.

 

Cheers - N

 

 





--

 

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


2214 posts

Uber Geek

Subscriber

  #2522158 13-Jul-2020 14:51
Send private message quote this post

Yea, wondered about that. Never mind.


3164 posts

Uber Geek

Trusted
Lifetime subscriber

  #2522219 13-Jul-2020 15:32
Send private message quote this post

EnragedStoat:

 

Tracing route to cache.google.com [219.88.188.70]
over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  192.168.81.1
  2    18 ms    18 ms    19 ms  125-239-203-1.jetstream.xtra.co.nz [125.239.203.1]
  3    21 ms    21 ms    21 ms  222.152.41.187
  4    21 ms    21 ms    21 ms  cache.google.com [219.88.188.70]

 

Trace complete.

 

 

The only way anyone else would see this is by doing a traceroute on a wired connection (not over wiif) and seeing the latency on the first hop after your router.

 

The issue is that Spark do de-prioritize ICMP traffic, but this does show up the problem.

 

This does make me chuckle a lot, and I wonder if other ISPs have the same / similar problem depending on how distributed their BNGs are across the country or if they are all aggregated back to Auckland.





and




233 posts

Master Geek


  #2522371 13-Jul-2020 17:52
Send private message quote this post

cbrpilot:

 

Quick update from me here.

 

I believe we have found the issue for both Napier and Kapiti for Bigpipe customers.  Thanks for bringing this to my attention.

 

It would appear that (unknown to us) Chorus seem to take your traffic on a grand tour before it is handed over to our network - and is working as designed from their perspective.  Obviously not ideal and we are exploring options to see if we can avoid this.  Can't make any guarantees at this point but we are working on it!

 

Dave.

 

 

 

 

Good to hear, but I changed from BigPipe partly because of this, wouldn’t mind a contribution from Spark/BigPipe on the early termination charge as I was the reporter of this unexpected behaviour (despite being shot down by many!). Any tips on who I can contact there, BigPipe CS is not very helpful tbh, get what you pay for I guess.

 

 

 

I can confirm the Spark performs much better for those that care about latency in Napier. Night and day.


12 posts

Geek


  #2522564 14-Jul-2020 08:46
Send private message quote this post

cbrpilot:

 

I believe we have found the issue for both Napier and Kapiti for Bigpipe customers.

 

 

I would say so :)  1.0 x 10^3 thanks!

 

Pinging 219.88.188.70 with 32 bytes of data:
    Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
    Minimum = 2ms, Maximum = 2ms, Average = 2ms
    (was previously Minimum = 21ms, Maximum = 21ms, Average = 21ms)

 

Pinging 219.88.188.134 with 32 bytes of data:
    Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
    Minimum = 6ms, Maximum = 7ms, Average = 6ms
    (was previously Minimum = 25ms, Maximum = 26ms, Average = 25ms)
 
Pinging 219.88.188.7 with 32 bytes of data:
    Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
    Minimum = 11ms, Maximum = 11ms, Average = 11ms
    (was previously Minimum = 30ms, Maximum = 32ms, Average = 30ms)

 

Also seeing improved throughput, previously I was lucky to hit 600Mbp/s, now consistently >900.

 

 

Assuming you can roll this fix out to other affected locations will it also work if I change back to a static IP?


 
 
 
 


'That VDSL Cat'
12469 posts

Uber Geek

Trusted
Spark
Subscriber

  #2522650 14-Jul-2020 12:19
Send private message quote this post

JonoNZ:

 

Good to hear, but I changed from BigPipe partly because of this, wouldn’t mind a contribution from Spark/BigPipe on the early termination charge as I was the reporter of this unexpected behaviour (despite being shot down by many!). Any tips on who I can contact there, BigPipe CS is not very helpful tbh, get what you pay for I guess.

 

 

 

I can confirm the Spark performs much better for those that care about latency in Napier. Night and day.

 

 

Hey Jono,

 

 

 

we certainly appreciate it.

 

The team will be in contact :)





#include <std_disclaimer>

 

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

 


738 posts

Ultimate Geek

Trusted
Spark NZ

  #2522678 14-Jul-2020 13:43
Send private message quote this post

EnragedStoat:

 

cbrpilot:

 

I believe we have found the issue for both Napier and Kapiti for Bigpipe customers.

 

 

I would say so :)  1.0 x 10^3 thanks!

 

Pinging 219.88.188.70 with 32 bytes of data:
    Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
    Minimum = 2ms, Maximum = 2ms, Average = 2ms
    (was previously Minimum = 21ms, Maximum = 21ms, Average = 21ms)

 

Pinging 219.88.188.134 with 32 bytes of data:
    Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
    Minimum = 6ms, Maximum = 7ms, Average = 6ms
    (was previously Minimum = 25ms, Maximum = 26ms, Average = 25ms)
 
Pinging 219.88.188.7 with 32 bytes of data:
    Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
    Minimum = 11ms, Maximum = 11ms, Average = 11ms
    (was previously Minimum = 30ms, Maximum = 32ms, Average = 30ms)

 

Also seeing improved throughput, previously I was lucky to hit 600Mbp/s, now consistently >900.

 

 

Assuming you can roll this fix out to other affected locations will it also work if I change back to a static IP?

 

 

Hi EnragedStoat, we rolled this out solely to you as a test to ensure that it had the desired impact - which it has :)

 

We have not rolled this out more widely as yet (few hoops to jump through etc).

 

Assuming that goes smoothly we will endeavour to roll this out more widely in the coming weeks.





My views are my own, and may not necessarily represent those of my employer.




233 posts

Master Geek


  #2522713 14-Jul-2020 14:36
Send private message quote this post

hio77:

 

JonoNZ:

 

Good to hear, but I changed from BigPipe partly because of this, wouldn’t mind a contribution from Spark/BigPipe on the early termination charge as I was the reporter of this unexpected behaviour (despite being shot down by many!). Any tips on who I can contact there, BigPipe CS is not very helpful tbh, get what you pay for I guess.

 

 

 

I can confirm the Spark performs much better for those that care about latency in Napier. Night and day.

 

 

Hey Jono,

 

 

 

we certainly appreciate it.

 

The team will be in contact :)

 

 

 

 

Thanks, they’ve been in touch — much appreciated!


1 | 2 | 3 | 4 
View this topic in a long page with up to 500 replies per page Create new topic




News »

Pre-orders for Huawei MateBook 13 open now
Posted 14-Aug-2020 14:26


Freeview On Demand app launches on Sony Android TVs
Posted 6-Aug-2020 13:35


UFB hits more than one million connections
Posted 6-Aug-2020 09:42


D-Link A/NZ extends COVR Wi-Fi EasyMesh System series with new three-pack
Posted 4-Aug-2020 15:01


New Zealand software Rfider tracks coffee from Colombia all the way to New Zealand businesses
Posted 3-Aug-2020 10:35


Logitech G launches Pro X Wireless gaming headset
Posted 3-Aug-2020 10:21


Sony Alpha 7S III provides supreme imaging performance
Posted 3-Aug-2020 10:11


Sony introduces first CFexpress Type A memory card
Posted 3-Aug-2020 10:05


Marsello acquires Goody consolidating online and in-store marketing position
Posted 30-Jul-2020 16:26


Fonterra first major customer for Microsoft's New Zealand datacentre
Posted 30-Jul-2020 08:07


Everything we learnt at the IBM Cloud Forum 2020
Posted 29-Jul-2020 14:45


Dropbox launches native HelloSign workflow and data residency in Australia
Posted 29-Jul-2020 12:48


Spark launches 5G in Palmerston North
Posted 29-Jul-2020 09:50


Lenovo brings speed and smarter features to new 5G mobile gaming phone
Posted 28-Jul-2020 22:00


Withings raises $60 million to enable bridge between patients and healthcare
Posted 28-Jul-2020 21:51



Geekzone Live »

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


Support Geekzone »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



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.

Alternatively, you can receive a daily email with Geekzone updates.