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
Well I think you're not a lucky one, but just someone who's happy with the current situation which seems to fit your purpose of the VPS.
I'm the first to acknowledge that things have been worse; especially around the beginning of April it was drama all over. Then, I think around the 10th, it shifted in time that the issue occured and it became less intrusive, but still observable. For my use of the VPS this kind of packet loss is devastating so I'm keen on noting when it occurs and create a ticket for it.
Hello,
I genuinely feel the frustration and inconvenience it is causing to all of our respected customers.
Please know that we are not taking the situation lightly. While the issue seems to have improved for some users, it’s clear from inputs that it’s not fully resolved across all nodes yet. I’ve shared it again with our team for deeper investigation.
We’re specifically asking them to re-check the affected nodes and routing paths being highlighted.
Please allow some more time to investigate it further. I'll share detailed feedback after team investigation.
It is literally happening right now and has been ongoing for the last several hours. https://imgur.com/a/t13fUPd
It is time to isolate the affected nodes and move VMs to stable nodes... Just saying...
Good news: something changed. Bad news: while usually it's normal again after 6 hours, it is now already happening for 7...
Mine is pretty normal at the moment. I'm seeing significant packet loss to China, but that doesn't bother me.
Yeah, it's pretty normal again, but the timespan today was longer as normal. And as we speak... here we go again...
Can confirm. Essentially unusable at the moment.
Only 20% packet loss at the moment. It was 45% earlier today.
I still have a lot of vms with them but haven't been watching . What's the best way to check and provide additional data?
Originally, I was seeing the problem because Hetrix Tools was sending me a site down alert. Now, it is "fixed" to a degree the HT doesn't go down. I only notice it if someone posts in this thread or I'm actually using the VPS. I know it's happening when I'm using it because I have random disconnects when connected via SSH or the terminal is just laggy as hell. If you know it's happening, ping.pe will show it very clearly. You'll see anywhere for 15-65% packet loss to nearly every node. If you find that it's happening to any of your machines, you can go to vps.hostsailor.com, and it will show you the node name. I think that would be useful information to have in this thread. We know it is happening on more than one node, but I suspect it isn't happening to all of their customers, or more people would be upset.
Thanks. I will check tomorrow when I'm sober. Don't encounter issues as I only using them as slaves but happy to provide additional data.
The failure profile of this provider has definitely changed somewhat, before it was just one big blob of incompetence at a certain time period, but now it expands and also shows itself as little farts of inability to run a hosting company also later during the day
Yes precisely.
Bit harsh but admit I lol'd.
Lol. So true though...
Having the normal morning freakout.
30% packet loss for me, can't really complain when I am paying like $16 for 4 cores 4GB 100gb nvme annually.
Bro, anything above 0% is to much.
30% is basically not usuable.
No dude. 30% packet loss is a fundamental failure. I can understand being ok with slow performance because the thing is cheap, but this isn't poor performance. This is completely broken.
41 packets transmitted, 23 received, 43.9024% packet loss, time 40367ms
rtt min/avg/max/mdev = 751.481/1263.065/3942.971/891.371 ms, pipe 4
a vps on moon would probalby give simlar results .
Thats a point of view. Another point of view is that you are paying for something you cant use. Im thinking of requesting a refund for my $9 a year server. Just for the sake of it.
haha
Keep it for testing random stuff, that's what I do at least.
I agree but this thread has been open for a few weeks now, provider does not care or is not capable of fixing the issue, I can only complain like others.
You can say that you are still getting some value based on the price you paid, but don't just let them off the hook by saying it's cheap so their incompetence is ok.
Ultimately, I think the issue is that they are oversold on bandwidth, so there is nothing they can do if they aren't willing to buy more capacity.
I hate it when someone says it's cheap so it's ok to malfunction. You can see some hosts act like that as well, mentioning in their offers that the servers in offer do not get the same level of support as their regular servers.
Hi everyone,
I completely understand where the frustration is coming from. Repeatedly saying that we are working on a fix while some of you are still experiencing packet loss reflects poorly on us, and I acknowledge that.
To clarify one point that has been mentioned: this issue is not related to anyone being on a discounted plan. We’ve been in this business for over 14 years, and our credibility matters far more to us than short-term sales. There is no difference in how services are handled based on pricing.
I’m fully aware that this issue has been ongoing for several weeks, which is extremely frustrating. Please rest assured that this is our top priority, and we are doing everything we can to resolve it as quickly as possible.
14 years in business and it takes weeks to fix packet loss issues? ok.
I'd stick to believing I am getting low quality of service because I am on a discounted plan. Feeling sad for people paying full price, they deserve better.
Then don't add to that frustration by saying:
when it's well over a month. Maybe "several" matches the dictionary meaning, it doesn't sound right.
According to my monitoring it started on the 25th of March - I've mentioned that before and also (with screenshots) in my ticket. That I (and possibly others) didn't put in a ticket straightaway is because I expect a hoster to monitor themselves and act upon it, so usually these kind of things are really temporary (days).
Saying now "several weeks" sounds to me a bit as downplaying and adds to the frustration.
30 days, 6 pages, ∞ promises, 0 solutions
And it still going