- Home
- Monitoring
- SLA monitoring
SLA monitoring: measure the uptime you promised, from the outside
Uptime for each monitor is computed from confirmed incidents, with planned maintenance left out. It lands on a status page and in a monthly report, so the number you quote to a client is one you can show.
- 30 monitors free
- No credit card
- Failures confirmed from other regions
- Uptime so far
- 99.98%
- Allowed downtime
- 43 min 12 s
- Used
- 9 min 40 s
- Incidents
- 1
Illustrative example
Check it now, in your browser
No account. SLA monitoring: type a target and see roughly what it looks at. Nothing you type is stored.
Pure arithmetic in your browser; nothing is sent. A saved monitor fills the “so far” number from confirmed incidents.
What a sla monitor looks at
Uptime from confirmed incidents
Downtime is the time between an incident opening and recovering. An incident opens only when the confirming regions agree, so one bad route does not eat your allowance.
Maintenance excluded
Work inside a maintenance window suppresses alerts and is left out of the uptime figure, which matches how most contracts are written.
Shown where clients look
The figure appears on the status page and in the monthly report: a plain summary e-mail from Starter, a branded PDF from Pro, one per client workspace on Agency.
A budget, not just a percentage
The calculator below turns 99.9% into minutes for a month or a year, and tells you whether the downtime so far still fits.
SLA monitoring: what an alert looks like
The same event arrives as an e-mail, a Telegram message or a Slack card. This is the wording the channels send; the host, times and numbers are made up.
shop.clienta.com
shop.clienta.com · 503 Service Unavailable · confirmed from Amsterdam (AMS), London (LON)
| Error | 503 Service Unavailable |
|---|---|
| Confirmed by | Amsterdam (AMS), London (LON) |
| Since | 14:02:11 UTC |
| Target | shop.clienta.com |
| Next step | Check the server / hosting panel. Acknowledge so the team knows you are on it. |
AcknowledgeOpen incident
<title>503 Service Temporarily Unavailable</title>
Tenium · checked from Amsterdam · 14:02 UTC
Tenium alerts
🔴 DOWN · shop.clienta.com · 503 Service Unavailable · confirmed from Amsterdam (AMS), London (LON)
reply /ack or acknowledge · open incident
TTenium APP 2:02 PM
DOWN · shop.clienta.com
shop.clienta.com · 503 Service Unavailable · confirmed from Amsterdam (AMS), London (LON)
- Error: 503 Service Unavailable
- Confirmed by: Amsterdam (AMS), London (LON)
- Target: shop.clienta.com
AcknowledgeOpen incident
Check the server / hosting panel. Acknowledge so the team knows you are on it. · checked from Amsterdam
SLA monitoring: e-mail, Discord and Google Chat work on every plan; Slack, Telegram, Teams and Mattermost start on Starter. There are no SMS or voice-call alerts.
A month of downtime against the allowance
Confirmed incidents add up through the month. The line is the allowance your SLA target gives you.
How fast you find out
Pick a plan to see its check interval and how long a failure takes to reach you, including the confirmation round.
SLA monitoring: a failure lands at a random moment between two checks, so on average you wait half an interval, and the worst case is a whole interval plus the confirmation window. A single failing region is not enough: all two regions must agree before an incident opens. The other regions are asked straight away, and we allow up to 60 seconds for the answers.
How to set up sla monitoring in 30 seconds
Monitor what the contract names
Add a website or API monitor for each service the SLA covers. Pick the URL a customer would use, not an internal health page.
Schedule planned work as a window
Create a maintenance window for each planned deploy or migration so it neither alerts anyone nor counts as downtime.
Publish a status page
Put the monitors on a status page so the uptime figure and incident history are visible without a login.
Let the report go out
Reports are sent on the 1st for the previous month. Compare the figure with the target in your contract.
What each error means
This is the text an incident shows in its Error line, the usual cause, and the first thing to look at.
COUNTSA confirmed outage counts
Time from the incident opening to its recovery is downtime. It opens only after the confirming regions agree.
Shown as: A confirmed outage counts
BLIPA one-region blip does not count
A failure that other regions do not confirm never opens an incident, so a bad route does not eat your allowance.
Shown as: A one-region blip does not count
WINDOWMaintenance windows are excluded
Planned work inside a maintenance window suppresses alerts and is left out of the uptime figure.
Shown as: Maintenance windows are excluded
GAPYour host’s number can differ
A host measures from inside its own network and per server. Tenium measures what a visitor outside sees, so the two rarely match.
Shown as: Your host’s number can differ
SLA monitoring by plan
| Free $0/mo | Starter $7/mo | Pro $29/mo | Agency $59/mo | |
|---|---|---|---|---|
| Available | ✓ | ✓ | ✓ | ✓ |
| Monitors | 30 | 100 | 300 | 1000 |
| Fastest interval | 5 min | 1 min | 30 s | 30 s |
| Regions | 1 | 2 | 2 | 2 |
| Custom headers | — | — | ✓ | ✓ |
| Response-time alerts | — | — | ✓ | ✓ |
| Escalation to a second contact | — | — | ✓ | ✓ |
| Status pages | 1 | 3 | 10 | Unlimited |
Other monitor types
What counts as downtime in the number we report
Tenium measures uptime as the share of a period not covered by a confirmed incident. An incident opens only when the confirming regions agree that the check is failing, and it closes when they agree it has recovered. A single region that cannot reach you, a flaky route, or one failed request that the next check disproves never opens an incident and therefore never costs you any of your allowance.
Two things are deliberately outside the number. Time inside a maintenance window is excluded, because most contracts carve out planned work. And the figure is an outside view: it says what a visitor would have seen, not what your host's internal dashboard says about its servers. The two rarely agree, and when a contract is signed on the host's number, quote that one in the contract and use ours as the independent check.
From percentage to minutes
Percentages flatter. Over a 30-day month, 99% allows 7.2 hours of downtime, 99.9% allows 43.2 minutes, 99.95% allows 21.6 minutes and 99.99% allows 4.3 minutes. Each extra nine divides the allowance by ten, while the effort to meet it grows much faster. The calculator on this page turns your target into minutes and compares it with the downtime so far; the full table is in the uptime calculator, which also has a mean time to repair mode.
If one component promises 99.9% and another 99.95%, a page that needs both is available about 99.85% of the time. Promise the client less than your best component, and keep the arithmetic where they can see it.
Showing the number to the client
The uptime figure appears on the status page and in the monthly report. Starter ($7) sends a plain summary e-mail to the account owner. Pro ($29) adds one branded PDF report, and Agency ($59) sends an own-brand report for every client workspace on the 1st. See client reports.
Tenium does not calculate service credits, does not file claims with your host, and does not promise that its own measurements are legally binding. It is the evidence layer: timestamps, confirming regions and response excerpts for every incident, in a form you can attach to an e-mail.
SLA monitoring questions
Does a slow response count as downtime?
A slow response opens a degraded incident on Pro and Agency when the slow threshold is exceeded. Whether that counts toward your SLA is a contract question; the incident list gives degraded incidents their own severity, so you can tell slowness from outages.
Can I set an SLA target inside Tenium?
The calculator on this page does the arithmetic, and the report shows the measured figure. There is no automatic breach alert today, so compare the report with your target on the 1st.
Are maintenance windows really excluded?
Yes. Alerts are suppressed during a window and the period is excluded from reported uptime. Schedule windows before the work starts.
How long is the history kept?
Free keeps 90 days, Starter and Pro 365 days, and Agency 730 days.
Start sla monitoring free
30 monitors on the Free plan, no card needed, with failures confirmed from other regions (2 regions live today). Upgrade when the client list grows.