Исследования

On 12 October 2026, as protests over a school dress code spread in Baku, Instagram and TikTok stopped loading for users across Azerbaijan. Public OONI measurements show the block on eight networks: DNS answers are correct and TCP connects, but the TLS handshake dies after the client names the site. Facebook, YouTube and X kept working. We read the raw measurements, compare them with the TikTok blocks of 2022 and 2023, and set out the filtering equipment and the laws behind them.

Adaptive Connect 4 moves the choice of server and protocol into a small scoring model on the device, adds city-level hints from other devices, detects allow-list networks and hides servers the device cannot reach. We ran the panel side on the live service and tested test builds on an Android phone and a Windows PC, plus the automated suites of all five apps. All 14 device and live checks passed, three only after a fix. We found nine problems: eight are fixed, one was a phone state cleared by a reboot. iOS, Linux and the extension were covered by automated tests only.

During an on-device test of Hysteria2 port hopping, traffic on an Android phone stopped after about a minute of a speed test, and the app moved to its TCP spare. The hopping was fine. We captured the packets, ruled out six other causes, reproduced the stall on one PC with the official Hysteria server, found that a target which stops reading blocks the whole QUIC connection, and patched the server with about 37 lines. It recovers in 7.8 seconds where the official build never does, and the fix is rolling out to the servers without an app update.

We cut protocols, injected resets, froze TCP flows after 16 KB, blocked UDP, dropped packets and took whole servers away, for one Android phone on a home Wi-Fi in Russia, with eleven faults in a fixed order. The first runs found two flaws in Adaptive Connect 2.0: a slow return to Hysteria2 after a UDP block, and a dead warm spare that was never replaced. Both are fixed in a test build; the second run could not yet prove the fixes, and we say why.

An outside reviewer suggested a test: let the tunnel handshake succeed but drop everything inside it, and see whether the app still calls the connection verified. We ran it on the Windows and Linux apps, during fallback and across a network change, and checked app traffic and DNS too. It found three problems; all are fixed.

From two consumer connections in Russia, TLS-based transports to one Dutch hosting network delivered only the first TCP segment of the handshake. The same clients connected normally elsewhere.