AI incidents: ElevenLabs Dubbing, SIP and Runway Seedance recoveries — 9 October 2026

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

Three official notices qualify for this edition: two ElevenLabs disruptions and a Runway integration issue. They are component-specific events, with no evidence here of a simultaneous outage across all three providers.

The research window is 6 October at 12:17 through 9 October at 11:58 Europe/Istanbul (UTC+3). The Runway event was discovered during today’s overlap scan and occurred on 6 October. All times below are Istanbul time; dates remain attached to events crossing midnight. Product announcements are in the separate 9 October news roundup.

ElevenLabs Dubbing: recovery followed a recurrence

ElevenLabs closed the Dubbing incident at 01:10 on 9 October, citing stable error metrics since 20:55 on 8 October. Its notice names ElevenCreative and ElevenAPI’s Other component. Original incident and updates.

The closure’s recovery reference differs from the interim update. We retain both and do not calculate a total outage duration: acknowledgement is not an established impact start, and the recurrence complicates a single interval. The upstream provider and underlying cause were not named. These notices do not establish that every failed dubbing job completed afterward.

ElevenAgents SIP: call failures cleared before the closure notice

ElevenLabs says Agent SIP conversation failures had cleared by 18:15 on 8 October. It acknowledged the issue at 18:00 and posted resolution at 18:43, promising a root-cause analysis after its investigation. The affected component was ElevenAgents Telephony; it expressly said non-SIP Agent conversations were unaffected. Original SIP incident.

The notice does not establish a reliable impact-start time or publish a root cause, so the 43 minutes between posts is not presented as outage duration. It gives no model, plan or regional breakdown. This is a separate incident ID from the 6 October EU SIP disruption covered in our 7 October edition; a shared cause has not been established.

Runway Seedance: face-input failures on 6 October

Runway reported elevated failures for Seedance generations containing human faces at 21:52 on 6 October. Its notice lists the App, Backend and Public API, and says it was working with the Seedance team. The event was marked Resolved at 23:22. Original Runway incident.

There is a source inconsistency: the final status is Resolved, but its accompanying text still says investigation is underway. We report the status label and preserve that limitation. The notice does not supply a root cause, model version, region, precise impact interval or customer workaround. It supports an incident affecting Seedance through Runway, not a claim that all ByteDance or Seedance deployments failed. This is newly discovered coverage of an earlier event, not a new 9 October outage.

Claude follow-up: usage reporting resolved on 13 October

Update, 14 October: Anthropic resolved this reporting incident on 13 October at 21:00 Istanbul. See the recovery roundup.

What affected users can check

Start with the linked notice for the workflow you actually used: Dubbing, SIP telephony or Runway’s Seedance integration. The notices do not promise refunds, automatic recovery of individual jobs or a universal workaround. For an unresolved task, keep its timestamp, product and error details when checking with that provider’s support; exclude credentials and private source media from public posts.

Sources

• ElevenLabs: Dubbing timeline and SIP call notice.
• Runway: Seedance incident and incident history.
• Anthropic: usage-data incident.

These are provider acknowledgements, not measurements by MUVO. We checked OpenAI’s history, Google Cloud status, other major services and music/video/remix customer-review sources. Google’s Gemini API status was inaccessible, and several providers exposed limited history. No additional customer allegation met the evidence standard for publication. A missing qualifying item is not a clean bill of health. The source scope and evidence rules are described in our reporting method.

Update timeline

• 9 October 2026, 11:58 Istanbul / 08:58 UTC: Initial edition records two ElevenLabs recoveries, newly discovered Runway coverage and an unchanged Claude follow-up. No total outage duration is inferred from acknowledgement and closure posts.

• 14 October 2026, 13:26 Istanbul / 10:26 UTC: Added the later Anthropic reporting recovery; original publication date and URL preserved.