olcRTC is the transport for networks where Reality, Hysteria2 and XHTTP are blocked. Your app joins a video call on a major video-conferencing service, where the exit node's olcRTC server is waiting in the same room; your traffic travels as the call's data and leaves to the internet from the exit node. A network observer sees a video call.
What to expect
- It is metered and charged. Every user has a personal olcRTC key and the node counts bytes per key. Until 20 November 2026 olcRTC traffic is charged at the price locked into your route to that node, like any other transport. From then on it has the network's own olcRTC price, one price per GB for every exit and route, read when the traffic moves and not locked when you connect. A rise is announced at least 30 days ahead, and the olcRTC page lists the steps.
- It carries UDP, so voice and video calls and games work over it.
- It exits from the node's own IP. WARP does not apply to olcRTC: it works in the node's Xray, which olcRTC does not pass through. Torrent Guard's BitTorrent detection works there too, so it does not see olcRTC traffic; the connection watch counts its destinations, which the olcRTC server hands it, the exit itself drops what it sends to the BitTorrent and DHT ports, BitTorrent handshakes sent in the clear and DHT queries, and the upload check applies as on any transport.
- It is slower than the other three: a video call has limited bandwidth.
- Each exit takes a limited number of olcRTC users at a time. When an exit is full, its olcRTC line is left out of your list until a place frees up.
- It always goes to the exit directly. On a 2-hop route the olcRTC line reaches the exit through the video service, not through the entry node.
Why one location shows up more than once
Some exits can be reached through more than one video service. Your list then shows the same location more than once: the plain line and ones ending in · WB, · SJ and · VK. Each is the same exit, with the same key, over a different video service. Keep them all: if the one you normally use will not connect, because that service is blocked on your network or the room is busy, try the next.
Which apps run it
olcRTC needs an olcRTC-capable app. Happ, Hiddify and V2RayNG cannot run it; the open-source Ghostlane can. In the dashboard's Subscription URL block, choose Ghostlane, copy the URL and add it in the app. Transports in subscription can narrow that list to olcRTC alone; All keeps Reality, Hysteria2 and XHTTP beside it.
For operators
olcRTC runs on exit nodes whose operator switched it on, and its traffic counts toward the node's bytes and earnings like the other transports; from 20 November 2026 the exit earns 80% of the olcRTC price for it. See olcRTC carriers.