No components marked as affected
Resolved
Our investigation into the root cause of this incident suggests that it was not related to the GCP service disruption. We will continue to investigate, but will mark this status page incident as resolved as everything is operating is normally.
Monitoring
We continue to investigate the cause of the service disruption but regular operation has returned since 10:28 UTC.
Monitoring
While we continue to investigate the cause of the service disruption, regular operation had mostly returned by 10:25 UTC and errors ceased by 10:28 UTC.
Investigating
We are investigating elevated error rates on the Ravelin API and Dashboard. This may be a result of the on-going GCP incident (https://status.cloud.google.com/incidents/fmEL9i2fArADKawkZAa2) and are in the process of confirming. We'll update in 30 minutes or sooner.