Comment by xyzzy4747

Well actually, if they had used Next.js deployed via Vercel or something similar, it would have been statically cached on a CDN and prevents issues like this. But because they want to use older technology that's more difficult to cache and proxy, this happens.