New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Sue & chargeback!
It's interesting how a persistent issue like this can change the perceived value of a system.
the quailty of @hostsailor went down dramatically this few months, I for sure won't renew with them
Sorry for the misunderstanding. I am still a paying customer like you. I just moved out my services to another host cause having a video call server for example in this network doesn't work out.
What I ment is that my trust in hostsailor is broken since the issue (which in not a minor one) is ongoing for quite a long time and the guys there are apparently unable to deal with it.
OK - no problem. I read it as "just move to somewhere else, why bother". And yes, ofcourse I get critical processes away from it, but on the other hand it has been paid for.
I have no issues on my Romania VPS. Its been running very stable.
Romania != Amsterdam
Hello Everyone,
I just want to update that team is working to fix the issue. But it seems like continuous planned spam attack. Honestly this does not justify the problem but we are implementing new protocols to solve it permanently.
Please know, we genuinely feel your pain and frustration and working on it to fix issue on priority basis.
If you are facing issue and support team is not addressing properly, please reach to [email protected] with support ticket number and I'll take care of it.
Thank you.
you mean ddos attack? I dont get how "spam attack" can cause such packet loss over the whole NL network
Yea i didn't want to pick on that cuz i assume it's just a language/terminology glitch but the idea that you're absolutely destroying your connectivity to filter spam made me snicker a little bit!
Anyway hoping it clears up someday, not even tracking the timeframe anymore.
Any free months added as compensation, after this is solved?
Assuming this is ever solved.
Doesn't have to be a terminology glitch, can also be very simple: have a 10G network, introduce a device that you use to filter and has only 1G interfaces and you'll introduce a bottleneck on 1G that only displays whenever you exceed that bandwidth.
In the meanwhile it's all guessing, because @HostSailor simply states "I just want to update that team is working to fix the issue.". Which is about the same as their support is saying (on repeat): "Hold on while we're checking".
But the problem would be obvious then? Oh possibly they know but they don't have another solution for whatever reason so they're just "working to fix the issue".
I'm so naive.
I suspect it's because the VM's platform likely has a large number of firewall rules, and after making adjustments, the network surged unexpectedly.
Surged during the same time period every 24 hours?
Wondering if others observe also that their VPS is less CPU Idle during the periods that the issues are occuring. I can see that there is a slightly more CPU steal during the times that I also see the lost network packets.
Normally, steal on my VPS is reported as 0.053% average, in the timespan the packet loss occurs I see an average of 0.095% - most likely also resulting in the lower CPU Idle percentages.
I'm on kvmnvme06 - curious if on other hosts it is the same.
Same node here. I'm seeing one little spike of steal in Hetrix Tools over the last 24 hours. It happened at 12:30am EST yesterday and was about .075% steal.
... and a week has passed since the last update from @HostSailor and nothing really changed from a customer perspective: issues are still there...
I have a network and server management background. And I know that sometimes issues can take a lot of time to find what it is, but if they occur every day in the same time period it makes it a whole lot easier and I've never encountered an issue that then takes so long to get under control...
A very regular anomaly.（GMT+8）
Hi everyone,
This is to update that the issue has been resolved for most users, and many have already confirmed in tickets that things are working fine on their end.
However as some are still still facing problems, I would request to please just update your existing ticket with issue facing and team will check it case by case and get it sorted for you.
Thank you.
So basically it's back to "it's resolved, please check" again.
No it's not resolved as you can see on the comments here. You're using your customers as monitoring system again.
I've put on a ping.pe test to the VPS and within a minute I already see multiple hosts having packet loss.
Is it so f*cking difficult to do that yourself to see if everything works or not? Yes, I'm really getting annoyed by this - we're back to square one after one month of issues.
This is amazing that this issue was solved to anyone that is not on LET, but not to a single person visiting this thread :-D
charitably perhaps the person posting as @HostSailor doesn't realize his people are lying to him that it's fixed?
Unfortunately, the problem is still not resolved. Here is the MTR output I’m getting right now:
mtr 1.1.1.1
My machine is taking forever to update
I guess I am a lucky one. Situation has improved but overall there are still issues. However, my use case does not require me to keep staring at the network status and run tests 25/8
I'm seeing 15-40% pl from various locations to my wee sailor, there's not really anything I can use it for with that going on. Happy to hear someone's fine though.
We know that Calypso and I still have problems and we're both on the same node, kvmnvme06. Could other people still having problems drop their node here?
kvmnvme04 heavy pl basically unusable.
Could be hostbased ofcourse, but even if it is/was, coming here and saying that it's solved for most people while you can know and check that the main ones criticizing you here are still having issues... is... well... [fill in yourself]
When I put on a ping.pe to my IP at HostSailor and I see loss within 60 seconds from several places around the globe (even 60+% of the Dutch locations), then it's clear it isn't fixed at all.