Request volume
all endpoints · Requests · Response time · Cumulative load00:0004:0008:0012:0016:0020:00
Product tour · Epsilon Delta Orion · Mobile app monitoring
Mobile API latency and failure monitoring
API details times every request your app makes while the user waits for it, splits server time from everything else, and catches failures your servers never see.
API details every request the app makes
“How long does each API call take, and which ones fail?”
- Sample data
- Ending 24 hrs
- Metric: Median
- All platforms
- All versions
- Total requests
- 22.0M
- Avg total time
- 203 ms
- Error rate
- 0.5 %
- Slowest endpoint (P90)
- 55,763 ms
- /logger/v1/log
- /v1/delivery/arrived P90 is 245% slower than yesterday
- 4.45% error rate on /v4/order/progress: 34,249 failed requests
- 6.54% error rate on /v7/check-auth
- Request volume spiked 2.6× between 12:10 and 12:15
Response status distribution
98%success
- 2XX97.9%
- 4XX0.5%
- 3XX / 5XX1.6%
Version comparison
P90 current vs previous v5.4.1 is 454% slower than v5.4.0Top error endpoints
by failed request count| Endpoint | Errors | Rate |
|---|---|---|
| /v4/order/progress | 34,249 | 4.45% |
| /v4/location/current | 13,099 | 0.50% |
| /v1/listing/short-list | 4,862 | 0.42% |
| /v7/check-auth | 2,436 | 6.54% |
| /v7/get-config | 2,270 | 6.19% |
Sample data on example domains (shop.example.com). Your dashboard shows your own sites and apps.
What you can see on API details
- Latency per endpoint at median and p90
- Server time and network time, kept separate
- Failures on the device
- Activity Clustering: API time grouped by screen
Includes what used to be Activity Clustering and Networks. Old links redirect here.
Questions about API details
Why does API time in the app differ from server logs?
Server logs miss DNS, connection, network and queueing time on the phone.
Which failures do servers never see?
Requests that time out, lose connection or fail DNS on the device never reach the server.
Last updated 6 Nov 2026 · Reviewed by [Name], [Role]