one-line definition
Uptime is the percentage of time your service is operational and accessible to users, typically measured over a monthly or annual period.
formula: Uptime % = (Total minutes in period − Minutes of downtime) ÷ Total minutes in period × 100. 99.9% uptime = ~43 minutes of downtime per month.
tl;dr
99.9% uptime sounds impressive until you realize it allows 43 minutes of downtime per month. For most indie SaaS products, that is the right target. Chasing 99.99% will eat your weekends and require infrastructure complexity that slows down shipping. Ship fast, monitor well, fix quickly.
Simple definition
Uptime measures how reliably your product is available. If your app was accessible for 43,157 out of 43,200 minutes in a 30-day month, your uptime is 99.9%. The remaining 43 minutes were downtime — your users saw errors, timeouts, or a blank page. For solo founders, uptime matters because unreliability drives churn faster than almost any missing feature. Users will tolerate a rough UI or limited features. They will not tolerate a tool that is down when they need it.
How to calculate it
Uptime % = (Total minutes − Downtime minutes) ÷ Total minutes × 100
The common uptime tiers and what they mean in practice:
| Uptime | Monthly downtime | Annual downtime |
|---|---|---|
| 99% | 7.3 hours | 3.65 days |
| 99.9% | 43 minutes | 8.76 hours |
| 99.95% | 22 minutes | 4.38 hours |
| 99.99% | 4.3 minutes | 52.6 minutes |
Monitor uptime with free tools: UptimeRobot (50 monitors free), Better Stack, or Checkly. Set up alerts for when your site goes down. Measure from multiple locations — your server might be up but unreachable from Europe due to a network issue.
Example
You run a client portal SaaS. Your Vercel-hosted frontend has 99.98% uptime — basically never goes down. But your API server on a $5 DigitalOcean droplet crashed twice last month during traffic spikes. Total downtime: 2 hours 15 minutes. That is 99.7% uptime. Three paying customers emailed asking if the service was reliable enough for their business. You add a simple health check, set up auto-restart on crash, and upgrade to a $12 droplet with more memory. Next month: zero crashes. The $7/month upgrade prevented losing $150/month in MRR from frustrated customers considering alternatives.
Related reading
Related terms
- Churn Rate
- NPS
- Session Duration
FAQ
What uptime should an indie SaaS target?+
99.9% (three nines) is the practical target — about 43 minutes of downtime per month. 99.99% (four nines) requires redundant infrastructure and on-call rotations that most solo builders can't sustain. Focus on 99.9% first. Your users will forgive 10 minutes of downtime once a month. They won't forgive 4 hours.
Do I need a status page?+
Yes, and it's trivially easy. Use a free tool like Instatus, Betteruptime, or a simple static page. A status page turns an outage from 'is this thing broken?' frustration into 'they know, they're fixing it' patience. It also reduces support tickets during incidents by 60-70%.