Ravelin incident

3DS traffic via US cluster is degraded

Resolved after 1 hour 40 minutes, affecting 3DS API and 3DS API, on September 1, 2026.

resolved Sep 01, 2026, 05:01 PM UTC

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

Started
Sep 01, 2026, 03:21 PM UTC
Resolved
Sep 01, 2026, 05:01 PM UTC
Duration
1h 40m
Detected by Pingoru
Sep 01, 2026, 03:21 PM UTC

Affected components

3DS API3DS API

Update timeline

  1. investigating Sep 01, 2026, 03:21 PM UTC

    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.

  2. monitoring Sep 01, 2026, 03:44 PM UTC

    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.

  3. monitoring Sep 01, 2026, 04:22 PM UTC

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

  4. resolved Sep 01, 2026, 05:01 PM UTC

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

Your product runs on more than Ravelin

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →