This is a real problem for anyone relying on match endpoints!

Just brought to my attention in a league I help run...

https://www.chess.com/club/matches/obsessive-chess-disorder/1678137/games

See board #6 - both game points awarded to @Jose_Kagaoan because the account @Jezzabythesea was closed (unspecified). Usually this is only for FPV but the odd thing is, there's no symbol to indicate that.

I hoped it was only a webpage glitch but looking at the endpoint...

https://api.chess.com/pub/match/1678137

... the status of @Jezzabythesea is shown as:  "status": "premium"

However, look at the player endpoint & it shows: "status": "closed:fair_play_violations"

https://api.chess.com/pub/player/jezzabythesea

Up until now match endpoints have been sufficiently reliable to be able to compile results & decide wins for tournaments that participating teams can place faith in but this is really troubling. I hope it's a one-off?

If this is a case of an interim or provisional judgment by the staff, which might be reversed, then ok but if it's yet another example of crumbling infrastructure then the API is on its way to being unusable for most practical purposes.

Not an isolated problem. Same issue with this one. I put in a bug report. Looks as though we have another own goal by the devs. (not really an API issue though)

@LightningShadow00 

Yeah but at least the endpoint is correct? But it does start to look like the creeping deterioration in (parts of) the API.

Really sad if it gets to the point we can't trust the results we've been producing for years, not to mention the investment of time & effort spent in coding etc.

Both of those players have been banned recently. lightningshadow today the other one played yesterday. So I guess also less than 24 hours ago.

Maybe it is just a timing issue and one part of the data is still cached. I would guess it will be fine by the time.

Some good news! The following match is now showing the correct status for the player on board 6 (@Jezzabythesea) with a closed account:-

https://api.chess.com/pub/match/1678137

Only half-fixed because there's no indication of it being a closed account (FPV) on the webpage but 'baby steps'?

https://www.chess.com/club/matches/obsessive-chess-disorder/1678137/games

I didn't notice this before but there's also a self-closed accunt on board 10 (@ChessTitan249) which has no closed icon attached.

I have that player in another match and I'm almost certain a couple days ago the closed icon was showing...

Hi everyone, thanks so much for your patience.
I was able to get some answers: The inconsistencies between the profile and API data you are observing can most likely be traced back to Redis outages. Our developers can fix them with a backend process, but we need the affected usernames. Please list the cases you encountered. Your help is greatly appreciated! Feel free to comment with the usernames here in this thread.

"Redis outages"?

I think @Tricky_Dicky found a number of other matches with similar problems but I can't remember where he posted the details.

The issue is NOT between web page header and API endpoint.

The problem is that some member closures are not filtering down to game archives and member popup.

Example @LightningShadow00

I have another issue with match endpoints, for instance here: api.chess.com/pub/match/1740531 the player "guluphatep" does not have a daily rating. They had one yesterday on the same page, and they also have one on their stats page. api.chess.com/pub/player/guluphatep/stats

This thing is slowly falling appart.

That one might actually be as per expectation.. It;s a rating restricted match and @guluphatep has just gone over the rating limit and the API doesn't display rating in match registration in that condition.. It doesn't have much logic behind it but it is how it works.

Oh right, once you know it makes sense. Thanks. That's an interesting choice of data display.

Here's another failure. Been there since last July. Completed Dec 2024 and suddenly not available. https://api.chess.com/pub/match/1650597

No doubt it will return sometime. Maintenance mode sucks. The dictionary definition of maintenance 'the process of preserving a condition or situation or the state of being preserved.'

I don't think so.