hio77: Do you use a switch or connect directly to modem?

I don't have a modem, I'm on fibre

But my router is connected to a switch that serves the LAN.  Symptoms say it isn't the switch though, because why would that affect the connection speed via WiFi, that is independent of the switch?

Given that the slow speed is on ethernet and Wifi, is identically slow with two different routers, and is unaffected by an ONT reset, I can't see how this can be due to anything on the customer side of the ONT.  Surely it has to be a problem with provisioning or the fibre connection to the ONT?

More thoughts:

Your results: Fast ping and very good upload speed, yet slow download. It appears you have done isolate testing.

Are you on a capped fibre plan? You could be limited to dialup speed if you exceed your cap.

You have been on DSL with Slingshot in the past. Maybe Slingshot config has slipped from fibre back to DSL?

Are you a big data user? Maybe Slingshot has throttled your download speed. Test using a VPN to isolate your IP and speed test again.

Stuff fibre customer here (in Wellington with IPV6 enabled if it makes any difference). Am seeing slow speeds to various Vocus speedtest sites as well.

All tested using wifi on a laptop, but, the higher speed tests before and after show issues are not local (well, max speed on wireless is ~450-550 Mbps) I get 920Mbps when connected via gigabit ethernet.

Vocus Communications Sydney 444 Mbps down, 105 Mbps up

Spark Wellington  152Mbs down, 88Mbps up

Chorus fibre lab auckland 497Mb/s down 236Mb/s up

But

Vocusgroup Nz Christchurch    30.54Mb/s down, 64Mb/s up

Vocusgroup NZ Auckland 34.76 Mbps down, 89.32 Mbps up

Some more tests

Kordia Auckland 471 Mbps down, 93.93 Mbps up.

Telstra Sydney 22.55 Mbps down, 51.20 Mbps up

2 Degrees Sydney   29.88Mbps Down, 62.45Mbps up

MyRepublic Auckland 419Mbps down, 206 Mbps up.

Have retested Vocus group speedtests a few times and see similar results.

General browsing not too impacted on my connection.

Gordy7:

 

More thoughts:

 

Your results: Fast ping and very good upload speed, yet slow download. It appears you have done isolate testing. 1

 

Are you on a capped fibre plan? You could be limited to dialup speed if you exceed your cap. 2 

 

You have been on DSL with Slingshot in the past. Maybe Slingshot config has slipped from fibre back to DSL? 3

 

Are you a big data user? Maybe Slingshot has throttled your download speed. Test using a VPN to isolate your IP and speed test again. 4

 

 

 

1. Still could be smashing download speeds with a very well seeded torrent(has op ruled this out? you're not torrenting anything are you that just so happens to be slamming your download speed?)

2. If they were on a cap their download speeds wouldn't be on dial up speed, probably 1mbps that would also include their upload, also slingshot don't appear to slow you down, they just charge you $5 for every 50gb data block over 150gb, again doubtful they'd be on the data cap plan and again both upload and download speed would be affected if they were being slowed down by slingshot.

3. DSL and fibre are 2 different technologies, could be a provisioning error but no way that's DSL.

4. Slingshot do not enforce a fair use policy anyway so I don't believe slingshot is throttling anyway.

MaxineN:

 

Gordy7:

 

More thoughts:

 

Your results: Fast ping and very good upload speed, yet slow download. It appears you have done isolate testing. 1

 

Are you on a capped fibre plan? You could be limited to dialup speed if you exceed your cap. 2 

 

You have been on DSL with Slingshot in the past. Maybe Slingshot config has slipped from fibre back to DSL? 3

 

Are you a big data user? Maybe Slingshot has throttled your download speed. Test using a VPN to isolate your IP and speed test again. 4

 

 

 

 

1. Still could be smashing download speeds with a very well seeded torrent(has op ruled this out? you're not torrenting anything are you that just so happens to be slamming your download speed?)

 

2. If they were on a cap their download speeds wouldn't be on dial up speed, probably 1mbps that would also include their upload, also slingshot don't appear to slow you down, they just charge you $5 for every 50gb data block over 150gb, again doubtful they'd be on the data cap plan and again both upload and download speed would be affected if they were being slowed down by slingshot.

 

3. DSL and fibre are 2 different technologies, could be a provisioning error but no way that's DSL.

 

4. Slingshot do not enforce a fair use policy anyway so I don't believe slingshot is throttling anyway.

 

Thanks for the info on my points. I was just thinking of a few possible ideas to help explain the OPs slow download situation.

Shortly I am due to go on to Slingshot unlimited gigabit and I would hate to be in the OPs position with slow download.

Gordy7:

 

More thoughts:

 

Your results: Fast ping and very good upload speed, yet slow download. It appears you have done isolate testing.

 

Are you on a capped fibre plan? You could be limited to dialup speed if you exceed your cap.

 

You have been on DSL with Slingshot in the past. Maybe Slingshot config has slipped from fibre back to DSL?

 

Are you a big data user? Maybe Slingshot has throttled your download speed. Test using a VPN to isolate your IP and speed test again.

 

 

 

Thanks, good thinking there.  I'm on unlimited fibre and don't even have a copper connection to the house, so I think that eliminates some options.  We are quite big data users but definitely no torrents running at the moment or for the last few days.  The problem also persisted when I reverted to the ISP router, with nothing connected to it except one machine for testing.

Slingshot's website shows my average daily use around 15GB, much lower for the last few days!

I'm going to switch back to the ISP router again this afternoon, with a new WiFi password so I know exactly what is connected.

Interesting to see the other slow speed results to Vocus servers

shk292:

hio77: Do you use a switch or connect directly to modem?

I don't have a modem, I'm on fibre

But my router is connected to a switch that serves the LAN.  Symptoms say it isn't the switch though, because why would that affect the connection speed via WiFi, that is independent of the switch?

Given that the slow speed is on ethernet and Wifi, is identically slow with two different routers, and is unaffected by an ONT reset, I can't see how this can be due to anything on the customer side of the ONT.  Surely it has to be a problem with provisioning or the fibre connection to the ONT?

Try connect your PC directly to the ONT, create a DHCP interface with VLAN10 and run a speedtest that way

nztim:

 

Try connect your PC directly to the ONT, create a DHCP interface with VLAN10 and run a speedtest that way

 

Thanks, I'll try that this afternoon

nztim:

 

Try connect your PC directly to the ONT, create a DHCP interface with VLAN10 and run a speedtest that way

 

Well, that was strange. I tried to set up a direct connection to the ONT from a PC but couldn't make that work - Error 651.  It may be because there was no (obvious) way to set a VLAN for the ethernet interface on the laptop I was using.

But, when I plugged the ISP router back in, speed is now restored.  Not sure if that is coincidence, whether Slingshot has done something or whatever.  Going back to my mesh system kills it again, which is odd because I've been using that for around 2 years with no problems up to now.  I've connected the mesh in access point mode to the ISP router for now and will see how this goes for a while.

And, no idea what the issue was with only the vocusgroup nz speedtests, but, this is also resolved.

Vocusgroup Nz Christchurch    30.54Mb/s down, 64Mb/s up

Vocusgroup NZ Auckland 34.76 Mbps down, 89.32 Mbps up

is now

Vocusgroup Nz Christchurch    508.74 Mb/s down, 342.85 Mb/s up

Vocusgroup NZ Auckland 380.16 Mbps down, 234.43 Mbps up

Again, Wi-Fi on laptop so not real maximum, would probably be faster if wired.

shk292: In case anyone is interested in the conclusion of this, below is slingshot explanation of fault and resolution:

The issue was due to conflicting IP sessions with another account. This was resolved by assigning you a new IP address.

How the heck did the manage to assign 1 IP address to a single static

nztim:

How the heck did the manage to assign 1 IP address to a single static