Google Cloud MAJOR

Looker Studio customers may experience high latency on operations that involve Spanner read / write.

November 26, 2024 · 12:30 AM UTC – 03:49 AM UTC · Duration: 3h 19min

Affected Services

Looker Studio

Timeline

03:49 AM
The issue with Looker Studio has been resolved for all affected users as of Monday, 2024-11-25 19:48 US/Pacific. We thank you for your patience while we worked on resolving the issue.
02:27 AM
Summary: Looker Studio customers may experience high latency on operations that involve Spanner read / write. Description: Our engineering team continues to work on the mitigation while also identifying any measures that can be taken to reduce the overall time of the rollout. We currently do not have an ETA for complete mitigation. We will provide more information by Monday, 2024-11-25 22:30 US/Pacific. We apologize to all who are affected by this disruption. Diagnosis: Customers impacted by this issue may intermittently encounter timeouts, in addition to the latency observed on the affected operations. Workaround: None at this time.
01:29 AM
Summary: Looker Studio customers may experience high latency on operations that involve Spanner read / write. Description: Our engineering team has identified the steps required to mitigate the issue and is currently in the process of the rollout. We do not have an ETA for mitigation at this point. We will provide more information by Monday, 2024-11-25 18:30 US/Pacific. Diagnosis: Customers impacted by this issue may encounter timeouts, in addition to the latency observed on the affected operations. Workaround: None at this time.
01:05 AM
Summary: Looker Studio customers may experience high latency on operations that involve Spanner read / write. Description: Our engineering team has identified the steps required to mitigate the issue and are currently in the process of the rollout. We do not have an ETA for mitigation at this point. We will provide more information by Monday, 2024-11-25 18:15 US/Pacific. Diagnosis: Customers impacted by this issue may encounter timeouts, in addition to the latency observed on the affected operations. Workaround: None at this time.