Skip to main content

Filter TUIC servers

More filters

About measurements and countries

Filters apply to the full catalog. Speed is the measured download rate. Latency is the HTTPS response time through the tunnel. Unknown measurements are excluded when a limit is set.

Success rate uses saved check attempts in the last 7 days, including failures. Proxy history retains up to 100 checks per configuration. This is a sample, not continuous uptime. A rate filter requires at least 5 checks; increase the minimum checks for a larger sample.

Exit country is an approximate location of the verified exit IP. IP Geolocation by DB-IP (2026-10, CC BY 4.0). Unmapped addresses appear as Unknown.

Recently verified TUIC endpoints

Each source catalog applies its freshness and publication checks. A row requires a real protocol tunnel, successful HTTPS traffic and a public exit IP different from the checker’s direct IP. Reachable ports and source-reported status are excluded.

Search indexing paused: insufficient qualified history. The gate requires at least 10 unique endpoints, 3 independent sources and 7 qualifying days in the last 14. The page remains available with noindex,follow while evidence accumulates.

EndpointConnectionExit IP / countryPerformanceChecked / stabilitySourceConfig
UDPTLS
146.235.16.130Singapore
Speed3 MbpsHandshake839 msHTTPS1427 ms
100% successful 1/1 checks · last 7d · small sample MK Studio TUIC candidates Download
UDPTLS
146.235.16.130Singapore
Speed1 MbpsHandshake2297 msHTTPS3108 ms
100% successful 1/1 checks · last 7d · small sample MK Studio TUIC candidates Download

TUIC JSON API

Use /api/v1/servers?protocol=tuic&status=online to retrieve the same fresh, downloadable and full-tunnel-verified rows without scraping this table. The response includes stable public IDs, transport metadata, the observed exit IP, checker timings and the current config download URL.

Open the TUIC API guide or read the complete API v1 documentation.

About TUIC

A TUIC client opens a TLS-protected QUIC connection, authenticates, and multiplexes proxy traffic through that connection. Current clients and servers need compatible protocol versions and congestion-control settings. Full-device routing is supplied by the client, not by the share-link format alone.

What a working configuration needs

TUIC requires a complete UUID/password pair and UDP-capable checking; incomplete metadata is never listed as working.

Connection material is quarantined and never printed in tables or logs. A download is returned only for a fresh full-tunnel result whose exact URI is still present in an allowlisted public source permitted by the publication policy.

Unknown public infrastructure may observe or manipulate traffic. Do not use community endpoints for banking, work accounts, private source code or other sensitive activity. Read the public endpoint risk guide.

Read the complete TUIC protocol, configuration and troubleshooting guide.