Previous incidents

Google Cloud Run customers experienced a service disruption
Start: 26 June 2025 at 07:16 UTC+1
Symptom identified: 26 June 2025 at 08:32 UTC+1
Resolved: 26 June 2025 at 08:42 UTC+1

Impact:
Some of our components that rely on Google Cloud Run were temporarily impacted due to an upstream issue. This may have caused brief service interruptions for a subset of users.

Root Cause:
The disruption was related to a misconfiguration in the networking infrastructure supporting Cloud Run, which has sin...

Google has published their full incident report on https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW

We are sharing it also here for your convenience:

---

Incident Report

Summary

Google Cloud, Google Workspace and Google Security Operations products experienced increased 503 errors in external API requests, impacting customers.

We deeply apologize for the impact this outage has had. Google Cloud customers and their users trust their businesses to G...

We’re happy to share that the issue affecting Viator Self-Mapping in the Ventrata interface has now been resolved.

Our team addressed the recent change on Viator’s side, and the product sync is now functioning as expected. Users can once again map and remap products directly from the Ventrata interface without issue.

🛠 No further action is needed—you can resume normal use of the self-mapping functionality.

📩 Need help?
If you continue to experience any issues, please don’t hesitate to reac...

The issue with transactional email delays has been fully resolved. All previously queued emails have now been successfully delivered, and the system is operating normally.

Our partner Adyen has released a Root Cause Analysis on their webpage, which you can find at the following link: https://www.adyen.com/knowledge-hub/mitigating-a-ddos-april-2025

Recent improvements have resolved the issue for most users. We’re continuing to monitor. If you’re still experiencing issues, please contact our support team via 24/7 live chat.

At 16:52 and 17:25 GMT yesterday, we experienced a 33-minute period of service degradation that caused all channels to either become unresponsive or significantly slower. We've completed a detailed investigation and identified the root cause as a sharp spike in traffic volume driven by aggressive pre-emptive loading of our checkout widgets. In response, we've refined the loading logic and increased service capacity tenfold. With these changes in place, we do not expect a recurrence.

The pre-...