Intermittent Service

zappaDPJ · Jul 29, 2009, 01:46:22

The problem is BT and/or Openreach have lied either to me or IDNet which has left me in limbo. The engineer told me that my line from the faceplate to the exchange is fine, capable in his opinion of 14.0-16.0 Mbps. He told me the problem was an issue at the exchange and that a 'lift and shift' would be requested. BT simply reported back to IDNet that the line was fine with no further detail.

Before I moved to this house I actually went as far as checking how much throughput the BT line was capable of. The previous resident was with Be and had a sync rate of around 16000. When I first moved in I went with Be and had a sync rate just below that but I migrated to IDNet because of the peak time contention on Be's network. I had near full sync with Max, no disconnects and apart from some short lived latency issues everything was fine.

So now I'm stuck on WBC with a fault that means I can't work to anywhere near my full potential during the day (I need over 2.5Mbs + some headroom) and these continual interuptions of service mean I can't adequately run my on-line gaming organisation in the evenings which numbers over 400 people. My daughter had to go to an Internet cafe in the middle of her exams and she that must be obeyed has been restricted to using her employer's connection for her needs. All in all the switch to WBC has been two months of a nightmare and there's no end in sight.

I'd prefer to stick with IDNet but they haven't been able to sort the problem out in two months and I can't see any way forward. I know that my line will support at least quadruple what it is currently giving me because it has done so for 10 months prior to WBC. AAISP have had all the data and they too are convinced that my line can do a lot better than 2Mbs and have offer a money back guarantee on it, I can't see that I have much to lose.

Sorry if this sounds like a rant but desperation has started to set in. I've was told categorically on three occasions that I could switch back to Max if WBC did not work out but this doesn't seem to be the case now and I believe I'm now stuck on some pseudo capped service which runs at one third below the cap in real money and it just isn't enough. I have to make other arrangements for my email which if I honest is something I should have done ages ago. Once that is in place, if things haven't improved drastically I will be moving on I'm afraid.

zappaDPJ · Jul 29, 2009, 01:47:49

Oh and thanks for the feedback, I do read it and it is greatfully received

Rik · Jul 29, 2009, 10:30:38

I understand your frustration, Zap, and I wish I had an answer for you. As I think you know, my move to WBC has been smooth, but I don't think the product is mature and certainly my line is less stable now. At the time IDNet launched WBC, they did not know that BT would not revert people, but that's turned out to be the case.

I am assured that the hostlink is 'running light, ie at a small percentage of its capacity, so there does seem to be some issue with the BT infrastructure on this problem.

Whatever you decide to do, don't be a stranger, you don't have to be a customer to be a Netter, and we'd like to know how you get on.

James_D · Jul 29, 2009, 13:38:36

Indeed let us know how you get on, theres a wide range of issues effecting people moving to WBC and it'd be interesting to see if moving to another ISP cures the issue, I have to admit it's crossed my mind.

zappaDPJ · Jul 29, 2009, 15:11:06

IDNet support have been in touch today with an update so I'm holding fire for now. I'll keep you informed.

Rik · Jul 29, 2009, 15:12:26

That's good, Zap.

Simon · Jul 29, 2009, 15:18:37

Good to know, Zap.

Sebby · Jul 29, 2009, 18:06:13

zappaDPJ · Jul 29, 2009, 23:10:24

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\zappaDPJ>ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=236ms TTL=59
Reply from 212.69.36.10: bytes=32 time=300ms TTL=59
Reply from 212.69.36.10: bytes=32 time=332ms TTL=59
Reply from 212.69.36.10: bytes=32 time=368ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 236ms, Maximum = 368ms, Average = 309ms

C:\Users\zappaDPJ>

Ouch! And that's on WBC tonight

zappaDPJ · Jul 29, 2009, 23:17:33

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6323 kbps(DOWN-STREAM), 1183 kbps(UP-STREAM)
IP profile for your line is - 5500 kbps
Actual IP throughput achieved during the test was - 877 kbps

If you wish to discuss these results please contact your ISP.

I think my connection is about to disappear up its own pipe

Sebby · Jul 29, 2009, 23:44:32

Negative sync... I'm surprised BT haven't thought of that.

zappaDPJ · Jul 30, 2009, 02:59:29

Well, as it happens, things got steadily worse until I couldn't even get a ping to return. I had zero throughput and then this...

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\zappaDPJ>ping idnet.com

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=9ms TTL=59
Reply from 212.69.36.10: bytes=32 time=7ms TTL=59
Reply from 212.69.36.10: bytes=32 time=8ms TTL=59
Reply from 212.69.36.10: bytes=32 time=7ms TTL=59

Ping statistics for 212.69.36.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 9ms, Average = 7ms

C:\Users\zappaDPJ>

Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6323 kbps(DOWN-STREAM), 1183 kbps(UP-STREAM)
IP profile for your line is - 5500 kbps
Actual IP throughput achieved during the test was - 5141 kbps

If you wish to discuss these results please contact your ISP.

So you were right Sebby, negative sync. I dissapeared up my own pipe and came out the other end

I think somewhere, in a reality not so far away, there's a malevolent gremlin laughing his b******s off everytime he twangs my line

Simon_idnet · Jul 30, 2009, 03:05:31

Blimey, those ping times are more in line with a leased-line than a DSL circuit!

Lance · Jul 30, 2009, 07:08:28

Lets hope the gremlin stops twanging your line now then!

And Simon, get some sleep!

Rik · Jul 30, 2009, 08:42:40

I'm issuing Temazepam to everyone tonight.

Steve · Jul 30, 2009, 08:52:18

Quote from: Rik on Jul 30, 2009, 08:42:40
I'm issuing Temazepam to everyone tonight.

That'll mess up the ping time

Rik · Jul 30, 2009, 08:56:42

It depends which port you insert it into.