Is NotebookLM Down? Checks and Ways to Resume Your Research

When Gemini Notebook (formerly NotebookLM) fails to load or stops responding, the first question is whether the problem is on Google's side or yours. Most of the time, a quick browser or account check resolves it in a few minutes. Tools like fenbs help when a real outage hits: if your sources, verified findings, and reference links are saved there, you can continue the work in another AI assistant without losing your place.

Check whether Google is having a wider issue

Google provides a status dashboard at https://www.google.com/appsstatus↗ (opens in a new tab) that shows the current state of its services, including Workspace products. If Gemini Notebook is listed as disrupted or under an outage, the fix is to wait.

You can also check current reports from other users on social platforms. A widespread problem surfaces quickly. If you see nobody else reporting an issue, the problem is likely local to your browser or account.

Local checks to try first

Most loading failures have a local cause. Work through these before assuming an outage:

1. Reload the page. A stuck resource load is the most common cause of a blank page or unresponsive interface.
2. Try a different browser. Chrome and Edge tend to have the fewest issues with Google tools.
3. Open a private or incognito window. This bypasses cached data and extensions. If the notebook loads there, a browser extension is likely causing the problem.
4. Clear the browser cache. Go to your browser's settings and clear cached files and cookies for the site.
5. Check your internet connection. A slow or intermittent connection can make the tool appear broken when it is simply timing out.
6. Sign out of Google and sign back in. An expired session token sometimes causes a persistent loading failure.

Account-specific problems

If Gemini Notebook loads on a different Google account but not yours, the issue is account-specific. Check:

• Whether your organization's Google Workspace admin has restricted access to the tool.
• Whether you are signed in on the correct Google account. It is easy to have multiple accounts active and be on the wrong one.
• Whether your account has exceeded a usage limit. This is less common but can happen on high-volume research sessions.

When the notebook loads but a specific notebook will not open

If the tool loads but one of your notebooks gives an error, the issue may be with a specific source file in that notebook. A corrupted or very large PDF can prevent a notebook from opening. Try removing the most recently added source and reloading.

If a shared notebook will not open, check whether the owner still has access or whether sharing was revoked.

What to expect during a Google outage

Most Google service disruptions last from a few minutes to a few hours. Full-day outages are rare. If the status dashboard shows a disruption, check it again after 30 minutes before trying extensive workarounds.

Google typically posts updates on the status page as an incident progresses, noting when it is investigating, when a fix is being rolled out, and when the service is restored. You do not need to refresh the product page repeatedly — check the status dashboard instead.

If the disruption affects only certain features — for example, source uploads fail but chat works — it may be worth continuing with what is available rather than waiting for full restoration. Chat-only sessions can still answer questions from sources already in the notebook.

Continue your research in another assistant

If the outage is genuine and you need to keep working, a general AI assistant — Claude, ChatGPT, or Gemini in a browser — can continue source analysis if you can paste or upload the relevant source passages. The experience is less structured than a dedicated notebook, but a real outage should not stop your work entirely.

See NotebookLM alternatives for other tools that handle source-grounded research in case you need a longer-term backup. For a direct comparison with the tool most people consider first, Claude Projects vs NotebookLM covers the differences.

Preventing data loss during an outage

An outage does not delete your notebooks. Your sources and notebooks are stored in Google's infrastructure and survive the disruption. When the service restores, your notebooks appear exactly as you left them.

What you can lose is work done during a session that was not saved. If you were in the middle of composing notes from a notebook chat when the outage hit, those notes may be incomplete. Get in the habit of saving findings to an external document as you work rather than planning to copy everything at the end.

How to keep your research accessible with fenbs

The most frustrating part of a Gemini Notebook outage is that your research context — sources, findings, open questions — is inside the tool you cannot reach. Keeping that record in fenbs means any outage stops your access to the notebook, not to the work itself.

1. Create a free account and add a project for each active research area.
2. Save links to your source documents in the project's Links and listings section, not just inside the notebook.
3. After each session, record approved findings as decisions and open questions as tasks.
4. Connect a supported AI assistant from Integrations. During an outage, it reads your research record from fenbs and lets you continue without the notebook.
5. Update "Where we left off" before each session ends, so any assistant can start from the right point.