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
If you notice latency differences or other issues with your servers, it is possible you are using the wrong servers for the speed test, since geolocation updates take time, you might be assigned an incorrect server, which automatically increases latency. Theoretically, however, nothing has actually changed, an IP switch does not break the network, as everything runs on the exact same infrastructure. While it may take a few more hours for everything to stabilize, there is no cause for alarm, and the situation is certainly not catastrophic or unresolvable. In any case, if something seems amiss, we can assist you via support tickets, we are processing them quickly and helping everyone.
@DK87
@CHALI787
Will check this when we have some free time sir, i’m sorry for the delay, i think for today/tomorrow
Will check it today.
I'll see what went wrong and we'll help you, don't worry.
Thanks for the reply.
But take a look to ping test from your DE vps to NL vps with newly assigned ip:
PING 143.20.154.177 (143.20.154.177) 56(84) bytes of data.
64 bytes from 143.20.154.177: icmp_seq=2 ttl=53 time=19.1 ms
64 bytes from 143.20.154.177: icmp_seq=4 ttl=53 time=316 ms
64 bytes from 143.20.154.177: icmp_seq=7 ttl=53 time=27.0 ms
64 bytes from 143.20.154.177: icmp_seq=8 ttl=53 time=14.9 ms
64 bytes from 143.20.154.177: icmp_seq=10 ttl=53 time=16.6 ms
64 bytes from 143.20.154.177: icmp_seq=12 ttl=53 time=157 ms
64 bytes from 143.20.154.177: icmp_seq=14 ttl=53 time=133 ms
64 bytes from 143.20.154.177: icmp_seq=16 ttl=53 time=16.4 ms
64 bytes from 143.20.154.177: icmp_seq=19 ttl=53 time=47.1 ms
64 bytes from 143.20.154.177: icmp_seq=21 ttl=53 time=324 ms
64 bytes from 143.20.154.177: icmp_seq=22 ttl=53 time=218 ms
64 bytes from 143.20.154.177: icmp_seq=23 ttl=53 time=348 ms
64 bytes from 143.20.154.177: icmp_seq=25 ttl=53 time=114 ms
64 bytes from 143.20.154.177: icmp_seq=26 ttl=53 time=15.1 ms
64 bytes from 143.20.154.177: icmp_seq=27 ttl=53 time=19.5 ms
64 bytes from 143.20.154.177: icmp_seq=28 ttl=53 time=15.6 ms
64 bytes from 143.20.154.177: icmp_seq=29 ttl=53 time=46.7 ms
64 bytes from 143.20.154.177: icmp_seq=30 ttl=53 time=89.5 ms
64 bytes from 143.20.154.177: icmp_seq=32 ttl=53 time=292 ms
64 bytes from 143.20.154.177: icmp_seq=33 ttl=53 time=201 ms
64 bytes from 143.20.154.177: icmp_seq=36 ttl=53 time=113 ms
64 bytes from 143.20.154.177: icmp_seq=37 ttl=53 time=14.3 ms
64 bytes from 143.20.154.177: icmp_seq=38 ttl=53 time=17.7 ms
64 bytes from 143.20.154.177: icmp_seq=39 ttl=53 time=14.6 ms
64 bytes from 143.20.154.177: icmp_seq=40 ttl=53 time=17.9 ms
64 bytes from 143.20.154.177: icmp_seq=41 ttl=53 time=57.1 ms
--- 143.20.154.177 ping statistics ---
41 packets transmitted, 26 received, 36.5854% packet loss, time 40582ms
rtt min/avg/max/mdev = 14.302/102.592/348.192/109.931 ms
just right now your DE location experiencing some serious network failure.
there is obviously nothing compared to wrong speedtest server.
CMU5VSM0YJO9U still waiting that you fix my login to your webpage. It doesnt help nothing if you just reply something in to ticket.
I Cannot access your webpages to my account.
Same here. Noticeably increased latency, jitter, packet loss. Seems to have started around midnight, but has gotten worse since before noon. Both IPv6 and IPv4.
support is broken need one month to reply. LoL
It's literally one thing after another with y guys
@DeluxHost, let me fix this for you:
*Our team replies in months
thanks for the report, we already work it.
Unfortunately, some things do not depend on us, but I think that the situation has been handled well
Some new employees are already working on tickets, support is much smoother.
We know about this problem in the past, but mainly in technical tickets, because generally there are no major problems in the others.
i don't have any server problem, i got some problem in billing, #20711
Matteo is might busy,
i told all billing problem to Anastasia and Alessandro.
i have 1 small question why hard drive is like slow there is mention nvme, and I'm getting results in Italy on Netherlands server, mine server is Q3
i know you very old you guys doing better now ❤️
i advice everyone goto Q Nodes it's better then all😁
Let me check with Matteo what happend and i let you know for today
yeah hit 1 slap from me, where he goes like disappear 🤣🤣🤣
4756134021Q-3
The network has been half-dead for a couple of days already, and closer to the evening it's completely dead. Matteo, please solve the problem.
-------------------- A Bench.sh Script By Teddysun -------------------
Version : v2026-01-31
Usage : wget -qO- bench.sh | bash
CPU Model : AMD Ryzen 9 7950X 16-Core Processor
CPU Cores : 2 @ 4499.996 MHz
CPU Cache : 1024 KB
AES-NI : ✓ Enabled
VM-x/AMD-V : ✗ Disabled
Total Disk : 39.9 GB (3.0 GB Used)
Total RAM : 3.8 GB (582.6 MB Used)
System Uptime : 0 days, 22 hour 8 min
Load Average : 0.00, 0.00, 0.00
OS : Debian GNU/Linux 12 (bookworm)
Arch : x86_64 (64 Bit)
Kernel : 6.1.0-53-amd64
TCP Congestion Ctrl: bbr
Virtualization : KVM
IPv4/IPv6 : ✓ Online / ✗ Offline
Organization : AS214677 Matteo Martelloni trading as DELUXHOST
Location : Amsterdam / NL
Region : North Holland
I/O Speed(1st run) : 34.5 MB/s
I/O Speed(2nd run) : 548 MB/s
I/O Speed(3rd run) : 1.2 GB/s
I/O Speed(average) : 603.8 MB/s
Node Name Upload Speed Download Speed Latency
Speedtest.net 3908.39 Mbps 3704.35 Mbps 0.96 ms
Los Angeles, US 1885.96 Mbps 4902.89 Mbps 142.77 ms
Dallas, US 2028.99 Mbps 5529.85 Mbps 115.18 ms
Montreal, CA 1057.57 Mbps 1935.32 Mbps 100.06 ms
Paris, FR 8395.41 Mbps 6277.70 Mbps 17.86 ms
Amsterdam, NL 8233.27 Mbps 5937.78 Mbps 7.22 ms
Suzhou, CN Test failed
Ningbo, CN Test failed
Hong Kong, CN 461.79 Mbps 1953.11 Mbps 193.79 ms
Singapore, SG 1016.23 Mbps 2424.97 Mbps 256.42 ms
Taipei, CN 1315.07 Mbps 4269.97 Mbps 202.58 ms
Tokyo, JP 904.13 Mbps 4309.55 Mbps 253.42 ms
Finished in : 5 min 31 sec
Timestamp : 2026-09-21 22:44:40 +03
Pretty Good 😊
13021
With this message I want to make you think twice before buying vps at @DeluxHost
I ordered my vps in February 2026.
In March I got first problems - i/o read write errors. No solutions, just answers like "The issue should be resolves". But it wasn't
May - June DDos attacks, 95% downtime
Since DDos problem was solved I got my vps working no longer than 10 days. Usually 6-7 days after each restart.
Last month my vps randomly stops after 4-6 days working. I also wrote tickets that I couldn't EVEN start it. That happend twice. And still i/o read write errors.
My last ticket #TMTCIBEXQS5XY still not resolved, my website shows "500 Internal Server Error", a lot input/output errors. Nice.
dude why my ticket showing waiting sign?🍼
Thanks, no problem—I just want to know that my issue will be resolved.
Thanks for your cooperation. To be honest, I don’t really understand why people here are so upset - I’ve had 30 VPS servers purchased from DeluxHosting running without any issues for over a year now, and I’ve already renewed 20 of them for another year.
That depends on how you defined "well".I've lost ipv6 on all my servers now!
order #20255 +1 GB Ram please
What do you mean by "lost"? What might have happened is that they changed, but they should work without any issues.
When you have a large client base, facing criticism,!especially when issues arise,!is inevitable, however, this isn't a problem for us, as we are happy to resolve such issues. We also have just as many happy, satisfied clients, not everyone uses LET, so naturally, they tend to be more "silent."
I will check your ticket as soon as possible, many of the issues you described appear to be resolved on my end, though others,!such as the 500 error, are unfamiliar to me. I’ll see what I can do for help you.
Well, it is lost though. IPv4 changed automatically, but IPv6 didn't.
I've changed it in 50-cloud-init manually (got new one from the client area), but it still doesn't work. It is neither accessible from the outside, nor can I access the IPv6 network from within the VPS.
I thought it's a known issue, so I didn't raise a ticket.