FTTC/VDSL - Installation Delayed

Started by .Griff., Aug 19, 2010, 17:27:00

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

.Griff.

Hi peeps,

First post so go easy on me.

I submitted my order for Home Plus Fibre on August 6th. On the 9th I received a reply acknowledging my order and later that day another email confirming an Openreach engineer would visit on August 16th. The following day I received another emailing informing me that due to a lack of available engineers the installation had been delayed a month to September 14th. I thought this was fair enough as demand was probably high and after all we're all in the same boat and other people have probably had their orders delayed too. I'm no VIP and can wait like the rest of them.

However today I came home from work early to find an Openreach van had just pulled up outside my home. Excited that my installation had been brought forward I got out the car and chatted to the engineer only to find he'd come to install FTTC/VDSL at my neighbours. We had a brief chat and he was pretty clear that to his knowledge there was no shortage of engineers. An hour later I saw the engineer leave my neighbours so I went over and spoke to my neighbour about his installation and it turns out he only placed an order at the end of last week.

So my query is this.. If my neighbour can place an order for the same product as me less than a week ago and have his installation completed already why do I have another month to wait having ordered over two weeks ago? Should I shut up and be patient or is there any way IDNET can double check my installation date with Oprenreach?

Rik

Welcome to the forum. :welc: :karma:

Gives support a ring, they can chase the order for you.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Cheers for the welcome guys!

Brian (IDNET support) has asked BT/Openreach for a closer appointment date and he's calling me back tomorrow to let me know if the request has been successful.


Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Ray

Ray
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Result!!

Brian called me back just as he promised and Openreach will now be here on Monday!

Awesome support so far.

(PS - I've been with Bethere for years now and their support was generally excellent too but IDNET is on another level so far)

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

MisterW

QuoteOpenreach will now be here on Monday!
BT Openreach must have suddenly found a load of spare engineers hiding somewhere :evil:

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Glenn

The BT engineer at work, he is being moved to refit exchanges.
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Rather than start a new thread I'll add my question here..

Not that I plan on doing so but what happens in I go over my download limit on the "Home Plus Fibre" service/product/plan ?


Glenn

when you get near the limit, you will be sent a warning email, once over the limit, bandwidth is charged at £1/Gb
Glenn
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Is there any package info for fibre.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Cheers Glenn. I guess there's always the option of upgrading to the next product if I find myself near the limit.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Cheers, Perhaps it was just me but it seemed well hidden.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Openreach have been and what a nice guy friendly guy he was too.

I can't access the line stats from the modem but he was happy for me to have a look at the multifunction tester/device which reported a downstream attenuation of 10.4dB (cabinet is approximately 400 metres away).









I'll do some more speedtests in the evening and late tonight.

Rik

Takes up a bit of desk space doesn't it. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Quote from: Rik on Aug 23, 2010, 12:27:48
Ping's not bad either...

Very impressed with the pings -

Pinging www.bbc.net.uk [212.58.244.68] with 32 bytes of data:
Reply from 212.58.244.68: bytes=32 time=13ms TTL=57
Reply from 212.58.244.68: bytes=32 time=13ms TTL=57
Reply from 212.58.244.68: bytes=32 time=13ms TTL=57
Reply from 212.58.244.68: bytes=32 time=13ms TTL=57

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

Pinging www.idnetters.co.uk [212.69.36.28] with 32 bytes of data:
Reply from 212.69.36.28: bytes=32 time=13ms TTL=59
Reply from 212.69.36.28: bytes=32 time=13ms TTL=59
Reply from 212.69.36.28: bytes=32 time=14ms TTL=59
Reply from 212.69.36.28: bytes=32 time=13ms TTL=59

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

Pinging 85.236.101.22 with 32 bytes of data:
Reply from 85.236.101.22: bytes=32 time=14ms TTL=123
Reply from 85.236.101.22: bytes=32 time=14ms TTL=123
Reply from 85.236.101.22: bytes=32 time=14ms TTL=123
Reply from 85.236.101.22: bytes=32 time=13ms TTL=123

Ping statistics for 85.236.101.22: (Multiplay COD4 server)
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 13ms, Maximum = 14ms, Average = 13ms