Thanks.
We tried to deploy our new CDN we wanted to use as a fix for this issue, but that introduced other issues (where things are blocking it due to it being a new domain).
So, ive disabled that for now.
We think we found the root cause of this issue so the assets should be working again.
We'll discuss internally about using something like cdn.kagi.com for our new cdn instead
Thanks!
(please comment on the thread if the issue persists for you)