Detecting Event Loop Blocking in Production Node.js — Without Touching Your Code

You're on call. Alerts fire. Your Node.js service is responding slowly — or not at all. You suspect event loop blocking, but the app is running in production. You can't redeploy with --inspect . You can't add require('blocked-at') to the source. You definitely can't restart it. What do you do? This is the problem that led me to build node-loop-detective — a diagnostic tool that attaches to a running Node.js process, detects event loop blocking and lag, and tells you exactly which function in which file is causing it. Zero code changes. Zero restarts. In this article, I'll walk through the problem, the approach, and the internals of how it works. The Event Loop Problem Node.js runs JavaScript on a single thread. The event loop is the scheduler — it picks up callbacks, timers, I/O completions, and runs them one at a time. When one of those callbacks takes too long, everything else waits. This is "event loop blocking," and it's one of the most common performance killers in Node.js applica