In reply to a post by craski:

Can anybody on here offer any feedback based on direct experience of an EoFTTC service?

It isnt clear if the dedicated downstream bandwidth is just the first 20Mb or the full capability of the connection. i.e. If the FTTC connection currently syncs at 80/20, on EoFTTC would the 80Mb be dedicated or just the first 20Mb dedicated with the rest coming from shared availability?

My experience from having it for 12 months with TTB was just as others have said. They guaranteed 20mbps both ways but my line often ran at the full 80mbps down sync - AS for service I had no problem. I used tech support once and it was my own doing that caused the problem on my router - this was at 3am and I spoke to someone in Manchester.

I paid £130 a month inc VAT - I used about 25-30TB a month during a time when we were doing on demand content and lots of testing was needed.

So, if the FTTC cab gets wiped out by a vehicle (as has happened numerous times) it will get replaced and working in 7 hours? Rather than the weeks it normally takes?

I can�t see how the physical vulnerability of FTTC cabs is compatible with a high SLA business service.

In reply to a post by AL66:

So, if the FTTC cab gets wiped out by a vehicle (as has happened numerous times) it will get replaced and working in 7 hours? Rather than the weeks it normally takes?

I can�t see how the physical vulnerability of FTTC cabs is compatible with a high SLA business service.

Nope, won't get fixed any quicker just because a high care level is on one of the cirxuits. An axcident like that is considered an MSO so it gets fixed as quickly as possible.

Typically that would need a new cabinet deployed, which can be turned around in a day or two in some cases, but if for example the incident impacted the power supply (requiring the power company to be involved) or tore up the tie cables to the PCP, it's going to take a lot longer to sort.

Now when you compare this to a point to point ethernet circuit, yes there's *traditionally* less exposed elements, but there's a lot of nodes that are just as susceptible to an incident in the same way as you suggest, including equally as exposed cabinets, housing fibre.
You may actually find that repair of this is as, if not more, complicated than dropping a pre-built VDSL cabinet on top of a footprint. Poles running down the side of a busy road for example.

I agree though, time to restoration should be shorter on a dedicated pt-pt service, and it rightly is a superior service, and priced accordingly.

The benefits of a circuit like this is speedy fault restoration for line specific issues (more likely on copper), and the bandwidth guarantee which you just don't get on a consumer grade service. Lower rental, quicker deployment and none of the build-out challenges you find with EAD.

The minimum speed "guarantees" you're seeing pop up on some consumer grade packages now are just a, "sorry have some money back" or "you can leave if you want" promises.
This type of service typically wound have proper QoS being applied on the carrier's network to ensure bandwidth and such an issue being treated as a fault until resolved, with proper investigation.
These circuits also tend to use a native ethernet presentation, which has some benefits for larger businesses with bespoke or MPLS like arrangements (routing protocols, stacked vlans etc).

In reply to a post by Blmcg:

The minimum speed "guarantees" you're seeing pop up on some consumer grade packages now are just a, "sorry have some money back" or "you can leave if you want" promises.

The "business broadband" FTTC packages appear to take a similar stance.

In reply to a post by Blmcg:

These circuits also tend to use a native ethernet presentation.

Does EoFFTC require a modem like standard FTTC does?

I've seen OpenReach deploy a mobile DSLAM (it was basically a truck with a DSLAM and generator in the back) and have every line on the cabinet back up and running in 48 hours. Not quite the 7 hours guaranteed here but pretty impressive.

I think they have quite a few of the mobile DSLAMs. No idea how often/how quick they are usually deployed though.

In reply to a post by 23Prince:

I paid £130 a month inc VAT - I used about 25-30TB a month during a time when we were doing on demand content and lots of testing was needed.

Seems a fair enough price for that sort of throughput.
We are currently typically doing around 3 TB a month but that is growing steadily. I wonder at what level ISPs would actually start complaining that their unlimited business broadband isnt actually unlimited!

Good idea. It must be a fairly regular occurrence to justify having such a thing.

In reply to a post by craski:

Does EoFFTC require a modem like standard FTTC does?

Yes. Profile 17a VDSL2 same as anything else over OpenReach FTTC.

They only have a few. General course of action would be to commence a full replacement of the DSLAM typically within 48-72 hours. Longest delay is getting the power supply restored as it's considered low priority by the DNO's, so often left on batteries for extended periods with the consequent loss of service when they run out.

In reply to a post by craski:

Can anybody on here offer any feedback based on direct experience of an EoFTTC service?

It isnt clear if the dedicated downstream bandwidth is just the first 20Mb or the full capability of the connection. i.e. If the FTTC connection currently syncs at 80/20, on EoFTTC would the 80Mb be dedicated or just the first 20Mb dedicated with the rest coming from shared availability?

We have installed a few EoFTTC for a clients and have found them very reliable and in the main to deliver the correct speed. the only issue we've ever had is if the underlying speed of the FTTC isnt up to scratch. you get guaranteed a symetrical 20mb in the backhaul and if you can get 80/20 you will get the guaranteed 20mb