DeluxHost.net | NEW V Series NVMe VPS | Storage VPS & Ryzen 9950X Available | From €4/yr | AMS / NED

isxyol

Order Placed #5968925644
Prefer +1 vCore. Thanks.

71144139

Is the BGP session enabled by default after purchase, or do I need to submit a support ticket to apply?

DeluxHost

@71144139 said:
Is the BGP session enabled by default after purchase, or do I need to submit a support ticket to apply?

Please send a ticket for this sir.

itsnotmeqr

I purchased the item and waited a day, but it hasn't been activated and I haven't received the gift yet. Are you okay with that?

DeluxHost

@itsnotmeqr said:
I purchased the item and waited a day, but it hasn't been activated and I haven't received the gift yet. Are you okay with that?

Hello, can you please send the order number or open a ticket?

itsnotmeqr

@DeluxHost said:

@itsnotmeqr said:
I purchased the item and waited a day, but it hasn't been activated and I haven't received the gift yet. Are you okay with that?

Hello, can you please send the order number or open a ticket?

Invoice #16603, pls check

eushells

Hello! I wanted to purchase a VPS storage, they appear available on the site, but when I ordered them they were out of stock.

DeluxHost

@itsnotmeqr said:

@DeluxHost said:

@itsnotmeqr said:
I purchased the item and waited a day, but it hasn't been activated and I haven't received the gift yet. Are you okay with that?

Hello, can you please send the order number or open a ticket?

Invoice #16603, pls check

Solved! Thanks for the order

DeluxHost

@eushells said:
Hello! I wanted to purchase a VPS storage, they appear available on the site, but when I ordered them they were out of stock.

You can wait a restock today sir

SSs

Order Placed #9272253509 Please add 1 vCore thank u！！！

kkoneko

@kkoneko said:
Order Number : 3962617083
Extra RAM or Vcore would be nice

Hi, so uh I just checked, I haven't got my freebies

lowendftw

@DeluxHost said:

@eushells said:
Hello! I wanted to purchase a VPS storage, they appear available on the site, but when I ordered them they were out of stock.

You can wait a restock today sir

i bought a w3 cause there were no other left. is possible to upgrade to an w5 if am fast enough and buy one. can you then give me then difference back, cause i only need one vps for testing?

fitkoh

@DeluxHost said:

@fitkoh said:

@DeluxHost said:

@fitkoh said:

@DeluxHost said:

@fitkoh said:

@DeluxHost said:

@fitkoh said:
Looks like my disk is completely locked up with this last yabs run. Never seen 0 iops before.

Would this be considered completely unusable?

`fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda3):---------------------------------

Block Size	4k (IOPS)	64k (IOPS)
Read	41.60 MB/s (10.4k)	114.45 MB/s (1.7k)
Write	41.69 MB/s (10.4k)	115.05 MB/s (1.7k)
Total	83.29 MB/s (20.8k)	229.51 MB/s (3.5k)
Block Size	512k (IOPS)	1m (IOPS)
------	--- ----	---- ----
Read	147.06 MB/s (287)	337.00 KB/s (0)
Write	154.87 MB/s (302)	369.00 KB/s (0)
Total	301.94 MB/s (589)	706.00 KB/s (0)`

I check this soon

I'll ask again since you sidestepped the question: Would you consider a vps in this state to be completely unusable?

Follow up questions:

If no, thanks for benchmarking performance criteria with your service.

If yes, why has this been allowed to persist for so long?

Hello,

The behavior you are observing has occurred intermittently over the past weeks and is related to periodic saturation of the shared SATA storage layer, not to disk failure. This is one of the reasons we previously announced the planned migration from SATA to NVMe, which directly addresses I/O queueing and latency under contention.

In many cases, this situation has already been mitigated or fully resolved through applied improvements to storage scheduling and capacity distribution. Where necessary, we have also taken action against disk-abusive workloads that negatively impact other users on the same host.

While this behavior is not ideal, it remains intermittent and the service has stayed operational, which is why it has not been classified as a fault condition.

For completeness, we responded to your ticket within one hour. At the time of writing, we have not yet received a reply from you.

We remain available should you wish to continue the discussion or review alternative solutions.
Knowing which node is affected would help us solve the problem.

In short, is there a problem? Yes.

Can we solve it? Yes.

If you mean intermittent by every ~2 minutes then yes it is a very intermittent problem. The images from hetrixtools showing systematic iowait over the last month, not an occasional blip.

Yes your support team was quick to reply to my ticket, if not to answer my query.

As an end user, perhaps I don't understand the administrative side of your hypervisor panel in connection with the billing panel; I know that when I open a ticket there is a dropdown menu to select an affected service. It seems to me that this should be sufficient means to identify the affected node; this is only an assumption and I may very well be wrong, yet it seems like common sense to me.

If there is no means for you to identify an affected node from a ticket-referenced service then I owe you and your staff an apology, and my long wait is entirely my own fault.

If, on the other hand, your support has the ability to identify a node from a referenced service, yet they neglected to do so (for whatever reason) then your support could use some improvement.

As it stands, since it seems that you are waiting on hardware to fix a systemic problem, I'll power down the affected services and try again if NVMe drives are ever installed.

Thank you for the clarification.

To address this point directly: we do not see which specific service you selected as “affected” in the ticket. Our support system does not automatically expose that information to the technician handling the request.

For this reason, our support team replied asking you to specify which server is experiencing the issue, especially since you have more than one service with us. This step is necessary to immediately identify the host node and isolate or investigate the problem. Unfortunately, we did not receive a response to that request, which prevented us from proceeding further at that time.

As for immediate solutions, we can offer to move the affected VPS free of charge to a more performant NVMe-backed node, while we continue to investigate what is happening on the current node.

At this stage, without knowing exactly which service was affected and without follow-up data, we cannot determine precisely what occurred on that node.

We remain available to proceed as soon as you confirm which server is impacted in the ticket.

I do apologize, however, for any problems you may have encountered, and you will be compensated for them.

Please deliver my humble apologies to your staff for not following up in a timely manner. My frustrations are my own and I do not seek any compensation for them. The loss would be more valuable as a lesson learned.

The offer to move to a more performant node is entertaining. I would graciously accept it if you could perform a seamless migration. If a move would require obtaining a new IP address I'd just as soon wait for new drives to be installed. I've recently migrated two services elsewhere and I prefer not to take on another if I have a choice in the matter.

Thank you for your message, and please don’t worry about apologies at all. We fully understand how frustrating these situations can be. When issues occur and they are on our side, the responsibility is ours, not yours.

If you can simply confirm in the ticket which service is affected (or if multiple services on different nodes are involved), I will personally handle the migration for you.

The migration can be performed live, within a few minutes, without data loss, and with the same IP address preserved, should you wish to proceed. Everything will remain exactly as it is now, files, configuration, and services.

Once we have that confirmation in the ticket, we can move the service to a more performant NVMe node immediately while we continue investigating what is happening on the current one.

We’re here when you’re ready.

I tendered the affected services to support roughly 30 minutes from the time deluxhost replied to my last comment.

5 hours later still twiddling my thumbs between timeouts. Currently on my fourth timeout trying to make a user account through my web panel.

I would not choose to endure this level of frustration for any amount of money.

I'm really over being lied to, led on, and neglected.

If I were in your shoes I'd strongly consider offering me a refund.

@DeluxHost said:

@fitkoh said:

@DeluxHost said:

@fitkoh said:

@DeluxHost said:

@fitkoh said:

@DeluxHost said:

@fitkoh said:
Looks like my disk is completely locked up with this last yabs run. Never seen 0 iops before.

Would this be considered completely unusable?

`fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda3):---------------------------------

Block Size	4k (IOPS)	64k (IOPS)
Read	41.60 MB/s (10.4k)	114.45 MB/s (1.7k)
Write	41.69 MB/s (10.4k)	115.05 MB/s (1.7k)
Total	83.29 MB/s (20.8k)	229.51 MB/s (3.5k)
Block Size	512k (IOPS)	1m (IOPS)
------	--- ----	---- ----
Read	147.06 MB/s (287)	337.00 KB/s (0)
Write	154.87 MB/s (302)	369.00 KB/s (0)
Total	301.94 MB/s (589)	706.00 KB/s (0)`

I check this soon

I'll ask again since you sidestepped the question: Would you consider a vps in this state to be completely unusable?

Follow up questions:

If no, thanks for benchmarking performance criteria with your service.

If yes, why has this been allowed to persist for so long?

Hello,

The behavior you are observing has occurred intermittently over the past weeks and is related to periodic saturation of the shared SATA storage layer, not to disk failure. This is one of the reasons we previously announced the planned migration from SATA to NVMe, which directly addresses I/O queueing and latency under contention.

In many cases, this situation has already been mitigated or fully resolved through applied improvements to storage scheduling and capacity distribution. Where necessary, we have also taken action against disk-abusive workloads that negatively impact other users on the same host.

While this behavior is not ideal, it remains intermittent and the service has stayed operational, which is why it has not been classified as a fault condition.

For completeness, we responded to your ticket within one hour. At the time of writing, we have not yet received a reply from you.

We remain available should you wish to continue the discussion or review alternative solutions.
Knowing which node is affected would help us solve the problem.

In short, is there a problem? Yes.

Can we solve it? Yes.

If you mean intermittent by every ~2 minutes then yes it is a very intermittent problem. The images from hetrixtools showing systematic iowait over the last month, not an occasional blip.

Yes your support team was quick to reply to my ticket, if not to answer my query.

As an end user, perhaps I don't understand the administrative side of your hypervisor panel in connection with the billing panel; I know that when I open a ticket there is a dropdown menu to select an affected service. It seems to me that this should be sufficient means to identify the affected node; this is only an assumption and I may very well be wrong, yet it seems like common sense to me.

If there is no means for you to identify an affected node from a ticket-referenced service then I owe you and your staff an apology, and my long wait is entirely my own fault.

If, on the other hand, your support has the ability to identify a node from a referenced service, yet they neglected to do so (for whatever reason) then your support could use some improvement.

As it stands, since it seems that you are waiting on hardware to fix a systemic problem, I'll power down the affected services and try again if NVMe drives are ever installed.

Thank you for the clarification.

To address this point directly: we do not see which specific service you selected as “affected” in the ticket. Our support system does not automatically expose that information to the technician handling the request.

For this reason, our support team replied asking you to specify which server is experiencing the issue, especially since you have more than one service with us. This step is necessary to immediately identify the host node and isolate or investigate the problem. Unfortunately, we did not receive a response to that request, which prevented us from proceeding further at that time.

As for immediate solutions, we can offer to move the affected VPS free of charge to a more performant NVMe-backed node, while we continue to investigate what is happening on the current node.

At this stage, without knowing exactly which service was affected and without follow-up data, we cannot determine precisely what occurred on that node.

We remain available to proceed as soon as you confirm which server is impacted in the ticket.

I do apologize, however, for any problems you may have encountered, and you will be compensated for them.

Please deliver my humble apologies to your staff for not following up in a timely manner. My frustrations are my own and I do not seek any compensation for them. The loss would be more valuable as a lesson learned.

The offer to move to a more performant node is entertaining. I would graciously accept it if you could perform a seamless migration. If a move would require obtaining a new IP address I'd just as soon wait for new drives to be installed. I've recently migrated two services elsewhere and I prefer not to take on another if I have a choice in the matter.

Thank you for your message, and please don’t worry about apologies at all. We fully understand how frustrating these situations can be. When issues occur and they are on our side, the responsibility is ours, not yours.

If you can simply confirm in the ticket which service is affected (or if multiple services on different nodes are involved), I will personally handle the migration for you.

The migration can be performed live, within a few minutes, without data loss, and with the same IP address preserved, should you wish to proceed. Everything will remain exactly as it is now, files, configuration, and services.

Once we have that confirmation in the ticket, we can move the service to a more performant NVMe node immediately while we continue investigating what is happening on the current one.

We’re here when you’re ready.

All i have to say is: poop.
100% poop.

Opened ticket. Waited. 12 hours later someone else handled it. Nothing has changed. Waited another half a day. No response. Garbage. Poop. Refuse. Junk. Crap.

eijil

Order Number: 2675095921 +1 vcore

strmd

Installed Proxmox Backup Server on my STORAGE-2 service, now performing a simple sync job after having issues even getting the storage disk mounted (takes more than three minutes). Corresponding spikes in CPU with RAM usage at only 14%. I did open a ticket: EKB-715860

eushells

Order Number: 7354644037 (product V-2)
I would like to get +1 vCore if possible.
Order Number: 4847777708 (product V-3)
I would like to get +1 vCore if possible.

Thanks.

eushells

@DeluxHost said:

@eushells said:
Hello! I wanted to purchase a VPS storage, they appear available on the site, but when I ordered them they were out of stock.

You can wait a restock today sir

Thank you! I haven't been able to see the available stock yet

azhai

out of stock

webontop

Order Placed #8804462534
+1 vCore required for free! Preferred VM category is already SOLD!

braunis

Order Number: 4406707759 Thanks!

couldbeanygoo

Order Number: 2748237695, a vcore please and thank you.

nghialele

You guys lucky that can still do yabs, my VM gone after the first day lol

olimpx

@olimpx said:
Order Number: 9159103782, anything as freebies will be great, but preferred extra space:)

@DeluxHost Still haven't received any freebies.

71144139

@olimpx said:

@olimpx said:
Order Number: 9159103782, anything as freebies will be great, but preferred extra space:)

@DeluxHost Still haven't received any freebies.

Me too.

71144139

Please process Ticket #SUF-415968.

sdworlld

Please process Ticket #NBO-406705
And Invoice : #16679

sdworlld

@fitkoh said:

@DeluxHost said:

Opened ticket. Waited. 12 hours later someone else handled it. Nothing has changed. Waited another half a day. No response. Garbage. Poop. Refuse. Junk. Crap.

As of now I don't have to react but yes I am also waiting from past 4 hour for their reply
wish they need to improve over here

DeluxHost

@sdworlld said:

@fitkoh said:

@DeluxHost said:

Opened ticket. Waited. 12 hours later someone else handled it. Nothing has changed. Waited another half a day. No response. Garbage. Poop. Refuse. Junk. Crap.

As of now I don't have to react but yes I am also waiting from past 4 hour for their reply
wish they need to improve over here

Hello, I'll check soon, sorry for the delay.

fitkoh

@sdworlld said:

@fitkoh said:

@DeluxHost said:

Opened ticket. Waited. 12 hours later someone else handled it. Nothing has changed. Waited another half a day. No response. Garbage. Poop. Refuse. Junk. Crap.

As of now I don't have to react but yes I am also waiting from past 4 hour for their reply
wish they need to improve over here

After some waiting Matteo personally handled the migration of 2 VPS affected with severe service degradation.

1 was repaired to my satisfaction and greatly improved. The other was botched during migration. Matteo apologized for mishandling the procedure and failing to verify the repair was effective before returning the service to me.

I'm waiting again for repair on the second VPS.

sdworlld

root@delux:~# df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           588M  1.1M  587M   1% /run
/dev/vda1        29G  3.7G   25G  14% /
tmpfs           2.9G     0  2.9G   0% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/vda16      881M  117M  703M  15% /boot
/dev/vda15      105M  6.2M   99M   6% /boot/efi
tmpfs           588M   12K  588M   1% /run/user/0
/dev/vdb        2.9T   28K  2.8T   1% /mnt/drive-b
root@delux:~#

1. Dude I did place order for 4 TB but I got 2.9 TB May I know the Reason.
2. Invoice ID : #1712-7918-2025 Please upgrade the PORT to 10 Gb/s