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
1406 posts

Uber Geek
+1 received by user: 260

Subscriber

  Reply # 2090255 13-Sep-2018 16:32
Send private message quote this post

I'm with Skinny Broadband - I'm pretty happy with it along with the fact that it doesn't use VLAN tagging which makes life a whole lot easier in terms of router choice. I noticed a slight speed and latency improvement with moving away from CGN and bring it under the Spark network umbrella rather than operating its own.





Laptop: MacBook Pro (15-inch, 2017)
Desktop: iMac (27-inch, 2017)
Smartphone: iPhone X 256GB 'Space Grey'
Additional devices: Unifi Security Gateway, Unifi Switch, Unifi AP AC HD, Unifi Cloud Key, Apple TV 4K 64GB
Services: iCloud, YouTube Premium, Wordpress, Skinny

 




33 posts

Geek
+1 received by user: 2
Inactive user


  Reply # 2091897 17-Sep-2018 12:47
Send private message quote this post

How long should I expect to wait for this to be resolved?


Meow
7906 posts

Uber Geek
+1 received by user: 3929

Moderator
Trusted
Lifetime subscriber

  Reply # 2091947 17-Sep-2018 13:55
Send private message quote this post

KitChan:

 

How long should I expect to wait for this to be resolved?

 

To be honest I don't see it as a problem. Basically the answer here is "it'll be resolved when it is resolved"

 

Just be patient. I'm sure Nick will update soon. It is only Monday afterall.







33 posts

Geek
+1 received by user: 2
Inactive user


  Reply # 2092058 17-Sep-2018 16:57
Send private message quote this post

michaelmurfy:

 

KitChan:

 

How long should I expect to wait for this to be resolved?

 

To be honest I don't see it as a problem.

 

 

Not getting what I paid for is a problem

 

Even on Slingshot ADSL, League of Legends was at least barely playable


232 posts

Master Geek
+1 received by user: 187

Trusted
2degrees

  Reply # 2092067 17-Sep-2018 17:22
Send private message quote this post

KitChan:

 

How long should I expect to wait for this to be resolved?

 

 

Hiya,

 

I replied on Friday with this reply - https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=240393&page_no=1#2090157 . The route you have is the best we can do for the destination specified with the peering offered. There's 40ms of bouncing around their internal network we cannot 'resolve' using your words.

 

Nick


Meow
7906 posts

Uber Geek
+1 received by user: 3929

Moderator
Trusted
Lifetime subscriber

  Reply # 2092087 17-Sep-2018 17:39
Send private message quote this post

@KitChan I also don't understand - League of Legends is more than playable... I did test this and (failed) as per normal with a game without any hitches.

 

It is also a non-issue. The problem is with LoL itself and not the ISP. 2degrees is also one of the better providers as below:

 

2degrees UFB:
PING 104.160.131.3 (104.160.131.3) 56(84) bytes of data.
64 bytes from 104.160.131.3: icmp_seq=1 ttl=58 time=208 ms
64 bytes from 104.160.131.3: icmp_seq=2 ttl=58 time=209 ms
64 bytes from 104.160.131.3: icmp_seq=3 ttl=58 time=208 ms
64 bytes from 104.160.131.3: icmp_seq=4 ttl=58 time=209 ms
^C
--- 104.160.131.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 208.483/208.845/209.251/0.575 ms

 


Spark UFB:
PING 104.160.131.3 (104.160.131.3) 56(84) bytes of data.
64 bytes from 104.160.131.3: icmp_seq=1 ttl=52 time=218 ms
64 bytes from 104.160.131.3: icmp_seq=2 ttl=52 time=221 ms
64 bytes from 104.160.131.3: icmp_seq=3 ttl=52 time=221 ms
64 bytes from 104.160.131.3: icmp_seq=4 ttl=52 time=219 ms
^C
--- 104.160.131.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 218.552/220.175/221.830/1.474 ms

Voyager VDSL:
PING 104.160.131.3 (104.160.131.3) 56(84) bytes of data.
64 bytes from 104.160.131.3: icmp_seq=1 ttl=52 time=191 ms
64 bytes from 104.160.131.3: icmp_seq=2 ttl=52 time=191 ms
64 bytes from 104.160.131.3: icmp_seq=3 ttl=52 time=191 ms
64 bytes from 104.160.131.3: icmp_seq=4 ttl=52 time=191 ms
^C
--- 104.160.131.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 191.353/191.525/191.604/0.545 ms

Orcon UFB:
Average 212ms (got a friend to do a ping test).





30 posts

Geek
+1 received by user: 6


  Reply # 2092112 17-Sep-2018 18:20
Send private message quote this post

Orcon UFB - Auckland

 

 

 

Pinging 104.160.131.3 with 32 bytes of data:
Reply from 104.160.131.3: bytes=32 time=168ms TTL=53
Reply from 104.160.131.3: bytes=32 time=167ms TTL=53
Reply from 104.160.131.3: bytes=32 time=168ms TTL=53
Reply from 104.160.131.3: bytes=32 time=168ms TTL=53

 

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

 

some of those pings seem a little high to me but as nick said there is 40MS delay inside riot games network




33 posts

Geek
+1 received by user: 2
Inactive user


  Reply # 2092136 17-Sep-2018 19:10
Send private message quote this post

michaelmurfy:

 

@KitChan I also don't understand - League of Legends is more than playable... I did test this and (failed) as per normal with a game without any hitches.

 

It is also a non-issue. The problem is with LoL itself and not the ISP. 2degrees is also one of the better providers as below:

 

2degrees UFB:
PING 104.160.131.3 (104.160.131.3) 56(84) bytes of data.
64 bytes from 104.160.131.3: icmp_seq=1 ttl=58 time=208 ms
64 bytes from 104.160.131.3: icmp_seq=2 ttl=58 time=209 ms
64 bytes from 104.160.131.3: icmp_seq=3 ttl=58 time=208 ms
64 bytes from 104.160.131.3: icmp_seq=4 ttl=58 time=209 ms
^C
--- 104.160.131.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 208.483/208.845/209.251/0.575 ms

 


Spark UFB:
PING 104.160.131.3 (104.160.131.3) 56(84) bytes of data.
64 bytes from 104.160.131.3: icmp_seq=1 ttl=52 time=218 ms
64 bytes from 104.160.131.3: icmp_seq=2 ttl=52 time=221 ms
64 bytes from 104.160.131.3: icmp_seq=3 ttl=52 time=221 ms
64 bytes from 104.160.131.3: icmp_seq=4 ttl=52 time=219 ms
^C
--- 104.160.131.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 218.552/220.175/221.830/1.474 ms

Voyager VDSL:
PING 104.160.131.3 (104.160.131.3) 56(84) bytes of data.
64 bytes from 104.160.131.3: icmp_seq=1 ttl=52 time=191 ms
64 bytes from 104.160.131.3: icmp_seq=2 ttl=52 time=191 ms
64 bytes from 104.160.131.3: icmp_seq=3 ttl=52 time=191 ms
64 bytes from 104.160.131.3: icmp_seq=4 ttl=52 time=191 ms
^C
--- 104.160.131.3 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 191.353/191.525/191.604/0.545 ms

Orcon UFB:
Average 212ms (got a friend to do a ping test).

 

 

I got drastically different results with 2Degrees than Stuff and my ping was higher ingame than what is reported in the ping test (in the reddit thread where Riot posted the ip they say to expect different results ingame)

 

Looking at this, it seems like Voyager is the best isp for me.

 

Also, where did you and your friend pinging from. The next poster after yours pinged from Orcon in Auckland and got a significantly lower result.


3607 posts

Uber Geek
+1 received by user: 2069

Trusted
Lifetime subscriber

  Reply # 2092139 17-Sep-2018 19:20
Send private message quote this post

Routing is not static and does change depending on many factors

John




Ex JohnR VodafoneNZ 17 years 4 days



33 posts

Geek
+1 received by user: 2
Inactive user


  Reply # 2092142 17-Sep-2018 19:29
Send private message quote this post

What sorts of factors? I found Stuff was pretty consistent.

 

I'm located in Wellington if that's any relevant


3607 posts

Uber Geek
+1 received by user: 2069

Trusted
Lifetime subscriber

  Reply # 2092144 17-Sep-2018 19:43
Send private message quote this post

KitChan:

 

What sorts of factors? I found Stuff was pretty consistent.

 

I'm located in Wellington if that's any relevant

 

 

Many factors but one is cost

 

John





Ex JohnR VodafoneNZ 17 years 4 days

Meow
7906 posts

Uber Geek
+1 received by user: 3929

Moderator
Trusted
Lifetime subscriber

  Reply # 2092188 17-Sep-2018 20:56
One person supports this post
Send private message quote this post

KitChan:

 

I got drastically different results with 2Degrees than Stuff and my ping was higher ingame than what is reported in the ping test (in the reddit thread where Riot posted the ip they say to expect different results ingame)

 

Looking at this, it seems like Voyager is the best isp for me.

 

Also, where did you and your friend pinging from. The next poster after yours pinged from Orcon in Auckland and got a significantly lower result.

 

Friend is in Wellington and no - you won't notice any difference in 20ms. Also remember, routes can change at any given point and each ISP can become better / worse every day. It is how the internet works.

Voyager and 2degrees are both great ISP's but there is no problem here. The game works fine in my testing.







33 posts

Geek
+1 received by user: 2
Inactive user


  Reply # 2092759 18-Sep-2018 19:18
Send private message quote this post

michaelmurfy:

 

KitChan:

 

I got drastically different results with 2Degrees than Stuff and my ping was higher ingame than what is reported in the ping test (in the reddit thread where Riot posted the ip they say to expect different results ingame)

 

Looking at this, it seems like Voyager is the best isp for me.

 

Also, where did you and your friend pinging from. The next poster after yours pinged from Orcon in Auckland and got a significantly lower result.

 

Friend is in Wellington and no - you won't notice any difference in 20ms. Also remember, routes can change at any given point and each ISP can become better / worse every day. It is how the internet works.

Voyager and 2degrees are both great ISP's but there is no problem here. The game works fine in my testing.

 

 

I found with Stuff, it was consistent over a month. On my past ADSL and VDSL isps they seemed pretty consistent too.

 

It sounds like the difference has something to do with what Nick said about Sydney Megaport peering




33 posts

Geek
+1 received by user: 2
Inactive user


  Reply # 2093051 19-Sep-2018 10:52
Send private message quote this post

NickMack:

 

KitChan:

 

How long should I expect to wait for this to be resolved?

 

 

Hiya,

 

I replied on Friday with this reply - https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=240393&page_no=1#2090157 . The route you have is the best we can do for the destination specified with the peering offered. There's 40ms of bouncing around their internal network we cannot 'resolve' using your words.

 

Nick

 

 

What I meant with my question was in reference to

 

NickMack:

 

1/ We could manipulate our import policies to prefer the particular prefix from the US - this could potentially impact other services.

 

 

 

2/ We could take a more comprehensive approach and engage SoftLayer to find out if they have communities (these are use to tag a collection of prefixes) to aggregate a collection of prefixes by location. We can use this to make routing policy decisions.

 

 

 

We are exploring Option 2 at the moment to see if Softlayer will work us to resolve.

 

I wanted an estimate on exploring option 2.


Meow
7906 posts

Uber Geek
+1 received by user: 3929

Moderator
Trusted
Lifetime subscriber

  Reply # 2108393 15-Oct-2018 18:19
Send private message quote this post

@KitChan If you want to attempt to discuss this further then post in this thread. Stop creating new threads please (also I feel your questions have already been answered):

 

OP has changed over to Stuff again: https://www.geekzone.co.nz/forums.asp?forumid=49&topicid=242190 

 

KitChan:

 

In the absence of advice, I've emailed Stuff with the concerns I mentioned in the original thread. I will also get in touch with Mixer, (not Riot Games, I don't have an issue with them!) and ask them about how they work, for all I know they have some elaborate system that streams uploads between their different servers no slower than if I used their CA server directly with Orcon. If that's the case, then my concerns shrink down to US side video game lag spiking which probably isn't just limited to League of Legends. I'll see if one of my friends with Overwatch will be willing to invite me to the US server tonight or tomorrow (OW automatically places me in AU server unless AU server is down or I've partied up)

 

My concerns incase it wasn't clear enough in the previous thread are as follows:

 

Good Japan ping for playing with Japanese gamers with Stuff, US side is having some spiking problems that I don't seem to recall having in August. Meanwhile Good Mixer US ping with Orcon and lower US pings in general with Orcon. So I'm wondering which ISP I should stick with. Besides the spiking, I'm pretty happy gaming wise with Stuff, but I'm trying to decide if it's worth sacrificing the good connection to the US Mixer server that Orcon offers.

 

Was having reliable 11Mbps upload overseas on Stuff in August, now its reliably 5Mbps. I've suggested in my email to Stuff based on other data I have, that I think it may be an issue on Megaport's end.

 

Are there any other technical mumbo jumbo I should be asking Stuff about?





1 | 2 | 3 | 4
View this topic in a long page with up to 500 replies per page 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:



Geekzone Live »

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



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.