We've had the same issue (predominantly relating to Edge), but haven't yet found a cause.