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
@Calypso You are absolutely right to be frustrated. Please know, we really feel all the frustration you experienced. This is not the experience we want to have for one of our respected customer.
Our earlier email was based on the significant improvement we observed after mitigation was implemented, but it was slightly premature to state that the issue had been fully resolved for everyone. I take full responsibility for that and make sure it won't happen again.
The good news is that the root cause has been identified and the latest reports from multiple customers indicate that network stability has improved significantly. Thank you for your patience and for continuing to provide candid feedback throughout this process.
And thank you everyone for your patience. We are encouraged to see several customers reporting packet loss has dropped to near-zero levels.
We are continuing to monitor the network closely and will keep this under observation to ensure stability is maintained consistently for all customers.
We sincerely apologize for the prolonged disruption and appreciate the patience.
@HostSailor Any comment why my AMS Sailor has now sailed to Romania?
Only SOME client locations are affected, which is gonna be fun, another 2 months of "please recheck if this is solved"?
And again in your reply you simply ignore every mention of some kind of compensation for affected and (in your words) respected customers.
It's not that I want to pull someone's leg out, it's simply that for 1,5 month customers didn't got what they've been paying for. I've seen providers compensating customers for also cheap VPSes when they even had a day of issues. By themselves - nobody asked for it. You are only speaking of "feeling the frustration", but everytime you are hinted about maybe giving a signal that you mean it, you're ignoring it.
If all your customers would say "well, HostSailor is a provider I feel comfortable with, giving good value for money, and we can use those services, but we're still cancelling them" you would think "well, those words mean nothing, in the end it's what they're doing". And that's exactly how I feel about you saying that you "feel the frustration".
This happened to me today, and from what ive seen is Only ips connected to the vms ip have this route to m247, all others are having normal routes. My 3 ips which were connected to the vm at the time this occurred have all been rerouted to m247. They have been firewalled and cant connect/ping my vm ip. In those 3 ips is even 8.8.8.8 . Someone messed something there.
they're doing some stupid new tricks with filtering.
local resolver can't run queries.
can't talk to google ips over ipv4.
annoyed.
They just fucked up the routing and Google tries to reply to you via Romania.
As well as half of the world.
Before
After
AS9009 M247 Romania, not seen before, becomes almost the main uplink for the glorious sailor. But evidently fails to actually route their packages properly.
Pics from BGPlay by RIPE: https://stat.ripe.net/bgplay/185.244.149.0/24#starttime=1778939983&endtime=1779112783&instant=0,1779098301
This is hilarious!...
Wait I need to check mine! Ah flip, the routing is completely messed up!...
Back to the ticket...
No problems on my end, good luck getting this solved in less than 2 months. 👍🏼
Fascinating. My AMS VPS IP range is now marked even in whois as Romania as well.
Pretty sure it's always said that, my /27
It's caused me grief in the past with several geo services, only ipinfo had it correct in Amsterdam.
Mine only on google was in arabic, all other websites were NL
Not every node, but kvmnvme07 seems to be completely messed up for the last 11 hours. I can't even reach the installed Squid proxy.
Mine is on kvmnvme04
Yeah, they fucked up something 12 hours ago. I can't reach even their own ircnet.hostsailor.com IRC server from kvmnvme07 hosted VPS.
This issue is certainly not node-based, but IP-range based.
It appears at least the whole 185.244.149.0/24 is going to Romania, while at least for some IPs it shouldn't (or perhaps for all of them).
I believe how IPs are allocated across nodes is random, it's not like there's a specific IP range for each node.
You appear to be correct. My other VPSes don't have this issue, only the one in the 185.244.149.0/24 subnet does.
Both of my servers are within that subnet & on
kvmnvme04.hostsailor.com.The support answered the ticket and asked me if I was still facing issues... and I am.
But the stranges part is, not all ips route to Romaina. If you use globalping you can see that most of the probes are routing fine. The ones in m247 networks says private ip range. Only the blocked ips are routing to Romania. The ips wich were connected to hostsailor at the moment of occurance, which was at 07:00 gmt+1 yesterday morning.
Seems fixed right now - only a 20-hour downtime, not 2 months, great success.
Yeah I got a reply to my support ticket, and it seems resolved now!
yea i didn't bother tracking the issue but my resolver is able to .. connect to the internet again so thanks for that team.
edit: removed unhelpful comment
y'all should be thankful hostsailor isnt hostslick.
I am very thankful
He's very thankful!
There is a reason (well multiple) I got rid of my HostSlick VPS long ago. And after a very short service time.
HostSailor had a better reputation, but is flushing it into the drain quickly these days...
So I see they hard at work...
Loss 100%
Something is still very fecked up in/on their network... The routing is so bad...
Even https://clients.hostsailor.com is unreachable at this very moment.
They're f*cking things up AGAIN. Even their own site is unavailable...
https://vps.hostsailor.com/ is unreachable too~ (from where I am now)