Is anyone having issues with ImpactVPS this week?

mudmin

I have multiple servers across multiple data centers that are showing very light server load, but are crawling and timing out. Performance has been impeccable since 2016 or so. This is a first for me.

deank

Your ticket has been received at Lowend support department.

We will ensure that your voice is heard. You can expect to receive a reply to your ticket soon.

mudmin

I didn't know I was filling out a ticket Thanks though.

DP

You have now been impacted by ImpactVPS.

zafouhar

@deank said:
Your ticket has been received at Lowend support department.

We will ensure that your voice is heard. You can expect to receive a reply to your ticket soon.

Lowend drama support department*

deank

I removed the drama part since I didn't smell a scent of PMS.

FrankZ

I have not noticed any problems with mine, but I am only using it as a jump box, so no cpu or I/O. From the yabs below it seems that the I/O is down quite a bit, and CPU @ 1437.036 MHz says there is no load on the node or VPS is now restricted.
Just my 2 cents there Mike Schmidt.

Dallas Node:dal3

# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
#              Yet-Another-Bench-Script              #
#                     v2021-05-28                    #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #

Thu Jun  3 15:57:15 CDT 2021

Basic System Information:
---------------------------------
Processor  : Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz
CPU cores  : 1 @ 1437.036 MHz
AES-NI     : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM        : 512.0 MiB
Swap       : 0.0 KiB
Disk       : 12.1 GiB

fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k            (IOPS) | 64k           (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 6.83 MB/s     (1.7k) | 29.21 MB/s     (456)
Write      | 6.85 MB/s     (1.7k) | 29.63 MB/s     (463)
Total      | 13.68 MB/s    (3.4k) | 58.84 MB/s     (919)
           |                      |
Block Size | 512k          (IOPS) | 1m            (IOPS)
  ------   | ---            ----  | ----           ----
Read       | 33.57 MB/s      (65) | 29.73 MB/s      (29)
Write      | 35.71 MB/s      (69) | 32.52 MB/s      (31)
Total      | 69.29 MB/s     (134) | 62.25 MB/s      (60)

iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider        | Location (Link)           | Send Speed      | Recv Speed
                |                           |                 |
Clouvider       | London, UK (10G)          | 1.59 Gbits/sec  | 1.06 Gbits/sec
Online.net      | Paris, FR (10G)           | 2.00 Gbits/sec  | 1.49 Gbits/sec
WorldStream     | The Netherlands (10G)     | 1.26 Gbits/sec  | 1.07 Gbits/sec
Biznet          | Jakarta, Indonesia (1G)   | 511 Mbits/sec   | 62.3 Mbits/sec
Clouvider       | NYC, NY, US (10G)         | 2.40 Gbits/sec  | 2.68 Gbits/sec
Velocity Online | Tallahassee, FL, US (10G) | 3.69 Gbits/sec  | 3.99 Gbits/sec
Clouvider       | Los Angeles, CA, US (10G) | 2.29 Gbits/sec  | 3.15 Gbits/sec
Iveloz Telecom  | Sao Paulo, BR (2G)        | 189 Mbits/sec   | 814 Mbits/sec

Geekbench 5 test failed. Run manually to determine cause.

TimboJones

I don't have any notifications for my openvz or kvm in Seattle.

However, if I saw disk speeds this low, I'd ticket them to ask them to check the RAID. For years, a quick dd test would be 300+MB/s and once when I noticed lag I checked it and it was 60MB/s. Ticketed support and they confirmed raid issue and next day things were normal again.

Their support is best out of any of the provider's I use, open a ticket and it'll be addressed quickly.

Also, point out the CPU frequency to their support, it should be 2.2GHz and likely need to change a setting.

TimboJones

@deank said:
Your ticket has been received at Lowend support department.

We will ensure that your voice is heard. You can expect to receive a reply to your ticket soon.

You're doing it wrong. He's not asking anyone to fix it, only asking if others experience similar symptoms as him. It's self troubleshooting, which everyone should start with and be encouraged at LET, don't be a cunt.