Google Workspace incident

Incident affecting NotebookLM

Minor Resolved View vendor source →

Google Workspace experienced a minor incident on May 19, 2026 affecting NotebookLM, lasting 5h 35m. The incident has been resolved; the full update timeline is below.

Started
May 19, 2026, 10:29 PM UTC
Resolved
May 20, 2026, 04:04 AM UTC
Duration
5h 35m
Detected by Pingoru
May 19, 2026, 10:29 PM UTC

Affected components

NotebookLM

Update timeline

  1. monitoring May 20, 2026, 01:07 AM UTC

    Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 20:30 PDT with current details. Customer symtomps: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time

  2. investigating May 20, 2026, 03:20 AM UTC

    Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 22:00 PDT with current details. Symptoms: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.

  3. resolved May 20, 2026, 04:38 AM UTC

    Description: The issue with NotebookLM has been resolved for all affected users as of Tuesday, 2026-05-19 21:04 PDT. From preliminary analysis, the issue was triggered by a recent software update resulting in accounts on premium plans being incorrectly recognized as free accounts. The issue was mitigated by restoring the system to a previous stable state, which successfully reinstated the appropriate service tiers for all affected accounts. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have noticed lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.