Ongoing error with Time Out rates

Example for member @rendiorton

There appears to be no logic to the approach and no thought into how these results are presented. 

How can this be trusted with the obvious inaccuracies?

I have submitted a bug report (although that is noiw buried under many layers of 'are you sure') via help button.

lets see if I get a response within three days or even the reported nonsense of 29 hours average response time.

Thanks Richard. Your table shows that the situaton is even worse than I thought!

I've added my own report...

The issue of 'incongruous' player timeout values is becoming an increasing headache for those of us who use the site's API data.A case in point: https://www.chess.com/member/rendiorton

None of the endpoints give values that correspond even closely with those of the webpage:-Standard chess timeout is 46% on the webpage but 0% in the relevant endpoint!

Changing the way a value is calculated is fine, provided it's done consistently, but this has left a number of valuable data resources broken for those of us who use the API - can this please be fixed and quickly?

Becoming increasingly frustrated,Stephen (stephen_33)

I'm not going to hold my breath because I also have experience of how these things go but who knows, they might surprise us?

Richard, have you received a reply yet because much to my pleasant surprise I did....

 I just came across your bug report. Thanks for taking the time to write to us. I'll have our API-dedicated team look into this and provide a workaround or fix shortly. Thank you for your patience. I wish you a fantastic rest of day!James (Squirrel)

I reiterrated that this can't be fixed too soon, so let's see what progress is made?

Yes got a message from Support this AM. Very surprised but appreciated. I suspect it's now way down the bug fix list.

I just came across your bug report. Thanks for taking the time to write to us. I'll have our API-dedicated team look into this and provide a workaround or fix shortly. Thank you for your patience. I wish you a fantastic rest of day!

Snap! Cut and paste is so good.

Not sure when this was fixed but there does seem to be precise correlation again between timeout rates as shown in match endpoints and their webpage equivalents!

I've checked about ten across two matches (in registration) and they look fine. It would be nice if we were to be informed when this happens but I suppose we should be grateful for small mercies? 🙄

So are there different still timeout rates for 960 and standard chess? Does the timeout rate once again reflect the percentage of matches lost on time only in the last 3 months?

Haven't checked but it might not. They came up with a strange ,methodology.

If there are less than 20 games in the last 90 days then average over the last 20 games or all if less than 20.

Don't see the logic myself. Seems a bit weird. We have to calculate something so we will put in random number?

I think TO rates are split berween std and C960. And again it's flawed logic. If the split makes sense then split everything. Average move time is still across both formats.

"I think TO rates are split berween std and C960. And again it's flawed logic. If the split makes sense then split everything. Average move time is still across both formats."

Totally agree and it points to the haphazard thinking and methodology with which this site is maintained. Or perhaps more that the left hand doesn't know what the right is doing? Either way, quite disorganised.

You get a sense that no one really has any kind of master-plan on this site.