Skip to main content

Live checked VLESS servers

This table contains only endpoints that completed a real VLESS tunnel handshake in the isolated checker VM, carried an HTTPS request and returned a public exit IP different from the checker’s direct IP.

405 unique endpoints 1581 successful configurations 11 independent sources 15/14 qualifying days Snapshot 2026-10-09T06:38:46Z What is VLESS? How checks work Source policy VLESS API Validate a config VLESS vs VMess Trojan vs VLESS

Filter VLESS servers

More filters (2 active)
Min success rate (7d, %): 90 Min checks (7d): 10
Reset filters Stable servers Best speed Freshly checked Found: 0 / 405

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 VLESS endpoints

Checks expire from this list after three days. UUIDs, subscription URIs and REALITY keys are not embedded in the table or snapshot; an allowlisted URI is fetched only when its download button is used. A successful technical check is not an endorsement of the endpoint operator.

No servers match these filters. Try a higher latency limit or reset filters.

VLESS JSON API

Use /api/v1/servers?protocol=vless&status=online to retrieve the same fresh downloadable VLESS rows without scraping this page. API records include stable public IDs, transport and security metadata, the verified exit IP, tunnel timings and the current config download URL.

Read the VLESS API guide or open the complete API v1 documentation.

How downloads work

New to the protocol? Read what VLESS is and how TLS, REALITY, UUIDs and transports fit together before importing a public configuration.

The site does not store UUIDs in its public snapshot. When you request a URI for a recently verified endpoint, the download endpoint retrieves the allowlisted public source over verified HTTPS, matches its sanitized endpoint fingerprint and returns only the current VLESS URI. Downloads stop automatically when the tunnel check expires or the source removes the configuration.

A source can rotate a public UUID after a check without changing the host and transport. If that happens, the current URI may stop working until the next checker pass; the table never treats the download itself as fresh tunnel evidence.

Public endpoints can log traffic or change behavior without notice. Do not use unknown community infrastructure for banking, work accounts, private source code or other sensitive activity. See public VPN risks.