rewindex

CompaniesGoogle WorkspaceIncidents

Google Workspace: **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.

No impact listedStatus: resolvedStarted Resolved (6.3 h)1 updatewww.google.com (opens in new tab)

Affected components: Cameyo by Google

Timeline of updates

  1. resolved

    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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on www.google.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Google Workspace, started 2026-05-12 16:01 UTC, resolved after 6.3 h, 1 update(s).

Title
**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.
Vendor
Google Workspace
Date
URL
https://rewindex.com/company/google-workspace/incidents/ajqakweaixrf8ezj6ckk

Google Workspace profileRecent Google Workspace incidentsAll outages on May 12, 2026Google Workspace in May 2026MarkdownJSON