> It didn't say "router queue time" or "dyno queue time shown elsewhere". I can tell you that personally when I was writing the code that calculates that queue

> It didn't say "router queue time" or "dyno queue time shown elsewhere". I can tell you that personally when I was writing the code that calculates that queue time value, several years ago, we didn't think such time existed. It was either router time or nothing. > The tools were basically hiding the one problem that was solely Heroku's responsibility. Right, absolutely agree, but the problem is their current queue time measurements do not make a strong argument for this due to the issue of clock skew. They're essentially picking a more-or-less nonsense number and saying that it demonstrates that Heroku is bad. The only numbers that are fundamentally reliable are the total request time from the javascript side.