this is a known issue with NPM 12.3 . We raised the case to SolarWinds and, in theory, they will prepare a hotfix (HF4?) that will solve it.
By the way, at the moment we have only seen this issue on that resource (Top XX nodes by average response time), the rest of the Top XX nodes work fine (or at least the ones I've tried).
Installation | Consultancy | Training | Licenses
Do you know if this is fixed in NPM Hotfix 5?