Beyond the Event Loop: Tracking Slow I/O in Production Node.js

Your Node.js service is slow. You run a profiler. CPU usage is low. The event loop isn't blocked. Everything looks healthy. But users are still waiting 3 seconds for a response. This is the blind spot that most Node.js diagnostic tools have. They focus on what's blocking the event loop — CPU-bound work, synchronous I/O, regex backtracking. But in modern Node.js applications, the most common performance killer isn't CPU at all. It's waiting. Waiting for a database query. Waiting for an upstream API. Waiting for DNS resolution. The event loop is free. It's just got nothing to do until the network comes back. The Async I/O Blind Spot Node.js is designed around non-blocking I/O. When your code does await fetch('https://api.example.com/users') , the event loop doesn't block. It moves on to handle other requests. When the response arrives, the callback fires. This is great for concurrency. But it creates a diagnostic problem: traditional profiling tools see an idle event loop and report "eve