![]() ![]() ![]() ![]() |
|
Scotty1986:Sideface:Scotty1986: .... Will Vodafone bother doing any further upgrades with fibre so close? ...
Close for some, but not for others.
We don't get fibre until late 2019 at the earliest.
Theoretically, if enough people jump ship, congestion will improve for the stragglers.
That is not a very long time when it comes to building infrastructure though. How old is the cable tech already? Will they really want to spend much more if they know everybody will leave within 4 years? Unless they really do think it can compete with fibre in the long run and be as reliable, which I'm all for, competition is a good thing.
And again, a shout-out to the reps from Vodafone for their communication with us!
lchiu7:Skillie: Not sure if this is a problem - getting a higher ping on 130/10 in Kapiti after the upgrade too...
I've never seen higher than about 95Mb/s on my 130/10 connection recently so I would be happy with this. I am pretty sure when I first switched back to cable I saw > 100Mbs so it's not my TP Link router that is the bottleneck. And all my PC's are on GBE.
wigster:lchiu7:Skillie: Not sure if this is a problem - getting a higher ping on 130/10 in Kapiti after the upgrade too...
I've never seen higher than about 95Mb/s on my 130/10 connection recently so I would be happy with this. I am pretty sure when I first switched back to cable I saw > 100Mbs so it's not my TP Link router that is the bottleneck. And all my PC's are on GBE.
What type of cable modem do you have?
Your speed is typical of a 100Mb/s Ethernet interface. If you have a Cisco cable modem and the link light is amber, then your router is connecting at 100Mb/s. If the link light is green, then it has a 1000Mb/s Ethernet connection.
Have you tried taking your TP-Llink out of the picture and doing a direct connection between the cable modem and your PC/laptop to see what you get?
Another thing to check with your TP-Link, if it capable of setting the Ethernet link speed, make sure it it set to Autonegotiate
zaphodalive: I just experienced stalling when resolving google sites and CDNs again:
At 12:07 on 12/10/15:
Visiting geekzone.co.nz - stall on cse.google.co.nz from 12:07 until 12:10.
Visiting stuff.co.nz - stall on cse.google.com from 12:07 to 12:09, then (perhaps concurrently) www.google-analytics until 12:10.
Visiting cracked.com - stall on cdn.resignationmedia.com from 12:07 to 12:08, then (perhaps concurrently) www.google-analytics until 12:09.
Visiting thechive.com - stall on www.google-analytics from 12:07 to 12.09.
When I tried coming to this forum cse.google.co.nz stalled so I opened new browser windows for each of the above sites to confirm if it was a systemic issue. I probably should have done a traceroute but didn't think about it. Can Vodafone personnel confirm if these issues are related to the congestion issues at all, as several others in this forum are experiencing it as well?
wigster:lchiu7:Skillie: Not sure if this is a problem - getting a higher ping on 130/10 in Kapiti after the upgrade too...
I've never seen higher than about 95Mb/s on my 130/10 connection recently so I would be happy with this. I am pretty sure when I first switched back to cable I saw > 100Mbs so it's not my TP Link router that is the bottleneck. And all my PC's are on GBE.
What type of cable modem do you have?
Your speed is typical of a 100Mb/s Ethernet interface. If you have a Cisco cable modem and the link light is amber, then your router is connecting at 100Mb/s. If the link light is green, then it has a 1000Mb/s Ethernet connection.
Have you tried taking your TP-Llink out of the picture and doing a direct connection between the cable modem and your PC/laptop to see what you get?
Another thing to check with your TP-Link, if it capable of setting the Ethernet link speed, make sure it it set to Autonegotiate
zaphodalive: I just experienced stalling when resolving google sites and CDNs again:
At 12:07 on 12/10/15:
Visiting geekzone.co.nz - stall on cse.google.co.nz from 12:07 until 12:10.
Visiting stuff.co.nz - stall on cse.google.com from 12:07 to 12:09, then (perhaps concurrently) www.google-analytics until 12:10.
Visiting cracked.com - stall on cdn.resignationmedia.com from 12:07 to 12:08, then (perhaps concurrently) www.google-analytics until 12:09.
Visiting thechive.com - stall on www.google-analytics from 12:07 to 12.09.
When I tried coming to this forum cse.google.co.nz stalled so I opened new browser windows for each of the above sites to confirm if it was a systemic issue. I probably should have done a traceroute but didn't think about it. Can Vodafone personnel confirm if these issues are related to the congestion issues at all, as several others in this forum are experiencing it as well?
Scotty1986:zaphodalive: I just experienced stalling when resolving google sites and CDNs again:
At 12:07 on 12/10/15:
Visiting geekzone.co.nz - stall on cse.google.co.nz from 12:07 until 12:10.
Visiting stuff.co.nz - stall on cse.google.com from 12:07 to 12:09, then (perhaps concurrently) www.google-analytics until 12:10.
Visiting cracked.com - stall on cdn.resignationmedia.com from 12:07 to 12:08, then (perhaps concurrently) www.google-analytics until 12:09.
Visiting thechive.com - stall on www.google-analytics from 12:07 to 12.09.
When I tried coming to this forum cse.google.co.nz stalled so I opened new browser windows for each of the above sites to confirm if it was a systemic issue. I probably should have done a traceroute but didn't think about it. Can Vodafone personnel confirm if these issues are related to the congestion issues at all, as several others in this forum are experiencing it as well?
I have these issues as will I think. Often Geekzone wont completely load, it just, stalls, maybe minutes later it will finish. Same with speedtest, often the Speedo just wont load, but everything else is there. Then minutes later it shows up. Also on stuff. I'm in Woodridge Wellington if it matters.
Please support Geekzone by subscribing, or using one of our referral links: Samsung | AliExpress | Wise | Sharesies | Hatch | GoodSync | Backblaze backup
|
![]() ![]() ![]() ![]() |