Torzon Gateway Connectivity Bulletins

Twelve burnt obfs4 bridge IPs replaced this week after enumeration was confirmed on two ISP-level firewalls in South Asia. The published bridge manifest is signed with the same PGP fingerprint as before — only the IP set changed. Users on the affected networks should pull the fresh list from the mirror page and re-import.

The volunteer WebRTC proxy pool that backs the snowflake transport added approximately 1,200 new proxies through the month of April, focused on capacity for high-censorship regions where bridge IPs are burnt within hours of publication. End-to-end latency on Mirror β behind snowflake remained within the previous 200–280 ms band despite the larger churn surface.

Following two months of accelerated IP enumeration in three national firewalls, we shortened the obfs4 fingerprint rotation cadence from monthly to weekly. The published bridge manifest is regenerated and re-signed every Sunday at 00:00 UTC. PGP fingerprint of the signing key is unchanged and remains documented under Network Security.

Both Orbot 17.x on Android and Onion Browser 3.x on iOS now successfully reach all three Torzon mirrors over the recommended transport for each region. QR-code bridge import was tested on a clean install of each app; first-attempt connection time on 4G mobile data measured 6–11 seconds for obfs4, 9–14 seconds for snowflake. meek-azure remains more limited on iOS due to Apple's networking restrictions.

The self-host walkthrough is now live. It covers provisioning a $5/month VPS in a friendly jurisdiction, building obfs4 from source, and generating the bridge line to share with family or colleagues stuck on the same firewall. Targeted at users whose social graph keeps hitting the same blocks and benefits from a low-traffic dedicated entry point.

The meek-azure tunneling configuration was re-tested through three new corporate network policies that whitelist HTTPS only to a small set of known CDN fronts. Mirror γ remained reachable in all three test cases with end-to-end latency between 280–340 ms. The configuration documented under Connectivity Features requires no change.

The annual re-signing pass of the mirror manifest was completed on 15 January. The signing key did not rotate — its fingerprint remains 8C71 4F25 6A93 D182 E574 B91C 3D67 8F45 A2D6 C918, unchanged since the Gateway launched in 2022. Only the manifest contents (mirror addresses + valid-until timestamp) were updated.

The reachability monitor on the home page now sources from probe nodes inside three of the most aggressively filtered networks we have access to — one in East Asia, one in Central Asia, and one in West Asia. Status indicators reflect actual conditions inside the firewall, not the friendly side of it.