Hello,
I have to get rid of criticism of you again.
What do I need to see, in version 1.26? You’re now adding a bandwidth limit? Are you really serious now? This has never happened before, and you don’t see it with any other VPN provider. And you don’t inform customers about it? Sorry guys, but you’re clearly going a step too far!
What’s the point of this nonsense? How do you come to that conclusion? This is very customer-unfriendly and does not correspond to a VPN provider that restricts its customers. What is 2 TB? They’re gone in no time, donwloads, surfing streaming and so on and so forth…
Other problems seem unimportant to you, like lockdown mode, etc. But you can quickly implement a bandwidth restriction. And then you should also write to you if you want more bandwidth? But certainly only for a fee.
I don’t think we’re going down well with customers like this. I can guarantee you!
Greetings
Gerhard
I never pass 2TB, but I could guess it would be useful for Mixnet usage only, to not overload the Mixnet with torrents downloads etc.
1 Like
Hello, thank you for your reply.
It may well be that you never or rarely exceed 2TB. But did you know they were introducing this? Were you informed about this by Nym? But the fact that it has now been introduced quietly and secretly and the customer has not been informed about it, I do not think is fair and not good. No other VPN provider (that I know of) limits the use of the VPNn’ or bandwidth, but Nym does it. It is and was introduced secretly without the customer knowing about it.
I wonder what that’s all about?!
You pay something but only get a limited benefit and if you want more, you are asked to pay. Or you still have to justify to support why you need the more bandwidth you want.
They are welcome to do this with the mixnet, but not with normal surfing.
But not even the basics have been incorporated yet, like:
- Lockdown mode
- Automatic connection when the computer starts
- no protection against AI snooping/location
- no protection against being recognized as a VPN customer, as X does
- App start after computer restart takes an extremely long time to start.
And much more! They promise a lot but don’t implement! But there is a bandwidth limitation, as they are very quick to introduce/build this, instead of finally getting their construction sites (errors, missing functions, etc.) finished.
Gerhard
Well, I for myself are quite happy with what NymVPN offers. But you can be rest assured that the Nym team is always listening to it’s customers and always quick in implementing proposed things. Well, that at least is my impression.
1 Like
The bandwidth limit exists because your subscription gets converted into NYM token purchases that fund the node operators running the network. A bandwidth cap is just what your subscription actually buys when it has to pay hundreds of independent node operators to keep running.
While it may be painful, it’s not just some arbitrary decision Nym decided to implement.
Without a cap, a small number of heavy users could easily overwhelm the node operators’ infrastructure. Every byte gets multiplied across multiple hops, so one person torrenting 20TB actually costs the network 40-100TB of aggregate bandwidth across operators. Their VPS costs would blow past what they’re earning in rewards, and the rational thing to do at that point is shut the node down. The bandwidth limit is basically what keeps the operator economics viable, without it the whole incentive model falls apart.
5 Likes
Makes sense! Edit: I selected to reply to the official Nym response but i don’t think it captured that in my original post (may be a bug). I’ll just add that that is probably the best reasoning for a vpn throttle possible and makes total sense; definitely needed (a potential downside of a dvpn of this nature).
While the tone of these posts (and poor grammar (not that i am much better)) annoy me, im grateful for @stryken bringing these issues/potential issues to the forefront and making the community aware. Edit again: Nvm i see where it captured the reply 
1 Like
Hi @strykenKN, the bandwidth limit isn’t new. It’s been there since the beginning but may have surfaced as slightly different errors in older app versions. You can read more about it in our help centre article here.
We’re actively working through requests from users hitting this error, and in most cases we can top up your bandwidth at no extra cost (though this may change if network abuse is detected).
We’re also working on more accurate handling of bandwidth tickets and an anonymous top-up flow so users won’t need to contact support at all.
As for the other features you mentioned, they’re on our radar. Ad blocking, custom DNS, and alternate login methods were all community requests from recent months, and all of them are already part of our latest releases!
1 Like