Orders latency on payment dependency
p95 crossed 750 ms for 3 evaluation windows · orders-api → payments-api
Incident timeline
Scenario F-04 started
Dependency-path latency armed with a three-minute TTL.
Orders p95 crossed 750 ms
First qualifying window · 31 requests sampled.
Incident opened
High dependency latency persisted for three evaluations.
Discriminating trace retained
Client 1,137 ms · paired server 42 ms.
Diagnosis validated
4 claims · 100% valid citations · mock/deterministic-v1.
Latency is on the dependency path,
not inside Payments.
The Orders client span is 27× slower than the paired Payments server span. Payments processes the request normally; delay is introduced before it reaches the service.
Orders p95 increased to 1,246 ms from a 151 ms baseline.
The Orders → Payments client span took 1,137 ms.
The paired Payments server span completed in 42 ms.
Inspect the dependency path, proxy, and network between Orders and Payments. Compare client/server span boundaries before reviewing the Payments deployment.
Limitations and confidence rationale
This deterministic diagnosis recognises the controlled failure mode. Confirm live network and deployment context before acting. Confidence is descriptive, not statistically calibrated.