Uptrue monitored Midjourney and Runway during the week of 20 April 2026. Runway achieved 100% uptime with an average response time of 89ms, while Midjourney reported 0% uptime during the monitoring period. Both services recorded zero incidents, though the uptime disparity reflects significant availability differences.
- Runway maintained 100% uptime; Midjourney recorded 0% uptime during monitoring week
- Runway's average response time was 89ms with zero downtime minutes logged
- Both providers reported zero incident events in the 7-day period
- Data collected by Uptrue's independent monitoring infrastructure for the week of 20 April 2026
Uptime This Week
Runway delivered complete availability at 100% uptime during the monitoring period, indicating consistent service accessibility. Midjourney's 0% uptime indicates the service was inaccessible throughout Uptrue's monitoring window. This stark contrast suggests fundamental infrastructure or access differences between the two platforms during this specific week.
Response Time
Runway responded to requests with an average latency of 89ms, demonstrating acceptable performance for AI tool operations. Response time data for Midjourney was unavailable due to the complete uptime failure during monitoring.
Incidents & Downtime
Neither provider triggered incident alerts during the week of 20 April 2026, despite Midjourney's sustained unavailability. The zero-incident classification for Midjourney likely reflects monitoring methodology rather than service health, as 0% uptime indicates a pervasive accessibility issue beyond discrete incident events.
Which Should You Choose?
For reliability-critical workflows during this period, Runway is the only viable choice based on observed availability. Teams should verify current status independently, as monitoring data reflects specific week conditions and may not represent ongoing performance.
All uptime, response time, and incident data is collected by Uptrue's independent monitoring infrastructure. HTTP checks run every 5 minutes. An incident is recorded only after 2+ consecutive failed checks. Uptrue is not affiliated with any monitored service. For corrections: reports@uptrue.io