I have had that problem with my own web servers when the certificate is new.
When renewing a cert, I always but new cert with new private key several days before it goes live so it isn't an issue, but with brand new sites or if there is reason to believe a private key may have been compromised, with the new cert that sometimes happens during the first 24 to 48 hours of use.
I don't think it is godaddy, I think it is the certificate authority. If the server can't get fresh OCSP to send to the client because the CA isn't responding, then the server may send outdated OCSP info to the client (if using OCSP stapling) which may result in that error.
I don't know that's the case here, but it may be.
