It’s possible that it’s adding 1998ms latency, but seems unlikely. I also can’t really understand how our middleware would change that. The only thing I could think of is if our middleware executes first, and theres an error being hit, maybe it’s waiting on the errors to send and showing that as part of latency. Normally that happens in a thread though, and I’m fairly confident New Relic’s SDK isn’t smart enough to identify what any of that means.