Understanding Response Time Metrics¶
Learn how to interpret the response time data shown on the GoZen Host Status Page.
What is Response Time?¶
Response time (also called latency or ping) measures how long it takes for a service to respond to a request. It's measured in milliseconds (ms).
| Response Time | Quality |
|---|---|
| < 100ms | Excellent |
| 100-300ms | Good |
| 300-500ms | Acceptable |
| 500-1000ms | Slow |
| > 1000ms | Very Slow |
Metrics Explained¶
Current Response Time¶
The most recent ping measurement. This tells you how the service is performing right now.
Example
42ms means the service responded in 42 milliseconds.
Average Response (24h)¶
The average response time over the last 24 hours. This smooths out temporary spikes and gives you a better picture of typical performance.
Example
65ms avg means responses averaged 65ms over the past day.
P95 Latency¶
The 95th percentile response time. This means 95% of requests were faster than this value, and only 5% were slower.
Why P95 Matters
P95 filters out occasional outliers and shows you the "worst case" for most users. If P95 is 150ms, that means even your slowest typical requests complete in under 150ms.
Example
P95: 120ms means 95% of requests completed in 120ms or less.
Uptime Percentage¶
The percentage of time the service was operational:
| Uptime | Meaning | Downtime per month |
|---|---|---|
| 100% | Perfect availability | 0 minutes |
| 99.99% | Excellent | ~4 minutes |
| 99.9% | Very Good | ~43 minutes |
| 99.5% | Good | ~3.6 hours |
| 99% | Acceptable | ~7.3 hours |
The Response Time Sparkline¶
The small chart displayed next to each service shows the response time trend.
Reading the Chart¶
- Downward slope = Response times are improving (faster)
- Upward slope = Response times are degrading (slower)
- Flat line = Response times are stable
- Spiky line = Response times are variable
What a Good Sparkline Looks Like¶
| Pattern | Meaning |
|---|---|
| Flat or gently sloping downward | Healthy |
| Gradual upward trend or spikes | Concerning |
| Sharp upward spike, sustained high | Problem |
Factors Affecting Response Time¶
Response times can vary based on:
- Your Location – Physical distance to our data centers
- Network Conditions – Internet routing and congestion
- Service Load – How busy the service is
- Time of Day – Peak usage hours may show higher latency
- Maintenance – Scheduled work may temporarily affect performance
What to Do About Slow Response Times¶
- Check if there's an active incident on the status page
- Wait a few minutes and check again
- Contact support if it persists
- Check your own internet connection
- Try from a different network
- The issue may be between your ISP and our network
- We're already aware and working on it
- Subscribe to alerts to get notified when it's resolved
Next Steps¶
-
How we communicate planned downtime
-
Understanding incident lifecycle