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.


BTR



1510 posts

Uber Geek
+1 received by user: 459


# 207770 13-Jan-2017 09:41
Send private message

I am looking at moving to big pipe as their business model and pricing suits me, but before I move across does anyone thats is already on bagpipe have examples of ping times for games, one game I play a lot of it Rocket League and my current ping times are about 240 when playing with mates in the US. 

 

 

 

i'm interested to know if there is much if any difference in ping times.

 

 

 

 

 

Thanks for your help.


Create new topic
8446 posts

Uber Geek
+1 received by user: 2890

Lifetime subscriber

  # 1702469 13-Jan-2017 09:48
Send private message

post up the IP addresses of the servers so people can check for you

 

And are you on ADSL/VDSL or UFB?


BTR



1510 posts

Uber Geek
+1 received by user: 459


  # 1702488 13-Jan-2017 10:02
Send private message

Jase2985:

 

post up the IP addresses of the servers so people can check for you

 

And are you on ADSL/VDSL or UFB?

 

 

 

 

I'll see if I can find any but the game doesn't actually display server IP's so I might have to use wireshark, I'll have a look tonight


 
 
 
 


BTR



1510 posts

Uber Geek
+1 received by user: 459


  # 1702528 13-Jan-2017 10:31
Send private message

Sorry stupid auto correct, currently on VDSL with My Republic. 


8446 posts

Uber Geek
+1 received by user: 2890

Lifetime subscriber

  # 1702544 13-Jan-2017 10:41
Send private message

if you google how to find the server Ip you might find a way to do it :)

 

 


298 posts

Ultimate Geek
+1 received by user: 161

Trusted

  # 1702618 13-Jan-2017 12:27
Send private message

Pretty sure this has been answered in other threads (not specifically Rocket League but ping times for US gaming servers in general). My flat is full of gamers and we haven't had issues with RL or any other notable AAA titles; we are on UFB not VDSL though.

Note that VDSL is more susceptible to line faults which can cause higher latency regardless of who you get on Bigpipe VDSL to provide you with their ping stats, and this is also slightly dependant on where in NZ you live - everyone will be slightly different.





Lannah - find me on twitter.


1265 posts

Uber Geek
+1 received by user: 66


  # 1702724 13-Jan-2017 14:43
Send private message

When it comes to ping times to overseas, Bigpipe/Spark (and other ISPs which use "Global Gateway") are... far from ideal.

 

Australia isn't too bad, but as for the US/EU...

 

Compare Bigpipe to Slingshot. Both are fibre, first hop adds 10ms on Bigpipe (up to Auckland):

 

traceroute to 104.224.178.x (104.224.178.x), 30 hops max, 38 byte packets
 1  219.88.232.x (219.88.232.x)  9.248 ms  9.258 ms  9.234 ms
 2  122.56.60.68 (122.56.60.68)  9.174 ms  9.072 ms  9.170 ms
 3  122.56.60.69 (122.56.60.69)  9.923 ms  9.622 ms  9.430 ms
 4  ae11-201.akbr6.global-gateway.net.nz (122.56.118.145)  9.551 ms  9.621 ms  9.777 ms
 5  ae5-2.akbr7.global-gateway.net.nz (210.55.202.213)  9.870 ms
ae7-2.akbr7.global-gateway.net.nz (122.56.119.53)  9.568 ms
ae5-2.akbr7.global-gateway.net.nz (210.55.202.213)  9.329 ms
 6  xe0-0-4.sgbr3.global-gateway.net.nz (122.56.127.94)  34.018 ms
122.56.119.18 (122.56.119.18)  32.933 ms
xe0-0-4.sgbr3.global-gateway.net.nz (122.56.127.94)  34.071 ms
 7  ae2-10.sgbr4.global-gateway.net.nz (202.50.232.246)  32.976 ms  33.019 ms  33.065 ms
 8  ae-3.a04.sydnau03.au.ra.gin.ntt.net (103.13.80.125)  33.024 ms  33.747 ms  33.133 ms
 9  ae-4.r21.sydnau03.au.bb.gin.ntt.net (202.68.64.124)  32.857 ms  33.132 ms  33.213 ms
10  ae-11.r31.tokyjp05.jp.bb.gin.ntt.net (129.250.5.34)  147.390 ms  146.377 ms  146.434 ms
11  *  ae-11.r27.tokyjp05.jp.bb.gin.ntt.net (129.250.2.154)  146.006 ms  150.952 ms
12  ae-0.pccw.tokyjp05.jp.bb.gin.ntt.net (129.250.66.102)  151.357 ms  150.551 ms  151.252 ms
13  TenGE0-0-0-0.br04.lax05.pccwbtn.net (63.223.43.2)  189.698 ms
TenGE0-0-0-7.br04.lax05.pccwbtn.net (63.223.43.22)  236.321 ms
TenGE0-0-0-0.br04.lax05.pccwbtn.net (63.223.43.2)  189.434 ms
14  TenGigE0-1-0-0-371.br04.lax05.pccwbtn.net (63.218.212.170)  220.844 ms  236.265 ms  220.933 ms
15  colo-lax13.as8100.net (96.44.180.94)  242.911 ms  220.655 ms  235.063 ms
16  dialup-ae2.2.lax-4.it7.net (96.44.162.186)  230.714 ms  228.061 ms  237.353 ms
17  v729.sioru.com (107.182.184.30)  190.960 ms  189.360 ms  203.909 ms
18  xx (104.224.178.x)  235.206 ms  220.708 ms  220.327 ms

 

Tracing route to xx [104.224.178.x]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     4 ms     3 ms     3 ms  pts-s.cpcak4-r1.tranzpeer.net [101.98.5.21]
  5     4 ms     4 ms     6 ms  bundle-100.bdr02.akl05.akl.vocus.net.nz [175.45.102.65]
  6   128 ms   128 ms   128 ms  bundle-10.cor01.akl05.akl.VOCUS.net.nz [114.31.202.100]
  7   128 ms   128 ms   128 ms  bundle-200.cor02.lax01.ca.VOCUS.net [114.31.202.47]
  8   128 ms   128 ms   128 ms  100G-0-1-0-0.cor01.lax01.ca.vocus.net [49.255.255.7]
  9   128 ms   128 ms   128 ms  bundle-101.bdr01.lax01.ca.vocus.net [49.255.255.9]
 10   128 ms   127 ms   129 ms  quadranet.as8100.any2ix.coresite.com [206.72.210.159]
 11   128 ms   128 ms   129 ms  colo-lax13.as8100.net [96.44.180.98]
 12     *        *        *     Request timed out.
 13   127 ms   127 ms   127 ms  v729.sioru.com [107.182.184.30]
 14   128 ms   129 ms   128 ms  xx [104.224.178.x]

Trace complete.

 

traceroute to 107.155.79.x (107.155.79.x), 30 hops max, 38 byte packets
 1  219.88.232.x (219.88.232.x)  9.404 ms  9.477 ms  9.278 ms
 2  122.56.60.68 (122.56.60.68)  9.188 ms  9.162 ms  9.054 ms
 3  122.56.60.69 (122.56.60.69)  9.670 ms  9.773 ms  9.532 ms
 4  ae11-201.akbr6.global-gateway.net.nz (122.56.118.145)  9.600 ms  9.878 ms  9.934 ms
 5  ae7-2.akbr7.global-gateway.net.nz (122.56.119.53)  10.130 ms
ae5-2.akbr7.global-gateway.net.nz (210.55.202.213)  9.175 ms  9.658 ms
 6  ae1-10.tkbr12.global-gateway.net.nz (202.50.232.37)  9.643 ms  9.443 ms  9.666 ms
 7  xe2-3-1.lebr7.global-gateway.net.nz (122.56.127.22)  135.745 ms
xe7-0-1-10.lebr7.global-gateway.net.nz (202.50.232.162)  133.886 ms  134.902 ms
 8  ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25)  165.384 ms  142.941 ms
ae0.pabr5.global-gateway.net.nz (203.96.120.74)  134.111 ms
 9  ae0.pabr5.global-gateway.net.nz (203.96.120.74)  138.356 ms  138.037 ms  138.368 ms
10  ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41)  139.918 ms
ae-2.r05.plalca01.us.bb.gin.ntt.net (129.250.5.237)  135.735 ms
ae-8.r06.plalca01.us.bb.gin.ntt.net (129.250.203.41)  139.119 ms
11  ae-2.r05.plalca01.us.bb.gin.ntt.net (129.250.5.237)  140.005 ms  139.499 ms  140.854 ms
12  ae-15.r01.snjsca04.us.bb.gin.ntt.net (129.250.5.33)  176.229 ms
ae7.cr2-sjc1.ip4.gtt.net (173.241.129.197)  135.803 ms
ae-15.r01.snjsca04.us.bb.gin.ntt.net (129.250.5.33)  174.974 ms
13  ae7.cr2-sjc1.ip4.gtt.net (173.241.129.197)  141.139 ms  139.800 ms  141.264 ms
14  xe-1-0-0.cr3-dal3.ip4.gtt.net (89.149.132.9)  204.284 ms
xe-2-3-6.cr3-dal3.ip4.gtt.net (89.149.130.197)  174.967 ms
xe-5-1-0.cr3-dal3.ip4.gtt.net (89.149.132.17)  175.998 ms
15  ip4.gtt.net (173.205.47.98)  203.902 ms  203.691 ms  204.709 ms
16  *  *  *
17  144.168.34.82 (144.168.34.82)  205.139 ms
node010.vpspal.com (23.227.170.58)  198.981 ms  199.152 ms
18  node010.vpspal.com (23.227.170.58)  203.205 ms  203.011 ms  *
19  *  *  *

 

Tracing route to x-customer-incero.com [107.155.79.x]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     4 ms     4 ms     4 ms  pts-s.cpcak4-r1.tranzpeer.net [101.98.5.21]
  5     4 ms     4 ms     4 ms  bundle-100.bdr02.akl05.akl.vocus.net.nz [175.45.102.65]
  6   128 ms   127 ms   128 ms  bundle-10.cor01.akl05.akl.VOCUS.net.nz [114.31.202.100]
  7   127 ms   128 ms   127 ms  bundle-200.cor02.lax01.ca.VOCUS.net [114.31.202.47]
  8   128 ms   128 ms   128 ms  bundle-102.bdr02.lax01.ca.vocus.net [49.255.255.15]
  9   160 ms   159 ms   160 ms  eqix-ix-da1.1515roundtable.com [206.223.118.118]
 10     *        *        *     Request timed out.
 11   161 ms   161 ms   160 ms  144.168.34.82
 12   159 ms   160 ms   160 ms  node010.vpspal.com [23.227.170.58]
 13     *        *        *     Request timed out.

 

traceroute to 195.154.167.x (195.154.167.x), 30 hops max, 38 byte packets
 1  219.88.232.254 (219.88.232.254)  9.449 ms  9.357 ms  9.232 ms
 2  122.56.60.68 (122.56.60.68)  10.208 ms  9.264 ms  9.134 ms
 3  122.56.60.69 (122.56.60.69)  9.538 ms  10.153 ms  9.533 ms
 4  ae11-201.akbr6.global-gateway.net.nz (122.56.118.145)  9.900 ms  10.179 ms  10.333 ms
 5  ae5-2.akbr7.global-gateway.net.nz (210.55.202.213)  9.262 ms  9.563 ms  9.643 ms
 6  ae1-10.tkbr12.global-gateway.net.nz (202.50.232.37)  9.445 ms  9.460 ms  10.206 ms
 7  xe7-0-1-10.lebr7.global-gateway.net.nz (202.50.232.162)  133.482 ms
xe-0-0-7-3.sjbr3.global-gateway.net.nz (202.50.232.18)  137.483 ms
xe8-0-2-0.lebr7.global-gateway.net.nz (210.55.202.194)  164.720 ms
 8  ae3-10.sjbr3.global-gateway.net.nz (122.56.127.25)  141.498 ms  164.612 ms  141.565 ms
 9  ae0.pabr5.global-gateway.net.nz (203.96.120.74)  138.058 ms  139.727 ms  138.437 ms
10  ix-xe-8-2-5-0.tcore1.PDI-Palo-Alto.as6453.net (66.198.127.49)  140.162 ms  143.520 ms  140.458 ms
11  if-ae-2-2.tcore2.PDI-Palo-Alto.as6453.net (66.198.127.2)  290.631 ms
if-ae-5-2.tcore2.SQN-San-Jose.as6453.net (64.86.21.1)  327.541 ms
if-ae-2-2.tcore2.PDI-Palo-Alto.as6453.net (66.198.127.2)  290.946 ms
12  if-ae-5-2.tcore2.SQN-San-Jose.as6453.net (64.86.21.1)  331.772 ms  331.624 ms  331.887 ms
13  if-ae-1-2.tcore1.SQN-San-Jose.as6453.net (63.243.205.1)  302.487 ms
if-ae-12-2.tcore1.NTO-New-York.as6453.net (63.243.128.28)  328.013 ms  328.410 ms
14  if-ae-11-2.tcore2.L78-London.as6453.net (63.243.128.38)  296.436 ms
if-ae-12-2.tcore1.NTO-New-York.as6453.net (63.243.128.28)  331.777 ms  332.062 ms
15  if-ae-7-2.tcore1.N0V-New-York.as6453.net (63.243.128.26)  290.038 ms
if-ae-2-2.tcore1.L78-London.as6453.net (80.231.131.2)  330.570 ms
if-ae-11-2.tcore2.L78-London.as6453.net (63.243.128.38)  307.387 ms
16  if-ae-2-2.tcore1.L78-London.as6453.net (80.231.131.2)  331.441 ms
if-ae-2-2.tcore2.N0V-New-York.as6453.net (216.6.90.22)  304.332 ms  303.121 ms
17  *  if-ae-3-6.tcore1.PYE-Paris.as6453.net (80.231.130.86)  333.286 ms
if-ae-2-2.tcore1.L78-London.as6453.net (80.231.131.2)  328.519 ms
18  if-ae-30-2.thar2.VI8-Vitry-Sur-Seine.as6453.net (5.23.25.5)  288.179 ms  288.397 ms
5.23.25.18 (5.23.25.18)  329.338 ms
19  if-ae-3-6.tcore1.PYE-Paris.as6453.net (80.231.130.86)  335.932 ms
5.23.25.18 (5.23.25.18)  331.859 ms  327.611 ms
20  45x-s44-1-a9k2.dc3.poneytelecom.eu (195.154.1.99)  287.405 ms  295.339 ms  287.825 ms
21  45x-s44-1-a9k2.dc3.poneytelecom.eu (195.154.1.99)  284.659 ms  288.420 ms
5.23.25.18 (5.23.25.18)  332.996 ms
22  xx (195.154.167.x)  320.751 ms  315.160 ms
45x-s44-1-a9k2.dc3.poneytelecom.eu (195.154.1.99)  293.755 ms

 

Tracing route to xx [195.154.167.x]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     3 ms     3 ms     4 ms  pts-s.cpcak4-r1.tranzpeer.net [101.98.5.21]
  5     4 ms     4 ms     6 ms  bundle-100.bdr02.akl05.akl.vocus.net.nz [175.45.102.65]
  6   128 ms   128 ms   127 ms  bundle-10.cor01.akl05.akl.VOCUS.net.nz [114.31.202.100]
  7   127 ms   127 ms   127 ms  bundle-200.cor02.lax01.ca.VOCUS.net [114.31.202.47]
  8   127 ms   127 ms   128 ms  bundle-102.bdr02.lax01.ca.vocus.net [49.255.255.15]
  9   127 ms   127 ms   128 ms  v301.core1.lax2.he.net [64.62.151.125]
 10   127 ms     *      128 ms  100ge2-2.core1.lax1.he.net [72.52.92.121]
 11   192 ms   287 ms   186 ms  100ge12-1.core1.ash1.he.net [184.105.80.201]
 12   265 ms   271 ms   273 ms  100ge12-1.core1.par2.he.net [184.105.213.174]
 13     *        *        *     Request timed out.
 14   264 ms   264 ms   264 ms  a9k2-pni-th2.dc3.poneytelecom.eu [195.154.1.74]
 15   265 ms   264 ms   265 ms  45x-s44-1-a9k2.dc3.poneytelecom.eu [195.154.1.99]
 16   264 ms   264 ms   263 ms  xx [195.154.167.x]




rm *


BTR



1510 posts

Uber Geek
+1 received by user: 459


  # 1703908 16-Jan-2017 08:22
Send private message

Thanks for the replies, I did;t get a chance in the weekend to run some tests. I'm guessing fibre may provide a little improvement but being that we are so far away from the US that ping times are always going to by high and thats just how it is.

 

 

 

Thanks again


1 post

Wannabe Geek


  # 1719100 12-Feb-2017 21:54
Send private message

For me I wouldnt recommend Bigpipe if you're a gamer, when switching from 2degrees to Bigpipe my ping went up roughly 20% on the BF4 servers I play on US/AUS, the ping can also be far from stable, which was never an issue with previous ISP's. I gave Bigpipe a year, I will be switching ISP soon.


Mr Snotty
8606 posts

Uber Geek
+1 received by user: 4502

Moderator
Trusted
Lifetime subscriber

  # 1719116 12-Feb-2017 22:09
One person supports this post
Send private message

@FuzetsuShinkai 20ms is NOTHING and to be perfectly honest unnoticable. I've already spoken about "ping" but you won't be getting any improvement apart from a pure placebo effect if you move providers. Also if you're playing on servers overseas you've got to remember routes can change to the gaming servers at any time so they're always going to be unstable. Unless if your ISP owns a direct connection to the gaming server they also can't control this.

 

I've been on 2degrees broadband, I've also got a connection via Voyager and BigPipe and all providers work fine for gaming. There are many gamers on BigPipe and Ping isn't everything - it is the stability of the connection and many factors can change this but 99% of the problems come from your own home when it comes to stability issues.

 

I've been monitoring several overseas services at https://smokeping.murfy.nz - most of the BigPipe staff are gamers and thus pride themselves on providing a stable service. I'm a gamer too and my BigPipe connection performs like any other connection I've been on. Just remember, the word "ping" means very little these days since connections have got much better especially to NZ. Many things could have changed with your connection in a year including upstream congestion, your connection type etc adding to the problems but I am yet to see or record any problems with gaming on at-least a Gigabit BigPipe connection.





4537 posts

Uber Geek
+1 received by user: 2642

Trusted
Lifetime subscriber

  # 1719124 12-Feb-2017 22:30
Send private message

As above ' placebo effect ' and nothing else

 

Linux


5 posts

Wannabe Geek


  # 1725144 23-Feb-2017 13:23
Send private message

This is the exact reason I switched to BigPipe.

 

Before moving from Trustpower (don't ask) I shopped around asking most providers where their servers were based.

 

 

 

Some had no idea or didn't even know what I was asking...

 

 

 

I'm in Auckland and Bigpipe advised their server was near Skytower so I picked them to start with the least amount of latency.

 

 

 

Big League of Legends fan here and the ping of VDSL to the Oceania server is currently around 34ms which is amazing. So I'm happy :)


98 posts

Master Geek
+1 received by user: 5


  # 1725209 23-Feb-2017 14:43
Send private message

The most latencies in any network connection, the biggest single factor is the amount of time required for the light from your screen to trigger a reaction from your brain, and then for it to make you fingers do something about it.  

 

20ms is nothing, your latency is about 12 times that, almost as long as it takes for your eyes to blink.


Create new topic



Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:





News »

Video game market in New Zealand passes half billion dollar mark
Posted 24-May-2019 16:15


WLG-X festival to celebrate creativity and innovation
Posted 22-May-2019 17:53


HPE to acquire supercomputing leader Cray
Posted 20-May-2019 11:07


Techweek starting around NZ today
Posted 20-May-2019 09:52


Porirua City Council first to adopt new council software solution Datascape
Posted 15-May-2019 12:00


New survey provides insight into schools' technology challenges and plans
Posted 15-May-2019 09:30


Apple Music now available on Alexa devices in Australia and New Zealand
Posted 15-May-2019 09:11


Make a stand against cyberbullying this Pink Shirt Day
Posted 14-May-2019 20:23


Samsung first TV manufacturer to launch the Apple TV App and Airplay 2
Posted 14-May-2019 20:11


Vodafone New Zealand sold
Posted 14-May-2019 07:25


Kordia boosts cloud performance with locally-hosted Microsoft Azure ExpressRoute
Posted 8-May-2019 10:25


Microsoft Azure ExpressRoute in New Zealand opens up faster, more secure internet for Kiwi businesses
Posted 8-May-2019 09:39


Vocus Communications to deliver Microsoft Azure Cloud Solutions through Azure ExpressRoute
Posted 8-May-2019 09:25


Independent NZ feature film #statusPending to premiere during WLG-X
Posted 6-May-2019 22:13


The ultimate dog photoshoot with Nokia 9 PureView #ForgottenDogsofInstagram
Posted 6-May-2019 09:41



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.