durin
Book A Demo
Knowledge base
Security & activity

Investigate request latency

Investigate slow MCP requests in Durin Performance, compare gateway and provider timing, and check errors before retrying uncertain actions.

Admin1 min readUpdated

Inspect the timing

Open Performance in the Admin workspace.

  1. Select the time range containing the slow request.
  2. Identify its connection or tool and inspect the available timing breakdown.
  3. Compare Durin and upstream timing across similar requests.
  4. Match slow requests with errors or uncertain outcomes in activity.

Compare usage and cost

Use Performance for request volume, latency and data transfer, and Cost insights for modeled cost and reported usage. Select the relevant period and filters, then inspect chart details before comparing totals. Modeled cost estimates and provider-reported usage are distinct from Durin connection charges.

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.

Try Durin with your MCP workflow.

Book a demo to explore agent access, policy checks, approvals, and audit records with our team.

Book a demo

Choose which optional purposes this browser allows. Cookies that keep the site working, keep you signed in and remember this choice are always on, as is the referral cookie a referral link sets for up to 90 days. Your choice is stored in a first-party cookie for 180 days. Saving a choice that turns analytics off reloads this page if analytics was running on it. Read the privacy notice.