Is this your status-server glitch in v3.2.5?