SLA & Performance Overview
Track vendor uptime against SLA targets with automated breach detection and reporting.
PulsAPI's SLA and performance tracking gives you a clear picture of how your vendors are performing against their published service-level agreements.
SLA and performance features are available exclusively on the Pro plan. Upgrade to Pro to unlock uptime reports, breach detection, and data exports.
What SLA tracking does
Most cloud providers publish uptime guarantees — typically 99.9% or 99.95%. PulsAPI continuously monitors service statuses and calculates actual uptime so you can:
- Verify vendor claims — See whether your providers are meeting their published SLAs.
- Detect breaches — Get notified the moment a service drops below its SLA target within a given time window.
- Track trends — Review uptime, latency, and downtime over rolling time windows to spot degradation early.
- Generate evidence — Export detailed reports for internal reviews, vendor negotiations, or compliance audits.
Uptime calculation windows
PulsAPI calculates uptime percentages over three rolling time windows:
| Window | Description |
|---|---|
| 7 days | Short-term view. Useful for spotting recent incidents and their impact. |
| 30 days | Standard monthly view. Aligns with most vendor SLA billing cycles. |
| 90 days | Quarterly view. Best for trend analysis and long-term reliability assessments. |
Uptime is calculated as the percentage of time a service reported an operational status within the window. Partial outages (degraded performance, partial outage) are weighted proportionally.
Key metrics at a glance
For each tracked service, PulsAPI shows:
- Uptime % — The percentage of time the service was fully operational, calculated over rolling 7, 30, and 90-day windows.
- SLA target — The uptime percentage being tracked. PulsAPI resolves this automatically using a three-tier system: your custom target (if set), the vendor's published SLA (sourced from PulsAPI's curated vendor database), or a 99.9% system default.
- SLA source — Indicates whether the active target is Custom, Vendor, or Default, so you always know where the target comes from.
- Latency P50 / P95 / P99 — Median, 95th percentile, and 99th percentile response times. P95 gives a realistic measure of typical performance; P99 surfaces tail latency that affects your worst-case users.
- Downtime budget — Minutes of downtime remaining before the SLA target is breached for the current window.
- Breach status — Whether the service has breached its SLA target in the current window, with a full breach event history available.
SLA target resolution
PulsAPI automatically determines the SLA target for each service using a three-tier priority order:
| Priority | Source | Description |
|---|---|---|
| 1 (highest) | Custom | A target you have manually set for this service on your subscription. |
| 2 | Vendor | The provider's published SLA, sourced from PulsAPI's curated vendor SLA database covering 40+ providers. |
| 3 (fallback) | Default | 99.9% applied when no custom or vendor target is available. |
You can override the vendor or default target at any time by setting a custom SLA target on the service detail page or in the SLA report table.
Getting started
- Make sure you are on the Pro plan.
- Navigate to the SLA section from the sidebar.
- PulsAPI automatically tracks SLA data for all services on your board.
- Optionally set a custom SLA target per service to override the vendor or default — useful for enterprise contracts with negotiated uptime terms.
For a detailed walkthrough of the report table, see Uptime Reports. To learn about exporting data, see Exporting Data.