Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


Shells Virtual Desktop
BMail.ag - Secure Email Service
Server.net
CPLicense.net
VPS Server
Buy VPN
Vultr
VMs for AI
HostDare
ReliableSite White-Label Dedicated Hosting for Resellers
InterServer VPS
BMail.ag - Secure Email Service
Best VPN
High-Performance Bare Metal Server Solutions
Karvl.com
Server Mania Cloud Hosting
DataWagon Hosting
AlphaVPS Hosting
Evoxt.com
Clouvider
VPS Hosting with NVMe
Residential IPs in the US & 4G Mobile Proxies in EU & US with Unlimited Bandwidth
ReliableSite White-Label Dedicated Hosting for Resellers
Shells Virtual Desktop
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.

IPv4 connection in HostSlim's Estonia Region has gone

PorlamPorlam Member
edited May 28 in Outages

IPv4 connection in HostSlim's Estonia region has been unreachable but IPv6 is still alive.
As I checked, they have stopped to announce the space or RETN blocked their routes.
https://bgp.tools/prefix/69.12.83.0/24#connectivity

Comments

  • rpqurpqu Member

    🍿

    Thanked by 1vastness4594
  • yoursunnyyoursunny Member, IPv6 Advocate

    😈

  • amjamj Member

    From: HostSlim OÜ sales@hostslim.eu
    Subject: We would like to inform you about an ongoing network issue affecting the subnet 69.12.83.0/24.
    Date: Thu, 28 May 2026 11:26:12 +0200

    Dear *,

    We would like to inform you about an ongoing network issue affecting the subnet 69.12.83.0/24.

    Approximately 6 hours ago, one of the upstream supplier engineers accidentally removed the route object associated with this subnet, causing reachability issues for services using IPs within this range.

    At this moment, we are still actively attempting to reach the supplier and their engineering department in order to get the route restored as soon as possible. Unfortunately, despite multiple escalation attempts, we have not yet received a resolution timeframe from their side.

    In parallel, we have already started preparing migration plans for all remaining clients still using this subnet. Based on this incident and previous operational concerns, we no longer consider this supplier sufficiently reliable for long-term production usage.

    To prevent future disruptions, affected services will be migrated to alternative IP space operated through our own stable and fully managed network infrastructure. Our team will contact impacted clients individually regarding migration scheduling and any required configuration changes.

    We sincerely apologize for the inconvenience caused by this situation and appreciate your patience while we work toward a permanent resolution.

    If you have any questions or require urgent assistance, please contact our support team.

    Kind regards,

    The Network Operations Team

    visit our website | log in to your account | get support
    Copyright © HostSlim OÜ, All rights reserved.

    Thanked by 2Porlam zed
  • sshboxsshbox Member

    Good thing they weren't single homed...

  • NeoonNeoon Community Contributor, Veteran

    IPv6 was fucked before, my VPS died, sad, cry.

  • rm_rm_ IPv6 Advocate, Veteran
    edited May 28

    @amj said: Subject: We would like to inform you about an ongoing network issue affecting the subnet 69.12.83.0/24.

    I wondered why I didn't receive that mail. Turns out rDNS of the mail server didn't resolve:

    May 28 09:45:47 rin postfix/smtpd[10449]: NOQUEUE: reject: RCPT from unknown[193.3.189.74]: 450 4.7.25 Client host rejected: cannot find your hostname, [193.3.189.74]; from=sales@hostslim.eu to=<me@mydomain> proto=ESMTP helo=<server.hostslim.eu>

    Who handles that?

    dig +trace 74.189.3.193.in-addr.arpa
    ...
    189.3.193.in-addr.arpa. 86400   IN  NS  dns0.hostslim.nl.
    189.3.193.in-addr.arpa. 86400   IN  NS  dns1.hostslim.nl.
    

    And

    dns0.hostslim.nl has address 69.12.83.100
    dns1.hostslim.nl has address 2.59.254.10

    The first DNS server is in the affected IP range.
    Which is funny, considering how they talk about this being an unreliable subnet in some way, on its way to being decommissioned, and only has "remaining" customers in it.

    # host 193.3.189.74 2.59.254.10
    ;; communications error to 2.59.254.10#53: connection refused
    ;; communications error to 2.59.254.10#53: connection refused
    ;; no servers could be reached

    And the second one is just not responding, despite being pingable and all.

  • rm_rm_ IPv6 Advocate, Veteran

    The subnet is back up right now, and sure enough, now that mail announcement went through as well.

  • Now Direct Admin CP error:

    Unable to reach licensing servers for license validation.

    DNS lookup failed with error lookup licensing.directadmin.com on 8.8.8.8:53: read udp 2.27.170.2:50195->8.8.8.8:53: i/o timeout.

    Check if DNS is properly configured in the server and file /etc/resolv.conf has valid DNS servers configured.

    DNS lookup from CLI can be checked with command:

    dig +short licensing.directadmin.com

    If DNS working properly please open a support ticket.

  • amjamj Member

    From: HostSlim OÜ sales@hostslim.eu
    Subject: Update Regarding Subnet 69.12.83.0/24
    Date: Thu, 28 May 2026 20:35:08 +0200

    Dear *,

    We would like to inform you that the issues affecting subnet 69.12.83.0/24 have now been resolved and services are currently operating normally again.

    However, due to the instability and reliability concerns we experienced with this subnet and its upstream handling, we have decided to proactively migrate all remaining services on 69.12.83.0/24 to a new subnet within the next 48 hours. This is being done to ensure stable and uninterrupted operations going forward.

    For VPS clients:
    Your new IP assignment will automatically appear inside your client portal. In most cases, the VPS should begin using the new IP configuration automatically after a reboot.

    For dedicated server clients:
    Our team will personally contact you with the new subnet details and migration instructions to ensure a smooth transition.

    We will make every effort to minimize any possible disruption during this migration process.

    We appreciate your patience and understanding while we continue improving the reliability of our network infrastructure.

    If you have any questions or require assistance, please feel free to contact our support team.

    Kind regards,

    Network Operations
    HostSlim 

    visit our website | log in to your account | get support
    Copyright © HostSlim OÜ, All rights reserved.

  • beanman109beanman109 Member, Host Rep, Megathread Squad

    where did it go
    hope you guys find it soon
    ta x

    Thanked by 2buggedout barbarza
  • nomoretearsnomoretears Member
    edited May 29

    They are going to migrate to new subnet. Be prepared to update DNS records and do some other work.

  • buggedoutbuggedout Member

    @beanman109 said:
    where did it go
    hope you guys find it soon
    ta x

    I got news from my sources that its hiding in a shed. Got to find that shed !! Do you happen to know any shed?? 😆😁

    Thanked by 1beanman109
  • What is the status of shared hosting in Estonia? Web sites are offline as I write this.

  • PorlamPorlam Member

    @Turbo_Pascal said:
    What is the status of shared hosting in Estonia? Web sites are offline as I write this.

    I'm using their shared hosting but it's online now but DirectAdmin panel hasn't recovered yet.

  • I'm not using the shared hosting for anything critical. Therefore I think this is a good opportunity to test the provider. Will they eventually fix it without action from a paying customer? Will they even attempt communication regarding a service disruption?

    Anything would be better than simply allowing web sites to die.

    @Porlam said: it's online now

    Did you take action to restore service or did it recover by itself?

  • rm_rm_ IPv6 Advocate, Veteran
    edited May 29

    @amj said: Your new IP assignment will automatically appear inside your client portal. In most cases, the VPS should begin using the new IP configuration automatically after a reboot.

    Meanwhile already 24hr into the promised 48 and nothing of the sort has appeared inside my client portal, and overall a smooth handling of this would be to first add the IPs as secondary, THEN announce via mail. Instead it seems they want to switch over instantly, with inevitable downtime, and you don't know when.

  • VPSSLIMVPSSLIM Patron Provider, Veteran

    @rm_ said:

    @amj said: Your new IP assignment will automatically appear inside your client portal. In most cases, the VPS should begin using the new IP configuration automatically after a reboot.

    Meanwhile already 24hr into the promised 48 and nothing of the sort has appeared inside my client portal, and overall a smooth handling of this would be to first add the IPs as secondary, THEN announce via mail. Instead it seems they want to switch over instantly, with inevitable downtime, and you don't know when.

    You are right. We are indeed first adding the IPs as secondary to the VPSses, then client have 72 hours +- to adjust everything and then we'll delete the old IPS. We are very sorry for the trouble.

    Thanked by 1rm_
  • VPSSLIMVPSSLIM Patron Provider, Veteran

    @Turbo_Pascal said:
    What is the status of shared hosting in Estonia? Web sites are offline as I write this.

    Should be all OK. If not, send me a PM.

    Thanked by 1Turbo_Pascal
  • @VPSSLIM said: You are right. We are indeed first adding the IPs as secondary to the VPSses

    Is this valid for shared hosting?

  • rm_rm_ IPv6 Advocate, Veteran

    @VPSSLIM said: Should be all OK. If not, send me a PM.

    And since yesterday just about when new IPs were added, I see some kind of degradation, random ping spikes all over. Note that the graph below is not due to the new IP, it is from IPv6 of the same VPS. But IPv4 is affected the same way.

  • rm_rm_ IPv6 Advocate, Veteran
    edited May 30

    @VPSSLIM My random guess is that you had something firewalled or filtered to solve the prior long-running network issue: https://lowendtalk.com/discussion/204670/horrible-network-on-hostslim-14-eur-let-deal/p1
    With new IPs in place, the firewall is no longer acting on those, having the old IPs still listed in it. So the solution is now not applied anymore, and the issue reappears.

Sign In or Register to comment.