Skip to content
OutageDeck

Incident detail

**Summary** Some Cameyo by Google customers could not start their sessions after rolling out the new channel version.…

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.

Resolved incidentMinor

Timeline window

to

Outage alerts

Get alerted the next time Google Workspace breaks

Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.

Set up free alertsHow Google Workspace alerts work

Timeline

Incident updates

Every update Google Workspace posted, oldest to newest, exactly as it appeared on their official status page.

  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.

Keep exploring

More from Google Workspace

Neighboring incidents on Google Workspace's timeline and the rest of their record on OutageDeck.

← Older incident

**Summary** Gmail Android users using Microsoft Exchange Online may fail to log in due to authentication issues.…

Newer incident →

**Summary** NotebookLM customers are experiencing an issue where account tiers are being incorrectly downgraded.…

All Google Workspace incidentsGoogle Workspace live status