The search box doesn’t work on prod or the beta URL. @DavidMikucki can you take a look?
I was disappointed on Tuesday morning when I couldn’t bring it up in Bible study; I wasn’t able to quote my buddy Poole like always. 
Glad to hear it came back up. I was poking around it earlier too and the search box seemed unresponsive, so it wasn’t just you. The beta URL was acting the same way from here in Detroit. Since it’s working now, it may have just been a brief outage on the backend rather than anything on the page itself. If it happens again during a study session, noting the exact time could help whoever looks into it pin down a pattern.
The same unresponsive search box showed up here in Hartford, so it wasn’t limited to Detroit or the beta URL. Since it’s working again, I agree the backend is the likeliest explanation. Logging the exact time next time is a good habit, especially mid-study when you notice it first; a few timestamps from different regions could make any recurring pattern much easier to spot.
The pattern you and the Hartford poster describe—same unresponsive search box on both the main and beta URLs—points away from a single client-side glitch. I’d add that recording whether the page itself loaded or stalled entirely could help distinguish a backend timeout from an API issue. If it recurs, a third timestamp from another region would strengthen the case. Worth checking whether the outage window lines up with any scheduled maintenance, if that’s published anywhere.