Investigate request latency
Compare Durin timing with the upstream provider’s response time.
Inspect the timing
Open Performance in the Admin workspace.
- Select the time range containing the slow request.
- Identify its connection or tool and inspect the available timing breakdown.
- Compare Durin and upstream timing across similar requests.
- Match slow requests with errors or uncertain outcomes in activity.
Troubleshooting
Most of the delay is upstream
Check provider state and errors for that connection. Verify with a small reviewed read after the provider recovers.
A slow write ended with an uncertain outcome
Check the upstream system directly before retrying. A timeout does not prove the write failed.
Frequently asked questions
Does one slow request prove the gateway is slow?
No. Compare similar tools and periods, then use the available breakdown to locate the delay.