This incident has been resolved.

An infrastructure issue caused CV2 downtime. After a server restart, we were able to resolve the connection issue.

A misconfiguration in monitoring software caused the servers to reboot. This has now been rectified.