Live / Runway / Incident
Runway: Aleph delayed generations
Runway · runwayml.comMinor incidentResolved2026-08-28 17:31 UTC
Public — what happened
Summary
Runway reported that jobs using its Aleph generation tool were slow to begin processing, an issue it rated as minor. The company began looking into the problem at 16:07 UTC on August 28, 2026, and said at 17:19 UTC that it was deploying a fix. Runway did not say what caused the slowdown. It marked the incident resolved at 17:31 UTC, saying Aleph jobs were starting without delay again.
Affected
App, Backend, Public API
Timeline
- Started — 2026-08-28 16:07 UTC
- Investigating — 2026-08-28 16:07 UTC
- Monitoring — 2026-08-28 17:19 UTC
- Resolved — 2026-08-28 17:31 UTC · 1h 24m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Runway against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Runway: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Runway report →
More from Runway