AI services & audio tools · Daily incidents

AI incidents: Claude Calendar recovery and ElevenLabs billing reports — 29 October 2026

Anthropic reports Google Calendar connector recovery after a 55h 45m impact window. Two new ElevenLabs reviews raise separate post-cancellation billing concerns.

Publisher disclosure: MUVO offers competing music, remix, and video tools. This report summarizes public sources and provider documentation; it is not an independent product test or a claim that MUVO is free of similar issues. Read our reporting method.

Incident summary and status at publication

Anthropic reports recovery of Claude’s Google Calendar connector; two new ElevenLabs reviews describe disputed charges after attempted cancellation. These are different evidence classes: an acknowledged service event and customer accounts that have not been independently verified.

The research window is 26 October at 12:03 through 29 October at 12:08 Europe/Istanbul (UTC+3). This edition includes developments within that window, not a claim that all events happened on 29 October. Earlier unresolved reports were rechecked.

Claude: Google Calendar connector errors are resolved

Anthropic gives a 55-hour-45-minute impact interval, from 26 October at 14:07 to 28 October at 21:52 Istanbul. Some Calendar list/search requests failed in claude.ai, Claude Code and Claude Cowork. The notice does not establish a Google Calendar-wide or Claude API-wide outage. Official incident phg1y2yh07n2.

Impact and provider-response timeline

Milestone Istanbul time (UTC+3)
Reported impact began 26 October, 14:07
First public acknowledgement 28 October, 19:19
Investigation update 28 October, 20:59
Reported impact ended 28 October, 21:52
Monitoring: error rates normal 28 October, 22:47
Resolution notice posted 28 October, 23:05

The duration uses the provider’s stated impact boundaries, not the shorter acknowledgement-to-resolution interval. Anthropic described coordination with an upstream provider but did not publish a root cause or a workaround. Resolution is the provider’s service assessment; it does not prove that every previously failed operation later completed.

This is distinct from the Gmail connector recovery in the 28 October incident edition.

ElevenLabs: new reviews report charges after attempted cancellation

Two independent reviews with experience dates of 28 October describe billing concerns after attempted cancellation. One says a cancelled monthly account returned to Free before an unexpected Scale charge appeared. Another says an attempted cancellation did not complete and a renewal followed. These continue the category of concern reported on 25 October, without establishing a shared technical cause. First review, second review, original listing where both accounts were readable.

Status: customer-reported, unresolved at cutoff. No account-specific provider reply was visible. We have not inspected receipts, cancellation confirmations or account records, and cannot establish whether either charge was erroneous. The reviews do not prove deliberate conduct, a service outage or prevalence. Separate positive product feedback and other isolated complaints do not resolve these two accounts.

Practical checks and coverage limits

For a failed calendar task, check the resulting event or search directly before relying on a completion message. This is MUVO’s practical advice, not an Anthropic workaround. If a billing dispute occurs, retain the plan name, cancellation confirmation, invoice and support correspondence; those records are more useful than assumptions about other users’ cases.

OpenAI’s official history and the previously published Sol and hosted-review notices supplied no new qualifying recurrence. Google’s London postmortem and Runway’s Magnific recovery remained unchanged. ElevenLabs’ accessible history did not establish a fresh service incident or a completed version of its previously promised write-ups. OpenAI history, Google Cloud history, Runway history, ElevenLabs history.

Coverage is incomplete where consumer Gemini history, tenant-specific Microsoft notices, specialist archives or review feeds are inaccessible. A green status indicator is not evidence that no earlier disruption occurred. Isolated account-access, generation-quality and credit complaints remain unpublished unless corroborated.

Sources

MUVO publishes these reports and offers competing creative tools. Read our reporting method and the separate product-news edition.

Update timeline