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
@rm_ I have opened a ticket from my side, using Google and CloudFlare as targets (so they can't say it comes from my ISP). My 2x VPS are on the same node but for some reason they have different routing... In any case: I am now getting losses on BOTH.
Meh, got this back from the ticket
OK I sent the commands over in the ticket so they can see the problem for themselves. I will update back here.
That's the way to do it, maybe at some volume of tickets it will become harder for them to pretend "there are no issues on our side". Unfortunately many don't monitor PL to their VMs, and others feel they are too lazy to open a ticket, or hope it will resolve itself somehow.
Unless the support is not just lazy and incompetent, but straight out lying right now. But I don't see how this can work out for them in the long term.
Also, it is especially bad today:
More or less, looks like a certain upstream is fugged.
04.04.2026 21:06:46 INFO Total 138, Packetloss 90
Despite that, my smoke is green, shitty routes are skipped.
@HostSailor how many tickets do we need, so you start moving your ass?
Update: after some back & forth, the agent (Udeek) finally saw the problem and escalated the issue, his last reply is: "we will check with our team and update you", with the ticket being "On Hold". So let's wait, it might need to wait until MON 6 APR 2026 or TUE 7 APR 2026 for a resolution I think!Update: nothing back from the ticket~ will come back here on TUE 7 APR 2026.The suspected malfunction occurred a few days ago. For now it's back to normal.
NODE: kvmnvme06 AMS
(from:hetrixtools monitor)
Created a ticket also - still seeing periods of packet loss
Hey at least they are consistent /s
well this isn't amusing now
Update: nothing back from HostSailor in the ticket being still "On Hold", which I guess means they are still working on it (or waiting on someone to act in the AMS DC?). I think they just have a faulty NIC or Switch...is your node affected too now?
yes i probably should have said something sooner but frankly i was annoyed that issues cropped up almost immediately after i posted that everything was fine.
i'm seeing up to 30% packet loss into my hostsailor vps now from most of my other locations though there's a few with no issue (budgetvm in miami, massivegrid in nyc, sparkedhost in miami).
i guess i'll add my own ticket to the pile this morning when i get a free moment from posting nonsense on let.
AH! That's reassuring (for us)~ and it means it is not segregated to one node alone.
Yay 🥳!!~ Let's 🌊 swamp 🌊 them!
Ofcourse they came back with a "we don't see anything, try from another host" while I already explained in my ticket I encounter it from several other hosts during periods of time.
Those Indian helpdesk people are even more "funny" as the IT Crowd series...
What I can see here, my main issues the last 2 days are between 1am and 8am (local time).
Still think it's a networkport (either internally or on an interconnect) that is saturated.
I have never seen anything like this, almost half of the network packets are just disappearing:
I got a reply from the ticket and it has been fixed:
Thank you for your service! I just got back to my desk, whew.
Also got an update to my ticket that apparantly it is fixed, however, I'm still a bit cautious - there have been periods that it was OK before...
Same reply (at about "Tue 18:00"), and that was complete bs, earlier today it was bad again.
(12:00 gap was my ISP, ignore that)
Hey, at least they are consistent
I tried each Network Card and it did not change anything.
Did you get any follow-up in your ticket since then?
It's stupid that they don't give quick feedback when something happens to us or breaks, which we pay money for?
Yes, like to everyone else with a ticket, yesterday they told me it's "fixed".
Update: I have re-opened the ticket because the errors are still on 1x VPS only out of the 2x I have. But the loss of packets is tiny @ 0.4% compared to before (but maybe it varies during the day/night).@jcn50 that's zero packet loss. If not reconfirmed by each line lower than that, losses on single lines along the way can be ignored. Simply a router having better things to do than answering pings, but still passing all the actual data packets further just fine. I guess you just measured during a "green" period, those seem to be a bit longer now after their "fixed" message.
Otherwise you could have said "wow 83.1% loss".
I don't know, on my other VPS I have 0% loss. The support agent told me they will look into it (most likely tomorrow). I did say in the ticket that 5~6 hours per day were a lot worse.
it is back, on some routes. i'm guessing the intermittent nature of the issue is leading support folk to holler fixed without anything actually being changed.
i'm really bummed, this was my most stable and favorite vm for over a year.
90% I am certain, its a upstream problem.
Why?
09.04.2026 00:38:30 INFO Total 77, Packetloss 42
But my Smokeping looks like this:
TLDR: There is fuckery but upstream fuckery.
Maybe even 2 or more problems at the same time, given these large spikes.
Hello,
Thank you for bringing this to our attention. We genuinely understand the concerns raised here and take them seriously.
We will investigate this matter internally with our network and operations teams to identify the root cause and share an update here.
If anyone is currently experiencing issues, please feel free to open a support ticket with relevant details so we can check specific cases as well.
We appreciate your patience and feedback.