I was AFK yesterday evening, but am not aware of any planned outages, nor have I seen any notes from the Leago staff. (They do have monitoring tools in place that alert them to issues.)
Do you have tracking on how long it takes an average player search to return? That was the issue - I could get to events but player search would just spin.
I don’t know if that’s tracked, I can ask at today’s status update meeting. My experience has been that most searches take less than a few seconds.
I don’t think there’s anything in the scheduled job queue that runs on Tuesday evening. There’s a large rerate (4 years) that runs overnight early Tuesday but it should have been done long before 7PM. As a reminder, tonight is the cutoff for the October Ratings List.
Next week (Sep 22nd) is when we’re hoping to complete the transfer of the MUIR Azure assets from Leago ownership/management to US Chess ownership/management, there will probably be some down time but I don’t know exactly when yet. I think the CIVI membership system may also have a maintenance window then.
I had that happen on the legacy MSA site with Firefox a couple of days ago, reinstalling Firefox corrected it.
Was this on legacy MSA or on MUIR?
The developers say there has been some increase in load, perhaps attributed to the new 2.0 APIs, they’ve increased the DB resources a bit to see if that will help.
It is Firefox on one particular computer. (Edge worked on the same computer.) It flashes a “Verification Successful” but then goes back to saying that it’s verifying. Every so often, it puts up the “I am not a bot” dialog then goes back into the verification loop.
You had to do a complete re-install of Firefox? I tried deleting the last couple of days and that didn’t help.
I did what they call a reinstall, which deletes the app and reinstalls it but keeps the existing bookmarks,though it loses all the cookies so I have to sign into everything again. I think I also lost browsing history. Didn’t solve some of the lockup problems I have with FF, but it did fix the endless loop verification issue.