The issue is now resolved. We had to upgrade the underlying Redis instance. Crawls may have been interrupted -- please reach out to support if you have any issues.

Elevated timeouts on the API due to load. We are working on resolving the issue.