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
@HostSailor: Please fire this guy:
Ticket #AZ421122
This issue goes on daily for 1,5 month, I've stated several times - also in the ticket - that I'm not your monitoring system, they can check with ping.pe themselves, and he got the nerves to "answer" a ticket with this?
F*cking solve it. Then apologise. Then compensate.
@Calypso I sincerely apologize for the issue going on from long time now. We are trying to solve it on urgent basis. Please be assured this is our top priority to fix it.
About ticket#AZ421122, a warning has been issue to support team member for not handling it properly. Please know this is not the experience we want our respected customers to face.
Just about the same then...
and back then:
Progress, just the same as addressing the issue.
If your Operations Manager didn't live up to the "addressed internally", I consider that as really bad...
Anyway, it's close to 11:30 (local time), so I'll get Packet Loss Detected mails soon...
I am getting 30% packet loss fix the damn network, it has been a month users are complaining.
20 packets transmitted, 12 received, 40% packet loss, time 19186ms
I'm almost having fun with this nowdays.
And now IPv6 connectivity is completely gone since just over an hour...
No problem with that on mine right now.
I manually set a default route via 2a04:dd01:0018:0000:0000:0000:0000:0001, do you rely on RA maybe?
No, also default route to gateway - but I got a different gateway because I'm on a different range.
Just as suddenly as this issue appeared it's also gone after just over 12 hours. Ticket has only been 'answered' (it almost appears like an answering bot) with "We'll look into this" and then put onto "hold" status...
Apparantly IPv6 worked again after a restart that took place this night. Didn't initiate it myself, and my question about cause is just being put "on hold" again. Must be one great job, just saying to customers that "please hold on, we're looking into it" and then put tickets on hold, sit back, relax, and don't actually do anything.
The packet loss issue seems to have cleared up for me today (kvmnvme03 node). Everything is back to normal now. How about you guys? Is anyone still experiencing any drops?
Works like a charm!
06 currently still has the packet loss. The whole node was definitely rebooted last night.
i'm not seeing much different on 04, the degree was always a bit variable so whatever. i only bother checking when i see updates here. sure miss using my hostsailor box.
Yep, and they don't know why. But that "solved" my IPv6 issue.
It doesn't solve the total stupidity of the HostSailor Helldesk (tm). When telling them that due to that reboot the IPv6 issue is gone, they keep on asking if "the problem still exists" and "shall we assign a different IPv6 range"... You get irritated when something is not working, you'll get frustrated by the HostSailor Helldesk (tm) responses.
And ofcourse the packet loss issue is still there
Things are getting better and better
36 packets transmitted, 18 received, 50% packet loss, time 35361ms
Guess it time to write it off and sell it to a MJJ, let them have fun with it
Today/yesterday it was different. While the last few weeks it was a defined period of about (localtime) 11:30 -> 18:00, now it was more scattered periods that the problem occured: between 13:00 -> 14:00 and some periods between 22:00 to 06:00. With some occasional packet loss on other moments.
"better" but not great...
OK have had the first 24 hour period with no problems
That's nice for you - I didn't. And they think it's resolved:
"The necessary adjustments and mitigation measures have been implemented on our network infrastructure, and we have continuously monitored the environment for more than 24 hours to ensure stability. We are pleased to confirm that the network performance is currently stable and operating normally."
Yesterday I've seen the issue between 12pm and 3:30 pm (local time) - from multiple locations (3+). So the "monitored for more than 24 hours" is definitely not correct for my situation.
I'll wait until later today, but if it's still there I'm gonna report it here and respond to them - but that won't be a nice "please try again".
I bought a VPS from another provider and migrated all my websites to the new VPS. I think many people have done, or will do, the same. My VPS is on node 1. It was fine before, but for the past two weeks it's been unstable all day. My website has lost all its revenue due to the instability. A company with many years of experience selling VPSs can't even solve network problems like this. I truly admire those who haven't migrated their websites to another provider.
Hello everyone,
I want to share status update on the Amsterdam packet loss issue.
Our engineers traced the problem to abnormal ARP traffic within the network, which was causing intermittent instability for a number of customers.
Corrective changes have been deployed and the overall situation has improved considerably. Several customers have already confirmed that their connectivity is back to normal.
However, it is clear that a few users are still seeing occasional packet loss as per recent comments. Because of that, we are continuing to treat this as an active issue and our network team remains focused on it until all affected services are stable.
We understand how disruptive this has been, especially given the duration of the problem, and we sincerely apologize for the inconvenience caused.
Our team will continue monitoring closely and will provide further updates if any additional action is required. If you are still experiencing packet loss, please reach out via support ticket so we can investigate your specific case, thank you.
@HostSailor - Please explain this: how can your organisation send out an e-mail stating that they've "continuously monitored" etc etc and I just checked and still observed the issue less than 24 hours ago, for quite some time and on all my monitoring hosts - exactly at the same time periods.
I can only think of a few possibilities:
[A] There are lies in the e-mail
[B] They're incompetent
[C] They haven't got a clue
[D] They look at the wrong places/the wrong way (Although explained a few times how they easily can)
[E] All of the above
I still hope that the issue is solved now, but at least the statement that it's considered stable over the last 24 hours is absolutely not true.
[Added remark] Our posts here have crossed, and you seem to be aware that the issue is not fixed for everyone. That only makes my comment more viable: how can someone send out an e-mail stating "it's solved" "we've monitored" and it's just not true...
.
I can see the background noise has dropped by about 400kbps starting almost 48hrs ago.
I am seeing less than 1% pl currently.
Up to now it's going OK. I keep my fingers crossed.
And for those who wonder why I'm p*ssed: communication has been a drama (first don't acknowledge, then asking over and over again if it's solved, now that there has been monitoring but the issue still happened) together with the almost 6 weeks runtime for this issue (after first comments here; the issue was already there a couple of weeks earlier) and no sign of offering some kind of compensation all shape my reaction (I know, read the ToS, if you're not a company you don't have any rights with this hoster, the VPSes offered here are cheap, etc etc - but still major things went wrong and it took way too long).
I haven't had time to monitor mine this morning, but when I did check quickly, it had much less packet loss than previously, but not zero. It's definitely a lot better.
Indeed, smokeping indicates, great success!
Congrats @HostSailor we shall partay.
checking in ~36hrs later background noise still banished, packetloss literally 0.1% on charts running the entire time.