Interpreting Response Time Charts and Check History
Read monitor charts to identify performance trends and incidents.
Response Time Chart
The chart shows response time over time. Look for:
- Baseline — your endpoint's normal response time (e.g., 50–100ms)
- Spikes — sudden increases that may indicate load issues or slow dependencies
- Trends — gradual increases that suggest a growing performance problem
- Gaps — periods where the monitor was paused or the endpoint was unreachable
Check History Table
Below the chart, the check history shows individual results:
| Time | Status | Response Time | Status Code |
|---|---|---|---|
| 14:03:00 | UP | 45ms | 200 |
| 14:04:00 | UP | 52ms | 200 |
| 14:05:00 | DOWN | 30000ms | Timeout |
| 14:06:00 | UP | 48ms | 200 |
Common Patterns
Single spike then recovery — likely a transient issue (garbage collection, cold start, network hiccup).
Sustained high response time — check your database queries, external API dependencies, or server resources.
Regular spikes at the same time — often caused by cron jobs or scheduled tasks competing for resources.
Gradual increase over days — possible memory leak, growing database without proper indexing, or increasing traffic without scaling.