Summary

What to do

• Check whether you use Google Workspace Cameyo by Google. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 6h 15m it lasted.

  Anything that failed between 2026-05-12 16:01 UTC and 2026-05-12 22:16 UTC may need a replay.

• Subscribe to Google Workspace's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=google-workspace works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Google Workspace 1

1. resolvedMay 13, 2026, 5:55 PM UTC

   **Summary** Some Cameyo by Google customers could not start their sessions after rolling out the new channel version. **Description** We were experiencing an issue with Cameyo by Google, beginning on Tuesday, 12 May 2026 09:01 US/Pacific. The issue was mitigated on Tuesday, 12 May 2026 15:16 US/Pacific by restarting the RAP system service, and performing full server reboots. From preliminary investigation, this was caused by a faulty code for logging improvement on the Player VMs. Log files were unexpectedly duplicated until the disk was full leading to the session failures. Some customers were recovered automatically after the channel binaries were rolled back, while the others were required to restart their VMs manually. Currently, the issue is fully mitigated and change is rolled back. We apologise to those who were impacted by this issue. **Customer Symptoms** The customers were experiencing an issue that couldn’t connect to the Player VMs normally. The disk utilization on the affected VMs reaches 99% or even 100%. **Workaround** Not needed because all affected servers have been mitigated.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.