Yobitel FTTH / Last-Mile Delivery

Overview

AI infrastructure is useful only if customers can reach it. Enterprise customers connecting to a Yobitel NeoCloud region need symmetric high-bandwidth last-mile fibre with documented SLAs; campus and branch deployments need reliable backhaul; consumer subscribers in serviceable areas need consistent gigabit service. Each of those needs a fibre service operator that owns the design, the civil works, the deployment, the OLT/ONT provisioning, and the ongoing operations — and that can deliver the service inside an SLA contract rather than a best-effort posture.

Yobitel FTTH is the telco fibre-to-the-home and last-mile connectivity service inside the Yobitel Infrastructure pillar. It is a telco offering distinct from the AI infrastructure surface above (Yobibyte, AI Applications, GPU Cloud, Edge AI); the AI infrastructure surface depends on connectivity, and the connectivity service exists in its own right to deliver it. Full lifecycle: design, build, provision, and operate, with the team that designs the network being the same team that operates it after handover.

Compared with BT Openreach and alternative UK fibre providers, the differentiator is integration with Yobitel NeoCloud regions: B2B customers connecting to a NeoCloud region for AI workloads see the fibre and the compute under a single operator contract with consistent SLAs, while B2C subscribers in serviceable areas benefit from the same operational discipline. Compared with running a separate fibre vendor alongside a NeoCloud deployment, the difference is operational consolidation — one NOC, one ticket queue, one accountability boundary.

Yobitel Communications — a UK-headquartered AI infrastructure company and NVIDIA Inception partner — operates the FTTH service in the UK as the primary footprint, with EU coverage rolling out through partner integrations as NeoCloud regions land. Pricing is published in USD per month per service tier; enterprise contracts include named SLA terms with credits for breach.

Service tiers and SLA matrix

The table below summarises the standard service tiers, the bandwidth envelope, and the contracted SLA. Custom enterprise tiers (above 10 Gbps, dark-fibre delivery, sovereign backhaul) are scoped per contract.

Tier	Bandwidth (symmetric)	Availability SLA	Latency profile	Packet loss SLA	MTTR target	Service credits
Consumer Gigabit	1 Gbps	99.5%	< 10 ms to nearest peering point	< 0.1%	8 business hours	Pro-rata month credit
Consumer Multi-Gigabit	2 Gbps	99.5%	< 10 ms to nearest peering point	< 0.1%	8 business hours	Pro-rata month credit
Small Business	500 Mbps	99.9%	< 5 ms to nearest peering point	< 0.05%	4 hours business; 8 hours OOH	Tiered against availability breach
Enterprise 1G	1 Gbps	99.95%	< 5 ms to NeoCloud; < 10 ms internet	< 0.05%	4 hours 24x7	Tiered against availability and latency breach
Enterprise 10G	10 Gbps	99.99%	< 3 ms to NeoCloud; < 8 ms internet	< 0.01%	2 hours 24x7	Tiered against availability, latency, packet loss breach
Enterprise 100G	100 Gbps (4x 25G or 1x 100G)	99.99%	< 2 ms to NeoCloud	< 0.01%	1 hour 24x7	Tiered against full SLA matrix
Dark Fibre	Customer-provided optics	99.99%	Physical-layer only	n/a (customer optics)	2 hours 24x7	Tiered against availability breach
Diverse Path (any tier)	+10–20% on base	Same as base tier	Failover < 50 ms	Same as base tier	Same as base tier	Same as base tier

Coverage areas and capacity

Coverage is published per region with the served metro areas, the tiers available, and the planned expansion windows. Coverage moves; the published map and the live feasibility check are the durable signals.

Region	Primary metros	Tiers available	B2B / B2C	NeoCloud backhaul
UK — Greater London	City, Docklands, West London, M25 corridor	All tiers including 100G	B2B + B2C in served streets	Direct to uk-london NeoCloud region
UK — Manchester / North West	Manchester central, Salford, Trafford Park, Liverpool	All tiers up to 10G; 100G in industrial estates	B2B + B2C in served streets	Direct to uk-manchester NeoCloud region
UK — Edinburgh / Central Belt	Edinburgh, Glasgow	Up to Enterprise 10G	B2B; B2C planned	Direct to uk-edinburgh NeoCloud region
UK — Cardiff / South Wales	Cardiff, Newport, Swansea	Up to Enterprise 10G	B2B; B2C limited	Backhaul via uk-cardiff partner facility
UK — Belfast / Northern Ireland	Belfast, Derry/Londonderry	Up to Enterprise 1G; 10G rolling	B2B	Backhaul via uk-belfast partner facility
UK — Rolling expansion	Birmingham, Leeds, Newcastle, Bristol	Up to Enterprise 10G	B2B-first	Partner backhaul to nearest NeoCloud region
EU — Partner-delivered	Frankfurt, Paris, Amsterdam, Dublin metros	Up to Enterprise 10G under partner contracts	B2B-first	Direct to relevant EU NeoCloud region

Ordering and install timeline

Enterprise FTTH service orders begin with a site survey. Submit a service order through the Yobitel commercial team or the partner channel: provide the site address(es), the required bandwidth tier, the connectivity intent (backhaul to a Yobitel NeoCloud region, public internet, both), the diverse-path requirement, and the contracted SLA term (12 / 24 / 36 / 60 months). Yobitel responds with a feasibility assessment based on existing fibre footprint, required civil works, and a delivery timeline.

Once feasibility is signed off, the design phase produces a GIS-anchored network plan: fibre route, splice diagrams, OLT/ONT specification, backhaul path into the chosen Yobitel NeoCloud region, and the bill of materials. Civil works follow per the design — aerial pulls where the duct exists, micro-trenching for urban infill, traditional trenching for greenfield — and every splice is OTDR-tested before commissioning. OLT/ONT provisioning lands the customer premises equipment, the BSS/OSS integration completes circuit activation, and the service goes live against the documented SLA.

From order to go-live, typical enterprise delivery is 6–12 weeks depending on civil-works complexity and permit timing. Consumer activations in serviceable areas typically land inside 10 business days. After handover, the same Yobitel NOC that runs Managed Operations operates the link 24x7 against the contracted SLA tier.

Tip: For enterprise customers planning to connect to a Yobitel NeoCloud region, place the FTTH order at the same time as the NeoCloud workspace commitment — civil works and OLT lead times typically gate the integrated go-live, so parallel execution shortens the calendar.

Pricing

FTTH is priced per site per month in USD by tier, with one-time install charges where civil works are required, term discounts for 24/36/60-month contracts, and explicit uplifts for diverse-path resilience and 100G/Dark-fibre tiers. The pricing below is indicative for UK delivery in mid-2026; specific contracts are scoped per feasibility outcome.

Service tier	Monthly USD per site	Install (one-time)	Term discount (36-mo)	Notes
Consumer Gigabit	$60 / mo	$120	n/a (consumer term)	Subject to serviceable-area check.
Consumer Multi-Gigabit	$90 / mo	$180	n/a	Same coverage as Gigabit.
Small Business 500M	$240 / mo	$600	10% off	12-month minimum.
Enterprise 1G	$650 / mo	$1,500	15% off	24-month minimum.
Enterprise 10G	$3,200 / mo	$8,500	18% off	24-month minimum.
Enterprise 100G	$18,500 / mo	Quoted per site	20% off	36-month minimum; quoted per site.
Dark Fibre	Quoted per fibre-km	Quoted per site	Quoted	Bespoke.
Diverse Path uplift	+15% on base	+30% one-time	Same as base	Required for 99.99% tiers.
NeoCloud virtual circuit	$0 / mo on backhaul-bundled tiers	$0	n/a	Free virtual circuit on Enterprise 10G+ contracts.
Service credit (SLA breach)	Pro-rata	n/a	n/a	Capped at 100% MRC per month.

Note: Pricing is illustrative; the feasibility response is the binding number. Civil-works-heavy sites can raise install materially; bundled NeoCloud contracts often offset the FTTH MRC against the AI infrastructure consumption. Treat the published pricing as a forecasting input rather than a fixed list.

Security and compliance

FTTH delivery follows UK telco regulatory norms — Ofcom oversight, network and information systems regulations, lawful-intercept requirements where applicable. This is a telco service rather than an AI workload, so AI compliance frameworks (NCSC Cloud Security Principles, EU AI Act) do not apply at the FTTH layer directly; they apply to the workloads carried over the link.

For enterprise customers carrying sovereign or regulated workloads over FTTH, the link is a transport layer underneath the workload's compliance posture. Yobitel ensures the link's operational security (BCP/DR for fibre cuts, OTDR-tested splices, segmented BSS/OSS), but the workload-level compliance (NCSC controls for the AI workspace, GDPR for the data crossing the link) sits at the layer above.

• Ofcom oversight — Yobitel operates under UK General Conditions of Entitlement (where applicable) and complies with Ofcom reporting on coverage and complaints.
• NIS 2 — Network and Information Systems Directive 2 alignment for network resilience and incident reporting.
• Lawful intercept — supported per UK regulatory obligations on warranted requests; out-of-scope for routine operations.
• ISO 27001:2022 — covers the operational security envelope (NOC, BSS/OSS, ticketing).
• PCI-DSS — payment-card data carried over FTTH is the customer's responsibility; link operational security is documented for the customer's PCI scope.
• GDPR — applies to customer-data telemetry the FTTH service generates (subscriber records, traffic volumes); DPA available.
• Wayleaves and right of way — managed per UK Electronic Communications Code; customers retain landowner relationships.

Alternatives

UK enterprise customers connecting to a Yobitel NeoCloud region without Yobitel FTTH have three practical alternatives. BT Openreach plus a chosen service provider is the national-footprint incumbent — broadest coverage, longest civil-works lead times in some areas (typically 8–16 weeks for enterprise circuits), and a separate vendor seam between the fibre layer and the compute layer. Alternative UK fibre operators (CityFibre, Virgin Media Business, Zen, and others) are metro-heavy with shorter lead times in their served streets and a similar two-vendor pattern when paired with a separate cloud. Dark fibre with customer-supplied optics is the third path: layer-1 capacity with the customer's own optics and routing — appropriate when the customer already runs a substantial network team, less so otherwise.

Yobitel FTTH is the right answer when the customer is consolidating fibre and compute under one operator (single NOC, single ticket queue, single set of service credits, single accountability boundary), when NeoCloud-integrated backhaul matters (the virtual circuit into the NeoCloud region is bundled rather than a separate procurement), or when published USD pricing aligns with the rest of the customer's Yobitel commercials. For customers whose only requirement is generic UK fibre with no downstream Yobitel relationship, an established national operator may be the simpler choice.

Note: The vendor-consolidation case is operational rather than commercial: customers running fibre and compute under separate vendors typically lose a quarter or more of available NOC time on inter-vendor coordination during incidents. Single-operator delivery removes that seam.

Where Yobitel FTTH fits in the Yobitel stack

FTTH is the connectivity layer of the Yobitel Infrastructure pillar — the transport service that brings enterprise B2B customers and B2C subscribers into the Yobitel network and, by extension, into Yobitel NeoCloud regions and the Yobibyte platform above. It is not part of the AI infrastructure surface; it is the prerequisite layer that makes the AI infrastructure surface reachable at the bandwidths and latencies AI workloads require.

Operationally, the same 24x7 NOC that runs Managed Operations for AI infrastructure customers runs the FTTH network monitoring service. Customers consolidating fibre and compute under one operator contract get a single accountability boundary — one ticket queue, one MTTR target, one set of service credits, one set of escalation paths.

Practically, three customer types interact with FTTH differently. An enterprise customer connecting to a Yobitel NeoCloud region buys FTTH as backhaul. A telco partner diversifying into AI uses Yobitel FTTH for the connectivity layer their existing customer base already expects. A consumer in a serviceable area buys FTTH as a standalone broadband service. The same operational discipline applies across all three; the SLA tier defines the contracted experience.