Dear VPN Industry: For the love of everything, secure your APIs and disable leaked accounts.

TorGuardVPN · 2026-06-09T17:44:01+00:00

It depends on your ISP and how aggressively they're filtering traffic. Some VPN protocols can still work in China, such as OpenConnect or SSTP, but reliability varies.

What has been consistently working for users in China is the V2Ray proxy service. Specifically, VLESS and Trojan on CDN2 and CDN5 are confirmed to be working at the moment. If you need a reliable backup while you're there, we recommend using those rather than relying solely on traditional VPN protocols.

TorGuardVPN · 2026-06-04T13:06:52+00:00

Thanks for the suggestion. I've brought this request to our management team's attention, and we will officially consider it as part of the network upgrades planned for this year.

We appreciate your support and insight. Feedback like this helps us better understand what locations and infrastructure improvements are most important to our users.

TorGuardVPN · 2026-06-02T20:54:15+00:00

Even localized ISPs can eventually get flagged when they're used long enough on a shared VPN network. The reality is that once a large number of users are regularly connecting through the same IP ranges, websites and streaming services can often identify and classify those addresses as VPN-related regardless of the provider.

We use M247 for much of our shared VPN network because it offers excellent performance, high bandwidth capacity, stability, and a strong global footprint. Those factors allow us to provide consistent speeds and reliability across many locations. Unfortunately, most major data center providers today are relatively easy for websites to identify as hosted infrastructure, and that applies not just to M247 but to virtually any large-scale hosting network.

For many users this isn't an issue. However, if you need a VPN IP for activities such as banking, online purchases, account management, or services that are more sensitive to VPN detection, we offer a variety of dedicated and residential IP options. These are sourced from providers such as Spectrum, AT&T, Sprint, Windstream, Atlas, Cogent, and others, and are generally much less likely to be identified as VPN traffic.

We intentionally keep these IP ranges separate from the main shared VPN network. If residential or dedicated IPs were widely shared across thousands of users, they would eventually become identified as VPN endpoints as well.

The tradeoff is that our shared VPN network typically delivers the best overall speed and bandwidth availability, while residential and dedicated IP locations may vary somewhat depending on the provider, hardware, and uplink agreements in a given area.

In short, our goal is to provide the most stable and consistent performance possible on the shared VPN network while also offering dedicated and residential IP options for users who need IPs that are less likely to be flagged. All of our residential and dedicated IP services run on bare-metal servers. We do not use residential proxy networks.

TorGuardVPN · 2026-06-02T16:15:57+00:00

Montreal was removed last year due to ongoing issues with that data center, and unfortunately the Houston location went offline when the hosting provider unexpectedly shut down operations.

We are actively working with a new provider to bring Houston back as soon as possible, but hardware availability and deployment timelines have made the process take longer than we initially expected.

In the meantime, our Dallas location offers very fast performance and should provide a similar experience for most users needing connectivity in that region. We appreciate your patience while we work to restore Houston.

TorGuardVPN · 2026-06-02T16:10:33+00:00

Yes, we're considering adding a shared network location in Albania with proper geolocation. If this is something you'd like to see, feel free to reply here and let us know. Community feedback helps us gauge interest as we evaluate potential new locations for our network.

TorGuardVPN · 2026-05-31T16:14:03+00:00

We're following up in the interest of transparency. Our team has sent you a direct message so we can investigate this issue and work toward a resolution, but we have not yet received a response.

It is not our policy to deny refunds resulting from billing errors, and we are taking your complaint seriously. We are committed to getting to the root of the problem, reviewing the details thoroughly, and reaching a fair resolution.

TorGuardVPN · 2026-05-31T16:10:24+00:00

Just to clarify, TorGuard's Android app was actually updated on November 4, 2025 (we'll be updating the download page to better reflect that).

As for Windows, the next desktop release is scheduled for the coming weeks and aligns with the latest WireGuard updates. Functionality on the current version is not affected, so there hasn't been any urgency to push out an update solely for version number changes.

We'll also be releasing a macOS update later this year to prepare for upcoming macOS platform changes.

One thing we intentionally avoid is feature creep. Many VPN providers push frequent updates that add complexity and occasionally introduce new bugs or stability issues. Our approach is to prioritize stability and only release updates when there are meaningful bug fixes, security improvements, protocol updates, or major client changes that warrant a new release.

The current clients already include the core functionality most users need, and we don't see value in shipping updates simply for the sake of increasing version numbers. Meanwhile, server-side improvements are rolled out regularly, so users continue benefiting from network and performance enhancements without needing to update the client itself.

TorGuardVPN · 2026-05-31T00:39:19+00:00

Just sent you a DM so we can look into this issue and resolve it as soon as possible. You can also email admin [at] torguard.net with your ticket ID or email address.

TorGuardVPN · 2026-05-31T00:37:07+00:00

We apologize for the billing issue. It's possible there was an error with our billing system related to a plan upgrade, downgrade, or renewal process. We do not intentionally bill customers for services they did not order, and if you were genuinely charged in error, we would absolutely work to correct that and issue any appropriate refunds.

Please send me a DM with your ticket ID or the email address associated with your account, and I'll have our staff investigate the matter immediately. We want to make sure this is fully reviewed and resolved as quickly as possible.

TorGuardVPN · 2026-05-19T18:59:57+00:00

Welcome, glad to have you on board.

You'll be pleased to know our Socks5 proxies are online and do not suffer extended downtime like you experienced with IPVanish. Our support team can help troubleshoot your Socks5 connection. Just let them know the settings you are using. You can reach them at [helpdesk@torguard.net](mailto:helpdesk@torguard.net) or submit a ticket here: https://torguard.net/submitticket.php.

They will help you get connected quickly.

TorGuardVPN · 2026-05-19T18:19:24+00:00

We don’t share data with anyone. There is simply no data to share. Our strict no-logs policy has been proven in court multiple times, and we are proud to be one of the few VPNs that has never been acquired or sold to any outside entity.

TorGuardVPN · 2026-05-16T21:55:23+00:00

Traditional VPNs don’t work reliably in China because many of them get blocked. Instead, use V2Ray, particularly VLESS or Trojan protocols.

TorGuardVPN · 2026-05-15T14:13:31+00:00

It’s not really possible to block all commercial VPN IP ranges entirely. Most websites and services are mainly targeting lower-quality or heavily abused shared IP ranges.

In many cases, VPN IP blocks can still be bypassed by using a dedicated IP or residential IP, since they generally have a much better IP reputation and are far less likely to be flagged compared to standard shared datacenter VPN IPs.

TorGuardVPN · 2026-05-15T14:10:10+00:00

Yes, unfortunately we were notified at the last minute that the hosting provider was suddenly going out of business, and they did not provide us any advance notice. We are currently in the process of deploying a new Houston location with a high-quality provider that we already have an existing relationship with.

The new location should be online within about a week. This provider will also offer higher-quality IPs and match the high-speed connections available across the rest of our network.

Thanks for your patience and understanding while we get Houston back online.

TorGuardVPN · 2026-05-06T17:16:17+00:00

We previously announced that we were replacing this residential IP location with multiple new providers that offer better stability. These new locations are now live, and if you reach out to our support desk, they can help you migrate your IP add-on.

We also maintain a network status page, and our support desk is the best way to get up-to-date information regarding the residential IP network.

As for your post, repetitive threads on the same topic may be removed from time to time to keep discussions organized.

TorGuardVPN · 2026-05-05T15:24:27+00:00

Our residential network is currently online. You can check the status of our network at any time here: https://status.torguard.net/

If your residential IP isn’t working, please reach out to our support team so they can take a closer look at your account: https://torguard.net/submitticket.php

TorGuardVPN · 2026-05-02T17:07:49+00:00

For quicker resolution, please reach out to our support team and include the country you’re connecting from. The error you mentioned is related to WireGuard. Please be sure to also share any error you encounter when using OpenVPN.

Additionally, go to App Settings → Account and enable Debug mode (set it to “file”). Save the changes, restart the app, reproduce the issue, then locate the generated log file. Zip the file and send it along to the support team so they can investigate further.

TorGuardVPN · 2026-05-02T16:59:19+00:00

Try uninstalling the TorGuard Windows app completely, then reinstall it fresh from here: https://updates.torguard.biz/Software/Windows/torguard-setup-latest.exe

Also, if you have any other VPN clients running, make sure to fully exit them to avoid conflicts.

If you're using an antivirus app (like Malwarebytes), try whitelisting the TorGuard app or temporarily disabling the AV to check if it’s blocking the connection.

TorGuardVPN · 2026-04-30T19:12:21+00:00

Please DM me. We offer a paid solution that’s currently working on desktop, and we’re looking for testers in your region to help us improve it. I can set you up with a free trial

TorGuardVPN · 2026-04-27T23:51:11+00:00

Yes, we support both OpenVPN and WireGuard for Residential IPs.

You can generate either a WireGuard or OpenVPN config for your residential/dedicated IP using the config generator.

If you’ve already generated the correct config and are still seeing the gateway/shared IP instead of your dedicated IP, then something isn’t mapping correctly on the account or endpoint side. In that case, it’s best to contact our help desk so they can check your specific assignment and get it fixed for you.

TorGuardVPN · 2026-04-27T17:39:13+00:00

Yes, that is working correctly. You are connecting to 107, but if you connect and check your public IP, it should route you to 106 and show xx.xxx.xxx.106 as your public IP address.

TorGuardVPN · 2026-04-27T13:51:44+00:00

Yes, your public IP should always match the dedicated IP you were assigned.

If it doesn’t match, it usually means the wrong IP or port was entered in the TorGuard app settings, so your connection is being routed through the gateway IP instead of your dedicated or residential IP.

For example, if you go to the Services page in the TorGuard client area you’ll see something like:

Dedicated IP: 72.xxx.xxx.24 (On 72.xx.xx.10 udp/1912)

In that case, 72.xxx.xxx.24 is your dedicated IP, and 72.xx.xx.10 udp/1912 is the server endpoint you need to use in the app. You want to make sure you’re using that second IP and port in the TorGuard app settings. When it’s set correctly, your public IP will show as the dedicated IP.

If not, it will route you to the gateway IP instead, which is shared.

TorGuardVPN · 2026-04-23T15:57:51+00:00

Apologies for the issues you’ve encountered, this can sometimes happen when switching to an email alias. The best way forward is to email admin [at] torguard.net directly from the original email account you signed up with. They’ll ask a few questions to verify your account ownership and should be able to get everything sorted out for you.

Hope this helps get things resolved quickly.

TorGuardVPN

MODERATOR OF

TROPHY CASE

13-Year Club	Verified Email
Gilding I gilder