[Snap] High Latency @ Night

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] High Latency @ Night

Zeon

3916 posts

Uber Geek

Trusted

#175764 10-Jul-2015 22:48

Hey guys,
Been on Snap ADSL for a couple of months now (ADSL2+) and getting really bad latency at night. Web browsing is really bad and RDP is unusable. Its especially bad tonight. I'm not sure if its Exchange or Snap congestion but I don't think we are on a Conklin or ADSL so not sure if its on the Chorus side. As an example:

What could it be?

Speedtest 2019-10-14

1 | 2

6018 posts

Uber Geek

Trusted

Geekzone

Lifetime subscriber

#1340901 10-Jul-2015 22:48

Hello... Our robot found some keywords in your post, so here is an automated reply with some important things to note regarding broadband speeds.

If you are posting regarding DSL speeds please check that

- you have reset your modem and router

- your PC (or other PCs in your LAN) is not downloading large files when you are testing

- you are not being throttled by your ISP due to going over the monthly cap

- your tests are always done on an ethernet connection to the router - do not use wireless for testing

- you read this topic and follow the instructions there.

Make sure you provide information for other users to help you. If you have not already done it, please EDIT your post and add this now:

- Your ISP and plan

- Type of connection (ADSL, ADSL2, VDSL)

- Your modem DSL stats (do not worry about posting Speedtest, we need sync rate, attenuation and noise margin)

- Your general location (or street)

- If you are rural or urban

- If you know your connection is to an exchange, cabinet or conklin

- If your connection is to a ULL or wholesale service

- If you have done an isolation test as per the link above

Most of the problems with speed are likely to be related to internal wiring issues. Read this discussion to find out more about this. Your ISP is not intentionally slowing you down today (unless you are on a managed plan). Also if this is the school holidays it's likely you will notice slower than usual speed due to more users online.

A master splitter is required for VDSL2 and in most cases will improve speeds on DSL connections. Regular disconnections can be a monitored alarm or a set top box trying to connect. If there's an alarm connected to your line even if you don't have an alarm contract it may still try to connect so it's worth checking.

I recommend you read these two blog posts:

- Is your premises phone wiring impacting your broadband performance? (very technical)

- Are you receiving a substandard ULL ADSL2+ connection from your ISP?

I am the Geekzone Robot and I am here to help. I am from the Internet. I do not interact. Do not expect other replies from me.

These links are referral codes: Sharesies | Mighty Ape

michaelmurfy

meow
13240 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1340912 10-Jul-2015 23:00

Disable IPv6 on your router.

Also on Snap (except on UFB) and am not seeing any latency problems. I also have IPv6 disabled.

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.

Zeon

3916 posts

Uber Geek

Trusted

#1340915 10-Jul-2015 23:13

michaelmurfy: Disable IPv6 on your router.

Also on Snap (except on UFB) and am not seeing any latency problems. I also have IPv6 disabled.

Lol wut? This happens on IPv4 also.

I'm going to be honest but a straight "disable IPv6" is terrible advice and the attitude which is going to hurt its adoption... Besides I need IPv6 for RDP in the first place!

Speedtest 2019-10-14

michaelmurfy

meow
13240 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1340916 10-Jul-2015 23:17

It has happened in the past with me on IPv6 w/ Snap - I have normally been a big adopter of it and you know that :) - I do run IPv6 on my servers natively.

Anyway, failing that it looks like something is iffy. You ruled out your router as being a cause?

Zeon

3916 posts

Uber Geek

Trusted

#1340917 10-Jul-2015 23:19

michaelmurfy: It has happened in the past with me on IPv6 w/ Snap - I have normally been a big adopter of it and you know that :) - I do run IPv6 on my servers natively.

Anyway, failing that it looks like something is iffy. You ruled out your router as being a cause?

Ah right I see :)

Yea I am using a Mikrotik with Draytek modem in full bridge. If running the Draytek in a routing function get the same problem. Its fine all during the day and after 00:00 so guessing its congestion?

Speedtest 2019-10-14

michaelmurfy

meow
13240 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1340918 10-Jul-2015 23:23

Well it is either on Chorus's or Snaps end. Based on your Speedtest (with its low latency) I would think it is indeed congestion however it is very unlikely unless if you're on an ASAM. Given Snap a call and asked?

fe31nz

1228 posts

Uber Geek

#1340922 10-Jul-2015 23:30

Does a traceroute show where the congestion might be?

Equinox IT

Cloud spending continues to surge globally, but most organisations haven’t made the changes necessary to maximise the value and cost-efficiency benefits of their cloud investments. Download the whitepaper From Overspend to Advantage now.

Lorenceo

904 posts

Ultimate Geek

Trusted

#1341099 11-Jul-2015 12:34

I've experienced this a few times over the years, although admittedly not as badly as the data you've posted. Has always been resolved by creating a support ticket and Snap following up the issue with Chorus.

RalphFromSnap

776 posts

Ultimate Geek

Trusted

Snap Internet

#1341662 12-Jul-2015 16:41

Hi Zeon,

I've checked with our tech's and we can't see anything in our network that would be causing this.

Would it be possible to PM us your username / customer number so we can check your line?

Snap

0800 BROADBAND (276 232)
www.snap.net.nz

@SnapInternet on Twitter
Snap Internet on Facebook

Our Social Media Team:
^RO Ricky - Technical Lead
^AT Ashleigh - Retail Marketing Coordinator

Zeon

3916 posts

Uber Geek

Trusted

#1341865 12-Jul-2015 23:56

fe31nz: Does a traceroute show where the congestion might be?

To be honest I didn't do one but my gut tells me that it will be that high even at the first hop. Good idea though.

I tested earlier this evening and just now and latency is 20ms so much better at the moment.

Ralph has received the details and will investigate :)

Speedtest 2019-10-14

Zeon

3916 posts

Uber Geek

Trusted

#1342921 14-Jul-2015 11:41

Hey guys,
I was working last night and it was getting worse and worse until suddenly voila at 02:37am it went from being basically worse than dial up back to really good. Check this out - I left the ping running as I was working:

Reply from 202.37.100.24: bytes=32 time=816ms TTL=61
Request timed out.
Request timed out.
Reply from 202.37.100.24: bytes=32 time=825ms TTL=61
Request timed out.
Reply from 202.37.100.24: bytes=32 time=676ms TTL=61
Request timed out.
Request timed out.
Reply from 202.37.100.24: bytes=32 time=765ms TTL=61
Reply from 202.37.100.24: bytes=32 time=788ms TTL=61
Reply from 202.37.100.24: bytes=32 time=771ms TTL=61
Reply from 202.37.100.24: bytes=32 time=740ms TTL=61
Request timed out.
Reply from 202.37.100.24: bytes=32 time=754ms TTL=61
Reply from 202.37.100.24: bytes=32 time=791ms TTL=61
Reply from 202.37.100.24: bytes=32 time=780ms TTL=61
Reply from 202.37.100.24: bytes=32 time=798ms TTL=61
Reply from 202.37.100.24: bytes=32 time=811ms TTL=61
Request timed out.
Reply from 202.37.100.24: bytes=32 time=825ms TTL=61
Reply from 202.37.100.24: bytes=32 time=742ms TTL=61
Request timed out.
Reply from 202.37.100.24: bytes=32 time=776ms TTL=61
Request timed out.
Request timed out.
Reply from 202.37.100.24: bytes=32 time=758ms TTL=61
Reply from 202.37.100.24: bytes=32 time=725ms TTL=61
Reply from 202.37.100.24: bytes=32 time=715ms TTL=61
Reply from 202.37.100.24: bytes=32 time=717ms TTL=61
Request timed out.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 192.168.88.1: Destination net unreachable.
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=21ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=20ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=94ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=52ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=19ms TTL=61
Reply from 202.37.100.24: bytes=32 time=18ms TTL=61
Reply from 202.37.100.24: bytes=32 time=20ms TTL=61

Speedtest 2019-10-14

fe31nz

1228 posts

Uber Geek

#1343124 14-Jul-2015 15:28

That looks like what you would expect if you had been disconnected and then immediately reconnected again. So maybe some monitoring software somewhere noticed the connection problem and reset your link to try to fix it. Snap connections work via PPPoE and PPPoE sends echo packets back and forth every so often to verify the connection. Maybe too many of those packets went missing and that triggered a reconnection. It looks like the reconnection happened in the sort of timescale that you would expect for PPPoE reconnecting with a FritzBox.

SCM

459 posts

Ultimate Geek

#1343126 14-Jul-2015 15:30

fe31nz: That looks like what you would expect if you had been disconnected and then immediately reconnected again. So maybe some monitoring software somewhere noticed the connection problem and reset your link to try to fix it. Snap connections work via PPPoE and PPPoE sends echo packets back and forth every so often to verify the connection. Maybe too many of those packets went missing and that triggered a reconnection. It looks like the reconnection happened in the sort of timescale that you would expect for PPPoE reconnecting with a FritzBox.

Snap aDSL uses PPPoA

RalphFromSnap

776 posts

Ultimate Geek

Trusted

Snap Internet

#1343156 14-Jul-2015 16:16

Hey Zeon,

Looks like the cause of this was the upload on your individual line maxing out. We've PM'd you some pointers to check for and what we believe the cause is.

Cheers,

Ralph ^JOB

Snap

0800 BROADBAND (276 232)
www.snap.net.nz

@SnapInternet on Twitter
Snap Internet on Facebook

Our Social Media Team:
^RO Ricky - Technical Lead
^AT Ashleigh - Retail Marketing Coordinator

Zeon

3916 posts

Uber Geek

Trusted

#1343424 15-Jul-2015 01:40

Thanks for the help Ralph, I think your suggestion was spot on.

For those interested it looks like our router was running an Open DNS resolver being used in a DNS amplification attack.

When I had got the router I only configured the PPP details and WLAN and presumed that the firewall must be preset but obviously not!

It's a Mikrotik RouterOS device. You could access the web control panel, SSH, telnet - pretty much everything over the WAN interface....

Speedtest 2019-10-14

1 | 2