# Argh94/Proxy-List: Hourly Refreshed Proxy and VPN Config Files for Developers and End Users > Argh94/Proxy-List aggregates public proxies and VPN configs into categorized text files and folders, refreshed every hour. It is a simple data source, not a service, and its usefulness depends on how you handle the lack of quality guarantees. **Argh94/Proxy-List** — The repository is refreshed every hour and offers categorized, ready-to-use text and config files for both developers and general users. - Repository: https://github.com/Argh94/Proxy-List - Stars: 242 · Forks: 16 - Language: Unknown - License: not declared - Published: 2026-08-21 · Updated: 2026-08-21 · Language: en - Canonical page: https://hysenlabs.com/projects/argh94-proxy-list ## What This Repository Actually Provides Argh94/Proxy-List solves a narrow problem: it gives you a regularly updated collection of proxy and VPN configuration lines in plain text files. The README lists HTTP, HTTPS, SOCKS4, SOCKS5, MTProto, WireGuard, Trojan, VLESS, VMess, Hysteria, and Tuic as supported categories. Each category maps to a file or folder, such as http.txt for HTTP proxies or wireguard/ for WireGuard configs. The target audience splits into two groups. Developers can use the files to rotate server IPs or automate proxy switching in scripts. End users can paste MTProto lines into Telegram or import VPN configs into clients. The project is not a proxy service itself. It is a data feed, and that distinction matters for every decision you make about using it. ## How the Hourly Refresh Works The README states that the repository is refreshed every hour. It does not explain the scraping mechanism, the source list, or the validation process. Based on the description, an automated job gathers proxy and VPN config strings from Telegram channels and websites, then writes them into the repository's text files. This means the data flow is one-way: sources to files, with no feedback loop for performance. The only quality control mentioned is that proxies are publicly scraped, so uptime and speed vary. There is no mention of testing each proxy before publication. As a result, the hourly refresh is a freshness promise, not a reliability promise. You should expect dead entries and slow connections, and you will need to filter the list yourself. ## Getting Started: Commands and Config Keys The README gives no command-line setup because there is no code to install. You simply browse the repository and download the files. For Telegram, the instructions are concrete: open Settings, go to Data and Storage, then Proxy Settings, add an MTProto proxy, and paste a line from mtproto.txt. For browsers or games, you take an IP and port from http.txt or socks5.txt and enter them into your app's proxy settings. For VPN clients, you import config files from the wireguard/, v2ray/, trojan/, hysteria/, or tuic/ folders. There are no config keys to adjust, no API endpoints, and no build steps. The repository is a static file dump, so the only real operation is fetching a raw file, for example with curl or wget. That simplicity is an advantage if you want to script a download, but it also means you get zero tooling for testing or rotating proxies. ## The Lack of Quality Control Is a Real Constraint The README warns that proxies are publicly scraped and performance may vary. That warning is the core limitation. Because there is no mention of uptime checks, speed tests, or geolocation verification, you cannot trust any single line to work. A proxy that works at the hour of refresh may be dead ten minutes later. For developers building a proxy pool, this means you must implement your own validation layer, which can be more work than the repository saves. For end users, the practical effect is that you will spend time testing multiple entries before finding one that connects. The project is also the wrong tool if you need a stable, authenticated proxy for a business application. Public scraped proxies are inherently ephemeral and often blocked by major services. The absence of a license file compounds the issue: you have no legal clarity on how you can use or redistribute the collected data, so any serious integration should pause until the maintainer adds a license. ## A Real Alternative: Commercial Proxy Services or Self-Built Scrapers The closest alternative to Argh94/Proxy-List is a commercial proxy service that sells access to a vetted, rotating proxy pool. Services like Bright Data or Oxylabs offer APIs, uptime guarantees, and location filtering. The difference in approach is fundamental: Argh94/Proxy-List gives you raw, unvalidated data for free, while commercial services charge a fee and provide a managed infrastructure that tests proxies, rotates IPs, and handles failover. If you need reliability for web scraping at scale, the commercial route is more expensive but saves engineering time. Another alternative is to build your own scraper that pulls from the same public sources and runs continuous health checks. That gives you full control over validation and licensing, but it requires significant maintenance. For a quick, free, and dirty proxy list, Argh94/Proxy-List works. For anything that needs consistency, it does not. ## Maintenance and Upgrade Cost The repository is archived: no, meaning it is still active, but the last push date is unknown, and there are no recent releases. The README invites contributions to add sources, report dead proxies, and submit pull requests. That suggests the maintenance model relies on community effort plus the automated hourly refresh. The upgrade cost for you is low in terms of installation, but high in terms of integration. You will need to write scripts to fetch files, parse lines, test connectivity, and prune dead entries. There is no versioning scheme, so you cannot pin to a stable snapshot. The hourly refresh means the file contents change constantly, which can break any system that expects a consistent set of endpoints. The license is listed as 'No license specified', which means you have no explicit permission to reuse the data in your own projects. That is a legal risk, not a technical one, and you should treat it as a blocker for any commercial use until the maintainer clarifies. ## Who Should Use This and What to Check First This repository is for developers who need a quick source of public proxies for testing or low-stakes tasks, and for end users who want to bypass regional blocks on Telegram or streaming sites. It is not for anyone who needs reliable, secure, or legally clear proxy infrastructure. Before you rely on it, verify three things. First, check the commit history to confirm the hourly refresh is actually happening. Second, download a file and test a sample of lines against your target endpoint; the README's own warning about varying performance means you should expect failures. Third, review the repository's license status. With no license, you cannot assume you have the right to redistribute the data or use it in a commercial product. If those checks pass for your use case, the files are easy to fetch and parse. If they do not, you should look for a licensed alternative or build your own validation layer. ## Conclusion Adopt Argh94/Proxy-List if you need a quick, automated source of public proxy and VPN config lines for testing, scraping, or personal access, and you can tolerate high churn and no uptime guarantees. Do not use it for production traffic, sensitive data, or any activity where a dropped connection is unacceptable. Before relying on it, verify the freshness of the files by checking the commit timestamps, test a sample of lines against your target service, and consider that the repository has no license, so you should contact the maintainer or find an explicitly licensed alternative if redistribution matters to you. ## FAQ ### What is in the Argh94/Proxy-List repository? Fourteen files at the top level and no directories: HTTP.txt, HTTPS.txt, SOCKS4.txt, SOCKS5.txt, MTProto.txt, WireGuard.txt, Trojan.txt, Hysteria2.txt, Tuic.txt, ShadowSocks.txt, ShadowsocksR.txt, All_Config.txt and singbox.json, plus the README. The files are rewritten every hour. ### How do I use a proxy from Argh94/Proxy-List in Telegram? For Telegram the documented route is Settings, then Data and Storage, then Proxy, then Add Proxy, selecting MTProto and pasting a line from the MTProto file. Note that the README names it `mtproto.txt` while the actual file is `MTProto.txt`, and the case difference breaks a raw fetch. ### Is Argh94/Proxy-List licensed? No. The README states that no licence is currently specified, asks users to use the material responsibly, and invites a licence suggestion through a pull request. No licence file or licence identifier is present in the repository. ### Does Proxy-List let me filter by ping, speed or country? The feature list claims selection by ping, speed and location, but no filtering mechanism is described. The published files are plain text lists of addresses with no index, metadata or documented schema, so those sort keys cannot be applied to them as published and the selection step is left to you. ### Where are the VMess and VLESS configs in Proxy-List? The README promises a `v2ray/` directory for them, and the repository has no such directory and no VMess or VLESS file. The one artifact that could carry multiple protocols is the undocumented `singbox.json`, a client configuration rather than a list. ## Sources - [Official README](https://github.com/Argh94/Proxy-List#readme) - [Project repository](https://github.com/Argh94/Proxy-List) - [README](https://github.com/Argh94/Proxy-List/blob/main/README.md) - [Releases](https://github.com/Argh94/Proxy-List/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/argh94-proxy-list