Features /
Platform
Response time monitoring beyond the average
A service can be up and still be slow. FrogStatus records how long each check took and shows it as percentiles and Apdex, so you see the slow tail that an average hides.
14 days, no commitment. Cancel any time.
How it works
- 1
Every check is timed
The response time is stored with each check result.
- 2
Read the distribution
See the median and the slowest requests (p95, p99) instead of one average.
- 3
Set your threshold
Choose what “too slow” means for this service, so a slowdown can be flagged.
What you get
Percentiles
The average can look fine while one request in a hundred takes seconds. Percentiles show it.
Apdex
One score from 0 to 1 for user satisfaction, based on a target time you choose.
Slow before down
Degradation usually comes first. Seeing it early gives you time to act.
Trends
Compare today with last week and see whether a release made things slower.
Where it helps
APIs with a latency target
Keep an eye on the promise you make to customers.
After a deploy
See at once whether response times changed.
Capacity planning
Watch the slow tail grow before it becomes an incident.
Questions
What is a percentile?
The 95th percentile is the time that 95 out of 100 requests beat. It shows the slower experience that an average hides.
What is Apdex?
A score between 0 and 1: requests faster than your target count as satisfied, slower ones count less, very slow ones count as frustrated.
From where is it measured?
From our probes, in the regions you chose for the monitor.
Related features
Try it on your own services.
Add your first monitor in a couple of minutes. The trial lasts 14 days.
Start free trial