Stats readings don't reflect actual stats

[PotatoVeggie 1]

Greetings,

Multiple servers are pegged to capacity, but neither UI nor client show that.
Was an issue for a while.
Please fix

 

Edited ... by OpenSourcerer
Edited topic headline to be less insulting

[Air4141841 25]

I recall reading previously.  that Texas servers were showing false information, I have no idea if that has been addressed or not 
I'm sure staff will give you a reply soon 

[go558a83nk 364]

I asked kindly about a year ago.  Still not fixed.  Maybe this kind of post will light a fire under somebody?  Or maybe they'll just delete it for being unkind.

[OpenSourcerer 1442]

"Fix your stuff" first, Mr. PotatoVeggie. That is a very poor topic headline. Please edit your first post and make it more objective.

Did any of you contact Support regarding this?

[go558a83nk 364]

1 hour ago, OpenSourcerer said:

"Fix your stuff" first, Mr. PotatoVeggie. That is a very poor topic headline. Please edit your first post and make it more objective.

Did any of you contact Support regarding this?

I did over a year ago.  The ticket is still open.

[OpenSourcerer 1442]

By the way, the stats issue is now reflected in the server stats and issue history -- and was, as a matter of fact, marked as such before this thread was created. So it is known and will probably be worked on in the coming week.

[PotatoVeggie 1]

@OpenSourcerer

Bro, look before you post things yourself.
This thread was created before issue showed up on the 'issue tracker'.

People submitted tickets for this years ago, yet it hasn't been fixed.
It seems that calling people out in public and saying 'yall screwed up once again', and allowing people to post "+1" is the only way to get this issue officially added to the tracker and get worked on in the first place. 
Don't like it? Add a "this server is experiencing issues" button that we can slap each time this happens.

 

[OpenSourcerer 1442]

13 hours ago, PotatoVeggie said:

Bro, look before you post things yourself.
This thread was created before issue showed up on the 'issue tracker'.

.. ah yes, I see my error. The stats issue was logged 08:15 AM UTC, which is 08:15, while your thread was posted at 10:40 AM UTC, which I erroneously interpreted as 10:40 but is actually 22:40 in the previous UTC day. Barring the question of why I am being shown AM/PM at all while being in a 24h region (and despite the setting to show me 24h-formatted times), yes, your post predates the issue, and probably was the principle reason for it being worked on right now. I apologize.

Kinda confirms that it's really looked at now, though.