[Snap] Latency up a fair bit in the evenings; Congestion or something else

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] Latency up a fair bit in the evenings; Congestion or something else

sidefx

3711 posts

Uber Geek

Trusted

#110582 11-Oct-2012 22:04

Not really sure what's normal but I usually get a pretty good latency on my connection (VDSL) - 7ms on speedtest, and 5-6ms if I ping the first external ip or snap DNS server.

I've noticed lately a that it's up quite a bit in the evenings. 44ms currently on speedtest (with throughput down a bit and it seems to take a lot longer to "ramp up")

I game a bit and have noticed it there to. And below is what pinging the dns server looks like right now. Congestion or something else? Is that much of an increase pretty normal? It's been a pretty constant increase in the evenings for the last couple of weeks I think.

C:\Users\Simon>ping 202.37.101.1 /t

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=40ms TTL=61
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61
Reply from 202.37.101.1: bytes=32 time=30ms TTL=61
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61
Reply from 202.37.101.1: bytes=32 time=43ms TTL=61
Reply from 202.37.101.1: bytes=32 time=41ms TTL=61
Reply from 202.37.101.1: bytes=32 time=35ms TTL=61
Reply from 202.37.101.1: bytes=32 time=38ms TTL=61
Reply from 202.37.101.1: bytes=32 time=45ms TTL=61
Reply from 202.37.101.1: bytes=32 time=38ms TTL=61

Ping statistics for 202.37.101.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 45ms, Average = 40ms

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

1 | 2 | 3 | 4 | 5

36 posts

Geek

ID Verified

#699959 11-Oct-2012 22:10

Hey,

First post here - When was this taken? Latency for me seems okay, I'm on Snap VDSL, running a vanilla fritzbox setup:

C:\Users\Admin>ping 202.37.101.1 /t

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=8ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=7ms TTL=61

Ping statistics for 202.37.101.1:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 8ms, Average = 6ms

sidefx

3711 posts

Uber Geek

Trusted

#699963 11-Oct-2012 22:14

Pretty much when I posted it so 22:03ish. It's still the same right now. Based on the last few evenings if I wait an hour or so it'll go back down to a very steady 6-7ms (I tried this evening at 19:30 and it was fine - but it seems to last from around 20:30 - 23:30 I think)

EDIT: current pingtest:

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

Scholarly

36 posts

Geek

ID Verified

#699968 11-Oct-2012 22:21

Odd. I haven't noticed any issues with latency while playing CS:S or GW2. I'm currently using the Fritz's wireless to do all of this - Whenever I've had performance issues latency wise, it's always been related to the wireless proved by a traceroute.

sidefx

3711 posts

Uber Geek

Trusted

#699974 11-Oct-2012 22:37

Nope, no wireless here - straight to gigE switch plugged into LAN1 on the FritzBox.

C:\Users\Simon>tracert google.com

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

1 <1 ms <1 ms <1 ms h001.home.net [192.168.51.1]
2 47 ms 46 ms 45 ms 16.17.69.111.static.snap.net.nz [111.69.17.16]
3 39 ms 41 ms 42 ms 54.32.69.111.dynamic.snap.net.nz [111.69.32.54]
4 69 ms 61 ms 57 ms 2.56.69.111.dynamic.snap.net.nz [111.69.56.2]
5 55 ms 56 ms 59 ms 3.56.69.111.dynamic.snap.net.nz [111.69.56.3]
6 68 ms 59 ms 54 ms 66.249.95.234
7 60 ms 59 ms 59 ms 72.14.237.53
8 72 ms 63 ms 58 ms syd01s05-in-f9.1e100.net [74.125.237.41]

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

NZSimplicity

135 posts

Master Geek

#699976 11-Oct-2012 22:49

here is mine, from chch to ak

sidefx

3711 posts

Uber Geek

Trusted

#699984 11-Oct-2012 23:18

Getting better, pretty similar to previous evenings:

C:\Users\Simon>ping 202.37.101.1 /t

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=26ms TTL=61
Reply from 202.37.101.1: bytes=32 time=27ms TTL=61
Reply from 202.37.101.1: bytes=32 time=26ms TTL=61
Reply from 202.37.101.1: bytes=32 time=24ms TTL=61
Reply from 202.37.101.1: bytes=32 time=24ms TTL=61
Reply from 202.37.101.1: bytes=32 time=22ms TTL=61
Reply from 202.37.101.1: bytes=32 time=21ms TTL=61
Reply from 202.37.101.1: bytes=32 time=18ms TTL=61
Reply from 202.37.101.1: bytes=32 time=17ms TTL=61
Reply from 202.37.101.1: bytes=32 time=23ms TTL=61
Reply from 202.37.101.1: bytes=32 time=23ms TTL=61
Reply from 202.37.101.1: bytes=32 time=26ms TTL=61

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

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

sidefx

3711 posts

Uber Geek

Trusted

#699987 11-Oct-2012 23:24

And now it looks better:

C:\Users\Simon>ping 202.37.101.1 /t

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61

Ping statistics for 202.37.101.1:
Packets: Sent = 16, Received = 16, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 6ms, Average = 5ms

EDIT: And pingtest FWIW

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

coffeebaron

6231 posts

Uber Geek

Trusted

Lifetime subscriber

#700016 12-Oct-2012 07:18

School holidays?

Rural IT and Broadband support.

Broadband troubleshooting and master filter installs.
Starlink installer - one month free: https://www.starlink.com/?referral=RC-32845-88860-71
Wi-Fi and networking
Cel-Fi supply and installer - boost your mobile phone coverage legally

Need help in Auckland, Waikato or BoP? Click my email button, or email me direct: [my user name] at geekzonemail dot com

frizianz

105 posts

Master Geek

#700017 12-Oct-2012 07:26

Potentially an issue to do with Chorus backbaul from your cabinet to where Snap's handover is.

Reason i'm saying this this is it looks as if it may only be effecting you and latency is high from the first hop outside your network which would be Snap's BRAS terminating the PPPoE session. Which the bits between are usually only Chorus's backhaul network.

I'd email them or call Snap and get them to take a look.

Scholarly

36 posts

Geek

ID Verified

#700099 12-Oct-2012 10:57

Would like to see if other Snap users in your area can weigh in with similar results - You'll find faster action will be taken if it effects multiple users.

sidefx

3711 posts

Uber Geek

Trusted

#700317 12-Oct-2012 17:26

Scholarly: Would like to see if other Snap users in your area can weigh in with similar results - You'll find faster action will be taken if it effects multiple users.

How wide an area would we be looking at?

Anyone reading this live near the corner of Balmoral and Dominion Roads in Auckland? :)

If it's occuring before snap handover would it affect non-snap users?

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

Lorenceo

904 posts

Ultimate Geek

Trusted

#700344 12-Oct-2012 17:49

I'm not too far from there, and haven't had any issues.
Although I'm running off of an exchange, not a cabinet.

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61
Reply from 202.37.101.1: bytes=32 time=5ms TTL=61
Reply from 202.37.101.1: bytes=32 time=6ms TTL=61

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

Stasis007

85 posts

Master Geek

#700360 12-Oct-2012 18:31

Maybe related, maybe not. I've had spells of horrible latency in World of Warcraft the last week or two. Usually happens between 8-11pm. Worst I've seen in over 3 years, etc. Actually DC's me often, and local pings are fine but 2k+ pings to eastern USA.

Mate on Telstra was experiencing exactly the same which seems significant.

richms

28172 posts

Uber Geek

Trusted

Lifetime subscriber

#701123 14-Oct-2012 20:33

My speedtests locally are great right now, but youtube performance is atrocious.

At night it will flatline the graph on the fritz till it is buffered. At the moment its lucky to get 4-5 megs sustained.

compared to night time

pings are stable at 5-7ms to my webhost at the skytower however.

Since the youtube is not in auckland when I last asked, perhaps its slowness within snaps network?

Richard rich.ms

sidefx

3711 posts

Uber Geek

Trusted

#701133 14-Oct-2012 20:52

Lorenceo: I'm not too far from there, and haven't had any issues.
Although I'm running off of an exchange, not a cabinet.

I'm connected to the cabinet near the white Balmoral sign on that corner (I think) Wonder if I can find anyone else on it.

Still not looking to hot.. and pretty much clears up every night between 11-11:30pm when I go back down to 5-6ms

C:\Users\Simon>echo %date% - %time%
Sun 14/10/2012 - 20:51:01.36

C:\Users\Simon>ping /t 202.37.101.1

Pinging 202.37.101.1 with 32 bytes of data:
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=39ms TTL=61
Reply from 202.37.101.1: bytes=32 time=42ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=46ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61
Reply from 202.37.101.1: bytes=32 time=44ms TTL=61

Ping statistics for 202.37.101.1:
Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 46ms, Average = 43ms

"I was born not knowing and have had only a little time to change that here and there." | Octopus Energy | Sharesies
- Richard Feynman

1 | 2 | 3 | 4 | 5