That's interesting, the endpoint seems to work for me
curl https://api.chess.com/pub/country/GB/players
Gives me
StatusCode : 200
StatusDescription : OK
Content : {"players":["---k---","-shinobi-","-winner-","0-michael-0","0-town","000000001a","000fox","000hello
world000","000isaac000","000mr000","000pdh","000sarah","001001011001","005s","007ajhughes","007bon"
,"...
RawContent : HTTP/1.1 200 OK
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Accept-Encoding
X-Chesscom-Matched: pubapi_country_players
Access-Control-Allow-Origin: *
Link: <https://api.chess.com/con.
Forms : {}
Headers : {[Transfer-Encoding, chunked], [Connection, keep-alive], [Vary, Accept-Encoding],
[X-Chesscom-Matched, pubapi_country_players]...}
Images : {}
InputFields : {}
Links : {}
ParsedHtml : mshtml.HTMLDocumentClass
RawContentLength : 1923254
Until recently I have had no problem with this end point for 'GB' although I am aware it will not work for 'US' due to the dataset size.
Is this now becoming an issue for all larger country login member lists? Typically I would get between 130k - 170k logins in the dataset and that has been OK until now.
https://api.chess.com/pub/country/GB/players
Error 524
Ray ID: 6ba55c8fff3e7556 • 2021-12-08 10:39:39 UTCA timeout occurred