Load Balancers — hosted in Lagos
Coming soonLoad Balancers
One IP in front, healthy servers behind.
Distribute HTTP, HTTPS, TCP and UDP traffic across your servers with smart health checks, SSL termination and automatic failover — at a flat monthly price with no per-request charges.
- HTTP, HTTPS, TCP & UDP
- SSL termination with auto-renewal
- Three locally-hosted regions — Nairobi, Dar es Salaam & Lagos
- Data residency for Nigeria's Data Protection Act (NDPA) — your data stays in-country
- 99.99% uptime SLA
Launching soon · Local billing in KES, TZS & NGN
Pricing
One flat price, no per-request fees
Pick a size for your traffic. Data transfer between the load balancer and same-region backends is unlimited and included. In your currency, no forex.
Small
Hosted in Nairobi, Dar es Salaam & Lagos
- 10,000 concurrent connections
- 250 Mbps throughput
- Up to 20 backends
- Basic health checks
- Unlimited same-region transfer
Medium
Hosted in Nairobi, Dar es Salaam & Lagos
- 50,000 concurrent connections
- 1 Gbps throughput
- Up to 50 backends
- Advanced health checks
- Unlimited same-region transfer
Large
Hosted in Nairobi, Dar es Salaam & Lagos
- 100,000 concurrent connections
- 2.5 Gbps throughput
- Up to 100 backends
- Health checks with SSL verification
- Unlimited same-region transfer
Enterprise
Hosted in Nairobi, Dar es Salaam & Lagos
- 250,000+ concurrent connections
- 5+ Gbps throughput
- Unlimited backends
- Custom-script health checks
- Unlimited same-region transfer
Flat monthly pricing with no hidden fees and no per-request charges. Upgrade or downgrade tiers anytime with zero downtime. Prices exclude VAT; local currency figures are indicative and settled at checkout.
The platform
Everything between your users and your servers
Termination, health checks, persistence, and protection — handled at the edge of your stack so your backends just serve.
Automatic failover
Failing backends drop out of the pool instantly and traffic reroutes to healthy servers — no manual intervention.
Smart health checks
Probe backends over HTTP, HTTPS, TCP, or ICMP with custom intervals, timeouts, and recovery thresholds.
SSL/TLS termination
TLS 1.2 and 1.3 with SNI for multiple certificates, automatic renewal, and encryption offloaded from your backends.
Four balancing algorithms
Round Robin, Least Connections, Source IP Hash, and Weighted Round Robin — match the algorithm to the workload.
Session persistence
Cookie-based or source-IP sticky sessions keep stateful clients pinned to the same backend.
DDoS protection built in
Rate limiting and connection throttling at the balancer, before traffic ever reaches your servers.
IPv4 & IPv6
Full dual-stack support on every load balancer, at every tier.
Real-time monitoring
Live traffic, connection counts, backend health, and access logs with request-level detail.
API & Terraform
Create and manage balancers from a REST API or the Terraform provider — wired into your CI/CD.
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.
Nigeria
Lagos
~4 ms
typical, within metro · Data stays in Nigeria
Kenya
Nairobi
~2 ms
typical, within metro · Data stays in Kenya
Tanzania
Dar es Salaam
~6 ms
typical, within metro · Data stays in Tanzania
Use cases
Built for what you're building
Web applications
Spread HTTP and HTTPS traffic across your web servers for high volume with zero downtime.
APIs & microservices
A single entry point routing requests across API instances and containerized services.
Database read scaling
Balance read queries across replicas while writes go straight to the primary.
Gaming & streaming
Low-latency TCP and UDP balancing for player connections and high-bandwidth media.
How it works
In front of your traffic in three steps
Create a load balancer
Pick a region and a size tier — live in under 60 seconds from the console or API.
Add backends & health checks
Point it at your servers, choose an algorithm, and set the health check that fits.
Point your DNS at it
One record change and traffic flows through — failover and monitoring are already on.
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.
Sales
Why Lineserve
Managed beats maintaining your own proxy
Running NGINX or HAProxy on a VPS means one more machine to patch, monitor, certify, and fail over — and it's usually the single point of failure in front of everything else.
FAQ
Questions, answered
It sits in front of your servers on a single IP and distributes incoming traffic across them. If a backend fails, traffic reroutes to healthy servers automatically — better availability, better performance, no single point of failure.
A flat monthly rate per size tier — Small, Medium, Large, or Enterprise. Data transfer between the load balancer and backends in the same region is unlimited and included. No per-request charges, no hidden fees.
Yes. Backends can be Lineserve Cloud Servers, VPS, dedicated servers, Kubernetes nodes — or servers hosted anywhere else, as long as the load balancer can reach them over the network.
Upload certificates to the load balancer and it terminates SSL/TLS for you, offloading encryption from your backends. TLS 1.2 and 1.3 are supported, with SNI for serving multiple certificates from one load balancer and automatic renewal.
The load balancer probes each backend over HTTP, HTTPS, TCP, or ICMP on an interval you set. Servers that fail their threshold are removed from the pool automatically and re-added once they recover.
Sticky sessions route a returning client to the same backend — essential for apps that keep session state locally. Choose cookie-based or source-IP persistence per load balancer.
Round Robin for evenly matched servers, Least Connections for long-lived connections, Source IP Hash to pin clients to a server, and Weighted Round Robin to send more traffic to bigger machines.
Yes. Upgrade or downgrade anytime with zero downtime — your configuration, certificates, and backend pools carry over unchanged.
Yes. Your data is hosted in Nigeria and stays in-country, giving you data residency for Nigeria's Data Protection Act (NDPA). It isn't moved out of Nigeria without your instruction.
In our Lagos data centre (ng-1a). Your content is stored and served from Lagos, close to your users.
Pay in Naira by card or bank transfer. No foreign card or forex conversion is required.
You're billed in NGN. Prices can be viewed in USD, KES, TZS, or NGN, but as a Nigeria customer you pay in NGN with no forex conversion.
Put a load balancer in front of it — soon
Load Balancers are launching soon. Talk to us to reserve early access and pricing in your local currency, with no card to start.
Launching soon · 99.99% uptime SLA · Local billing in KES, TZS & NGN