TL;DR: I'm aware of the problem, I know it's frustrating, I'm on it.
Unfortunately as much as I'm always happy to jump on the "Let's Blame Mojang" bandwagon (and let's face it, it is usually their fault), it just doesn't stand up in this case.
The issue is only affecting people who are geographically distant from the server location in Falkenstein. If the issue was 1.15 we would all (or at least randomly) be having the same issue.
@Gwydz You're also describing lag, but when you were on last night the server wasn't even remotely lagged, full 20 TPS, which is actually pretty impressive considering we had a few folk on.
The java error you're all reporting is related to latency, when latency is high you get all kinds of issues exactly as we're seeing just now. High latency feels like lag. Someone was on last night or the day before reporting latency in the 1000's of ms, which is really unusable. As a comparison my latency peaks about 40ms, some of the others are reporting 20ms. Those folk in Germany might even be in single figures.
So the long and short of it is we can basically blame the server host. Now it's not *really* their fault, it will be related to their international connections (most likely EU->US), or peering. Whilst we didn't change providers when we launched on 1.15, we did change servers, and it's possible that means we're in a different rack/building within the data centre. It's entirely possible that small change connected us to a different router, configured to use different upstream peering.
The problem is, I can't choose any options relating to this when I order a server. Their deployment system finds a chassis that matches the server spec I've asked for, and assigns it. As such, ordering another server is a gamble, it could fix the issue, it might make it worse...
My thoughts at this time are that I look to move the server to a UK provider, which will almost certainly mean London based. The huge advantage this carries is that London is incredibly well connected to the world and gives us the best chance of sorting the problem.
The issue is cost (and my time, I guess). It will likely add about £30-40 to the monthly costs to do this and whilst that isn't a massive amount of money, the donations have tailed off a little recently and would likely mean Barry and I have to start making up the difference. It also means we'll likely have to commit to a 12 month contract, but that's for us to work out if we're comfortable with that.
It could be the code, it could be the price of fish!
