Load Balancers — hosted in Nairobi, Dar es Salaam & 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 sovereignty — 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
Nairobi, Dar es Salaam or Lagos — and what decides it
The rule is unglamorous and it holds nearly everywhere: put the workload in the country whose users and whose records it serves. Per-unit prices are identical in all three regions, so the decision is geography and law rather than cost — and there is no useful midpoint, because traffic between the three cities is still commonly carried through Europe.
ke-1a is for Kenyan users and Kenyan records, and for regional teams whose head office is already in Nairobi. Every Kenyan subsea cable — TEAMS, SEACOM, EASSy, LION2, DARE1 and PEACE — comes ashore at Mombasa, and that capacity is carried roughly 480 km inland to the city where the carriers and the customers are. Domestic traffic never makes that trip: it is exchanged inside Nairobi at KIXP, the neutral exchange TESPOK has run since 2002, with 136 peer networks and 2.9 Tbps of connected capacity. Lineserve peers there.
tz-1a is for Tanzanian users, and it is where moving an origin changes the most: Tanzania has no content-delivery edge of its own, so a Dar es Salaam viewer is served from another country however the CDN is configured. There is no inland haul either — SEACOM, EASSy and SEAS come ashore in the city itself, and Dar es Salaam is a named landing point on 2Africa. Tanzanian networks meet at TIX, run since 2003 by the country's service-provider association, and 13,820 km of state fibre carries one origin on to Mwanza, Arusha and Dodoma.
ng-1a is for scale and for regulated Nigerian workloads. Eight subsea systems land in and around Lagos, among them MainOne, SAT-3, WACS, Equiano and 2Africa, which comes ashore at Lekki. Nigerian networks exchange domestic traffic at IXPN, founded in 2006 to stop domestic packets being hauled to London and now running 13 points of presence across seven states. Lagos also has a date attached: a Central Bank circular directs payment transaction data generated in Nigeria to be stored there from 1 January 2027.
All three give a buyer based elsewhere the same pair of things: a request from a user in the city reaches a machine in that city, typically in single-digit milliseconds, and the records it touches sit under one named country's law.
Kenya
Nairobi
~2 ms
typical, within metro · Data stays in Kenya
Tanzania
Dar es Salaam
~6 ms
typical, within metro · Data stays in Tanzania
Nigeria
Lagos
~4 ms
typical, within metro · Data stays in Nigeria
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
You are on a different continent from your infrastructure
That is the real reservation, and it is answerable with what exists. Architecture, quotes, contracts, a data processing agreement, the registered names and tax identifiers that have to appear on your invoices: [email protected], in writing, in a thread you can forward to your own legal and finance people. Running services are driven from the console, the API and the ticket system on your account. Two phone lines are published for the region — +254 119 039 063 in Kenya and +255 761 847 121 in Tanzania.
Scheduling across the distance is the practical problem, and the arithmetic is friendlier than it looks. Nairobi and Dar es Salaam run on East Africa Time, UTC+3; Lagos on West Africa Time, UTC+1. Neither observes daylight saving, so the gap between your clock and theirs moves only when your own clocks change, and a window agreed in June still means what you thought it meant in December. From London, Nairobi is three hours ahead in winter and two in summer, and Lagos an hour ahead in winter and level in summer. From New York in July, a 09:00 call is 14:00 in Lagos.
Most of what would be a phone call elsewhere is a call you make yourself. Building, resizing, rebooting, snapshotting and rebuilding an instance are API and console operations that behave identically at three in the morning your time or theirs, and a browser console reaches a machine that has lost its own networking. What needs a person in the building is a physical fault — and that person is there already.
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.
Your data stays in the region you deploy to. Across our data centres in Nairobi (Kenya), Dar es Salaam (Tanzania), and Lagos (Nigeria) it never has to leave the continent — deploy in the country closest to your users and your data is held there.
In whichever of our three regions you choose — Nairobi (ke-1a), Dar es Salaam (tz-1a), or Lagos (ng-1a). Your content is stored and served from that in-country facility.
Pay in USD by card or bank transfer — or switch to our Kenya, Tanzania, or Nigeria market to pay locally in KES, TZS, or NGN with methods like M-Pesa.
You can view and pay in USD, or switch to a local market to pay in KES (Kenya), TZS (Tanzania), or NGN (Nigeria). You're settled in the currency you choose at checkout.
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