Is Runware down?
Last checked just nowNo incidents right now.
Runware is operational right now. Last checked just now; the most recent incident resolved 2d ago.
Real-time Runware status, recent outages, and incident history: pulled directly from Runware's official status page at status.runware.ai every 5 minutes. Pingoru tracks 11 Runware services and has captured 17 incidents in the last 90 days (98.08% uptime). Get email, Slack, Discord, or webhook alerts the moment Runware reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Official Models
Timeline · 2 updates
- investigating · Oct 29, 2026, 04:57 PM UTC
Status: Investigating Customers could experience the rate-limiting (429) response. We are now taking action to process the load Affected components Official Models (Degraded performance)
- resolved · Oct 29, 2026, 07:19 PM UTC
Status: Resolved The issue with rate-limiting has been resolved. Affected components Official Models (Operational)
Latest: Status: Resolved The issue with rate-limiting has been resolved. Affected components Official Models (Operational)
-
- APIAPI
Timeline · 3 updates
- investigating · Oct 28, 2026, 05:31 PM UTC
Status: Investigating We are aware of the Serverless API experiencing an outage at the moment and the team is investigating. Affected components API (Partial outage)
- monitoring · Oct 28, 2026, 05:33 PM UTC
Status: Monitoring Issue identified and a fix rolled out. API is back operational. The team continues to monitor. Affected components API (Operational)
- resolved · Oct 28, 2026, 05:41 PM UTC
Status: Resolved Issue resolved. Affected components API (Operational)
Latest: Status: Resolved Issue resolved. Affected components API (Operational)
-
-
Timeline · 2 updates
- monitoring · Oct 19, 2026, 03:46 PM UTC
Status: Monitoring Increased load and slower than normal response times on Z-Image Turbo family of models.
- resolved · Oct 19, 2026, 04:51 PM UTC
Status: Resolved Queue wait times have been resolved. Some requests may return HTTP Error 429, but that is temporary and should self-resolve.
Latest: Status: Resolved Queue wait times have been resolved. Some requests may return HTTP Error 429, but that is temporary and should self-resolve.
-
- Official Models
Timeline · 4 updates
- identified · Oct 07, 2026, 07:14 PM UTC
Status: Identified One of our infrastructure vendors is currently experiencing network issues, which has caused some of our compute capacity to become unavailable. We are actively migrating affected workloads to alternative infrastructure to restore full capacity as quickly as possible. We apologise for the disruption and appreciate your patience while we work to fully resolve the issue. Affected components Official Models (Partial outage)
- identified · Oct 07, 2026, 07:16 PM UTC
Status: Identified One of our infrastructure vendors is currently experiencing network issues, which has caused some of our compute capacity to become unavailable. We are actively migrating affected workloads to alternative infrastructure to restore full capacity as quickly as possible. We apologise for the disruption and appreciate your patience while we work to fully resolve the issue. Affected components Official Models (Partial outage)
- monitoring · Oct 07, 2026, 07:59 PM UTC
Status: Monitoring Network issue has been resolved, we are monitoring the queues until they are drained Affected components Official Models (Degraded performance)
- resolved · Oct 07, 2026, 08:52 PM UTC
Status: Resolved Incident has been resolved, thank you for your patience. Affected components Official Models (Operational)
Latest: Status: Resolved Incident has been resolved, thank you for your patience. Affected components Official Models (Operational)
-
-
Timeline · 2 updates
- identified · Sep 28, 2026, 04:30 PM UTC
Status: Identified We are experiencing high load and slower than normal response times on FLUX.1 [dev] models.
- resolved · Sep 28, 2026, 08:03 PM UTC
Status: Resolved Degraded service resolved for FLUX.1 [dev]
Latest: Status: Resolved Degraded service resolved for FLUX.1 [dev]
-
See the full Runware outage history
10 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Runware outage history →Or sign up free to get alerts when Runware breaks · 10 free monitors · No credit card
Incident record
Since October 2026 · incident.io · 11 components checked every 5 minutesThe longest incident in the last year, Seedance 2.5 – Elevated Generation Latency on September 10, 2026, ran for 3 days. 2 maintenance windows announced in the same period.
Most affected components, last 12 months
- Official Models15
- API3
- API3
- Third-party Models3
- Compute1
Latest incidents
- Models experiencing delays due to increased traffic
Status: Investigating Customers could experience the rate-limiting (429) response. We are now taking action to process the load Affected components Official…
- Serverless API is currently unreachable
Status: Investigating We are aware of the Serverless API experiencing an outage at the moment and the team is investigating. Affected components API (Partial…
- Increased traffic on Z-Image Turbo Models
Status: Monitoring Increased load and slower than normal response times on Z-Image Turbo family of models.
- Started Oct 29, 2026, 04:57 PM UTC · Resolved Oct 29, 2026, 07:19 PM UTC · 2h 21m
- Started Oct 28, 2026, 05:31 PM UTC · Resolved Oct 28, 2026, 05:41 PM UTC · 10m
- Started Oct 19, 2026, 03:46 PM UTC · Resolved Oct 19, 2026, 04:51 PM UTC · 1h 4m
- Started Oct 07, 2026, 07:14 PM UTC · Resolved Oct 07, 2026, 08:52 PM UTC · 1h 38m
- Degraded performance of FLUX.1 [dev] ResolvedStarted Sep 28, 2026, 04:30 PM UTC · Resolved Sep 28, 2026, 08:03 PM UTC · 3h 32m
- Fast-flux increased traffic ResolvedStarted Sep 22, 2026, 12:47 PM UTC · Resolved Sep 22, 2026, 01:17 PM UTC · 29m
- Started Sep 13, 2026, 07:31 AM UTC · Resolved Sep 13, 2026, 07:42 AM UTC · 10m
- Started Sep 10, 2026, 07:21 PM UTC · Resolved Sep 13, 2026, 03:20 PM UTC · 2d 19h