Seems that container that serves the website hadn't auto-scaled well ;) (currently it's responding with 502 Bad Gateway) Based on Google cache results, I suspe

Seems that container that serves the website hadn't auto-scaled well ;) (currently it's responding with 502 Bad Gateway) Based on Google cache results, I suspect that the page's rendered server-side, with React, and the container's really busy doing the same DOM stuff over and over. If owners are reading - I think the easiest trick to try (besides scaling up) would be to tell nginx to cache the index page (with `proxy_cache`), heavily - just don't forget to forcibly drop the cookies on `GET /` requests (for safety). The page from Google's cache looks mostly static, so that should do the trick. It would not know the logged-in state, but at least something would show up.