# MUIR Overload, Upgrade, Other?

**URL:** <https://forum.uschess.org/t/muir-overload-upgrade-other/61715>\
**Category:** Running Chess Tournaments\
**Created:** [September 15, 2026, 7:01pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715 "2026-09-15T19:01:37Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![ulmont](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/ulmont/32/151_2.png) [@ulmont](https://forum.uschess.org/u/ulmont)\
**Post date:** [September 15, 2026, 7:01pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/1 "2026-09-15T19:01:37Z")

</div>

Is MUIR down, or is there an upgoing upgrade, or something else? Rated events seem to come up fine, but searching for a player is currently unusable.

…separately, if it does seem to be down, what’s the right email to report that at, as I’m 100% sure posting on the forums is not it?

EDIT: looks a little better now.

---

<div class="post-metadata">

**Author:** ![chessgary](https://avatars.discourse-cdn.com/v4/letter/c/34f0e0/32.png) [@chessgary](https://forum.uschess.org/u/chessgary)\
**Post date:** [September 15, 2026, 11:55pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/2 "2026-09-15T23:55:34Z")

</div>

7:54 EDT and it just keeps spinning. ☹

---

<div class="post-metadata">

**Author:** ![nolan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/nolan/32/174_2.png) [@nolan](https://forum.uschess.org/u/nolan)\
**Post date:** [September 16, 2026, 4:29pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/3 "2026-09-16T16:29:32Z")

</div>

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.)

It seems to be working now (11:30 AM CDT)

---

<div class="post-metadata">

**Author:** ![ulmont](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/ulmont/32/151_2.png) [@ulmont](https://forum.uschess.org/u/ulmont)\
**Post date:** [September 16, 2026, 4:34pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/4 "2026-09-16T16:34:01Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![nolan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/nolan/32/174_2.png) [@nolan](https://forum.uschess.org/u/nolan)\
**Post date:** [September 16, 2026, 4:38pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/5 "2026-09-16T16:38:21Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ulmont](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/ulmont/32/151_2.png) [@ulmont](https://forum.uschess.org/u/ulmont)\
**Post date:** [September 16, 2026, 5:14pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/6 "2026-09-16T17:14:12Z")

</div>

> [@nolan](#):
>
> 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.

That was definitely not what I was seeing yesterday, even if one stretches “a few” to “45”.

Also, I was seeing the issues Tuesday around 2pm Central, not in the evening (although chessgary was seeing issues around 7pm Central, as they noted).

---

<div class="post-metadata">

**Author:** ![TomDoan](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@TomDoan](https://forum.uschess.org/u/TomDoan)\
**Post date:** [September 16, 2026, 5:51pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/7 "2026-09-16T17:51:05Z")

</div>

I was stuck in a CloudFlare infinite loop yesterday morning on the Past Event Crosstables link. (Kept being asked to verify “I am not a robot”).

---

<div class="post-metadata">

**Author:** ![nolan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/nolan/32/174_2.png) [@nolan](https://forum.uschess.org/u/nolan)\
**Post date:** [September 16, 2026, 7:34pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/8 "2026-09-16T19:34:11Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ulmont](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/ulmont/32/151_2.png) [@ulmont](https://forum.uschess.org/u/ulmont)\
**Post date:** [September 16, 2026, 10:37pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/9 "2026-09-16T22:37:33Z")

</div>

> [@nolan](#):
>
> Was this on legacy MSA or on MUIR?

This was on MUIR, using Chrome.

---

<div class="post-metadata">

**Author:** ![nolan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/nolan/32/174_2.png) [@nolan](https://forum.uschess.org/u/nolan)\
**Post date:** [September 16, 2026, 10:54pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/10 "2026-09-16T22:54:52Z")

</div>

I wasn’t clear, I was asking about Tom’s endless loop issue.

---

<div class="post-metadata">

**Author:** ![TomDoan](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@TomDoan](https://forum.uschess.org/u/TomDoan)\
**Post date:** [September 17, 2026, 12:11am UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/11 "2026-09-17T00:11:36Z")

</div>

[http://www.uschess.org/datapage/event-search.php](http://www.uschess.org/datapage/event-search.php)

---

<div class="post-metadata">

**Author:** ![nolan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/nolan/32/174_2.png) [@nolan](https://forum.uschess.org/u/nolan)\
**Post date:** [September 17, 2026, 3:56am UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/12 "2026-09-17T03:56:06Z")

</div>

It is working for me today, but I had to reinstall Firefox to get it to work earlier this week.

---

<div class="post-metadata">

**Author:** ![TomDoan](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@TomDoan](https://forum.uschess.org/u/TomDoan)\
**Post date:** [September 17, 2026, 3:03pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/13 "2026-09-17T15:03:57Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![nolan](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.uschess.org/nolan/32/174_2.png) [@nolan](https://forum.uschess.org/u/nolan)\
**Post date:** [September 17, 2026, 6:58pm UTC](https://forum.uschess.org/t/muir-overload-upgrade-other/61715/14 "2026-09-17T18:58:40Z")

</div>

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.
