LINESERVE

Managed Kubernetes — launching in Lagos, ng-1a

Coming soon

Managed Kubernetes in Nigeria

The kickoff spike does not care that your etcd person is on annual leave.

Nigerian traffic arrives in shapes most markets never see — ninety seconds at kickoff, ten weeks from late October, a national exam date everybody knew about a year ahead. Kubernetes is the right tool for that, and running its control plane well is a full-time specialism most Lagos teams cannot staff. Managed Kubernetes runs that layer in ng-1a, with autoscaling worker pools underneath and clusters opening at NGN 27,860 a month plus the resources you use. It is launching soon. Join the waitlist and we will tell you the week it is ready.

Clusters fromNGN 27,860/month + resources
  • Launching soon — join the waitlist for early access
  • Managed control plane: API server, scheduler, etcd
  • Clusters in Lagos, ng-1a
  • Autoscaling worker pools, down to zero when idle
  • Quoted and billed in Naira, settled by transfer or card

Launching soon · Billed in NGN

Pricing

A cluster fee, plus what your nodes use

Pick a control plane — Basic or Fault Tolerant — then pay only for the vCPU, RAM, storage, and load balancers your worker nodes actually consume. In your currency, no forex.

Basic

Single master node for development, testing, and non-critical workloads.

NGN 27,860/mo + resources

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 1 master node
  • 99.5% control-plane SLA
  • Kubernetes 1.28–1.31
  • Autoscaling worker pools
  • Prometheus & Grafana included
Recommended

Fault Tolerant

3 master nodes with automatic failover — recommended for production.

NGN 116,340/mo + resources

Hosted in Nairobi, Dar es Salaam, Lagos & Kampala

  • 3 master nodes, automatic failover
  • 99.95% control-plane SLA
  • Kubernetes 1.28–1.31
  • Autoscaling worker pools
  • Prometheus & Grafana included

Worker node resources

Billed monthly, per unit consumed, on top of the cluster fee.

ResourceUnitPrice /mo
vCPUper vCPUNGN 6,660
RAMper GBNGN 3,060
Local diskper GBNGN 190
Network HDDper GBNGN 150
Universal SSDper GBNGN 230
Fast SSDper GBNGN 340
Public IPper IPNGN 1,500
Load balancer — Basicper LBNGN 16,380
Load balancer — Basic, redundantper LBNGN 32,770
Load balancer — Advanced, redundantper LBNGN 65,530

Your monthly total is the cluster fee plus the resources your worker nodes consume. Snapshots, file storage, and traffic beyond the included allowance bill at the same per-GB console rates. Prices exclude VAT; local currency figures are indicative and settled at checkout.

Where the cluster stands

Eight hops per request, all of them inside one building in Lagos

The reason to run containers is also the reason distance costs more once you do. A request hits the ingress, reaches a service, which calls two more, which each read from a database and a cache, and something writes an event on the way out. One user action, eight network hops, before a response exists. Inside ng-1a those hops happen inside one facility. Point the same architecture at Europe and you have spent the entire latency budget on transport: Lagos to the European hosting hubs typically runs around 110 to 125 ms before your own code does anything.

Nigeria makes it easy to know who is at the other end. The NCC counted 189.68 million active mobile subscriptions in May 2026 — MTN on 96.98 million and 51.19% of active lines, Airtel on 65.45 million and 34.55%, Globacom on 23.4 million and 12.39% — so two networks carry about 86% of the country, and every one of those people is inside it. Licensed fixed and wireless ISPs are a far smaller layer at 352,006 active subscribers, which is where the offices are rather than the handsets.

Domestic traffic between all of them is exchanged at IXPN, the neutral national exchange founded in 2006 by the NCC together with the Internet Service Providers Association of Nigeria. It now runs 13 points of presence across 7 states, more than 130 connected networks over 170 ports and 400G-capable core switching at three Lagos sites, with peak domestic traffic past 1 Tbps in April 2025 and 2 Tbps by March 2026. Nigeria built the places to exchange its own traffic and the volume moved to them.

And there is a reason not to put an ocean inside a domestic request. On 14 March 2024, WACS, ACE, MainOne and SAT-3 all failed near Côte d'Ivoire at once; thirteen countries were disrupted and repair estimates ran to eight weeks. Traffic from a Nigerian user to a cluster in Lagos never needed that fibre. No hyperscaler runs a full cloud region here either — Amazon's African region is Cape Town, Microsoft's is in South Africa, and what Lagos has from them is edge, which caches responses and does not schedule pods.

189.68M

Active mobile subscriptions in Nigeria (NCC, May 2026)

2 Tbps

Peak domestic traffic exchanged at IXPN (March 2026)

1.28–1.31

Kubernetes versions at launch

99.95%

Control-plane SLA on Fault Tolerant clusters

What comes wired in

A CSI driver that provisions HDD, Universal SSD or Fast SSD volumes straight from your PVCs. Services of type LoadBalancer that provision a cloud load balancer. An NGINX ingress controller and Helm from any repository. Prometheus and Grafana with alerting on every cluster. Private clusters — control plane and workers with no public IPs, reached over VPN or a bastion — from the first release rather than a later tier.

The role you would otherwise have to fill

Lagos has plenty of engineers who can write a Deployment manifest and very few who have carried a production control plane through three years of certificate rotations, etcd restores and minor upgrades. Those people are expensive, mobile, and usually already employed. That is the honest reason this product exists: the software is easy to install and costly to keep healthy, and most teams need that skill for far less than one full-time salary.

The platform

Everything a production cluster needs

Networking, storage, monitoring, and access control come wired in — so day two looks like day one.

Managed control plane

API server, scheduler, controller manager, and etcd — run, upgraded, and backed up by us.

Autoscaling worker pools

The cluster autoscaler adds and removes nodes with demand, down to zero when idle.

Auto-healing nodes

Unhealthy nodes are detected and replaced automatically, with no manual intervention.

Persistent volumes

A CSI driver provisions HDD, Universal SSD, or Fast SSD volumes straight from your PVCs.

Private clusters

Run control plane and workers with no public IPs, reached over VPN or a bastion host.

Load balancer integration

Services of type LoadBalancer provision cloud load balancers automatically.

Prometheus & Grafana

Built-in monitoring and dashboards on every cluster, with alerting included.

Helm & NGINX ingress

Deploy from any Helm repository, with a built-in NGINX ingress controller for traffic.

Multiple K8s versions

Choose Kubernetes 1.28–1.31 and upgrade through the console with zero downtime.

Regions

Lagos is home. Nairobi and Dar es Salaam are one API call away.

Deploy in ng-1a and the machine sits in Lagos, in the same city as most of the traffic it will ever serve. Nigeria makes that easy to reason about: 189.68 million active mobile subscriptions in May 2026, with MTN and Airtel together carrying about 86% of active lines and Globacom and T2 — the operator formerly branded 9mobile — behind them. Whichever of the four your customer is on, they are in Nigeria, and typical in-metro round trips here run around 4 ms.

Nigerian networks now hand traffic to each other in Nigeria. IXPN, the neutral national exchange founded in 2006 by the NCC, runs 13 points of presence across 7 states and more than 130 connected networks, with 400G-capable core switching at three Lagos sites; peak domestic traffic across it passed 1 Tbps in April 2025 and 2 Tbps by March 2026. Before it existed, two Nigerian networks exchanged packets by way of London — an intercontinental journey for a packet crossing one city.

Eight subsea systems come ashore in the country, Equiano landing on the Lagos coast in 2022 and 2Africa at Lekki, which is how Lagos became West Africa's arrival point for international capacity. Aim a request at Frankfurt or Virginia instead and that subsea path joins the critical route of every call the page makes, at typically around 110 to 125 ms before your application does any work. From Lagos, Accra and Nairobi typically sit further away in round-trip terms than London, because traffic between African networks still frequently transits Europe.

ke-1a in Nairobi and tz-1a in Dar es Salaam run on the same account and the same API, which makes a standby or a disaster-recovery plan a configuration rather than a second supplier. Make that call deliberately where personal data is involved: a copy of Nigerian personal data held abroad is a cross-border transfer under section 41 of the NDPA. Machine images and telemetry raise no such question.

Live

Nigeria

Lagos

~4 ms

typical, within metro · Data stays in Nigeria

Live

Kenya

Nairobi

~2 ms

typical, within metro · Data stays in Kenya

Live

Tanzania

Dar es Salaam

~6 ms

typical, within metro · Data stays in Tanzania

Live

Uganda

Kampala

~3 ms

typical, within metro · Data stays in Uganda

Expansion zonesSouth Africa · za-1aGhana · gh-1a

Use cases

Built for what you're building

Microservices

Run service meshes with built-in discovery, load balancing, and rolling deploys.

CI/CD pipelines

Host Jenkins, GitLab runners, or Argo CD close to your team, scaling with each build.

Batch & ML workloads

Queue batch jobs and training runs on autoscaling pools that shrink when idle.

Dev environments

Give every team an isolated namespace — one cluster, clean boundaries, less sprawl.

How it works

From zero to cluster in four steps

1

Pick region, version & cluster type

Choose your region, a Kubernetes version, and Basic or Fault Tolerant control plane.

2

Add worker pools

Size pools in vCPU, RAM, and storage, and set autoscaler bounds per pool.

3

Deploy with your tools

Download the kubeconfig, then kubectl apply or helm install like any cluster.

4

Let it run

The autoscaler tracks demand and auto-healing replaces bad nodes — day and night.

Uptime SLA

99.9%

  • Service credits applied automatically when we miss the SLA
  • Measured monthly, per region, on network and power availability
  • Tier III colocation facilities across all live regions

Support

West Africa Time, and a ticket that arrives with the facts

Two channels, doing different jobs. A ticket opened while signed in arrives carrying your account, your region and the instance, so the first reply is about the problem rather than about which machine you mean. [email protected] is the commercial address: a quotation against a purchase order, transfer details before a payment run, the billing account configured with your TIN and registered name before the first invoice, and the SLA terms and credit-claim process in writing while you are still choosing.

Before either, status.lineserve.net. Anything affecting a whole region is posted there faster than a reply could reach you, and checking it turns "my site is down" into "my instance is unreachable and the status page is clear" — a different ticket, and a much shorter one.

What to put in it, in the order it gets read: the region and the instance, the time the behaviour started in WAT, what changed just before it, the actual error text rather than a description of it, and whether it reproduces from more than one Nigerian network. An MTN handset and an office fibre line disagreeing is a different fault from both failing together.

Some of the fastest resolutions need nobody at all, and are worth knowing before the night you need them. Restore an on-demand snapshot. Roll back to a scheduled backup. Open the browser console when SSH is the thing that has broken. Resize or rebuild from the API. Migration planning and assistance are included at no extra charge.

Nigeria runs on West Africa Time, UTC+1, and does not observe daylight saving — two hours behind Nairobi and Dar es Salaam. A change window agreed in WAT means the same thing in January and in July. Note the offset when you schedule across regions.

Why Lineserve

Managed here beats self-managed anywhere

Running your own control plane on VMs means patching, etcd backups, and 2 a.m. failovers. Running on a distant hyperscaler means forex bills and latency. This is the third option.

CapabilityLineserveSelf-managed / global cloud
Control plane run and upgraded for you
Billing in NGN
Single-digit local latency
Data stays in Nigeria
Autoscaling worker poolsSometimes
Support in your timezone
No card or forex required

What it will cost

A cluster fee in Naira, then the resources your pods asked for

Two numbers make a Kubernetes bill, and keeping them apart is what makes the second predictable. The cluster management fee comes first: Basic, a single master node for development, testing and non-critical workloads, opens at NGN 27,860 a month behind a 99.5% control-plane SLA. Fault Tolerant, three master nodes with automatic failover, opens at NGN 116,340 behind a 99.95% SLA. Production belongs on Fault Tolerant — and in a market where the workload is a ninety-second spike, a control plane that cannot schedule is the outage.

Worker resources are the second number, billed per unit consumed: NGN 6,660 per vCPU and NGN 3,060 per GB of RAM a month, node-local disk at NGN 190 per GB, and persistent volumes at NGN 150 per GB for Network HDD, NGN 230 for Universal SSD and NGN 340 for Fast SSD. A public IP is NGN 1,500. Load balancers run NGN 16,380 for a Basic, NGN 32,770 for a Basic with automatic failover and NGN 65,530 for an Advanced redundant one. Nothing is bundled into a node size somebody else chose, which is what makes a pool you scale down actually get cheaper.

That structure is what makes the Nigerian traffic shape affordable rather than terrifying. Capacity you add in late October and give back in January costs what those weeks cost. A pool that exists for the ninety minutes around a fixture costs ninety minutes. Model three lines — the cluster fee, the steady-state pool, and what the peak costs for the hours the peak lasts — and the third line stops being the one that decides your year.

These are Naira figures from a Naira price list rather than a dollar rate converted when the page loads, and the charge is a domestic one, so it sits outside the international spending ceiling a Nigerian bank applies to a Naira card. VAT sits on top at 7.5%, administered by the Nigeria Revenue Service and shown separately at checkout — the lowest of the three markets Lineserve operates in. Send [email protected] your TIN and registered name when you join the waitlist and the billing account is configured once instead of corrected later.

Reserve pricing while you still have a budget cycle

Tell [email protected] the cluster tier and the rough pool shape and the team will put launch pricing in writing against your account. Nigerian procurement in the 2026 regime wants a supplier invoice that reconciles into a fiscal flow, and that is easier to arrange before a launch than during one.

Where a cluster stops being the cheap answer

Worth being blunt: one application with steady traffic runs better and cheaper on a cloud server from NGN 13,890 or a VPS from NGN 21,950, both live in ng-1a today. Kubernetes earns its cluster fee when you have many services, many clients, or a load whose shape changes by the hour. Nigerian workloads are unusually likely to be the third of those — which is why this page exists at all.

Prices exclude VAT; 7.5% is added at checkout. Figures are indicative launch pricing rather than an amount payable today, worker resources bill per unit consumed, and annual billing is ten months for twelve on eligible plans.

Data residency

The manifests are portable. The volumes are in a building, in a country.

It is easy to file a cluster under stateless and move on. Then you list the PersistentVolumeClaims: the Postgres a team installed with a Helm chart, the uploads directory holding identity documents, the queue with message bodies, the logs carrying phone numbers and transaction references, the registry cache. All of it is data on disks in one building, in whichever country the cluster was created in.

In Nigeria that country now has a date attached for part of the economy. On 15 June 2026 the Central Bank issued circular PSS/DIR/PUB/CIR/001/004, directing that payment transaction data generated within Nigeria be stored and managed in Nigeria, with full compliance from 1 January 2027, across deposit money banks, microfinance banks, mobile money operators, fintechs, switching companies, payment service providers and super agents. The affected data is reported to reach merchant records, transaction identifiers, timestamps, settlement information and processing logs — which is to say, several of the volumes attached to a fintech's cluster.

Around it sits the general regime. The Nigeria Data Protection Act 2023 is the statute and the Nigeria Data Protection Commission the regulator, with the General Application and Implementation Directive of 20 March 2025, effective 19 September 2025, operationalising it. Section 41 governs transfers of personal data out of Nigeria, permitted where the recipient is covered by an adequate law, binding corporate rules, contractual clauses, a code of conduct or a certification mechanism.

Create the cluster in ng-1a and the worker nodes, their volumes and their backups are in Lagos, under Nigerian law, and do not leave without your instruction. That is data residency for Nigeria's Data Protection Act. What a hosting provider supplies is the location; the assessment, the evidence and the sign-off stay with your compliance function, and they are a shorter piece of work when nothing crossed a border.

Point the backup target at the same country

Velero snapshots, database dumps and object storage mirrors are the classic route by which data quietly leaves a country, because that is where the credentials already pointed. Lineserve object storage runs a per-region endpoint in Lagos, so a backup target inside Nigeria is a configuration line rather than a project — and a restore that crosses the metro rather than the Atlantic.

Non-personal state can go anywhere

Container images, build artefacts, Helm charts and telemetry stripped of identifiers raise none of these questions. Drawing that line explicitly in your own architecture is an afternoon well spent — a system in which every byte is treated as regulated is a system nobody can operate at speed.

Who runs here

The Nigerian workloads a managed control plane is actually for

Nigeria's traffic has a shape. Flat baseline, violent scheduled peak, and a set of services behind it that each fail differently. That is the case for containers — and the case for someone else running the control plane underneath them.

Betting and iGaming

The sharpest burst on this site: odds ingestion all day, then bet placement at kickoff that lasts ninety seconds and is felt directly by the punter, with thousands of retail agent terminals reconciling against the same backend. Set autoscaler bounds against the fixture list, let the pools take the peak, and give the capacity back before the second half. Per-state reporting is now part of the workload too, after the November 2024 Supreme Court ruling moved regulation to the states.

Fintech and payments

The largest startup category in the country, and a set of services that genuinely want independent scaling: payment API gateways held to sub-second expectations, ledger and reconciliation workers, webhook receivers taking instant-transfer callbacks, KYC and BVN verification, fraud scoring. A Fault Tolerant control plane is the part you do not want failing mid-settlement, and the volumes underneath sit inside the CBN's 2027 perimeter.

E-commerce through the October–January peak

The longest peak of any market here: late October through Black Friday and the festive weeks, holding into January. Catalogue and search, cart and checkout, gateway callbacks arriving from several sources at once, dispatch integration, image serving. Capacity added in October and returned in January costs what those weeks cost, and the autoscaler makes that a policy rather than a set of manual decisions taken at midnight.

Edtech and exam windows

A national exam date is a hard, predictable peak that everyone knows about a year ahead — and a platform priced for Nigerian household incomes cannot carry a dollar cloud price per user. Video delivery, question banks and progress databases scaling into the window and back out of it, billed in Naira per vCPU and per GB, is the shape that makes the unit economics work.

Streaming and media

Nigeria produces an unusual amount of its own film and music and consumes a great deal of video. Transcoding is the textbook autoscaling job — heavy for an hour after an upload, idle overnight — and running it in Lagos beside the origin means the mezzanine file never crosses a subsea cable to be processed and come back.

Agencies, ISVs and platform teams

Lagos has a dense agency market reselling infrastructure to SME clients: a long tail of small services that would be uneconomic as individual VMs, and a namespace per client with quotas at the boundary that makes the model work at agency margins. Internal platform teams read the same page for a different reason — one cluster, one CI target, and a control plane that is not theirs to nurse.

CI/CD close to the artefacts

GitLab runners, Argo CD, Jenkins agents, review environments per branch. Build capacity is heavy for twenty minutes after a merge and idle overnight, which is exactly what an autoscaler with a floor of zero is for — and running it in Lagos removes an ocean from the middle of every pipeline run.

Customer references are available under NDA — ask [email protected] and the team will arrange one against the workload you are buying for.

Migrating

What moving a cluster here will look like at launch

From a control plane you run yourself

kubeadm on three VMs works, right up until the afternoon it does not — a certificate expires, etcd needs a restore rather than a restart, an upgrade goes sideways with production on it. At launch that layer is run, upgraded and backed up for you: API server, scheduler, controller manager and etcd, with unhealthy nodes detected and replaced automatically and version upgrades between 1.28 and 1.31 run through the console. Your manifests do not change. What changes is that the one engineer who knows how the cluster was built stops being a single point of failure — and if those masters are currently on hardware in your own office, the grid stops being one too. NERC put plant availability at 36% in January 2026, an average of about 4,901 MW against an estimated 30,000 MW of demand, and Nigerian business carries that gap itself in diesel.

From a managed cluster outside Nigeria

Kubernetes is the portable part and the standard tools do the work: kubectl, Helm and Velero. Export the namespaces, swap provider-specific annotations and storage classes for the CSI classes here, re-issue the ingress, run both clusters until the new one is healthy, then move DNS. What changes afterwards is three things at once: eight hops per request stop crossing an ocean, the bill becomes one Naira figure that does not move with the exchange rate or eat your international card allowance, and the volumes stop being a section 41 question. Migration planning is included at no extra charge and is better done before the service opens than after.

One question settles where a cluster really is, and it is worth asking of every provider you shortlist, this one included: which building are the worker nodes in, and in which country is that building? For ng-1a the answer is Lagos.

FAQ

Questions, answered

A service where we run the Kubernetes control plane for you — API server, scheduler, controller manager, and etcd — and handle upgrades, backups, and availability. You deploy and manage your applications; we keep the cluster healthy.

Basic clusters run a single master node and suit development, testing, and non-critical workloads, with a 99.5% control-plane SLA. Fault Tolerant clusters run 3 master nodes with automatic failover on a 99.95% SLA — recommended for production.

You pay the monthly cluster management fee (Basic or Fault Tolerant) plus the worker-node resources you actually consume — vCPU, RAM, storage, and load balancers. Scale worker pools up or down anytime; you only pay for what you use.

Versions 1.28 through 1.31, with new versions added shortly after upstream release. You upgrade your cluster through the console with zero downtime.

Yes. Enable the cluster autoscaler, set minimum and maximum node counts, and it adds or removes worker nodes automatically as your workload demands.

Yes. Create a cluster where the control plane and worker nodes have no public IP addresses, and reach it through a VPN or bastion host for maximum security.

Our CSI driver provisions volumes automatically when you create PersistentVolumeClaims. Choose HDD, Universal SSD, or Fast SSD storage classes to match your performance needs.

Yes. Every cluster ships with built-in Prometheus monitoring and Grafana dashboards. Container logs can flow to our logging service or your own backend.

Yes. Standard tools like kubectl, Helm, and Velero work directly, and our team assists with migration planning at no extra charge.

It is in build and not open for orders. Rather than publish a date that moves, we tell the waitlist directly — email [email protected] with the workload you have in mind and you will hear when the first release is ready.

Not yet. What you can do now is size the cluster and the pools with us, get launch pricing in writing against your account, and be in the first group given access. Cloud servers and VPS in ng-1a are live today if you need capacity in Lagos before then.

In ng-1a, our Lagos region. Control plane, worker nodes and their persistent volumes all sit there, in the same region already running cloud servers, VPS, dedicated hardware and object storage.

Basic runs a single master node and suits development, testing and non-critical workloads, on a 99.5% control-plane SLA at NGN 27,860 a month. Fault Tolerant runs three master nodes with automatic failover on a 99.95% SLA at NGN 116,340. Production belongs on Fault Tolerant.

The monthly cluster management fee plus the worker resources you consume — NGN 6,660 per vCPU, NGN 3,060 per GB of RAM, NGN 190 per GB of node-local disk, persistent volumes from NGN 150 per GB, public IPs at NGN 1,500 and load balancers from NGN 16,380. Scale pools up or down and the resource line follows.

No. Those figures are indicative launch pricing and nothing bills until the service opens. If your budget cycle needs a number sooner, ask [email protected] for a written quotation against your account.

In Naira, by bank transfer or card. Transfer is how most Nigerian business settles anything sizeable; a card suits a smaller cluster or a monthly renewal. Either way it is a domestic Naira transaction, so it sits outside the international spending cap your bank applies to a Naira card.

No. Displayed prices exclude VAT. Nigerian VAT on cloud and hosting services is 7.5%, administered by the Nigeria Revenue Service, and it is calculated and shown separately at checkout.

That is what they are for. Set minimum and maximum node counts per pool and the cluster autoscaler adds and removes nodes with demand, down to zero on pools that are idle — so a pool that exists for ninety minutes around a fixture is billed for ninety minutes.

1.28 through 1.31 at launch, upgraded through the console, with new versions added shortly after upstream release.

Yes — control plane and worker nodes with no public IP addresses, reached over VPN or a bastion host, from the first release.

A CSI driver provisions them from your PersistentVolumeClaims, with HDD, Universal SSD and Fast SSD storage classes. Those volumes are created in ng-1a and stay in Lagos.

Yes. Worker nodes and their volumes sit in ng-1a and are not moved out of the country without your instruction, which gives you data residency for Nigeria's Data Protection Act. Point your backup target at the Lagos object storage endpoint and the whole path stays in-country.

The grid stops being part of your availability story. NERC put plant availability at 36% in January 2026, an average of about 4,901 MW against an estimated 30,000 MW of demand, and Nigerian business covers the gap with diesel at a price nobody can budget a year out. A cluster in ng-1a is not on your building's supply, so a power failure at your address costs you the ability to sit in front of it, not the workload.

Often, no. One application with steady traffic runs better and cheaper on a cloud server from NGN 13,890 or a VPS from NGN 21,950, both live in ng-1a today. Kubernetes earns its cluster fee when you have many services, many clients, or a load whose shape changes by the hour — which, in this market, is a larger share of teams than usual.

Email [email protected] or use the contact form, with the cluster tier and pool shape you would use. No card, no commitment — it puts you in the first group given access and gets launch pricing written against your account.

Ship on Kubernetes, skip the control plane

Managed Kubernetes is launching soon. Talk to us to reserve early access and pricing in your local currency, with no card to start.

Launching soon · 99.95% control-plane SLA on Fault Tolerant · Billed in NGN