Skip to main content

Filter VMess 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 VMess 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.

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

VMess JSON API

Use /api/v1/servers?protocol=vmess&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 VMess API guide or read the complete API v1 documentation.

About VMess

A VMess client authenticates with a UUID and carries proxy requests over the configured transport. Deployments may add TLS and use TCP, WebSocket or gRPC. Every layer must match the server. Client and server clocks also need to be reasonably accurate for compatible authentication behavior.

What a working configuration needs

VMess connection details are transport-specific; the client must preserve TLS, host, path and transport settings.

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 VMess protocol, configuration and troubleshooting guide.