Practical guide

Read an uptime percentage without losing the context

Last materially reviewed 2026-09-26

Quick answerRead the denominator, exclusions and monitored path before treating a percentage as service reliability.
What to know

Name what was measured

An uptime percentage belongs to a particular monitor and reporting period. It does not automatically describe every page, visitor region, logged-in workflow or external supplier. Start with the exact address and check type. If a report combines multiple monitors, find out how the combined figure is calculated before comparing it with a single endpoint. Similar-looking percentages can refer to substantially different observations.

What to know

Understand the arithmetic

For a simple illustration, 60 minutes unavailable in a 30-day period of 43,200 minutes yields roughly 99.861 percent availability when nothing is excluded. This is arithmetic, not an UptimeRobot reporting specification or a service promise. Actual monitoring intervals, classification rules and maintenance treatment affect how a provider reports incidents. Consult the report definition rather than assuming that a familiar formula explains every displayed number.

What to know

Check excluded time

Scheduled maintenance may be treated differently from unplanned failure. A paused or newly created monitor may cover less than the whole calendar period. Note these limits when sharing a report with a client or colleague. Do not remove inconvenient incidents to improve a headline figure. If a contract defines a service level, its measurement rules and remedy are separate from a convenient dashboard statistic.

What to know

Pair the figure with the task

Add the incident summary that a percentage cannot express: which action failed, who was notified and whether recovery was checked. A short outage at an important time can matter more than its share of a month suggests, but its financial effect is not known without evidence. Use the percentage as one observation in a service discussion, not as proof of customer satisfaction, revenue protected or future reliability. Keep the monitored path visible beside the percentage.

Continue when useful

Next: Choose a useful monitoring review window

Compare like periods and operating conditions before changing the monitoring plan.

Open Choose a useful monitoring review window →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. UptimeRobot: website monitoring — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26
  2. UptimeRobot: status pages — Merchant documentation · uptimerobot.com · Merchant-controlled · checked 2026-09-26