Skip to content

Guides

Knowledge base

How uptime and latency monitoring works, and how to use every part of UpAll — from your first monitor to monthly SLA reports.

Monitoring concepts

What is uptime monitoring?

What uptime monitoring measures, how automated checks work, and why IT service providers treat it as core infrastructure.

What is downtime?

What counts as downtime, the failures that cause it most often, planned versus unplanned outages, and what an hour of downtime really costs a small business.

The nines of availability

What 99%, 99.9%, and 99.99% availability allow in real downtime per month and year, what each extra nine costs, and which target actually fits an MSP client.

What is latency?

Latency is the time between request and answer. What the millisecond numbers mean, what users notice, and why an up-but-slow system is still a problem.

Latency vs bandwidth

Bandwidth is how wide the pipe is; latency is how long a round trip takes. Why more bandwidth doesn't make things faster, and which one monitoring measures.

Percentiles and p95, explained

Why average response times hide real problems, what p50, p95, and p99 mean, and why UpAll reports the 95th percentile on status pages and in reports.

What is an SLA?

What a service level agreement commits you to, how uptime targets and measurement windows work, and why an SLA needs continuous independent measurement.

SLA, SLO, and SLI

SLI, SLO, and SLA are three different tools: the measurement, the internal objective, and the external promise. How they fit together in day-to-day MSP work.

How HTTP checks work

What happens inside an HTTP check step by step, how status codes decide up or down, and UpAll's exact rules for redirects, timeouts, and content.

How ping checks work

What an ICMP echo probe actually tests, why a reachable host is not the same as a working service, and when ping is the right check type.

How TCP checks work

How a TCP check completes a handshake on a specific port to prove a service is listening, what that evidence leaves out, and common ports.

DNS and monitoring

How name resolution works, the ways DNS itself takes services down, and how a failed lookup shows up in your HTTP and ping check results.

SSL/TLS certificates explained

What a TLS certificate proves, how the chain of trust works, validity windows and 90-day automated renewals, and what browsers do when it breaks.

Certificate expiry risks

What actually breaks the moment a TLS certificate expires, why capable teams still miss renewals, and how a 30-day warning closes the gap.

Incidents and severity

What an incident is, why severity ladders like Info, Degraded, and Outage exist, and the lifecycle every incident follows from open to resolved.

False positives and flapping

Why one failed check is weak evidence of an outage, how consecutive-failure thresholds filter the noise, and how they calm flapping monitors.

Monitoring intervals

The trade-off behind check frequency — what 1-minute and 5-minute intervals can each detect, and the math that sets your time to alert.

Why MSPs monitor

The business case for monitoring as an MSP — finding problems before the client does, proving SLA compliance, and turning uptime into retention.

Getting started

Monitors

Monitor types and check types

How a monitor's type label differs from its check type in UpAll, and how to pick the right probe — Ping, HTTP, or TCP — for each target.

HTTP monitors

How HTTP monitors work in UpAll — the under-400 success rule, redirect handling, the fixed 10-second timeout, and automatic certificate watching.

Ping monitors

How Ping monitors check servers and network devices with ICMP, what reachability proves, and what to do when firewalls block ICMP traffic.

TCP port monitors

How TCP port monitors verify that a specific service is accepting connections — mail, databases, RDP — and what a successful connect proves.

Check intervals and thresholds

How the check interval and failures-before-incident settings decide detection time, with worked examples and tuning advice per criticality.

The degraded latency threshold

What the Degraded status means in UpAll, how the latency threshold works, its per-type maximums, and how to disable latency as a health signal.

Test connection

What the Test connection button does in UpAll — an immediate probe before saving, what it returns, its rate limit, and which targets it refuses.

Pausing monitors

How the Enabled toggle pauses a monitor in UpAll, what stops and what is kept, and how to use pausing during planned maintenance work.

Monitor statuses explained

What Up, Down, Degraded, Paused, and Unknown mean in UpAll, the exact conditions that trigger each status, and where the colors appear.

Reading monitor charts

A tour of the monitor page in UpAll — the time-window selector, summary tiles, uptime timeline, latency chart, and how retention shapes long views.

SSL certificate monitoring

How UpAll automatically watches TLS certificates on HTTPS monitors, the incidents it opens as expiry approaches, and where the warnings appear.

Site and workspace timezones

How UpAll resolves a monitor's timezone from site to workspace to default, what each zone controls, and why storage stays in UTC underneath.

Incidents & alerts

Status pages & client portal

Reports

Billing & account