And I had an unusually large number of "404" responses for ordinary members removed from matches last night. The endpoints were all broken.
The API is creaking and I think we're going to have to get used to that. Shame because it wasn't like this before.
Sounds a bit worrying. I only had Match failures this morning. No member issues.
Just remembered, I did run a script yesterday on some members info and had quite a few failures. Run it again today and it has run OK.
It's a case of crossing our fingers and hitting 'Run' 😉
And when we get a load of "404"'s, try again later?
That first one is working now
Hi Martin, I've got one too - https://api.chess.com/pub/match/1857157, where the match is recently finished https://www.chess.com/club/matches/1857157
Just updated and all seem to be working again.
Going through some sort of refresh?
I think the process that refreshes endpoints occasionally has hiccups and can leave it in a broken state. They may update on a later refresh.
Three matches returning "code":0,"message":"An internal error has occurred."
All valid matches
WL2026 R2: Team USA vs Team Germany
10/05/2026 09:33:31 404 https://api.chess.com/pub/match/1906425
CC26 D1 R3 London vs Royal County of Berkshire
10/05/2026 09:53:28 404 https://api.chess.com/pub/match/1901349
CC26 D2 R6: Hertfordshire County Chess vs Team Cambridgeshire
10/05/2026 09:54:22 404 https://api.chess.com/pub/match/1937757