Howdy, Stranger!

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


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.

KVM VPS – From €6.99/year (~$8.03) – 512MB–16GB RAM – NVMe – 1Gbps – Amsterdam

1235»

Comments

  • e2e4e2e4 Member

    @VPSLAYER, could you please restock LET-2?

  • happy with the service purchased. ty.

    Thanked by 1VPSLAYER
  • order links all show 404.

  • VoidVoid Member

    Also happy with the €6.99/yr server. Surprisingly good for the price.

    Will there be a restock ? @VPSLAYER

    Thanked by 1VPSLAYER
  • It has worked well so far.

    Thanked by 1VPSLAYER
    1. Could you please clarify whether you have a mandatory KYC process, and is it possible that you might request it at a later stage?
    2. Are there any plans to restock LET-1 and LET-2?
  • @AndreyN said:
    1. Could you please clarify whether you have a mandatory KYC process, and is it possible that you might request it at a later stage?
    2. Are there any plans to restock LET-1 and LET-2?

    No, they dont. Yes, they might, but maybe far future.

    Updates for others:
    status page is just changed, less information, big down time (few hours) was removed.
    after the latest downtime of 10 minutes (scheduled), my average cpu usage increased 25% (vs the day before).

    I feel like the last update reduced disk speed a lot, @VPSLAYER : Did you just change to HDD by accident?

    cat /sys/block/sd*/queue/rotational
    1
    FIO test is bad, 1644 IOPS random 4K read — this is mid-tier SAN/shared storage performance. HDD range.

    util=92.95% at just iodepth=1 — disk is nearly saturated

    fio --name=rand4k --filename=/fio-test --size=1G --rw=randrw --rwmixread=70 --bs=4k --ioengine=libaio --direct=1 --iodepth=1 --runtime=30 --time_based --group_reporting && rm -f /fio-test
    rand4k: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=1
    fio-3.41
    Starting 1 process
    rand4k: Laying out IO file (1 file / 1024MiB)
    Jobs: 1 (f=0): [f(1)][100.0%][r=6672KiB/s,w=2836KiB/s][r=1668,w=709 IOPS][eta 00m:00s]
    rand4k: (groupid=0, jobs=1): err= 0: pid=1934145: Sat Oct 17 16:19:21 2026
    read: IOPS=1644, BW=6577KiB/s (6735kB/s)(193MiB/30003msec)
    slat (usec): min=10, max=1246, avg=17.61, stdev=10.69
    clat (usec): min=13, max=14398, avg=318.67, stdev=346.38
    lat (usec): min=158, max=14412, avg=336.28, stdev=346.67
    clat percentiles (usec):
    | 1.00th=[ 161], 5.00th=[ 169], 10.00th=[ 182], 20.00th=[ 198],
    | 30.00th=[ 225], 40.00th=[ 255], 50.00th=[ 277], 60.00th=[ 351],
    | 70.00th=[ 363], 80.00th=[ 379], 90.00th=[ 396], 95.00th=[ 416],
    | 99.00th=[ 717], 99.50th=[ 1811], 99.90th=[ 5866], 99.95th=[ 6063],
    | 99.99th=[ 6390]
    bw ( KiB/s): min= 3912, max= 8512, per=100.00%, avg=6577.42, stdev=942.33, samples=60
    iops : min= 978, max= 2128, avg=1644.35, stdev=235.59, samples=60
    write: IOPS=703, BW=2814KiB/s (2882kB/s)(82.5MiB/30003msec); 0 zone resets
    slat (usec): min=11, max=307, avg=19.94, stdev= 8.61
    clat (usec): min=2, max=18192, avg=605.70, stdev=1476.15
    lat (usec): min=72, max=18222, avg=625.64, stdev=1476.94
    clat percentiles (usec):
    | 1.00th=[ 67], 5.00th=[ 70], 10.00th=[ 72], 20.00th=[ 75],
    | 30.00th=[ 78], 40.00th=[ 82], 50.00th=[ 86], 60.00th=[ 93],
    | 70.00th=[ 102], 80.00th=[ 119], 90.00th=[ 1663], 95.00th=[ 5211],
    | 99.00th=[ 5932], 99.50th=[ 6128], 99.90th=[ 7242], 99.95th=[10683],
    | 99.99th=[15664]
    bw ( KiB/s): min= 1592, max= 3696, per=99.99%, avg=2814.45, stdev=438.02, samples=60
    iops : min= 398, max= 924, avg=703.60, stdev=109.52, samples=60
    lat (usec) : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=20.35%
    lat (usec) : 250=30.95%, 500=43.26%, 750=0.45%, 1000=0.38%
    lat (msec) : 2=1.63%, 4=0.41%, 10=2.53%, 20=0.02%
    cpu : usr=2.04%, sys=6.19%, ctx=70439, majf=0, minf=12
    IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
    submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
    complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
    issued rwts: total=49332,21109,0,0 short=0,0,0,0 dropped=0,0,0,0
    latency : target=0, window=0, percentile=100.00%, depth=1

    Run status group 0 (all jobs):
    READ: bw=6577KiB/s (6735kB/s), 6577KiB/s-6577KiB/s (6735kB/s-6735kB/s), io=193MiB (202MB), run=30003-30003msec
    WRITE: bw=2814KiB/s (2882kB/s), 2814KiB/s-2814KiB/s (2882kB/s-2882kB/s), io=82.5MiB (86.5MB), run=30003-30003msec

    Disk stats (read/write):
    sda: ios=49579/21025, sectors=414680/172288, merge=476/375, ticks=16012/12947, in_queue=29059, util=92.95%

  • VPSLAYERVPSLAYER Member, Patron Provider

    @CraigRoeder said:

    @AndreyN said:
    1. Could you please clarify whether you have a mandatory KYC process, and is it possible that you might request it at a later stage?
    2. Are there any plans to restock LET-1 and LET-2?

    No, they dont. Yes, they might, but maybe far future.

    Updates for others:
    status page is just changed, less information, big down time (few hours) was removed.
    after the latest downtime of 10 minutes (scheduled), my average cpu usage increased 25% (vs the day before).

    I feel like the last update reduced disk speed a lot, @VPSLAYER : Did you just change to HDD by accident?

    cat /sys/block/sd*/queue/rotational
    1
    FIO test is bad, 1644 IOPS random 4K read — this is mid-tier SAN/shared storage performance. HDD range.

    util=92.95% at just iodepth=1 — disk is nearly saturated

    fio --name=rand4k --filename=/fio-test --size=1G --rw=randrw --rwmixread=70 --bs=4k --ioengine=libaio --direct=1 --iodepth=1 --runtime=30 --time_based --group_reporting && rm -f /fio-test
    rand4k: (g=0): rw=randrw, bs=(R) 4096B-4096B, (W) 4096B-4096B, (T) 4096B-4096B, ioengine=libaio, iodepth=1
    fio-3.41
    Starting 1 process
    rand4k: Laying out IO file (1 file / 1024MiB)
    Jobs: 1 (f=0): [f(1)][100.0%][r=6672KiB/s,w=2836KiB/s][r=1668,w=709 IOPS][eta 00m:00s]
    rand4k: (groupid=0, jobs=1): err= 0: pid=1934145: Sat Oct 17 16:19:21 2026
    read: IOPS=1644, BW=6577KiB/s (6735kB/s)(193MiB/30003msec)
    slat (usec): min=10, max=1246, avg=17.61, stdev=10.69
    clat (usec): min=13, max=14398, avg=318.67, stdev=346.38
    lat (usec): min=158, max=14412, avg=336.28, stdev=346.67
    clat percentiles (usec):
    | 1.00th=[ 161], 5.00th=[ 169], 10.00th=[ 182], 20.00th=[ 198],
    | 30.00th=[ 225], 40.00th=[ 255], 50.00th=[ 277], 60.00th=[ 351],
    | 70.00th=[ 363], 80.00th=[ 379], 90.00th=[ 396], 95.00th=[ 416],
    | 99.00th=[ 717], 99.50th=[ 1811], 99.90th=[ 5866], 99.95th=[ 6063],
    | 99.99th=[ 6390]
    bw ( KiB/s): min= 3912, max= 8512, per=100.00%, avg=6577.42, stdev=942.33, samples=60
    iops : min= 978, max= 2128, avg=1644.35, stdev=235.59, samples=60
    write: IOPS=703, BW=2814KiB/s (2882kB/s)(82.5MiB/30003msec); 0 zone resets
    slat (usec): min=11, max=307, avg=19.94, stdev= 8.61
    clat (usec): min=2, max=18192, avg=605.70, stdev=1476.15
    lat (usec): min=72, max=18222, avg=625.64, stdev=1476.94
    clat percentiles (usec):
    | 1.00th=[ 67], 5.00th=[ 70], 10.00th=[ 72], 20.00th=[ 75],
    | 30.00th=[ 78], 40.00th=[ 82], 50.00th=[ 86], 60.00th=[ 93],
    | 70.00th=[ 102], 80.00th=[ 119], 90.00th=[ 1663], 95.00th=[ 5211],
    | 99.00th=[ 5932], 99.50th=[ 6128], 99.90th=[ 7242], 99.95th=[10683],
    | 99.99th=[15664]
    bw ( KiB/s): min= 1592, max= 3696, per=99.99%, avg=2814.45, stdev=438.02, samples=60
    iops : min= 398, max= 924, avg=703.60, stdev=109.52, samples=60
    lat (usec) : 4=0.01%, 10=0.01%, 20=0.01%, 50=0.01%, 100=20.35%
    lat (usec) : 250=30.95%, 500=43.26%, 750=0.45%, 1000=0.38%
    lat (msec) : 2=1.63%, 4=0.41%, 10=2.53%, 20=0.02%
    cpu : usr=2.04%, sys=6.19%, ctx=70439, majf=0, minf=12
    IO depths : 1=100.0%, 2=0.0%, 4=0.0%, 8=0.0%, 16=0.0%, 32=0.0%, >=64=0.0%
    submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
    complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, >=64=0.0%
    issued rwts: total=49332,21109,0,0 short=0,0,0,0 dropped=0,0,0,0
    latency : target=0, window=0, percentile=100.00%, depth=1

    Run status group 0 (all jobs):
    READ: bw=6577KiB/s (6735kB/s), 6577KiB/s-6577KiB/s (6735kB/s-6735kB/s), io=193MiB (202MB), run=30003-30003msec
    WRITE: bw=2814KiB/s (2882kB/s), 2814KiB/s-2814KiB/s (2882kB/s-2882kB/s), io=82.5MiB (86.5MB), run=30003-30003msec

    Disk stats (read/write):
    sda: ios=49579/21025, sectors=414680/172288, merge=476/375, ticks=16012/12947, in_queue=29059, util=92.95%

    1) status page is just changed, less information
    We did that for security reasons

    2) big down time (few hours) was removed.
    the old downtime logs are still existing, just only for us now.

    3) Did you just change to HDD by accident?
    No we dont use HDDs for vps hosting.

    Please open a ticket so we can check more.

  • All the links are showing 404 errors. When will the items be back in stock?

  • Is there an upgrade Path from let1 to let2 retaining recurring discount would that i realize 0.5g ram won’t allow amneziavpn?

  • @tenebriouslypuissant said:
    Is there an upgrade Path from let1 to let2 retaining recurring discount would that i realize 0.5g ram won’t allow amneziavpn?

    AmneziWG isn't compatible with VPS from this provider, is it?

  • le_creaturale_creatura Member
    edited October 22

    Aww, too bad that I slept on those special plans.

    Regarding the service, I've been a Vpslayer customer since July, so far it's okay, the only rough point is the frequency of downtimes in ams01, I hope you'll improve on that matter.

  • glws

    i missed it :C

  • VPSLAYERVPSLAYER Member, Patron Provider

    @le_creatura said:
    Aww, too bad that I slept on those special plans.

    Regarding the service, I've been a Vpslayer customer since July, so far it's okay, the only rough point is the frequency of downtimes in ams01, I hope you'll improve on that matter.

    sorry, we are working on it to be better. Most outages do not occur because our infrastructure itself is unstable. rather, they tend to be network related. However we are in close communication to get better

    Thanked by 1le_creatura
Sign In or Register to comment.