Operations / Reliability
How well it runs.
Uptime target 99.9%56.4%
Error budget used43625%
Mean time to recovery21m
Mean time between faults5d 18h
Response time by hour
00061218SunMonTueWedThuFriSat
FasterSlower31–140 ms
Response time distribution
- 0–50 ms73.0%35.5K
- 50–100 ms24.4%11.9K
- 100–200 ms2.3%1,113
- 200–500 ms0.2%100
- 500–1000 ms0.0%10
- 1000–2000 ms0.1%28
- 2000+ ms0.0%6
Certificates
| Host | Issuer | Days left |
|---|---|---|
| yaumalatsal.com | Let's Encrypt | 43 |
| pinglab.yaumalatsal.com | Let's Encrypt | 43 |
| baringan.yaumalatsal.com | Let's Encrypt | 43 |
| hotwork.yaumalatsal.com | Let's Encrypt | 43 |
| bisa.yaumalatsal.com | Let's Encrypt | 43 |
| simaksi.yaumalatsal.com | Let's Encrypt | 44 |
All applications
| Application | Uptime | Budget used | Faults | MTTR |
|---|---|---|---|---|
| BISa LMS | 56.3% | 43686% | 15 | 4m |
| SIMAKSI | 56.4% | 43638% | 3 | 24m |
| Baringan Inventory | 56.4% | 43625% | 3 | 21m |
| PingLab LMS | 99.82% | 181% | 82 | 1m |
| Hot Work Permit | 99.986% | 14% | 2 | 24m |
| Portfolio & Console | 99.988% | 12% | 5 | 9m |
The console measures the downtime across the period it watched, not across the whole window. A new application has a short history, so the page says how much of the window each figure covers. The console calculates the downtime from the health checks, not from the fault records. The checks are evenly spaced, so the ratio of bad checks is a fair estimate of the ratio of bad time. A fault record starts and ends on a check, so it would round each fault up to the check interval.