Shadowrocket Hysteria2 Guide: QUIC Performance and Network Compatibility

Learn how Hysteria2 uses QUIC and congestion control, how it performs on high-loss, long-distance links, and what to check when UDP is restricted.

At a glance

For Shadowrocket users who already have a service provider configuration, this guide explains how Hysteria2, QUIC, and UDP relate to one another. It distinguishes throughput, latency, and connection success rates, then walks through checking settings, comparing networks, and troubleshooting failures. Use it to assess whether Hysteria2 suits your current network instead of choosing a protocol based on a single latency test.

1. What Hysteria2, QUIC, and UDP Each Do

Hysteria2 in Shadowrocket is a proxy protocol option, not a network speed-up switch. It uses QUIC-based transport, which typically runs over UDP. UDP sends datagrams; QUIC adds encrypted connections, multiplexed streams, acknowledgments, and loss recovery; Hysteria2 provides proxy authentication and forwards requests. These operate at different layers, so using UDP does not mean there are no retransmissions or that a connection will always be faster.

For TCP proxy requests that require reliable delivery, QUIC streams must still deliver every byte in order. Lost data must be recovered, and later data in the same stream may have to wait for the missing bytes. One advantage of QUIC is that separate streams do not experience transport-level head-of-line blocking in the same way they would over a single shared TCP byte stream. However, all streams still share the connection's congestion and bandwidth resources.

UDP
Hysteria2's underlying transport
TLS 1.3
QUIC's integrated security handshake
443/UDP
Example port, not a fixed port for every service

The port is determined by your existing service provider's configuration. For example, 443/TCP and 443/UDP on the same address are separate transport endpoints: access to the former does not mean the latter is allowed. Hysteria2 does not require every service to use port 443. If your configuration specifies another port, check it as provided; do not change it to 443 just to make it “HTTPS-compatible.”

2. Why It Can Be Faster: Congestion Control and Network Conditions

Traditional loss-based congestion control typically reduces the sending rate when it detects packet loss, to ease network congestion. But wireless interference and traffic across different networks can also cause random loss, which does not necessarily mean the available bandwidth has been exhausted. If the sender consistently treats this kind of loss as congestion, usable throughput may fall below what the link can actually support.

Hysteria2 incorporates the Brutal congestion control approach: it uses a configured bandwidth target to control sending and adjusts based on loss feedback. The control method and available settings depend on the client, server, and negotiated configuration. It does not send data without limits or create bandwidth. Setting the target too high can cause queue buildup, more packet loss, and slower performance for other apps on the same network. Setting it too low can limit throughput unnecessarily.

Bottom line: Find the bottleneck before changing the bandwidth target

If sustained transfer speeds are low and round-trip latency is high, repeat the test on the same device, network, and destination. Adjust bandwidth settings only if your existing configuration provides them, and monitor latency under load as well—do not focus on download speed alone.

3. Which Networks Are Worth Testing—and When to Stop Tweaking

Hysteria2 is worth testing only if UDP can reach the server reliably and you already have a working Hysteria2 configuration. A protocol cannot make up for limited server capacity or bypass every network restriction. The comparisons below describe when it may be suitable; they do not promise specific results on any network.

UDP reachable, long-distance, with random packet loss

Recommended

Start with a side-by-side test. Record sustained transfer speed, latency under load, and any interruptions. Check whether improvements are repeatable; do not make a lasting switch based on a single test while the network is idle.

Best for: cross-region connections over a variable wireless link with a stable UDP path

Stable path with low latency and little packet loss

Keeping your current stable configuration is also reasonable. If speeds are already close to your local access or server limit, changing transport may not help. Compare connection success and how your apps actually respond first.

Best for: a stable local network where your current configuration already meets your needs

UDP blocked or consistently throttled

First check the network policy and whether the server is listening for UDP. If the path clearly does not allow UDP, use another existing configuration from your service provider that is permitted on the current network. Repeatedly raising the bandwidth target will not fix the restriction.

Best for: troubleshooting repeated connection timeouts that clear as soon as you switch networks

On shared Wi-Fi, faster downloads accompanied by severe video-call lag may indicate that queues are persistently filling up, not that the overall experience has improved. Lower the bandwidth target or reduce concurrency, and check the router's traffic management. Encrypted UDP traffic can also be throttled or restricted by network policies. Being able to browse websites over TCP does not prove that UDP is available.

4. Check Hysteria2 Settings in Shadowrocket

The steps below refer to Home, Config, and Settings on iPhone and iPad; layouts may differ on other platforms. Keep the original configuration from your service provider whenever possible. Add an entry manually only when they have supplied all the required settings. Hysteria2 and the earlier Hysteria do not necessarily use interchangeable settings, so do not change Type just because the names look similar.

  1. Keep the original configuration

    On Home, note the entry that currently works. In Config, check which configuration file is active. Keep the original entry before making changes so you do not mix up protocol issues with rule changes.

  2. Select the protocol

    To add an entry manually, go to Home → tap “+” in the upper-right corner → Type → Hysteria2. If the entry came from an existing subscription, check its Type first; do not put the subscription URL in the server address field.

  3. Check the connection details

    Compare the server address, port, and authentication password with the details from your service provider. If the port is 443, the server and network must still allow 443/UDP. The authentication password is not the same as an access token in a subscription URL.

  4. Check TLS

    Check the TLS server name and certificate requirements. When connecting by IP address, you may still need to enter the domain specified by your service provider as the SNI. If obfuscation settings are used, their type and password must also match the server.

  5. Verify the traffic path

    Save, return to Home, select the entry, and check the current mode in Global Routing. For a brief troubleshooting test, use Proxy to verify the proxy connection, then switch back to Config to check your rules. To rule out interference from automatic reconnection, check Settings → On Demand and note the original settings.

Proxy, Direct, Config, and Scene in Global Routing do not change Hysteria2's underlying transport. Proxy sends eligible requests handled by the client through proxy policies; Direct connects directly; Config follows the active configuration; and Scene applies behavior based on the selected scenario. Do not leave Global Routing set to Direct and then use access to a website to decide whether Hysteria2 is working.

5. How to Test Latency, Downloads, and Connection Drops

The latency test on Home reflects a particular test method and destination. A low result does not guarantee faster file downloads, and a timeout could mean the test method failed, the server is unreachable, or the protocol handshake failed. Before testing, note whether you are on Wi-Fi or mobile data, which entry is selected, the Global Routing mode, and the destination resource so you can reproduce the test.

Observed behaviorCheck firstNext step
The same configuration times out on Wi-Fi but connects on mobile dataWhether the Wi-Fi network blocks UDP, and whether router or upstream policies have changedKeep the address and settings unchanged, switch networks, and repeat the test; ask the network administrator about restrictions
Cannot connect on either networkAddress resolution, UDP port, authentication password, TLS, and server statusCheck each setting against the original configuration; do not change multiple fields at once
Connects and handles small requests, but sustained transfers stallUDP throttling, path MTU, congestion, and server loadReduce concurrency and the bandwidth target, compare on another network, then ask your service provider to check the path and server
Works with Proxy, but the destination behaves differently under ConfigRule matching, policy selection, and DNS resultsCheck the order of rules in the configuration and confirm that the request is actually being sent through the expected proxy
Works after connecting, then drops after sitting idleNAT mapping, network changes, background restrictions, or a server timeoutNote the conditions that trigger the drop. Test sustained foreground transfers and recovery after idle separately; do not assume the password is at fault

For each round, wait 30 seconds while idle, then download continuously for 60 seconds and note latency during the transfer. Repeat under the same conditions three times and use the middle result as a reference. This is a repeatable test procedure, not product performance data. If the test destination is throttled, results from another protocol do not represent the link's maximum capacity. On mobile data, keep an eye on data usage.

6. Keep Rules, Subscriptions, and Protocol Settings Separate

Hysteria2 determines how the proxy connection transports data; rules determine which policies requests use; and subscriptions provide and update connection details from a service provider you already use. Changing protocols will not automatically fix rules, and refreshing a subscription will not remove a local network restriction on UDP. First confirm that the connection itself works, then switch back to Config to check routing, and finally test your everyday apps.

Bottom line: Keep a stable configuration you can reproduce

Use Hysteria2 as your everyday connection only if sustained transfers, interactive latency, and connection stability all meet your needs under the same test conditions. If the UDP path is unreliable, keep your existing working configuration and give your service provider the network conditions, error details, and sequence of events to investigate.

Free download of Shadowrocket