---
title: "Comment by OneLifeVibe on \"The API Wasn't Slow: Finding a 2-Minute Delay in the Delivery Path\" | Hashnode"
description: "The Nginx timing split is the part I would steal for every team: upstream response time under 300 ms against a total request time of almost 80 seconds makes it"
url: "https://hashnode.com/posts/the-api-wasn-t-slow-finding-a-2-minute-delay-in-the-delivery-path/6af0c4620ba174b457f411ff/comment/6af19534bcff827a3c7a9b85"
---

[Discussion](https://hashnode.com/posts/the-api-wasn-t-slow-finding-a-2-minute-delay-in-the-delivery-path/6af0c4620ba174b457f411ff)

Comment [The API Wasn't Slow: Finding a 2-Minute Delay in the Delivery Path](https://hashnode.com/posts/the-api-wasn-t-slow-finding-a-2-minute-delay-in-the-delivery-path/6af0c4620ba174b457f411ff)

[OneLifeVibe](https://hashnode.com/@onelifevibe)

[1d ago](https://hashnode.com/posts/the-api-wasn-t-slow-finding-a-2-minute-delay-in-the-delivery-path/6af0c4620ba174b457f411ff/comment/6af19534bcff827a3c7a9b85)

The Nginx timing split is the part I would steal for every team: upstream response time under 300 ms against a total request time of almost 80 seconds makes it obvious the API never had the problem, and once both numbers are logged side by side, every future "slow API" report becomes a one-line check. One suspect I would add weight to is the load generator itself — when the generator runs short on CPU or bandwidth, the failure pattern looks exactly like a flaky network, and one in three requests failing rather than all of them slowing down fits that shape. Did you get a chance to check the generator's own resource usage while the test was running?

[Akshita Gupta](https://hashnode.com/@codeincontext)

[21h ago](https://hashnode.com/posts/the-api-wasn-t-slow-finding-a-2-minute-delay-in-the-delivery-path/6af0c4620ba174b457f411ff/comment/6af19534bcff827a3c7a9b85#reply-6af1f034c7d67eee8348faab)

Thanks! Logging both timings side by side is the habit I’d recommend most. The generator is a fair suspect, and the 1-in-3 failure pattern does fit that. \[I did check it during the run and CPU/memory were fine, so it pointed back to the path.\] Thanks for flagging.