# Connection Performance Vagon streams your cloud computer in real time, so connection quality directly affects responsiveness, visual quality, and stability. Most performance complaints come from a small set of root causes: insufficient bandwidth, distance from the nearest region, an interfering network setup, or an outdated GPU driver inside the Vagon Computer. ## Internet Speed Requirements Vagon does not need a high-end connection. A modest but stable link is enough to stream a cloud computer at usable quality. * Minimum recommended speed on the lowest Stream Preference: **5 Mbps**. * Higher Stream Preferences (sharper image, higher frame rate) require more headroom. Plan for additional bandwidth if you raise the quality. * Test your connection at [speedtest.net](https://www.speedtest.net) before troubleshooting anything else. {% hint style="info" %} Speed alone is not the full picture. A 200 Mbps connection that fluctuates or shares the network with heavy traffic can feel worse than a steady 10 Mbps line. {% endhint %} ## Unstable Network Use a stable Wi-Fi signal or wired Ethernet connection when possible. While using Vagon, avoid: * Heavy downloads or uploads on the same network. * Cloud sync clients (Dropbox, Google Drive, OneDrive) actively transferring large files. * Video calls and live streaming on other devices. * Mobile hotspots or 4G/LTE connections — limited bandwidth and jitter on mobile networks regularly cause lag. ## Region Distance Latency scales with physical distance. Vagon operates regions in North America, Europe, Mumbai, Singapore, and Sydney. Even a fast connection feels sluggish if you connect to a region on another continent. * During first setup, Vagon tests your connection and suggests the closest region. * If you have moved, traveled, or noticed lag after switching regions, recreate the computer in the nearest available region. ## Local Computer Requirements The streaming client is lightweight. Vagon runs on most modern devices, including Chromebooks and MacBook Air 2014 models. There is no need for a powerful local GPU because the rendering happens in the cloud. If your local device is very old or under heavy load, the client itself may not be able to decode the stream smoothly. Close other heavy applications, then reconnect. ## Browser Version and Plug-ins Outdated browsers and some extensions interfere with WebRTC streaming. * Update Chrome or Edge to the latest stable version, then restart the browser. * Disable extensions that block scripts, media, or trackers and reconnect. * Try an incognito/private window to rule out extension conflicts. * If browser issues persist, switch to the Vagon Desktop Application, which avoids browser-layer interference entirely. ## VPN, Proxy, and Firewall VPNs, proxies, corporate networks, and strict firewalls modify or restrict the traffic Vagon needs. Try: * Disabling VPN or proxy temporarily. * Testing from a different network (for example, a personal hotspot). * Asking your IT team to allow real-time media and WebRTC traffic. ### Using a VPN Inside the Vagon Computer Running a VPN client *inside* your Vagon Computer can also cause streaming issues because the VPN modifies the network adapter that Vagon uses to stream back to you. * Most consumer VPN clients change adapter settings in ways that break the stream. * OpenVPN has been tested and works reliably inside Vagon when a VPN is required. {% hint style="warning" %} If you connect to a VPN inside your Vagon Computer and the session freezes or disconnects, you may need to wait for the session to end or contact support to restore connectivity. {% endhint %} ## Cannot Connect After Changing Performance Option When upgrading to a Fire-series performance option (Spark, Blaze, Fire, or Lava), the connecting screen can hang for more than a minute. This happens when the GPU driver on your Vagon Computer is out of date and does not support the new hardware tier. The full driver update flow is covered in the GPU Driver Issues guide. {% content-ref url="/pages/fjJUvWUFqRo7MaD13CyM" %} [GPU Driver Issues](/computer/troubleshooting/gpu-driver-issues.md) {% endcontent-ref %} ## Upgraded Performance Still Feels Slow A higher performance option gives your Vagon Computer more CPU, GPU, and memory, but the issue may be inside the Vagon Computer rather than on the network. If the connection itself is healthy but the apps inside the session still feel slow, see the Computer Performance guide. {% content-ref url="/pages/S5Y14Lj21Bxc3t1x2ka0" %} [Computer Performance](/computer/troubleshooting/computer-performance.md) {% endcontent-ref %} ## What to Send Support If the issue continues after the steps above, include: * Your physical location. * Selected Vagon region. * Browser or desktop app version. * Network type (wired, Wi-Fi, hotspot) and a current speed-test result. * Performance option in use. * A short pattern description, such as constant high latency, periodic lag, or random disconnects. ## Next Steps {% content-ref url="/pages/5eC8iMR1VM0vuyIqNBEN" %} [Performance Options & Specs](/computer/features/performance-options-and-specs.md) {% endcontent-ref %} {% content-ref url="/pages/dOrYDK5NrHlLBbnJ3opQ" %} [Vagon Desktop Apps](/computer/features/vagon-desktop-apps.md) {% endcontent-ref %} {% content-ref url="/pages/trydFd4oFnVWu0wQKAQd" %} [Computer Connection](/computer/troubleshooting/computer-connection.md) {% endcontent-ref %} {% content-ref url="/pages/S5Y14Lj21Bxc3t1x2ka0" %} [Computer Performance](/computer/troubleshooting/computer-performance.md) {% endcontent-ref %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.vagon.io/computer/troubleshooting/connection-performance.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.