- SOCKS5
- HTTP
- Static IP
Gaming proxies with static Turkish IPs
Dedicated packages for Knight Online, Metin2 and Silkroad. Each one is a static Turkish IP you can use over SOCKS5 or HTTP, starting from a single address.
Packages
Gaming proxy packages
These titles have dedicated packages with a live order page. Every package is a static IP with HTTP or SOCKS5 selectable at checkout.
Knight Online Proxy
Static Turkish SOCKS5/HTTP IPs for Knight Online, from 1 to 250 IPs.
FromTRY 60 / monthExploreMetin2 Proxy
Static Turkish IPs for Metin2, from 1 to 250 IPs with SOCKS5 or HTTP.
FromTRY 60 / monthExploreSilkroad (Private SRO) Proxy
Static Turkish IPs for Silkroad and Private SRO servers, from 1 IP.
FromTRY 60 / monthExplore
Why static IPs
Why players choose static Turkish IPs
A fixed address
The IP stays the same through the plan, which keeps your account’s apparent location consistent.
Local, Turkish routing
IPs are Turkey-based from Turkish ISP networks listed by the provider, so you appear as a local player.
SOCKS5 for any client
SOCKS5 forwards the game’s own TCP connections without needing special support in the game.
From 1 IP up
Start with a single IP for one account or scale to hundreds for larger setups.
Other games
The same static Turkish IPs are asked about for other online games. These titles do not have a dedicated package page here — contact us on WhatsApp and we will tell you honestly whether our IPs suit your game.
- Albion Online
- Aion
- Black Desert
- Growtopia
- Lords Mobile
- New World
- Path of Exile
- RuneScape
- World of Warcraft
- Steam
Game names are trademarks of their respective owners and appear only to identify intended use. BuyProxy is not affiliated with or endorsed by any publisher, and no official logos or artwork are used.
Account-safety checklist
- Read the game’s terms; some prohibit proxies or running multiple clients.
- Use one IP per account unless the rules explicitly allow sharing.
- Never share your proxy credentials.
- Avoid changing IPs repeatedly on the same account.
- Test latency yourself — no ping or compatibility is guaranteed.
Setup
Connect your game client
Order and choose SOCKS5
Pick the number of IPs and billing period, then select SOCKS5 (or HTTP) on the order page and complete the purchase.
Use a proxifier for the game client
Most game clients have no proxy settings. A proxifier-style program forwards the client’s connections through your proxy.
Add the proxy and a rule
Enter host, port and credentials as a SOCKS5 server, then create a rule so only the game’s executable uses it.
Verify before you play
Check the exit IP with the IP tool and test the connection with the proxy checker before logging in.
In depth
The details that decide the outcome
How proxifier-style routing works
Most game clients have no proxy setting. They call the operating system’s socket functions to open TCP connections straight to the game’s servers. A proxifier-style program sits in the way: it either injects a small library into the chosen process to intercept connect calls, or uses a network filter driver to redirect that process’s connections. For each intercepted connection it opens its own connection to your SOCKS5 server, performs the handshake and a CONNECT request carrying the original destination, and then relays the bytes. The game keeps working as if it were connected directly.
Rules decide which connections take the proxy path. They are evaluated top to bottom and the first match wins, so put the specific rule for the game executable above a default rule set to Direct. Match by executable name rather than by destination address, because game hosts and ports can change after a patch. Decide deliberately about launchers and patchers: if the launcher is a separate executable and stays Direct while the game client uses the proxy, any authentication the launcher performs reaches the server from your real address and the play session from the proxy address. The connection log shows what actually happens.
Two practical details save hours. First, run the proxifier and the game at the same privilege level: a normal-user proxifier cannot hook an elevated process, and the symptom is an empty connection log. Second, enable name resolution through the proxy; if the client already resolved the name itself, the log simply shows an address. Either way the log lists the real hostnames and ports your client opens, which is the ground truth for any rule you write and a useful record to share with sales if something fails.
| Setting | Suggested value | Why |
|---|---|---|
| Proxy server | SOCKS5, with the host, port, username and password from your order | Matches the protocol selected at checkout |
| Rule applications | The game executable only | Keeps browsers and other programs on your own connection |
| Rule action | Use the SOCKS5 proxy | Sends only matched connections through the proxy |
| Default rule | Direct | Stops unrelated traffic from using the proxy |
| Name resolution | Through the proxy | Hostnames are resolved on the proxy side |
| Connection log | Enabled during first tests | Shows hosts, ports and which rule matched |
Latency, UDP and disconnects
A proxy adds a hop, so the right way to reason about latency is arithmetic, not hope. The delay you feel is roughly the round trip from you to the proxy plus the round trip from the proxy to the game server. As an illustration, if you reach a Turkish proxy in 20 ms and the proxy reaches the game server in 15 ms, you pay about 35 ms through the proxy against 30 ms on a direct path, a difference of 5 ms. Distance to either end makes the sum bigger. Nothing here promises lower ping.
UDP deserves a separate check. A SOCKS5 CONNECT request carries TCP only; UDP needs the UDP ASSOCIATE command, which both your proxifier and the proxy must support. Of the plans in this catalog, UDP over SOCKS5 is listed only for static mobile proxies, not for the gaming packages, so assume TCP only for gaming IPs unless sales confirm otherwise on WhatsApp. If a title also uses UDP for voice or other features, a proxifier may pass that traffic directly, exposing your real address, or drop it. Check the connection log for UDP entries before assuming everything went through the proxy.
Disconnects usually fall into a few patterns, and the timing is the clue. A drop at the same moment every time, such as the switch from login to the world, points to a second process or connection that your rule does not cover, for example a helper started by the launcher. A drop after a fixed idle period points to a timeout somewhere on the path, in your router, the proxifier or the proxy. Random drops across the whole session suggest an unstable link between you and the proxy. Write down the time of each drop and compare it with the connection log before changing anything.
A pre-session test routine with the free tools
Run the same short routine every time you receive new IPs. First, put the entries into the free proxy checker, which detects HTTP or SOCKS5 automatically and accepts up to ten proxies per request; a 48-IP pack therefore takes five runs. A pass shows the exit IP and the latency; failures carry codes such as auth, refused, timeout or not_socks5 that say which stage broke. Second, use the SOCKS5 proxy checker on one entry to confirm method negotiation, username and password, and a CONNECT by domain name. Keep the table of results; it is your baseline.
Third, check the path your game will really use. Point a browser at the proxy by adding a temporary rule for the browser executable, then open the IP address checker: the address it shows should be the proxy’s exit IP, not your own. Fourth, run the port checker against the game’s login host and port, taken from the connection log; it makes one TCP connection from our server and reports open, closed or filtered. That tells you whether the server is reachable from the internet at all, not from your machine or through your proxy, so it separates a server outage from a local problem.
| What you see | Likely meaning | Next step |
|---|---|---|
| Checker passes but the game never connects | The rule does not match, or the game uses another process | Open the connection log and confirm the game appears in it |
| Checker times out | The proxy host is unreachable from the checker | Retry later, then send the host, port and error code to sales |
| Checker reports auth | Wrong or truncated credentials | Copy the username and password again from your order |
| Port checker shows closed or filtered | The server is down, in maintenance, or restricts the port | Check the game’s status channels and try again later |
| Exit IP differs from the one you recorded | Entries were mixed up, or the rule points at another proxy | Compare host and port with your order and fix the rule |
Read the game’s terms before logging in on a real account: some titles forbid proxies or multiple clients, and no test can tell you that.
FAQ
Gaming proxy FAQ
Do you guarantee low ping?
No. A proxy adds a network hop, so latency depends on routing and distance. We do not publish ping figures we cannot measure for your connection.
HTTP or SOCKS5 for games?
SOCKS5 in most cases, because it passes any TCP connection. Both are selectable at checkout.
Are these packages allowed by the games?
That depends on each game’s rules, not on us. Always check the terms before using a proxy on an account.
What about other games?
Other titles are handled on request through the same static Turkish IPs. Ask via WhatsApp; compatibility is not guaranteed.
How many IPs do I need?
One per account is the safest approach. Packages scale from 1 IP upward; larger packs lower the cost per IP.
How can I tell that my game traffic really goes through the proxy?
Open the proxifier’s connection log while the game connects: each line shows the destination and the rule that matched. Then confirm the proxy’s exit address with the proxy checker, and check a temporary browser rule against the IP address checker. If the game’s connections show as Direct, your rule is not matching.
What happens if the proxifier closes while I am playing?
The proxifier is the only thing routing the game through the proxy. If it exits or crashes, existing connections usually drop, and a client that reconnects goes out directly from your own address unless something blocks that. Start the proxifier before the game, and consider a firewall rule or a proxifier setting that stops the game executable from connecting directly.
Will I keep the same IPs when my plan ends or renews?
The IPs are static for the duration of the plan. This site does not document whether the same addresses are kept on renewal or when you order again later, so do not assume it. If a consistent account location matters to you, ask sales on WhatsApp before the plan expires.
Need a larger quantity or a custom location?
Tell sales what you need — we will confirm availability and the right order path.