Runware incident

Seedance 2.5 – Elevated Generation Latency

Minor Resolved View vendor source →

Runware experienced a minor incident on September 10, 2026 affecting API and API, lasting 2d 19h. The incident has been resolved; the full update timeline is below.

Started
Sep 10, 2026, 07:21 PM UTC
Resolved
Sep 13, 2026, 03:20 PM UTC
Duration
2d 19h
Detected by Pingoru
Sep 10, 2026, 07:21 PM UTC

Affected components

APIAPI

Update timeline

  1. identified Sep 10, 2026, 07:21 PM UTC

    Status: Identified We’re aware of elevated latency on Seedance 2.5 due to capacity constraints with our upstream video generation provider. This is affecting generation times. We’re actively working with the provider to get this resolved and will share updates as we have them.. Affected components API (Degraded performance)

  2. monitoring Sep 11, 2026, 11:33 AM UTC

    Status: Monitoring We've seen a meaningful improvement in Seedance 2.5 generation latency over the past several hours as we continue working with our upstream provider. Performance is trending back toward normal levels. Affected components API (Degraded performance)

  3. resolved Sep 13, 2026, 03:20 PM UTC

    Status: Resolved We're continuing to monitor Seedance 2.5 performance. Generation times have improved and we'll keep watching closely. Affected components API (Operational)