Every budget VPS provider advertises “99.9% uptime.” Almost none of them show you the raw probe data behind that number, and the difference between a marketing figure and a measured one is frequently 30–90 minutes of downtime per month. The good news: you can audit the claim yourself with free tools in under an hour of setup, and you will have hard evidence the next time you need to justify a credit request or a migration.
What 99.9% Actually Means in Minutes
Uptime percentages sound similar but diverge sharply once you convert them to time. A provider quoting 99.9% is allowing 43 minutes of downtime per month; 99.99% allows just 4.3 minutes. Budget hosts often advertise 99.9% in marketing while the SLA contract specifies a lower figure with a credit schedule attached. Read both.
| Claimed uptime | Downtime / month | Downtime / year | Typical budget-plan reality |
|---|---|---|---|
| 99% | 7h 18m | 3.65 days | Very weak — avoid |
| 99.5% | 3h 39m | 1.83 days | Occasional cheap hosts |
| 99.9% | 43m 12s | 8.76 hours | Common advertised figure |
| 99.95% | 21m 36s | 4.38 hours | Strong for budget tier |
| 99.99% | 4m 19s | 52.6 min | Rare below $20/mo |
If a provider will not name a specific number in the terms of service, treat the marketing claim as 99.9% at best. Our breakdown of what hosting SLA credits actually cover explains why the credit schedule matters as much as the percentage.
The Free Tooling Stack for an Uptime Audit
You do not need a paid monitoring service to build a credible record. Three free layers give you overlapping, independently verifiable evidence.
- External HTTP checks. Uptime Kuma, UptimeRobot’s free tier (50 monitors, 5-minute intervals), or Better Stack’s free plan each probe your site from multiple regions and log HTTP status codes.
- Server-side metrics. Netdata, Prometheus with node_exporter, or a simple cron script writing load, memory, and reachability to a log — this distinguishes a network outage from an application crash.
- Independent third-party view. A status-page aggregator or a second monitor on a different host and network so a single provider outage does not blind you.
The critical design decision is running at least one probe from outside the provider’s own network. A monitor on the same VPS that goes down with it proves nothing. Five-minute intervals are the practical minimum; one-minute intervals are better for claiming credits, since most SLAs measure in minutes and you want evidence granular enough to match.
Building a Baseline Before You Trust Any Number
Run monitoring for a full 30 days before drawing conclusions. Short windows are dominated by your own reboots, deploys, and DNS changes. Tag every planned maintenance window in the tool so scheduled work is excluded from the calculation the same way a provider would exclude it.
| Metric to log | How to capture it | What it proves |
|---|---|---|
| HTTP 2xx/5xx ratio | External probe, 1–5 min | Real user-facing availability |
| Response time p95 | Same probe | Latency, not just reachability |
| Packet loss / ping | External ICMP or TCP probe | Network-layer health |
| Node uptime counter | node_exporter or /proc/uptime | Unplanned reboots |
| Your own DNS resolution | Local resolver query log | Distinguishes DNS outages |
Response time deserves equal billing with availability. A provider can be technically up while serving pages in four seconds, and your visitors experience that as downtime. Logging p95 latency alongside status codes turns “the site felt slow this week” into a defensible chart.
Turning Probe Data into a Claim
Most SLAs require you to open a ticket within a defined window — commonly 7–14 days — of the incident, and to supply evidence. Credits are usually calculated as a percentage of the monthly fee, scaled to how far below the guarantee the measured uptime fell.
| Measured monthly uptime | Typical credit | Evidence needed |
|---|---|---|
| 99.9% (at guarantee) | 0% | None |
| 99.0–99.89% | 10–25% of monthly fee | Probe logs showing the gap |
| 95.0–98.99% | 25–50% of monthly fee | Probe logs + ticket timestamps |
| Below 95% | 50–100% of monthly fee | Probe logs + escalation record |
Credits are almost always applied to future invoices, never refunded as cash, and almost never cover consequential loss such as lost sales. That is exactly why measuring matters more than claiming: the data tells you whether the provider is worth keeping, independent of whether the credit is worth chasing.
A 30-Day Audit Workflow
- Day 1: Set up an external probe at 1–5 minute intervals from at least two regions, plus a status-code and latency alert.
- Day 1: Add server-side node monitoring and confirm it reports independently of the external probe.
- Days 2–29: Log incidents, tag planned maintenance, and note every ticket opened against an outage.
- Day 30: Calculate real uptime as (total minutes − unplanned downtime) ÷ total minutes.
- Day 30: Compare the measured figure against both the marketing claim and the contractual SLA.
- Day 31: If measured uptime is more than 0.1% below the contract, file the credit request with the logs attached.
Run this audit once and you will know more about your host than the sales page ever told you. If the numbers come back strong, the provider has earned the renewal. If they come back weak, you now have a documented reason to move — and a measured baseline to compare the next host against. Review our budget VPS picks for providers with transparent SLA terms, and check our notes on provider shutdown and data protection before committing to a long prepaid term.
Related Articles：
How to Evaluate a Cheap VPS Host in 2026: 7 Questions with Real Pricing Examples
InterServer $3/Month VPS Review: Is It Really the Best Value for 2026?
Cloudways vs InterServer for Budget VPS: Which $10-$50 Plan Delivers Better Value in 2026?
Budget VPS Providers Compared: Real Specs, Renewal Pricing, and Uptime Data for 2026
