Is Runway Down?

The fastest ways to check Runway availability:

1. Prismix: prismix.dev/service/runway — live status + 30-day uptime + incidents aggregated in one place.
2. Runway's own status page: Check runway.com/status and look specifically at the "Video Generation" row — other rows can be operational while generation is degraded.
3. API call: curl https://prismix.dev/api/v1/statuses | jq '.services[] | select(.id=="runway")'

If Prismix shows Runway as "Operational" but your videos are not generating:

• Gen-3 generation queued indefinitely — Peak hours, especially US afternoons, cause long queues on the free tier. Pro and Unlimited tiers get priority processing. Check the "Video Generation" row on runway.com/status specifically — it can be degraded while other services appear fine.
• Credits depleted mid-generation — Runway charges credits at job start, not on completion. If a generation fails after charging, Runway issues an automatic refund within 24 hours. Check your credit history in account settings before contacting support.
• "Content policy violation" on normal prompts — Gen-3's safety filters are aggressive. Rephrase prompts to be more descriptive and less action-focused. Avoid terms like "explosion", "blood", or "crash" even in clearly benign contexts — use "large fire", "injury", or "collision" instead.
• Video export downloading at wrong resolution — Runway exports at the resolution the job was created with. 4K export requires the Unlimited plan; free and Standard tiers are capped at 720p. There is no way to upscale a completed job — re-generate at the target resolution.
• Inpainting / video editor tools not loading — The Runway editor relies on WebGL. If the canvas appears blank or tools fail to load, disable hardware acceleration in your browser settings. Chrome has the best WebGL support for Runway's editor; Firefox users see more WebGL-related failures.
• Team workspace projects not syncing — Workspace collaboration sync can lag 30–60 seconds. If a collaborator's changes are not appearing, refresh the project tab (not the full browser page) — a full reload can discard unsaved local state.