Recommended list: Top 100
Which file should I open?
top100.txt is the current recommended entry point. It is drawn from resilient proxies and prioritizes proven uptime then runner-measured latency while encouraging diversity across networks.
Per-network limits
The usual selection cap is five per network (ASN, or network prefix without ASN). The algorithm can raise the cap if the list could not otherwise be populated. The actual value is exposed in index.json as top100_info.network_cap.
Compatibility list
top50.txt remains available as the first 50 lines of Top 100 for existing subscribers, not as a separate verification category.
Understanding each tier
Verified
verified/ contains links that passed all three end-to-end rounds, including multiple aliases potentially pointing to one real server.
Resilient
resilient/ keeps at most one verified link per server IP to avoid counting duplicate hostnames as independent access.
Stable
stable/ requires at least 90% success over the published historical checks, with at least 12 checks as specified in the index criteria.
Fast
fast/ takes the fastest quarter of the resilient tier by runner-side median RTT; this does not measure speed at your ISP.
Secret types and countries
faketls/, secure/ and classic/ are verified subsets by MTProto secret type; countries/XX.txt groups by server geolocation.
Machine-readable data files
index.json
Overview of tier URLs, counts, criteria, last update time and runner location. Prefer these published URLs over guessed paths.
proxies.json
Per-proxy server, port, secret, type, country, ASN, RTT, uptime and source data when present.
health.json
Source health, diagnostic rejection reasons and contribution signals, as documented in the public README.
tg.txt and tme.txt
Telegram deep links and https://t.me/proxy links respectively, published inside tier folders.
Reading statistics correctly
Links are not servers
The verified link count can be much larger than the number of distinct servers. A single operator may publish many hostnames for one IP.
Geolocation and measurements
Country values use DB-IP geolocation; RTT is measured from the runner. These are descriptive fields, not connectivity guarantees.
Source: documented public repository and its README, criteria, and machine-readable files. Reviewed 27 October 2026. Live values can change every run. Inspect source