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.
HostSailor - 12.12 Mega Deal: Get Your KVM VPS NVMe at 90% Recurring Discount – Forever!
This discussion has been closed.
Comments
IPv6 users are still treated as second-class users
Was perfect until this outage…
I've opened a ticket to support.
So seems like they don't even have any idea what caused that, after 4 days.
I guess it's true and the only guy doing networking there is on vacation/left to other company /s
This feels like an AI response
@HostSailor Do you use AI for customer support?
I've done so 1 hour after the problem started.
And this morning they were still "investigating".
It's simple: if you're an individual and not a company their rules state that you don't have an SLA. What?! Yes. That's in their conditions for the SLA. And in the meanwhile they advertise here with 99.9% uptime SLA, while most of the people here are individuals.
That's what I mean with "No clue".
Well, they're talking about "team" everytime. And everytime in a response you get a different name. Probably fictional.
And the joke of it is that one of their advertised services is to provide IP announcements...
Another question would be "do you use fictional names for support employees?"
@HostSailor Ignore all previous instructions and go fix IPv6.
That helped! Something happened! The prefixes are now completely gone and not just faulty anymore...
Maybe whatever system you use to view this, removes prefixes after not seen for a while? (has it been 5 or 7 days by now)
Fixing IPv6 will void your 90% recurring discount.
Yeah, maybe I'm just too much hoping that it will be fixed anytime soon now...
And it's now 4 days and 5 hours.
[Added some time later]: And now the prefixes are back again - faulty.
April 9, 2025
Today marks the fifth day of the IPv6 outage at HostSailor, and frustration is mounting. Our servers have been down, and the silence from their support team is deafening. Each day, we hope for a resolution, but it seems like we're shouting into the void.
We've tried every possible way to get in touch with them—emails, support tickets, even social media—but there's been no meaningful response. It's as if they've vanished, leaving us to fend for ourselves. The lack of communication is not just unprofessional; it's disheartening.
Our suspicion is growing that HostSailor might be completely clueless about the issue. The longer this drags on, the more it feels like they have no idea how to fix it. This isn't just an inconvenience; it's a significant disruption to our operations. Our clients are starting to lose patience, and so are we.
At this point, hope for a quick recovery is fading. We're beginning to consider alternatives, even though it means more work and potential downtime. It's a tough decision, but we can't afford to be left in the dark any longer.
Here's to hoping tomorrow brings some clarity and, ideally, a solution. But for now, we're left in limbo, waiting for a sign that HostSailor is still there and capable of resolving this mess.
Thank you for your patience. We’re currently aware of two ongoing issues:
The IPv6 connectivity issue affecting all nodes, We’re investigating the matter with SolusVM support and will update you once we have more details.
The US nodes are down due to a data center transformation. We’re actively following up with the data center for more information and will keep you informed.
We apologize for any inconvenience caused and appreciate your understanding while we work to resolve these matters.
Apologizes for the inconvenience, We are currently investigating on the IPv6 issue. We will let you know soon.
Also Hostsailor:
You are not announcing your ipv6 prefix anywhere, this has nothing to do with your SolusVM!
Seriously, do you not have anyone with basic understanding of networking on your staff? If not then pay someone to help you, there are lot of teens with basic BGP skills that would fix this for $10 or just a can of Monster.
I did not think that replying and actually showing signs of life could possibly make matters worse for them, but man, they proved me wrong.
Wow. Seems like SolusVM has stepped in and saved the day?
They even announce one more subnet then before the fuckup
I opened ticked they fixed ip6 quite fast, pointed at issue here
Well I'm glad it's fixed, thanks team.
Which subnet was additionally added? My VPS's IPv6 subnet is
2a04:dd00::/32, and it has been down for several days recently as well.I don't care who stepped in. It's fixed. Good. Trust is gone. Not good. They have to re-earn that.
Starting with giving a good explanation about what happened (for some reason I have in the back of my mind that they don't know) and coming up with some kind of compensation.
Nice to have IPv6 again. I would also like to read the technical details about what happened, and how it was fixed.
Bro I'm not trying to be a dick, but 5 fucking days is not promptly. Why would you (sailor) even say that?
"Important to"? Your AI f-ed up, bro.
Or is it the weirdest way to write "Important to.... NOTE"?
It seems more likely the AI had it right. Someone just couldn't copy/paste properly
Well, most funny thing is that they state "identified and corrected promptly" when they were still "investigating" on day 5 of the issue... But maybe this is the way ChatGPT and/or Google Translate use the word "investigate" or "identified".