Uptime Reports
Read and interpret SLA report tables — uptime, latency, downtime budgets, and breach alerts.
Uptime Reports
The uptime report table is the central view for SLA tracking in PulsAPI. It shows real-time and historical performance data for every service you monitor.
Uptime reports are a Pro plan feature. Upgrade to Pro to access SLA tracking.
Accessing the report
- Navigate to the SLA section from the sidebar.
- The report table loads with all your monitored services.
- Use the time window selector at the top to switch between 7-day, 30-day, and 90-day views.
Reading the report table
Each row in the table represents a single service or component. The columns are:
| Column | Description |
|---|---|
| Service | The name of the monitored service (e.g., "AWS EC2", "GitHub Actions"). |
| Status | Current real-time status (Operational, Degraded, Partial Outage, Major Outage). |
| Uptime % | Percentage of time the service was fully operational within the selected window. |
| SLA Target | The vendor's published SLA target you have configured (e.g., 99.9%). |
| Latency P95 | 95th percentile response time in milliseconds for the selected window. |
| Downtime Budget | Minutes of downtime remaining before the SLA target is breached. |
| Breach | Indicates whether the SLA target has been breached in the current window. |
Understanding uptime %
Uptime is calculated as:
- Operational status counts as full uptime.
- Degraded performance counts as partial uptime (weighted at 50%).
- Partial outage and major outage count as downtime.
For example, with a 30-day window (43,200 minutes), a service that experienced 45 minutes of major outage would show:
Understanding downtime budget
The downtime budget tells you how much downtime you can still tolerate before the SLA is breached. It is calculated based on your configured SLA target and the selected time window.
For a 99.9% SLA target over 30 days:
If 20 minutes of downtime have already occurred, the remaining budget is 23.2 minutes.
When the budget reaches zero, the SLA is marked as breached.
Latency P95
The P95 latency metric shows the response time at the 95th percentile — meaning 95% of status checks completed faster than this value. This gives a more realistic performance picture than averages, which can hide spikes.
Breach detection and alerts
PulsAPI automatically detects when a service's uptime drops below its configured SLA target.
When a breach occurs:
- The service row in the report table is highlighted with a breach indicator.
- If you have alerts configured (Slack, Discord, email, or webhook), a breach notification is sent immediately.
- The breach remains flagged until the time window rolls forward and uptime recovers above the target.
Setting SLA targets
- In the SLA report table, click the SLA Target cell for a service.
- Enter the target percentage (e.g.,
99.95). - Press Enter or click Save.
PulsAPI begins tracking breaches against this target immediately.
If you do not set an SLA target for a service, PulsAPI still tracks uptime and latency — but breach detection and downtime budget calculations are disabled for that service.
Filtering and sorting
- Filter by status — Show only services that are currently experiencing issues.
- Filter by breach — Show only services that have breached their SLA target.
- Sort by any column — Click a column header to sort ascending or descending.
- Search — Use the search bar to find a specific service by name.