Ravelin Status
3DS traffic via US cluster is degraded

Started

Resolved

Duration

1 hr 34 min

Resolvedminor impact

Update timeline

Resolved

The previous incident has been now been resolved. We are sorry for any inconvenience.

Monitoring

Google have now posted details of the on-going incident here: [https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev](https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev "https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev") We will continue to monitor the 3DS API. We are sorry for any inconvenience.

Monitoring

``` Our US cluster has recovered and is processing traffic normally again. Google have identified the issued described below: Virtual Private Cloud (VPC) - VM to VM communication - VM to VM communication over internal IPs In the following locations: - asia-east1 (active) - us-central1 (active) This impacted the connectivity of our components running the us-central1 region. We shall continue to monitor the situation. ```

Investigating

We are experiencing increased error rates from our 3DS API. US based traffic is being rerouted to our EU cluster for processing, so you may experience elevated response times. We are currently in the process of repairing our US cluster. We are investigating to discover the cause. Please check back here for further updates.

3DS traffic via US cluster is degraded — Ravelin Incident Timeline & Status — DevHelm