We've identified a problem and are working on a fix
none- Started
- Oct 30, 3:16 PM EDT
- Resolved
- Oct 30, 3:56 PM EDT
- Duration
- 40 min
Runway's updates (3)
- investigating · Oct 30, 3:16 PM EDT
We have identified the root cause of the problem and are working towards a solution to restore the service for all users.
- monitoring · Oct 30, 3:21 PM EDT
We've released a fix and are seeing improvements. Delayed requests should start processing soon. Previously failed submissions can now be retried. We're monitoring closely to ensure the fix fully resolves the issue for everyone.
- resolved · Oct 30, 3:56 PM EDT
This incident has been resolved.
What our checks recorded
We checked Runway 8 times from Runway's start time to its resolution, once every five minutes. Every one of them reached Runway's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 755 ms, against 166 ms over the 24 hours before. Runway posted the incident at Oct 30, 3:16 PM EDT.
Updates are Runway's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗