Live checked TUIC servers
Fresh TUIC QUIC endpoints verified through a complete UDP tunnel, HTTPS request and changed public exit IP.
Fresh TUIC QUIC endpoints verified through a complete UDP tunnel, HTTPS request and changed public exit IP.
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.
| Endpoint | Connection | Exit IP / country | Performance | Checked / stability | Source | Config |
|---|---|---|---|---|---|---|
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 |
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.
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.
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.