enforcernz: Ok so it seems that it doesnt matter what plan you are on, speeds between 12am - 8am are crap
So why doesnt xNet acknowledge that there is a speed issue problem. This would atleast look like they give a +#*^ about there customers !!!
Of course Xnet acknowledge the issue, have you tried calling the helpdesk?
Prime I like people like you....your only answer is if you dont like it leave......
We are paying for a service, and that service was offered by Xnet, why should we have to leave because we are not getting what we paid for?
Because it's not likely to be changing dramatically anytime soon, you can't just change a plan without notice, or flick a switch and give awesome speeds to everyone. Changes if they'll happen will be slow and if you're not getting what you're paying for then switching isp's might be a good idea.
They know the problem and probably know people are leaving since its still not fix .I say if you can't take the speed call them up and address the issue.If nothing is done and you can't wait then join another ISP.
Sitting here and having a WAA is a waste of time .Join another ISP and move on!
It's not that easy if you're on naked DSL. There's bugger all in the way of decent plans out there if you don't have a voiceline :-( I've fired an email to Ralph from Snap, but haven't heard back yet.
In the meantime I've changed from the Torrent plan to the egular plan on Xnet. I HOPE this will improve my ability to actually do ANYTHING online at night.
"The surest sign that intelligent life exists elsewhere in the universe is that it has never tried to contact us."
I had the same experience with you martin308, I've got a good speed when I first sign in, say for the first 2-3 months and then just recently (3 weeks ago) it started to slow down to only ~ 3KB/s - 8KB/s.
Hmm...looks like the 75GB free monthly download during off-peak hour now is a big joke... and also it looks like the peak-hour now shifted to 12mn to 8am....(hehe joke)...
I was doing a multi-streamed HTTP download (with DownThemAll in Firefox) from a well provisioned download server and my bandwidth was yo-yoing.... I watch it, up to 75KB/s then down to 0, then up again, then down. Consistently, and averaging to around 16KB/s. Looks like shaping to me, and I call bulls--t on it. I pay for a 'Fullspeed' download, theres nothing to suggest my usage will be shaped at given times.
I just fired up a random well-seeded torrent and see a similar result. Speed goes up, then drops to zero. Then up, then down to zero. Same computer earlier today I was getting totally decent speeds.
Speedtest.net from Auckland (WXC no less) gives me almost exactly 1600kb/s at the moment. From Sydney I get 760kb/s but see a very familiar pattern of speed going up and then snapping down - however I think that Speedtest is streaming many small packets which seems to test at a higher rate than I can actually achieve (the transfers of parts may be complete before the throttler kicks in).
The plot is thickening... I can repeat my earlier connection throttling with the same download (coming from an Amazon S3 server), but testing with my own US server I get full speed.
So downloading the 11MB file to home PC from the Amazon server gets low speed, and yo-yoing connection. Downloading same file from Amazon server to my server gets >3MB/s. Downloading that file then from my server to home PC gets pretty reasonable speeds (70KB/s).
So it's not all international, it's not the source server, and it's not a content-sensitve filter.
The traces for the down downloads are:
Tracing route to s3-2.amazonaws.com [207.171.181.225] over a maximum of 30 hops:
1 * * * Request timed out. 2 49 ms 50 ms 50 ms ip-58-28-15-31.wxnz.net [58.28.15.31] 3 50 ms 50 ms 50 ms ip-58-28-13-131.wxnz.net [58.28.13.131] 4 51 ms 53 ms 57 ms ge-0-0-0-akl-core1.wxnz.net [58.28.8.8] 5 52 ms 58 ms 54 ms Gi9-1.gw1.akl1.asianetcom.net [203.192.166.105]
6 238 ms 230 ms 230 ms po0-0.gw1.sjc1.asianetcom.net [202.147.50.129] 7 204 ms 203 ms 204 ms po0-0.gw2.sjc1.asianetcom.net [202.147.50.130] 8 233 ms 239 ms 232 ms unknown.Level3.net [64.152.102.129] 9 250 ms 232 ms 234 ms vlan79.csw2.SanJose1.Level3.net [4.68.18.126] 10 215 ms 215 ms 216 ms ae-71-71.ebr1.SanJose1.Level3.net [4.69.134.197]
11 235 ms 236 ms 233 ms ae-3.ebr1.Seattle1.Level3.net [4.69.132.50] 12 223 ms 222 ms * ae-12-51.car2.Seattle1.Level3.net [4.68.105.3] 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * AMAZONCOM.car2.Seattle1.Level3.net [4.79.106.2] reports: Destination net unreachable.
Tracing route to wibble.net [72.249.126.132] over a maximum of 30 hops:
1 * * * Request timed out. 2 50 ms 52 ms 49 ms ip-58-28-15-31.wxnz.net [58.28.15.31] 3 50 ms 49 ms 50 ms ip-58-28-13-131.wxnz.net [58.28.13.131] 4 50 ms 51 ms 49 ms ge-0-0-0-akl-core1.wxnz.net [58.28.8.8] 5 49 ms 58 ms 59 ms Gi9-1.gw1.akl1.asianetcom.net [203.192.166.105]
6 177 ms 176 ms 177 ms po2-0.gw1.lax1.asianetcom.net [202.147.61.189] 7 177 ms 179 ms 179 ms eqix.lsan.twtelecom.net [206.223.123.36] 8 210 ms 211 ms 209 ms hagg-03-ge-0-0-0-460.dlfw.twtelecom.net [64.129.234.4] 9 210 ms 216 ms 216 ms ge-1-1.core1.colo4dallas.net [206.123.64.26] 10 213 ms 210 ms 212 ms 206.123.65.61 11 214 ms 215 ms 214 ms 72.249.125.31 12 209 ms 212 ms 211 ms 72.249.126.132
Similarly a download from Sourceforge (via Internode) was reasonably good. But the earlier problem download and torrents are very obviously affected.
So there's obviously something else going on here, possible upstream of WxC?
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.
and also it looks like the peak-hour now shifted to 12mn to 8am....(hehe joke)...
