Do you monitor the servers?

We monitor the host nodes around the clock, so a hardware or hypervisor problem surfaces on our side rather than waiting for a customer to notice. We do not monitor what runs inside your VPS — that is inside the boundary you control, and watching it would mean looking at your server, which we do not do.

Is there redundancy in the infrastructure?

At the facility level, yes — the datacenters run redundant power and network feeds, which is what keeps a whole room from going dark on a single failure. What we do not claim is automatic failover of your individual VPS to another node, or a spare copy of your data. Neither exists, so neither is advertised.

How do I find out about planned maintenance?

It is announced in the client area Announcements section before it happens, and posted on the network status page while it is in progress. Maintenance that requires your server to restart is not something we spring on you.

My server is unreachable. Is it you or me?

Usually it is worth thirty seconds of checking before it is worth a message. Test the IP from a connection other than your own — a phone on mobile data will do. If it answers from elsewhere, the route between you and the datacenter is the suspect. If SSH answers but your site does not, the machine is up and the problem is in your layer. If nothing answers from anywhere, tell us with the IP and the time it started.

What is the single biggest cause of downtime you see?

Customer firewall rules, by a wide margin — a UFW or firewalld change that locks SSH out, applied and then forgotten. Second is memory exhaustion on a plan too small for what is running on it. Both are inside your layer, which is why the responsibility table above matters more than any percentage would.

Can I reduce my own risk?

Yes, and it is mostly unglamorous. Take off-site backups. Add a monitoring check against your own service so you learn about a problem before your users tell you. Do not run production on the smallest plan that technically fits. Test firewall changes on a second SSH session before closing the first.

So is there a guaranteed uptime figure or not?

Not on standard plans. This page is about what we do; the contractual position — including what is committed, what the money-back guarantee covers, and how to arrange a custom SLA — is set out separately.

Reliability · Operations

What we actually do to keep servers up.

Nodes monitored around the clock, redundant power and network at the datacenter, and maintenance announced before it happens. Also, honestly: most of what takes a VPS offline sits in your layer rather than ours, and the table below says which is which.

24/7 node monitoring
Redundant power & network
Maintenance announced first

Who Owns Which Layer The Contractual Position

Layers we operate

5 of 10

The other five are inside your server, where we do not look

Host nodes watched continuously
Facility power and network redundancy
Advance notice of scheduled work

How VPS For Life Approaches Uptime

VPS For Life monitors its host nodes around the clock, runs on datacenters with redundant power and network feeds, and announces scheduled maintenance in the client area before it takes place. Servers are unmanaged, so the operating system, firewall, applications and backups sit with the customer — and in practice those layers account for most reported downtime. There is no contractual uptime percentage on standard plans; that position is documented separately.

Node monitoring: continuous, so hardware problems surface before customers report them.
Facility: redundant power and network feeds at the datacenters used.
Maintenance: announced in the client area in advance.
Virtualization: KVM — resources allocated to your instance, not pooled.
Not claimed: automatic failover, storage-level redundancy, or a measured uptime figure.
Backups: not held by us. The customer takes their own.

Which Layer Belongs to Whom

Ten layers between the mains socket and your visitor's browser. We operate five of them. Most hosting pages describe only their own half, which leaves people believing they are covered for things nobody is covering.

Responsibility for each layer of a VPS deployment
Layer	Whose	What that means in practice
Datacenter power and cooling	VPS For Life	Redundant power and network feeds at the facilities we use.
Network to and from the facility	VPS For Life	Upstream connectivity, routing, and volumetric DDoS filtering.
Physical host node	VPS For Life	Hardware, and monitoring of it around the clock.
KVM hypervisor	VPS For Life	The virtualization layer your server runs on.
Your allocated CPU, RAM and disk	VPS For Life	Allocated to your instance rather than drawn from a shared pool.
Operating system and patching	You	Unmanaged by design. An unpatched kernel is not an infrastructure fault.
Firewall and network config	You	The most common cause of "the server is down" reports we receive.
Your applications and services	You	A web server that has run out of memory looks identical to an outage from outside.
Backups of your data	You	We hold no copy. This is the assumption that hurts people most when it turns out to be wrong.
Domain and DNS	You	An expired domain takes a perfectly healthy server offline from the visitor's point of view.

This is not a way of avoiding responsibility — it is the definition of an unmanaged server, and it is why these plans cost what they do. If you would rather not own five of those layers, say so before ordering and we will tell you honestly whether this is the right product for you.

Reliability Questions

Questions about reliability? Ask before you order.

We would rather talk you out of the wrong plan than take the order and refund it in a week. Replies usually within the hour.

Talk to Us Read the SLA Position