Official server: "Slurtle Slime" went red+down with few players twice

[originalmaja_ds]

We have Sunday morning now. The Klei server Slurtle Slime just went down with few players.

The very same thing happened on Friday morning: a longterm world, already about two days running. This one:

This 113-day world started to get red with only 5 players online. Storms had been activated (which for many public servers adds to the risk of lag). It was odd with so few players, but has not been THAT unusual in the public gameplay DST community of the last months. So we shrugged it off for a moment. In the end, though, the server took [1] many seconds to simply save (in the gameday mornings). And then [2] started to take <minutes for seconds> (as in: a gameplay motion that would usually take 2 seconds would take, like, 40 seconds; i watched my wicker for about 10min walking accross the screen). Then [3] Slurtle Slime just crashed. 

I thought: maybe hack? (Happens on unofficial DST servers now and then. It's a real thing.) 

I also thought: maybe last DST update made memory leak or something?

Or: Maybe it's the server itself?

Today, same server, DIFFERENT world, different daycount, and no CC stuff yet, no storms: On day 255, Slurtle Slime just turns incredibly red (high lag) and then disconnects everyone. Then the automatic thing kicks in, and after 5min of ghosting, the server just resets to day 1.

Dear Klei people: please check (logs, settings and hardware of) your official server tagged "Slurtle Slime".

If the issue has nothing to do with the server, then it's the game itself.

Edited January 25 by originalmaja_ds

[originalmaja_ds]

@JesseB_Klei Could you look at this pls?

[originalmaja_ds]

Anyone reading this?