There is a caching error somewhere in our architecture that we still aren't able to 100% pinpoint. We just pushed a temporary fix to get the catalog working, but it might be a bit buggy until the caching error is completely resolved.
Sorry it took so long for us to find the temporary fix. We will continue to work on pinpointing exactly what broke and how to avoid that problem from happening again.