Hosting
Your host's uptime guarantee
A monitor on your own site measures the hosting SLA where your visitors are.
SLA monitoring
SLA monitoring: independent uptime reports and the credit you are owed
HostTracker measures a service's uptime from 300+ checkpoints in 158 cities, outside the provider's network, and keeps the record: uptime reports for every period, a 12-month SLA history on your status page, and each outage with the locations that confirmed it.
30-day trial · 100 monitors · 1-minute checks · no credit card
- Trusted since 2004
- 500,000+ websites monitored
- 300+ checkpoints worldwide
How a failed check becomes a confirmed outage in the SLA record
Measured from outsideChecks from 300+ checkpoints in 158 cities, not from the provider's own network or dashboard.
Every outage confirmedA failed check is re-run from up to seven other locations, and the majority decides whether it counts.
A record you can hand overUptime reports, a 12-month SLA history with a CSV export, and each incident with its timestamps.
What SLA monitoring measures, and why the provider's dashboard is not enough
Checking an SLA takes two numbers: the downtime the promise allows, and the downtime that really happened, measured by someone other than the provider.
THE TWO NUMBERS AN SLA CLAIM NEEDS
allowed period x (100 - SLA %) / 100 99.9% of a month = 43m 50s measured up / (measured - maintenance down) from 300+ checkpoints, confirmed
Independent of the provider
Checks reach the service the way your visitors and API clients do, so the figure does not rest on what the provider reports about itself.
Confirmed, not a single sample
A failed check is re-run from other locations before it counts, so one checkpoint's routing problem does not become downtime.
Kept, reported and exportable
Uptime per period by email, a monthly SLA history on a status page and the full incident list through the API. Turn it into a credit
SLA reporting
Uptime reports for every SLA period
The same measurements, read four ways: by email, in the dashboard, per monitor and as a document to attach to a claim.
Scheduled SLA reports by email
Daily, weekly, monthly, quarterly or yearly, as your plan allows: each subscribed monitor's uptime and downtime for the period and its total uptime since monitoring began. Weekly and monthly reports break down by day, quarterly by week, yearly by month.
The uptime report in your dashboard
Every monitor's uptime, outages and timeline, from the last 6 hours to 90 days, this or last month, or a custom range, with a daily trend against a 99.9% line.
Per-monitor statistics
Uptime for the last 7, 30 and 365 days and a custom range side by side, and whether the last 365 days stayed above 99.9%.
A report to download
PDF, CSV or XML for one monitor or a selection, over 7, 30 or 90 days or your own dates: statistics with the checks behind them, outages with start, end and duration, and incidents with the error each location reported.
Which report frequencies each plan includes is in the pricing table below.
Your own SLA
An SLA report your customers can download
If you promise uptime to customers, a status page shows the promise next to the measurement.
Setting the target. In the status page settings, under SLA and analytics, enter your SLA target, such as 99.9. The page shows it beside the overall uptime, with a 30-day error budget: the downtime allowed and the downtime used.
The monthly SLA history. Visitors open a table of the last 12 calendar months, each with its uptime and whether it met the target, and export it as CSV: Month, Uptime %, SLA target %, Within target. A month's figure is that of the page's weakest monitored service; paused and third-party rows are left out. The history is also public as JSON at /status/{page}/sla-export.json.
Limits. Never shown on a password-protected page. The SLA target is part of Complete, Webmaster, Business and Enterprise. Downtime inside a maintenance window shown on the page is left out, and the owner may count outages shorter than at most 10 minutes as up on the page (off by default; reports and the API are unaffected).
Evidence
Timestamped SLA evidence through the API
Every figure above is reachable from code, with the outages behind it. Times are Unix seconds; a token needs the monitor:read scope.
MONTHLY SLA FIGURES AND THE OUTAGES BEHIND THEM
GET /monitor/result/summary ?monitor=<id>&from=<unix>&to=<unix> &bucket=month each row uptimePercent slaTarget slaMet errorBudgetSecRemaining upSec downSec totalSec maintenance GET /monitor/incident?monitor=<id> &expand=recheck each row detectedBy confirmations[] {error, locations[]}
Uptime per month, scored against the SLA
GET /monitor/result/summary returns uptime for any window, whole or by hour, day, week or calendar month, scored against the monitor's own SLA target or a sla= value: slaMet and the error budget left.
The figure, auditable
Rows carry up, down and measured seconds and the maintenance share behind uptimePercent.
Each outage, with its witnesses
GET /monitor/incident lists every outage; expand=recheck adds which location saw it first and which confirmed it, with each error. Signed webhooks push incident.opened and incident.closed as they happen.
API access is included in Complete, Business and Enterprise. On plans with the full log, GET /monitor/incident/{id}/check also lists every failing check inside an incident. More in the monitoring API.
Method
Why the uptime figure holds up in a dispute
A provider will question any number that differs from its own. The record already carries the answers.
- Measured from outside. Checks run from 300+ checkpoints in 158 cities, in the regions you pick per monitor.
- Every outage confirmed. A check that disagrees with the confirmed state is re-run 10 seconds later from up to seven other locations, 2 seconds apart. The majority of countable results decides, a tie keeps the previous state, and recovery is confirmed the same way.
- Fine-grained. Checks run as often as every minute on the plans that allow it; an outage shorter than the interval can fall between two checks.
- Maintenance on your terms. A maintenance window can keep its downtime out of the uptime statistics; uptime inside the window still counts.
- Checkable. The API publishes the seconds behind every percentage: up, down, measured and the maintenance share.
More on multi-location availability monitoring and on what an uptime check counts as down.
SLA credit
SLA credit calculator and the downtime each SLA allows
An SLA credit is the share of the fee a provider returns when it misses the commitment.
allowed downtime = period length x (100 - SLA %) / 100
The table uses a 30.44-day month (2,630,016 seconds) and a 365.25-day year (31,557,600 seconds), the averages SLA tables use, rounded down to the second.
| SLA | Downtime per day | Per month | Per year |
|---|---|---|---|
| 99% | 14m 24s | 7h 18m 20s | 3d 15h 39m |
| 99.5% | 7m 12s | 3h 39m 10s | 1d 19h 49m |
| 99.9% | 1m 26s | 43m 50s | 8h 45m 57s |
| 99.95% | 43s | 21m 55s | 4h 22m 58s |
| 99.99% | 8s | 4m 23s | 52m 35s |
Worked example. A 99.9% monthly SLA and 1 hour 30 minutes of measured downtime. The allowance is 43 minutes 50 seconds, the actual uptime is 99.7947%, so the SLA is missed by 46 minutes 9 seconds. Under the example schedule of 10% credit below 99.9%, 25% below 99% and 50% below 95%, that is 10% of the monthly fee: 20.00 on 200.00. Check your contract's schedule.
Uptime to downtime and back for any target: the uptime and SLA calculator.
Who monitors an SLA
Six commitments worth measuring yourself
Each is a percentage in a contract and a credit nobody pays unless claimed.
SaaS
A vendor your business runs on
Monitor the vendor's login page or API endpoint and keep every outage on record.
APIs
A payment or data API
An API monitor asserts the response, so a wrong answer counts as an outage too.
Your SLA
The promise you make customers
A status page with an SLA target lets customers check the history themselves.
Agency
Client sites under a support contract
A monthly uptime report per client, sent by email without anyone compiling it.
Renewal
The vendor review before renewal
A yearly report, by month, shows the whole contract term.
Pricing
Plans for SLA monitoring and reporting
Read from the live plan catalog, the same numbers as the pricing page. Prices are per month on monthly billing.
| Plan | Price | Monitors | Shortest interval | Uptime reports | Status page SLA target | API access |
|---|---|---|---|---|---|---|
| Complete | $9 a month | 1 website, all monitoring types | 1 minute | Daily to yearly | Included | Included |
| Webmaster | $14 a month | 10 | 5 minutes | Daily to yearly | Included | Not included |
| Business | $29 a month | 25 | 1 minute | Daily to yearly | Included | Included |
| Enterprise | $99 a month | 150 | 1 minute | Daily to yearly | Included | Included |
Complete covers one website: all of its monitors belong to that site and its subdomains (fair use).
- 30-day money-back on your first payment
- Your price stays while your subscription stays active
Other billing periods and plan sizes are on the pricing page. The 30-day trial includes 100 monitors and 1-minute checks, plus the status page SLA target and API access.
Already monitoring with another service?
The importer in the New monitor panel reads exports from UptimeRobot, Pingdom, StatusCake, Better Stack, Site24x7 and Uptime Kuma. It converts HTTP, keyword, ping and port monitors and lists anything it cannot convert, with the reason. A plain list of URLs, one per line, works too.
Import your monitorsStart the 30-day trial first and confirm your email; the importer opens once the address is confirmed. HostTracker is not affiliated with any company named here; product names are trademarks of their owners.
Every layer of your stack, monitored
Websites, servers, APIs, certificates. One check type per page, the same locations, alerts and reports behind all of them.
Trusted by teams at
The full guide
Monitoring an SLA and claiming the credit
Every chapter opens in place, so the page stays short.
SLA, SLO and SLI in one paragraph
The SLI is what is measured, such as the share of successful checks; the SLO is the internal goal for it; the SLA is the contract's promise, with credits when missed. SLA monitoring measures the SLI independently against the SLA.
What counts as downtime in an SLA
Contracts differ; common practice, not rules: announced maintenance is usually excluded, short blips may be ignored, slow responses past a threshold can count as downtime, and causes on your side are excluded.
Claiming an SLA credit
- Find the period, exclusions, credit schedule and claim deadline in the contract.
- Take the period's uptime and outage list from the report or the API.
- Work out the credit with the calculator above.
- Claim before the deadline, outage list attached.
Setting up SLA monitoring
- Monitor the URL or endpoint the SLA covers, at your plan's shortest interval.
- Pick locations near the users the SLA is about.
- Add maintenance windows for work the contract excludes.
- Subscribe an email contact to monthly and yearly reports.
- For your own SLA, set the target on a status page.
Key takeaways
Key takeaways
- HostTracker measures SLA uptime from 300+ checkpoints in 158 cities, and a failed check is re-run 10 seconds later from up to seven other locations before it counts as downtime.
- Scheduled email reports give each monitor's uptime and downtime daily, weekly, monthly, quarterly or yearly, depending on the plan, plus total uptime since monitoring began.
- A status page with an SLA target shows a 30-day error budget and a 12-month SLA history that visitors can export as CSV.
- GET /monitor/result/summary returns uptime by calendar month with slaMet and the remaining error budget, and GET /monitor/incident lists each outage with the locations that confirmed it.
- A 99.9% SLA allows 43 minutes 50 seconds of downtime in an average month and 8 hours 45 minutes 57 seconds in a year.
Frequently Asked Questions
Measuring a service's availability independently against the uptime percentage its service level agreement promises, and keeping a record of every outage. HostTracker checks from 300+ checkpoints in 158 cities, outside the provider's network.
The uptime percentage for a period, the downtime behind it and the target. HostTracker's email reports give each monitor's uptime and downtime per day, week, month, quarter or year; a status page with an SLA target adds a 12-month history, exportable as CSV.
Compare the measured uptime with the commitment for the contract's period, then find the matching tier of the credit schedule. Example: a 99.9% monthly SLA allows 43 minutes 50 seconds of downtime; 1 hour 30 minutes of downtime gives 99.7947% uptime, so a schedule paying 10% below 99.9% returns 10% of the monthly fee. The calculator on this page does it for your figures.
43 minutes 50 seconds in an average month of 30.44 days and 8 hours 45 minutes 57 seconds in a year of 365.25 days. At 99.99% the monthly allowance is 4 minutes 23 seconds.
Not if the maintenance window is set to keep its downtime out of the statistics: downtime inside it is then left out, while uptime inside it still counts. A status page leaves out downtime inside the maintenance windows it shows.
Yes, on plans with API access (Complete, Business and Enterprise). GET /monitor/result/summary returns uptime for any window, by calendar month if you ask, with slaMet and the error budget left against the monitor's SLA target. GET /monitor/incident with expand=recheck lists every outage with the locations that confirmed it.
By default, a failed check is re-run 10 seconds later from up to seven other locations, 2 seconds apart, and the majority of countable results decides; a tie keeps the previous state. A single checkpoint's network problem does not become downtime in the record.
Up to 100 monitors with 1-minute checks for 30 days, plus the status page SLA target and API access, and no credit card. If you then choose a plan: 30-day money-back on your first payment; your price stays while your subscription stays active.
30-day trial, 100 monitors, no credit card
Start the SLA record before the next outage
Add the service, pick the locations and subscribe to the monthly report. The record starts with the first check, from 300+ checkpoints in 158 cities.
- Trusted since 2004
- 500,000+ websites monitored
- 300+ checkpoints worldwide
Part of HostTracker's website monitoring software.
30-day trial - no card needed
Start the 30-day trial