Hey, we're aware of the issue. It originates from our CDN, so we're working with them toward a solution. A refresh or two can clear it up temporarily, but it could return on another pageload until the issue is resolved. Thanks for bearing with us.