Hi all - the various issues with servers not doing anything should be resolved now. The command push functionality fell over and the monitoring didn't manage to catch that so I'll be re-doing tests to ensure that's caught in the future.
As for ny02, we mentioned a while ago about being aware that the routing for the IP it uses isn't optimal so users may be getting affected by this. We've got a ticket open with our provider to assign it a new IP from our usual IP block which should solve the routing issues and as soon as that's going ahead we'll post an update here with further details.
I still do ask that you follow the steps Rub gave on how to correctly report lag in a way that enables us to investigate it fully for you since there's very little we can do or say without something more than "it's lagging."
More info for you in this quote:
In future when reporting a problem please ensure you include the following information:
- Node hostname or IP - it's important that you know which node you're reporting a problem for so we can match logs up and find the issue. If you report a problem without knowing what node you're on (the above example says lag on NY01 but reports the NY02 IP, what?), your report cannot be followed up.
- Time and date including timezone - if we don't know when you're experiencing problems, we can't match logs up to work out and fix the problem. If there is a serious case of high latency and you don't think it's localised to you, it's important we find out times and routes so we can work with upstream providers to understand the issue.
- Server host - lag can sometimes be caused by high CPU usage, this needs to be checked in logs too
If you don't include that information, your report is 100% useless, will be considered as spam and reported accordingly. I'm happy to hear reports of problems so we can fix them and improve service quality, but if we're not receiving data, nothing can be done.
Thanks!
