The history of my line has been nothing short of excellent since having ADSL enabled. Always syncing at full 8128/448 and on FAST path without fail; all except for a short period last year when a fault developed up the pole outside my house.
At the time the line became uber unstable and syn's/speeds/pings really poor and random, the fault was rectified quickly and returned to normal, all except my pings. This is one of the crucial factors for me, as ping is closely related to latency and I am a very keen gamer.
Historicaly, I would alays get sub 20ms to a london server via speedtest.net and that temporarily improved more when I went onto the Premium IDNET home supermax service, for which I paid an additional £10 per month premium, up until the fault when everything went tat's oop! Subsequently, even after the fault was rectified and my profile recovered I can never get better than 57ms via the same test; some threefold increase in ping. And believe me, that makes a huge difference with gaming via the Xbox 360!
When the fault occurred and had been subsequently fixed I was told by support that my BT profile would be lifted and things would return to normal, however I have suffered the poor pings now (by historical comparison) for many many months and was under the impression that this was an IDNET network issue related to the rollout of ADSL2+ (between the have's & have not's).
Finally I decided last week that enough was enough, I am just completely hacked off with never getting host in Halo 3 now, so requested my MAC and placed an order vis FAST.co.uk; who currently seem to be offering the best ISP service. A decision that I did not take lightly as I have been impressed with IDNET since joining in Nov 2007.
However, I may have acted hastily as today when checking my router line stats I discovered that Interleaving was switched on for my line, clearly this would explain the ping issue, and I don't know why I had not noticed it before - other than the line stats are not in my Linksys WAG160N main menus (for some stupid reason the stats are a hidden page).
I have logged a support email with IDNET, but fear that it may all be too late. I would happily un-migrate if this issue could be resolved tout suite and I were able to cancel the migration!
My migration is due to happen Wed/Thur next week , am I too late?
I'm not sure, but I'd guess yes. Give support a call in the morning, they will be able to tell you.
Thanks Rik, that's kind of annoying since I have put up with this issue for a long time and finally nailed the problem only after requesting my MAC!
I'll phone support first thing and see what can be done, but I suppose the crux is going to be will I get charged a fee from Fast if I'm able to cancel? I would imagine so.
I suppose I really shot my self in the foot here too, because I understand that the line doesn't retrain upon migration and I'll probably have to wait ten days before I can get Fast to get Interleaving switched off?
You will, I'm afraid.
Whilst Fast are an exceptional ISP with superb support, I can tell you from 1st hand experience that my pings on fast path were double those I get with IDnet.
Mine have started to creep up again. Although IDNet pings at 20ms. So not sure if it's interleaving or the servers I use. I'm too shy to bother support to ask if it's been turned on or not. (they turned it off for me last year :thumb:) :blush:
Quote from: Technical Ben on May 16, 2010, 22:00:06
Mine have started to creep up again. Although IDNet pings at 20ms. So not sure if it's interleaving or the servers I use. I'm too shy to bother support to ask if it's been turned on or not. (they turned it off for me last year :thumb:) :blush:
Even if its been turned off if the line looks unstable to BT's computer gremlin it can switch it back on, and its then almost impossible to get it turned off again, BT's rules not IDnets.
Quote from: Technical Ben on May 16, 2010, 22:00:06
Mine have started to creep up again. Although IDNet pings at 20ms. So not sure if it's interleaving or the servers I use. I'm too shy to bother support to ask if it's been turned on or not. (they turned it off for me last year :thumb:) :blush:
IDNet can't see whether it's on or off, so check your router to see if that gives an answer. If not, drop support an email and ask them to turn it off, it's a simple thing for them to do, at least the first time, Ben. :)
Quote from: Rik on May 17, 2010, 09:05:42
IDNet can't see whether it's on or off, so check your router to see if that gives an answer. If not, drop support an email and ask them to turn it off, it's a simple thing for them to do, at least the first time, Ben. :)
It looks like he said he had it turned off last year, Rik. Thats why I said it may be hard a second time :dunno:
It may, Gary, ideally the first thing to do is find out whether it's on or off.
Quote from: Rik on May 17, 2010, 09:36:52
It may, Gary, ideally the first thing to do is find out whether it's on or off.
very true, I wonder how FTTC will work with VT software that's I take it new for it, out hopefully without this mess and confusion
It ought to be a much simpler system, but then we are talking about BT.
Quote from: Rik on May 17, 2010, 10:23:20
It ought to be a much simpler system, but then we are talking about BT.
;D I bet most of the engineers wont be trained up in time either ::)
That's a given. ;)
Good morning Sawest, All,
Unfortunately, if there is an order already progressing against your line number any modify orders will be rejected.
If you no longer wish to proceed with your migration, contact the new provider and see if the order can be cancelled. If the line has not yet been tagged to them you should be able to stop the migration process, we can then submit the modify order for you.
If you are at all uncertain do give us a call, we will be happy to discuss the procedure with you.
Kind regards,
Miriam
IDNet Support
Thank's Miriam.
As efficent as ever.
Quote from: Gary on May 16, 2010, 23:37:51
Even if its been turned off if the line looks unstable to BT's computer gremlin it can switch it back on, and its then almost impossible to get it turned off again, BT's rules not IDnets.
That's why I did not ask again. The line is great, and I know it's BT equipment that will auto switch me, and not IDNet. I really need to trouble shoot first. My line is super consistent and close to the exchange. So any gremlin will almost undoubtedly be a one off (tripping over the router etc). So I would prefer it off. :'(
But as said, other servers are ok. And it's a bit of a black art getting a reading off the router as to what setting it is on.
I wonder if Sawest has a local problem, a router problem or if it is only interleaving causing the trouble.
Sadly, we won't now be able to find out.
I just did! With a little bit of hand wavery on Router Stats I got it to show "fast path on" which means I'm still on it. ;D
So it's down to the servers themselves, or my pc, or exchange congestion. :( Just cleared a Java virus, so will see if that will help. (Darn Java updates!)
Welcome to the murky side of comms, Ben. ;)
Just an update of my longer pings and latency (sorry that it's slightly off topic). I just remembered they are digging up the road for a new estate just around the corner. It's also just by the exchange! Any bets on the whole connection going down some time soon due to a digger in the pipes?
60/40, Ben. ;)
You can get interleaving flagged to be never enabled on your line. Support did it for my line a year or so ago.
You can, but BT can decide to override it even then, as I understand it, Paul. With the new ISP controls on WBC DLM that doesn't happen. Sadly, the scheme has not yet been rolled out.