Runware incident
Some of the models has degraded performance or timeouts
Runware experienced a minor incident on August 5, 2026 affecting Official Models, lasting 5h 7m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 05, 2026, 01:19 PM UTC
Status: Investigating We're currently experiencing issues with some of the models. Issue sits on the infrastructure side, so team now is investigating. Affected components Official Models (Degraded performance)
- identified Aug 05, 2026, 01:46 PM UTC
Status: Identified The team is still investigating Affected components Official Models (Degraded performance)
- identified Aug 05, 2026, 02:36 PM UTC
Status: Identified We've identified the issue with our third-party provider and now preparing the remediation. Affected components Official Models (Degraded performance)
- monitoring Aug 05, 2026, 03:26 PM UTC
Status: Monitoring We’ve migrated some of the consumers to a stable location. Queues are back to normal, we will keep monitoring this incident for a while Affected components Official Models (Operational)
- monitoring Aug 05, 2026, 03:51 PM UTC
Status: Monitoring Some models are intermittently slow or timing out due to a network issue at one of our infrastructure providers. The issue comes in short bursts, and affected requests recover automatically once each burst passes. We are working with the provider on a fix and will post updates here. Affected components Official Models (Degraded performance)
- resolved Aug 05, 2026, 06:26 PM UTC
Status: Resolved The issue has been resolved. Thank you for the patience. Affected components Official Models (Operational)