Hi! John from Ghost here, had a quick look and can't see any issues on this side with the cert. It's a relatively new certificate, though, so there could be an old cache on an edge node somewhere which just hasn't fully updated yet.

I suspect this is a one-off, but please do reach out to us if you still have issues, I've already passed this along to the team to fast-track support if you do send us an email.