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
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
Rabisu - Hosting Solutions
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.

2025 Black Friday / Cyber Monday: FLASH SALE & MEGATHREAD - "The Trade War"

1727729731732733

Comments

  • @AlteredParadox said:

    @Arirang said:
    what will you use it for?

    Llama pictures

    Idle 🫠

    Thanked by 1NetPIMP
  • daily check in

  • rpqurpqu Member
    edited December 2025

    reposting replenished deals

    @NovaCloudHosting said:

    @ahson said:
    Offers have ended? Can't order anymore.

    https://shop.novacloud-hosting.com/store/winter-sale-2025
    Everything is still in stock. If you encounter an error on the order process, send me a DM and I'll help you.

    @bingobangobongo said:
    Hey Ya'll - quick update on order provisioning - All orders from Dec 2nd deals are provisioned now. Billing dates are updated and resources you were eligible for have been upgraded!

    I've thrown a couple more things in stock for the kind friends who read this thread - https://www.hostbilby.com/deals

    Happy Weekend!

  • 7$ PER YEAR DEALS
    plx

  • tarisutarisu Member, Host Rep

    @springai said:

    @tarisu said:

    @tarisu said:
    Hello Everyone!

    Let's end the 2025 LET Trade War with Tarisu Deals!

    With MRTARISU50 promo code 5 customer will have 50% OFF on VPS Server plans!
    Campaign expires tomorrow!

    https://tarisu.com/category/vps-server

    Regards.

    ( New Tarisu concept will be released soon )

    Still available!

    A TCKN is required to make a purchase, but since I am not a Turkish citizen and do not have a TCKN, I am unable to buy it.

    If you choose Turkey as country while registering it asks for TCKN, if you can create a ticket and share date of birth we can fix it.

  • anakaraanakara Member
    edited December 2025

    Add new idle

    Basic System Information:
    ---------------------------------
    Uptime : 0 days, 8 hours, 30 minutes
    Processor : AMD EPYC 7713P 64-Core Processor
    CPU cores : 12 @ 1996.249 MHz
    AES-NI : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM : 23.5 GiB
    Swap : 1.5 GiB
    Disk : 154.9 GiB
    Distro : Ubuntu 24.04.3 LTS
    Kernel : 6.8.0-90-generic
    VM Type : KVM
    IPv4/IPv6 : ✔ Online / ❌ Offline

    IPv4 Network Information:
    ---------------------------------
    ISP : HostBilby Inc.
    ASN : AS401665 HostBilby Inc.
    Host : HostBilby Inc
    Location : Toronto, Ontario (ON)
    Country : Canada

    fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda1):
    ---------------------------------
    Block Size | 4k (IOPS) | 64k (IOPS)
    ------ | --- ---- | ---- ----
    Read | 180.51 MB/s (45.1k) | 1.99 GB/s (31.1k)
    Write | 180.99 MB/s (45.2k) | 2.00 GB/s (31.3k)
    Total | 361.51 MB/s (90.3k) | 4.00 GB/s (62.5k)
    | |
    Block Size | 512k (IOPS) | 1m (IOPS)
    ------ | --- ---- | ---- ----
    Read | 2.35 GB/s (4.6k) | 2.28 GB/s (2.2k)
    Write | 2.48 GB/s (4.8k) | 2.43 GB/s (2.3k)
    Total | 4.84 GB/s (9.4k) | 4.71 GB/s (4.6k)

    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider | Location (Link) | Send Speed | Recv Speed | Ping
    ----- | ----- | ---- | ---- | ----
    Clouvider | London, UK (10G) | 1.93 Gbits/sec | 1.80 Gbits/sec | 83.0 ms
    Eranium | Amsterdam, NL (100G) | 2.46 Gbits/sec | 2.70 Gbits/sec | 92.6 ms
    Uztelecom | Tashkent, UZ (10G) | 1.13 Gbits/sec | 949 Mbits/sec | 178 ms
    Leaseweb | Singapore, SG (10G) | 917 Mbits/sec | 1.06 Gbits/sec | 213 ms
    Clouvider | Los Angeles, CA, US (10G) | 2.90 Gbits/sec | 2.92 Gbits/sec | 66.8 ms
    Leaseweb | NYC, NY, US (10G) | 5.38 Gbits/sec | 4.55 Gbits/sec | 19.4 ms
    Edgoo | Sao Paulo, BR (1G) | 932 Mbits/sec | 993 Mbits/sec | 201 ms

    Geekbench 6 Benchmark Test:
    ---------------------------------
    Test | Value
    |
    Single Core | 1236
    Multi Core | 6824
    Full Test | https://browser.geekbench.com/v6/cpu/15560533

    YABS completed in 9 min 59 sec

    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    #              Yet-Another-Bench-Script              #
    #                     v2025-04-20                    #
    # https://github.com/masonr/yet-another-bench-script #
    # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
    
    Sat Dec 13 07:27:35 CST 2025
    
    Basic System Information:
    ---------------------------------
    Uptime     : 0 days, 0 hours, 7 minutes
    Processor  : AMD EPYC 7713P 64-Core Processor
    CPU cores  : 12 @ 1996.249 MHz
    AES-NI     : ✔ Enabled
    VM-x/AMD-V : ✔ Enabled
    RAM        : 23.5 GiB
    Swap       : 1024.0 MiB
    Disk       : 157.5 GiB
    Distro     : Debian GNU/Linux 13 (trixie)
    Kernel     : 6.12.57+deb13-amd64
    VM Type    : KVM
    IPv4/IPv6  : ✔ Online / ✔ Online
    
    IPv6 Network Information:
    ---------------------------------
    ISP        : HostBilby Inc
    ASN        : AS401665 HostBilby Inc.
    Host       : Zappie Host LLC
    Location   : Toronto, Ontario (ON)
    Country    : Canada
    
    fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda3):
    ---------------------------------
    Block Size | 4k            (IOPS) | 64k           (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 185.96 MB/s  (46.4k) | 2.11 GB/s    (32.9k)
    Write      | 186.46 MB/s  (46.6k) | 2.12 GB/s    (33.1k)
    Total      | 372.42 MB/s  (93.1k) | 4.23 GB/s    (66.1k)
               |                      |                     
    Block Size | 512k          (IOPS) | 1m            (IOPS)
      ------   | ---            ----  | ----           ---- 
    Read       | 2.26 GB/s     (4.4k) | 2.12 GB/s     (2.0k)
    Write      | 2.39 GB/s     (4.6k) | 2.27 GB/s     (2.2k)
    Total      | 4.66 GB/s     (9.1k) | 4.40 GB/s     (4.2k)
    
    iperf3 Network Speed Tests (IPv4):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 1.84 Gbits/sec  | 1.59 Gbits/sec  | 77.0 ms        
    Eranium         | Amsterdam, NL (100G)      | 2.42 Gbits/sec  | 2.81 Gbits/sec  | 81.0 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 1.02 Gbits/sec  | 997 Mbits/sec   | 169 ms         
    Leaseweb        | Singapore, SG (10G)       | 832 Mbits/sec   | 980 Mbits/sec   | 217 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 2.51 Gbits/sec  | 339 Mbits/sec   | 65.1 ms        
    Leaseweb        | NYC, NY, US (10G)         | 5.39 Gbits/sec  | 4.50 Gbits/sec  | 13.2 ms        
    Edgoo           | Sao Paulo, BR (1G)        | 894 Mbits/sec   | 1.15 Gbits/sec  | 121 ms         
    
    iperf3 Network Speed Tests (IPv6):
    ---------------------------------
    Provider        | Location (Link)           | Send Speed      | Recv Speed      | Ping           
    -----           | -----                     | ----            | ----            | ----           
    Clouvider       | London, UK (10G)          | 2.35 Gbits/sec  | 2.60 Gbits/sec  | 77.1 ms        
    Eranium         | Amsterdam, NL (100G)      | 2.60 Gbits/sec  | 2.96 Gbits/sec  | 81.0 ms        
    Uztelecom       | Tashkent, UZ (10G)        | 1.66 Mbits/sec  | 1.02 Gbits/sec  | 169 ms         
    Leaseweb        | Singapore, SG (10G)       | 842 Mbits/sec   | 775 Mbits/sec   | 217 ms         
    Clouvider       | Los Angeles, CA, US (10G) | 2.12 Gbits/sec  | 271 Mbits/sec   | 64.8 ms        
    Leaseweb        | NYC, NY, US (10G)         | 5.21 Gbits/sec  | 4.44 Gbits/sec  | 13.1 ms        
    Edgoo           | Sao Paulo, BR (1G)        | 1.80 Gbits/sec  | 1.71 Gbits/sec  | 120 ms         
    
    Geekbench 6 Benchmark Test:
    ---------------------------------
    Test            | Value                         
                    |                               
    Single Core     | 1178                          
    Multi Core      | 7264                          
    Full Test       | https://browser.geekbench.com/v6/cpu/15549220
    
    YABS completed in 13 min 10 sec
    

    Woke up to a shiny new HostBilby vps!

  • PulsedMediaPulsedMedia Member, Patron Provider

    @rpqu said:
    @PulsedMedia

    Hi,
    [redacted] has suffered a catastrophic data loss.
    Despite being RAID0 (where eventual disk failure is expected), this time the cause was not the RAID set – it was a very rare software bug that has existed since at least 2011 and finally triggered on this node.
     
    Impact for you:
    - The /home filesystem on this server was wiped.
    - All user home directories and data on this node are unfortunately unrecoverable.
    We’ve written a detailed public announcement and incident report here:
    https://pulsedmedia.com/clients/index.php/announcements/650/PMSS-Rare-14-Year-Old-Bug-Found-and-Resolved-on-Single-Node.-Catastrophic-rm--rf-orhome.html
     
    The short version:

    • No sign of external compromise or intrusion.
    • A quota cron (updateQuotas.php) consumed fatal error output from listUsers.php during a partial update and ended up running rm -rf /home as root.
    • The boot NVMe in this server was also failing, so this node would have needed maintenance and migration soon regardless.
    • The bug has now been fixed in PMSS and the failure path removed. The patch is already rolling out across the fleet.
      Next steps for your service
      We will provision a fresh service to replace this one. Because this class of servers is currently quite full, the most likely path is:

    • maintenance + reinstall of [redacted], and

    • recreating accounts there (or moving you to an equivalent or better node),
      with an ETA of a few business days. We will email you again when your new service is ready.
      Compensation
      Even though the service is RAID0 and the SLA does not normally cover data loss, we are adding +2 months of extra service time for you once the new service is set up.
      You do not need to do anything right now. If you were affected by this incident, you’re receiving this email; if you didn’t get this email, your service and data are unaffected.
      Best regards,
      [redacted]
      Pulsed Media

    Well, it hasn't even been 2 weeks since my CM order. I thought it was a prank mail, then I saw the link.

    Yes. Imagine the WTFs over here when a 14 year old bug gets discovered like this.

    Sorry for the wait, that seedbox series is ~completely full after BF/CM.

  • waiting 7$/y

  • @openid said:
    waiting 7$/y

    Don't... unless you want to end up like this.

  • @MS said:

    @openid said:
    waiting 7$/y

    Don't... unless you want to end up like this.


    ok :'(

    Thanked by 1_MS_
  • @PulsedMedia said:

    @rpqu said:
    @PulsedMedia

    Hi,
    [redacted] has suffered a catastrophic data loss.
    Despite being RAID0 (where eventual disk failure is expected), this time the cause was not the RAID set – it was a very rare software bug that has existed since at least 2011 and finally triggered on this node.
     
    Impact for you:
    - The /home filesystem on this server was wiped.
    - All user home directories and data on this node are unfortunately unrecoverable.
    We’ve written a detailed public announcement and incident report here:
    https://pulsedmedia.com/clients/index.php/announcements/650/PMSS-Rare-14-Year-Old-Bug-Found-and-Resolved-on-Single-Node.-Catastrophic-rm--rf-orhome.html
     
    The short version:

    • No sign of external compromise or intrusion.
    • A quota cron (updateQuotas.php) consumed fatal error output from listUsers.php during a partial update and ended up running rm -rf /home as root.
    • The boot NVMe in this server was also failing, so this node would have needed maintenance and migration soon regardless.
    • The bug has now been fixed in PMSS and the failure path removed. The patch is already rolling out across the fleet.
      Next steps for your service
      We will provision a fresh service to replace this one. Because this class of servers is currently quite full, the most likely path is:

    • maintenance + reinstall of [redacted], and

    • recreating accounts there (or moving you to an equivalent or better node),
      with an ETA of a few business days. We will email you again when your new service is ready.
      Compensation
      Even though the service is RAID0 and the SLA does not normally cover data loss, we are adding +2 months of extra service time for you once the new service is set up.
      You do not need to do anything right now. If you were affected by this incident, you’re receiving this email; if you didn’t get this email, your service and data are unaffected.
      Best regards,
      [redacted]
      Pulsed Media

    Well, it hasn't even been 2 weeks since my CM order. I thought it was a prank mail, then I saw the link.

    Yes. Imagine the WTFs over here when a 14 year old bug gets discovered like this.

    I totally understand. It's hard to maintain codebase at such scale. There must be tons of awkward stare, eating emergency mämmi, sleepless night, hours at sauna and alternating dip at ice-filled pool and beating to the back with hot barbed wire to build character. Quintessentially Finnish.
    Anyway, please fill out the "WTFs" that happened, which would be inappropriate or extraneous to be written on your blog. (please get approval from your legal, opsec, HR, GA, etc)

    Sorry for the wait, that seedbox series is ~completely full after BF/CM.

    No worries, I haven't used the seedbox yet. But, I hope it will be running well by Christmas & new year holiday and never be broken in such hilarious ways when I store precious data on it .
    If not:

    • May your sauna heater die mid-löyly
    • May you forever relive the exact moment of your greatest blunder
      JK 🤣🤣🤣🤣🤣🤣🤣🤣🤣
  • PulsedMediaPulsedMedia Member, Patron Provider

    @rpqu said:

    @PulsedMedia said:

    @rpqu said:
    @PulsedMedia

    Hi,
    [redacted] has suffered a catastrophic data loss.
    Despite being RAID0 (where eventual disk failure is expected), this time the cause was not the RAID set – it was a very rare software bug that has existed since at least 2011 and finally triggered on this node.
     
    Impact for you:
    - The /home filesystem on this server was wiped.
    - All user home directories and data on this node are unfortunately unrecoverable.
    We’ve written a detailed public announcement and incident report here:
    https://pulsedmedia.com/clients/index.php/announcements/650/PMSS-Rare-14-Year-Old-Bug-Found-and-Resolved-on-Single-Node.-Catastrophic-rm--rf-orhome.html
     
    The short version:

    • No sign of external compromise or intrusion.
    • A quota cron (updateQuotas.php) consumed fatal error output from listUsers.php during a partial update and ended up running rm -rf /home as root.
    • The boot NVMe in this server was also failing, so this node would have needed maintenance and migration soon regardless.
    • The bug has now been fixed in PMSS and the failure path removed. The patch is already rolling out across the fleet.
      Next steps for your service
      We will provision a fresh service to replace this one. Because this class of servers is currently quite full, the most likely path is:

    • maintenance + reinstall of [redacted], and

    • recreating accounts there (or moving you to an equivalent or better node),
      with an ETA of a few business days. We will email you again when your new service is ready.
      Compensation
      Even though the service is RAID0 and the SLA does not normally cover data loss, we are adding +2 months of extra service time for you once the new service is set up.
      You do not need to do anything right now. If you were affected by this incident, you’re receiving this email; if you didn’t get this email, your service and data are unaffected.
      Best regards,
      [redacted]
      Pulsed Media

    Well, it hasn't even been 2 weeks since my CM order. I thought it was a prank mail, then I saw the link.

    Yes. Imagine the WTFs over here when a 14 year old bug gets discovered like this.

    I totally understand. It's hard to maintain codebase at such scale. There must be tons of awkward stare, eating emergency mämmi, sleepless night, hours at sauna and alternating dip at ice-filled pool and beating to the back with hot barbed wire to build character. Quintessentially Finnish.
    Anyway, please fill out the "WTFs" that happened, which would be inappropriate or extraneous to be written on your blog. (please get approval from your legal, opsec, HR, GA, etc)

    Sorry for the wait, that seedbox series is ~completely full after BF/CM.

    No worries, I haven't used the seedbox yet. But, I hope it will be running well by Christmas & new year holiday and never be broken in such hilarious ways when I store precious data on it .
    If not:

    • May your sauna heater die mid-löyly
    • May you forever relive the exact moment of your greatest blunder
      JK 🤣🤣🤣🤣🤣🤣🤣🤣🤣

    In the email was link, and we have the full incident report. through announcements you can see as well.

    It's still RAID0, so hope you keep backups of those precious linux isos!

    phew, saved! Wood burning sauna! ;)

  • @PulsedMedia said:

    @rpqu said:

    @PulsedMedia said:

    @rpqu said:
    @PulsedMedia

    Hi,
    [redacted] has suffered a catastrophic data loss.
    Despite being RAID0 (where eventual disk failure is expected), this time the cause was not the RAID set – it was a very rare software bug that has existed since at least 2011 and finally triggered on this node.
     
    Impact for you:
    - The /home filesystem on this server was wiped.
    - All user home directories and data on this node are unfortunately unrecoverable.
    We’ve written a detailed public announcement and incident report here:
    https://pulsedmedia.com/clients/index.php/announcements/650/PMSS-Rare-14-Year-Old-Bug-Found-and-Resolved-on-Single-Node.-Catastrophic-rm--rf-orhome.html
     
    The short version:

    • No sign of external compromise or intrusion.
    • A quota cron (updateQuotas.php) consumed fatal error output from listUsers.php during a partial update and ended up running rm -rf /home as root.
    • The boot NVMe in this server was also failing, so this node would have needed maintenance and migration soon regardless.
    • The bug has now been fixed in PMSS and the failure path removed. The patch is already rolling out across the fleet.
      Next steps for your service
      We will provision a fresh service to replace this one. Because this class of servers is currently quite full, the most likely path is:

    • maintenance + reinstall of [redacted], and

    • recreating accounts there (or moving you to an equivalent or better node),
      with an ETA of a few business days. We will email you again when your new service is ready.
      Compensation
      Even though the service is RAID0 and the SLA does not normally cover data loss, we are adding +2 months of extra service time for you once the new service is set up.
      You do not need to do anything right now. If you were affected by this incident, you’re receiving this email; if you didn’t get this email, your service and data are unaffected.
      Best regards,
      [redacted]
      Pulsed Media

    Well, it hasn't even been 2 weeks since my CM order. I thought it was a prank mail, then I saw the link.

    Yes. Imagine the WTFs over here when a 14 year old bug gets discovered like this.

    I totally understand. It's hard to maintain codebase at such scale. There must be tons of awkward stare, eating emergency mämmi, sleepless night, hours at sauna and alternating dip at ice-filled pool and beating to the back with hot barbed wire to build character. Quintessentially Finnish.
    Anyway, please fill out the "WTFs" that happened, which would be inappropriate or extraneous to be written on your blog. (please get approval from your legal, opsec, HR, GA, etc)

    Sorry for the wait, that seedbox series is ~completely full after BF/CM.

    No worries, I haven't used the seedbox yet. But, I hope it will be running well by Christmas & new year holiday and never be broken in such hilarious ways when I store precious data on it .
    If not:

    • May your sauna heater die mid-löyly
    • May you forever relive the exact moment of your greatest blunder
      JK 🤣🤣🤣🤣🤣🤣🤣🤣🤣

    In the email was link, and we have the full incident report. through announcements you can see as well.

    But, where's the curses, coffee intake increase, sauna session (with hot barbed wire to build character), the employees slowly walking around the room before taking their laptop and separately walk to the forest before regaining their composure? There's no way none of this happened.

    It's still RAID0, so hope you keep backups of those precious linux isos!

    Yeah, those are precious and I have to contribute to society too. Beside the benevolent purpose, I'm going to use it too as a place to store db backup, as I observe the 3-2-1 rule at minimum.

    phew, saved! Wood burning sauna! ;)

    Okay, if it spectacularly failed (again, especially within another short time)

    • May your coffee always lukewarm
    • May a tourist always chose the empty seat next to you and try to make a small talk

    Note: It's a joke. May you find mushroom in the forest.

    Thanked by 1PulsedMedia
  • you guys its ALMOST CHRISTMAS!!!

    Thanked by 1plumberg
  • plumbergplumberg Veteran, Megathread Squad

    @AlteredParadox said:
    you guys its ALMOST CHRISTMAS!!!

    No
    Its almost Black Friday 2026

    Thanked by 2ralf Smigit
  • @plumberg said:
    Its almost Black Friday 2026

    Thanked by 3plumberg op23 ralf
  • MOARRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR

  • @NetPIMP said:

    @plumberg said:
    Its almost Black Friday 2026

  • Moarrrrrrrrrrr69

  • Something tells me people want to keep this thread... just for fun and trolling.

    Come on! We have to move on. Christmas is coming and we need to spend time with the loved ones.

    LET this thread die! It has served its purpose well, especially considering the existing economic crisis.

  • Thanked by 3op23 Decicus ralf
  • @default said:
    Something tells me people want to keep this thread... just for fun and trolling.

    Come on! We have to move on. Christmas is coming and we need to spend time with the loved ones.

    LET this thread die! It has served its purpose well, especially considering the existing economic crisis.

    Thanked by 3NetPIMP op23 ralf
  • @default said:
    Something tells me people want to keep this thread... just for fun and trolling.

    Come on! We have to move on. Christmas is coming and we need to spend time with the loved ones.

    LET this thread die! It has served its purpose well, especially considering the existing economic crisis.

  • anakaraanakara Member
    edited December 2025

    @AlteredParadox said:

    @default said:
    Something tells me people want to keep this thread... just for fun and trolling.

    Come on! We have to move on. Christmas is coming and we need to spend time with the loved ones.

    LET this thread die! It has served its purpose well, especially considering the existing economic crisis.

    😈

  • Here's an idea:

  • plumbergplumberg Veteran, Megathread Squad

    @MS said:
    Here's an idea:

    99 bottles of beer on the wall.
    99 bottles of beer.
    Take one down, pass it around,
    98 bottles of beer on the wall.

    Thanked by 2NetPIMP _MS_
  • @plumberg said:

    @MS said:
    Here's an idea:

    99 bottles of beer on the wall.
    99 bottles of beer.
    Take one down, pass it around,
    98 bottles of beer on the wall.

    98 bottles of beer on the wall.
    98 bottles of beer.
    Take one down, pass it around,
    97 bottles of beer on the wall.

    Thanked by 1plumberg
  • Should we close this topic now or wait until page 1000?

  • plumbergplumberg Veteran, Megathread Squad

    @dzungbb said:
    Should we close this topic now or wait until page 1000?

    Still got 97 beers to go 🍻

    Thanked by 1_MS_
  • 97 bottles of beer on the wall.
    97 bottles of beer.
    Take one down, pass it around,
    96 bottles of beer on the wall

    Thanked by 1plumberg
This discussion has been closed.