Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


If you find Runway not working or unavailable, check three things in order: Runway's status page for a live incident, your workspace's credits and plan, and then the network. Runway's own help says firewalls, shared networks, and VPNs can stop uploads or generated media from loading, and it lists turning a VPN off or on as one of its diagnostic steps[4]. A VPN route helps only when the fault sits on the network you are using.
Key Takeaways
- Official availability and account eligibility are separate from network reachability.
- Start with the platform's own support, status, and privacy documentation.
- A VPN can only address a network-layer problem.
- Runway model, plan, and generation limits change; use current official documentation.
Runway does not publish a supported-countries list. Its Terms of Use, checked on 4 October 2026, say the services are offered from the United States with no promise that they are available elsewhere, bar use from U.S.-embargoed or "terrorist supporting" countries and by people on the Specially Designated Nationals list, and let Runway suspend or terminate the services immediately and without notice[3]. To compare how other AI tools publish availability, see our map of where popular AI tools are available.
A VPN changes the IP location Runway sees, so a check based only on IP may pass. Use from a location the terms exclude is still not permitted and can cost you the account[3], and your payment method, card country, and account details stay the same whatever IP you use.
Separate workspace access, credits or plan limits, the generation feature, and the network path before changing settings. Treat a country or region message, a sign-in failure, a missing feature, and a slow or blocked connection as different signals. Record the exact page or client, account state, full error text, network, and time before changing a route; a VPN can test the network layer, but it cannot change eligibility, billing, plan entitlements, or platform rules.
Check the availability notes above, then your workspace, plan, and account status. A model or tool your plan does not include stays missing on every network.[1]
Use the official app or website, update it, clear only local cache when appropriate, and test one browser or device at a time. Avoid unofficial clients and copied login pages.
Check whether the same URL works on another trusted network, whether DNS and HTTPS are normal, and whether the service itself reports an incident. If a VPN is permitted and the issue is clearly network-level, test one route without making account or billing changes.
Separate the web workspace, account or plan credits, model rollout, and usage policy.[1] A missing model or exhausted credits is a product entitlement issue, not a network diagnosis; check the current Runway Help Center and policy before changing a route. A VPN cannot add credits or unlock a model.
Runway runs in the browser and works inside a workspace, and every generation depends on that workspace's plan, credits, and the tools enabled for it.[1] A video that never renders can come from any of those, from the usage policy, or from the network, so it pays to check them one at a time.
Runway accounts can belong to more than one workspace, for example a personal one and a team one. Credits, plan features, and sometimes tool access belong to the workspace, not to you as a person. Note which workspace was selected when the generation failed, which plan it is on, and how many credits it shows. A team member who can generate while you cannot is often working in a different workspace or with different permissions.
Each generation uses credits, and longer or higher-resolution outputs use more. If the balance is low, a job can be rejected or never start. Some generation modes or models are introduced gradually or are limited to certain plans, so a tool that a tutorial shows may simply not be enabled for your workspace yet. Check the help center for the current tools and plan limits before treating a missing option as an outage.[1] No network change adds credits or unlocks a model.
Video generation can take a while, and busy periods add queue time. Before retrying, note when you started the job and whether it shows a queued, processing, or failed state. A job that fails with a message about content is a usage-policy decision, not a connection problem: change the input rather than repeating it, because Runway warns that resubmitting blocked content may lead to account suspension and that support cannot override the block.[2] A job that sits processing for a long time may still finish, and resubmitting it can spend extra credits.
For each attempt, write down the time, workspace, plan and credit balance, tool or mode, input type (text, image, or video), output length and resolution, browser and version, network, and the exact status or error. Do not attach private source footage or client material to a support message unless you are allowed to share it; describe it instead, following the input-protection habits in the beginner's guide to using AI. Large uploads that fail part-way are worth noting separately, since they are often limited by file size, format, or a slow connection rather than by Runway itself.
Use a short, low-cost test in the same workspace and change only the network: office Wi-Fi against home broadband or mobile data. If the web app loads or uploads succeed on one network but not the other, the first network is filtering, mis-resolving DNS, or inspecting HTTPS, which commonly affects large uploads. If local law and Runway's terms allow it, one VPN route can be a further comparison. Do not create extra accounts or workspaces to get more credits, and do not change billing details to work around a plan limit.
Stop testing networks once the same failure repeats everywhere. Workspace membership, seats, and shared credits are handled by the workspace owner or administrator; plan, billing, and generation errors go to Runway support. Send the redacted record with the job's time and status. Runway returns credits for a failed generation shortly after the error, so say so if the balance did not recover.[2]
It can change the path between your device and the service and replace the visible exit IP. This may help distinguish local blocking from an account or product restriction. The VPN for AI tools guide groups Runway with the other video generators, which helps separate a Runway-specific plan or credit limit from a regional one.
Runway sessions move large files, so an AethoVPN comparison should cover the upload, not just the page load. Connect on the computer you edit on (the Windows client, or on a Mac the setup-guide configuration, which needs Pro or Premium), choose one nearby location in the app, and re-upload the same short clip you used for the baseline, noting how long it takes and whether the workspace preview appears. Credits, job status, and model access remain account matters that a route cannot change. See the current plans to check which plan supports your editing computer.
The account stays the same on any route: its country and identity details, payment eligibility, age checks, subscription status, credits, and plan entitlements do not follow your IP address. Runway's terms apply wherever you connect from, and the company can suspend or terminate the services immediately and without notice[3]. Do not create extra accounts, alter billing, or use a route to get around a regional rule.
| What you see | Most likely layer | Next step |
|---|---|---|
| A colleague can generate, you cannot | Workspace, permissions, or plan | Check the selected workspace and ask its owner |
| A job is rejected or never starts | Credit balance or plan limit | Check credits and plan limits in the workspace |
| A tool from a tutorial is missing | Feature rollout or plan | Check the help center for current tools and plans |
| A content-related failure message | Usage policy | Read the policy and change the input |
| Uploads fail on office Wi-Fi only | Local filtering, DNS, HTTPS inspection, or upload limits | Compare networks and check file size and format |
A working workspace does not confirm that a generation job can finish. Record the selected model, input format, job error and credit balance; Runway's help distinguishes generation errors from page access.
Keep the job identifier and timestamp, then follow Runway's current stuck-generation guidance. Do not cancel or repeatedly submit until you understand the credit consequences shown in the account.
No. The account plan, credits, model availability and usage rules remain Runway decisions. Check Plans and Billing and the exact model notice before changing a network route.
No. A rejected input, unsupported media format, temporary processing failure and missing entitlement call for different checks. Preserve the exact notice and test one safe input change at a time.
Check the status page first. If it shows no incident, try a phone hotspot, another browser or a private window, and another device; if only one network fails, Runway's network guide lists the storage and delivery domains your network administrator can allowlist.[4]
Compare the same official page on two trusted connections if the site itself will not load. If the workspace loads but a job fails, inspect the account, input, model and job state first.
Disclaimer: This article is for general informational purposes only and does not constitute legal, technical, or professional advice. Platform availability, account rules, and privacy settings can change; follow official requirements and local law.
Sources:
Sources checked 4 October 2026.
Related Articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.