We have resolved the issue with the RocketReach API and are currently monitoring. We apologize for any inconvenience this caused.
