RepublicNodes Uptime and SLA

"99.99% uptime" means nothing if nobody explains how it's measured. Here's how RepublicNodes actually approaches it.

What Our SLA Covers

Our published SLA covers the infrastructure we're responsible for: the physical/virtual host, network path, and power to the node your service runs on. It does not cover problems inside your own server that you caused yourself — a misconfigured firewall rule, a crashed plugin, or software you installed that has a bug.

How We Actually Monitor

• Nodes and services are monitored continuously, not checked manually once a day
• Bandwidth and resource usage are sampled on a schedule (our VPS platform samples usage every few minutes, specifically so throttling or limits kick in based on real data, not guesswork)
• Failed provisioning attempts are logged with the exact failure reason, so our team can retry or fix the real cause instead of guessing

What Happens When Something Actually Breaks

If a node has a genuine hardware or network failure, our priority order is: get affected services back online first, then communicate what happened, then apply any SLA credit the incident qualifies for per our published terms. We'd rather over-communicate during an incident than go quiet and let you wonder.

Why This Matters More Than the Number Itself

A host that can explain how it monitors and responds to failures is giving you more real information than any single uptime percentage can. The number is a summary; the process behind it is what actually protects you.

Read our full current commitment on the SLA page.