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.

Has c-servers started deleting low-priced VPS instances?

2»

Comments

  • xvpsxvps Member
    edited October 1

    @Obelous said:

    @xvps said:

    @xieyang said:

    @alfatarsos said:
    The only VMs ever eliminated were the ones for the users that had executed fraud at Houston, Texas (Zeta.10), as described in March/April 2026 and sorted out at the time. That will most certainly include yours.

    There are many dozens of VMs at that price that stay available and working at Zeta.10 Houston - therefore, implying that we are deleting any services by cost is wrong.

    Good attempt to bring here some drama, though.

    The VPS was actually purchased on July 2nd, making it impossible for the fraud you allege—supposedly committed in March or April—to have taken place; after all, one cannot be held responsible for something that never happened.

    You are reading the date wrong. You bought it the 7th february 2026.


    (@alfatarsos, look at the screenshot again. He is lying.)

    Wait, are you telling me there aren't 31 months in a year!?

    Of course there are 31 months in a year.

    Here are the 31 months divided across the four traditional seasons:

    Winter
    •
    1. Prima (12 days) – The first month of the year
    •
    2. Gelus (12 days) – Named after frost
    •
    3. Skadi (12 days) – Named after the winter goddess
    •
    4. Nova (12 days) – The new month
    •
    5. Frika (11 days) – The middle of winter
    •
    6. Boreas (11 days) – Named after the north wind
    •
    7. Glacies (11 days) – Named after ice
    •
    8. Thaw (11 days) – The month when the thaw begins

    Spring
    •
    9. Anemo (12 days) – Named after the spring wind
    •
    10. Flora (12 days) – The blooming period
    •
    11. Zephyr (12 days) – The mild west wind
    •
    12. Germen (12 days) – The sprouting month
    •
    13. Viridis (12 days) – The month when everything turns green
    •
    14. Pluvia (11 days) – The spring rain
    •
    15. Aura (11 days) – The fresh breeze
    •
    16. Ceres (11 days) – Named after the goddess of agriculture

    Summer
    •
    17. Solaria (12 days) – The month with the most sunlight
    •
    18. Aestas (12 days) – High summer
    •
    19. Helios (12 days) – Named after the sun god
    •
    20. Therma (12 days) – The hottest month
    •
    21. Midra (12 days) – The midsummer month
    •
    22. Fulmen (11 days) – The month of summer thunder
    •
    23. Pyra (11 days) – The peak of the heat
    •
    24. Messis (11 days) – The early harvest

    Autumn
    •
    25. Autumnus (12 days) – The start of autumn
    •
    26. Opis (12 days) – Named after the harvest goddess
    •
    27. Folium (12 days) – The month when the leaves fall
    •
    28. Vindemia (12 days) – The grape harvest
    •
    29. Kora (11 days) – The month of the underworld
    •
    30. Hesperis (11 days) – The month of the evening sun
    •
    31. Ultima (11 days) – The absolute last month of the year

    Note: In leap years (366 days), the very last month, Ultima, gets one extra day, making it 12 days long.

    (The above answer is written by SI)

    Thanked by 1zejjnt
  • xieyangxieyang Member
    edited October 1

    @xvps
    Ahem, actually it's 52 months—seven days each month.

    Thanked by 2zejjnt Saragoldfarb
  • 🤓☝️
    Achually here's 8760 months, one per each hour.

    Thanked by 2zejjnt Saragoldfarb
  • SaragoldfarbSaragoldfarb Veteran, Megathread Squad

    :D

  • alfatarsosalfatarsos Member, Host Rep

    Okay, issue now sorted out. An API call from the WebStore actually went the wrong way on 30-09 and mistakenly eliminated a different VM on the Portal's database.

    I've not only made the service available again, but also corrected the sections of the code where the issue arose, both at the WebStore module and at the Portal, and this is not expected to happen again.

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    Thanked by 3insivimu jsg xvps
  • @alfatarsos said:

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    To be fair with @xieyang they said that their server must have been deleted sometimes within the past ten day.

    @xieyang said:

    However, this VPS was deleted within the past ten days.

  • alfatarsosalfatarsos Member, Host Rep
    edited October 1

    @fredo1664 said:

    @alfatarsos said:

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    To be fair with @xieyang they said that their server must have been deleted sometimes within the past ten day.

    @xieyang said:

    However, this VPS was deleted within the past ten days.

    I actually meant that period where he first said it was February, then July, then got the expiries wrong, etc... This one was actually correct and a good hint for what had happenned.

    Thanked by 1fredo1664
  • @alfatarsos said:
    Okay, issue now sorted out. An API call from the WebStore actually went the wrong way on 30-09 and mistakenly eliminated a different VM on the Portal's database.

    I've not only made the service available again, but also corrected the sections of the code where the issue arose, both at the WebStore module and at the Portal, and this is not expected to happen again.

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    So it's your own fuck up then, user is not at fault (like abuse) as you claimed earlier.

    Thanked by 2tentor Obelous
  • alfatarsosalfatarsos Member, Host Rep
    edited October 1

    @barbaros said:

    @alfatarsos said:
    Okay, issue now sorted out. An API call from the WebStore actually went the wrong way on 30-09 and mistakenly eliminated a different VM on the Portal's database.

    I've not only made the service available again, but also corrected the sections of the code where the issue arose, both at the WebStore module and at the Portal, and this is not expected to happen again.

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    So it's your own fuck up then, user is not at fault (like abuse) as you claimed earlier.

    An automated system's fuck up, and one that gets it right hundreds of times per week on dozens of different functions. Happens.

    I only advanced that one because the last two times someone mentioned that it was always Zeta.10 Houston, which is old news by far now. But I didn't entirely close the door to being something else, hence the use of the word "certainly" early on - which has eventually proved to be the case.

    To make it 100% clear: yes, the user was not at fault for any abuse. There was an early correlation to Zeta.10 which has proved not precise. The issue is now sorted out.

  • @alfatarsos said:

    @barbaros said:

    @alfatarsos said:
    Okay, issue now sorted out. An API call from the WebStore actually went the wrong way on 30-09 and mistakenly eliminated a different VM on the Portal's database.

    I've not only made the service available again, but also corrected the sections of the code where the issue arose, both at the WebStore module and at the Portal, and this is not expected to happen again.

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    So it's your own fuck up then, user is not at fault (like abuse) as you claimed earlier.

    An automated system's fuck up, and one that gets it right hundreds of times per week on dozens of different functions. Happens.

    I only advanced that one because the last two times someone mentioned that it was always Zeta.10 Houston, which is old news by far now. But I didn't entirely close the door to being something else, hence the use of the word "certainly" early on - which has eventually proved to be the case.

    To make it 100% clear: yes, the user was not at fault for any abuse. There was an early correlation to Zeta.10 which has proved not precise.

    Apology?

  • zedzed Veteran

    @zed said:
    looking forward to the highly-detailed overly-technical explanation for this heh.

    @zed said:
    i think it stands for consistent.

    Thanked by 1Saragoldfarb
  • alfatarsosalfatarsos Member, Host Rep

    @Obelous said:

    @alfatarsos said:

    @barbaros said:

    @alfatarsos said:
    Okay, issue now sorted out. An API call from the WebStore actually went the wrong way on 30-09 and mistakenly eliminated a different VM on the Portal's database.

    I've not only made the service available again, but also corrected the sections of the code where the issue arose, both at the WebStore module and at the Portal, and this is not expected to happen again.

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    So it's your own fuck up then, user is not at fault (like abuse) as you claimed earlier.

    An automated system's fuck up, and one that gets it right hundreds of times per week on dozens of different functions. Happens.

    I only advanced that one because the last two times someone mentioned that it was always Zeta.10 Houston, which is old news by far now. But I didn't entirely close the door to being something else, hence the use of the word "certainly" early on - which has eventually proved to be the case.

    To make it 100% clear: yes, the user was not at fault for any abuse. There was an early correlation to Zeta.10 which has proved not precise.

    Apology?

    The only one due here is due to the fact that the service had to be redeployed. That is some added work and inconvenience.

    But I already wrote earlier on that the user could request some compensation, for example, once things got sorted - that counts as an apology.

  • SaragoldfarbSaragoldfarb Veteran, Megathread Squad

    @zed said:

    @zed said:
    looking forward to the highly-detailed overly-technical explanation for this heh.

    @zed said:
    i think it stands for consistent.

  • alfatarsosalfatarsos Member, Host Rep

    @Saragoldfarb said:

    @zed said:

    @zed said:
    looking forward to the highly-detailed overly-technical explanation for this heh.

    @zed said:
    i think it stands for consistent.

    C-Servers is actually simpler for the meaning of C:

    it's C as in see. "You'll see (C) servers".

    Allows some accessible marketing around the brand. :)

    Thanked by 1Saragoldfarb
  • @alfatarsos said:

    @Saragoldfarb said:

    @zed said:

    @zed said:
    looking forward to the highly-detailed overly-technical explanation for this heh.

    @zed said:
    i think it stands for consistent.

    C-Servers is actually simpler for the meaning of C:

    it's C as in see. "You'll see (C) servers".

    Allows some accessible marketing around the brand. :)

    Or "you can't C your server because we deleted it"

  • SaragoldfarbSaragoldfarb Veteran, Megathread Squad

    @alfatarsos said:

    @Saragoldfarb said:

    @zed said:

    @zed said:
    looking forward to the highly-detailed overly-technical explanation for this heh.

    @zed said:
    i think it stands for consistent.

    C-Servers is actually simpler for the meaning of C:

    it's C as in see. "You'll see (C) servers".

    Allows some accessible marketing around the brand. :)

    Thanks for clearing that up. I always thought it stood for Cunnilingus.

  • SaragoldfarbSaragoldfarb Veteran, Megathread Squad

    @Obelous said:

    @alfatarsos said:

    @Saragoldfarb said:

    @zed said:

    @zed said:
    looking forward to the highly-detailed overly-technical explanation for this heh.

    @zed said:
    i think it stands for consistent.

    C-Servers is actually simpler for the meaning of C:

    it's C as in see. "You'll see (C) servers".

    Allows some accessible marketing around the brand. :)

    Or "you can't C your server because we deleted it"

  • alfatarsosalfatarsos Member, Host Rep
    edited October 1

    @Obelous said:

    @alfatarsos said:

    @Saragoldfarb said:

    @zed said:

    @zed said:
    looking forward to the highly-detailed overly-technical explanation for this heh.

    @zed said:
    i think it stands for consistent.

    C-Servers is actually simpler for the meaning of C:

    it's C as in see. "You'll see (C) servers".

    Allows some accessible marketing around the brand. :)

    Or "you can't C your server because we deleted it"

    Well, that's a good one 😂

    You could also say it was like "Now you C it, now you don't". hehe

    But it all got sorted. :)

  • openidopenid Member

    Fortunately, one of my nat vps has previously reached the end , but it was unavailable for most of the year.

  • @xieyang said:

    @alfatarsos said:
    The only VMs ever eliminated were the ones for the users that had executed fraud at Houston, Texas (Zeta.10), as described in March/April 2026 and sorted out at the time. That will most certainly include yours.

    There are many dozens of VMs at that price that stay available and working at Zeta.10 Houston - therefore, implying that we are deleting any services by cost is wrong.

    Good attempt to bring here some drama, though.

    The VPS I purchased on July 2 (priced at $3.55 with a 36-month term) has been flagged as fraudulent; this contradicts your previous statement that the relevant issues had been resolved between March and April 2026. This is particularly noteworthy given that another VPS I purchased on December 31, 2025 (originally priced at $7.09 with a 36-month term), remains secure and fully operational to this day.

    What is month 31 called where you're from? I only heard of the first 12.

  • TimboJonesTimboJones Member
    edited October 2

    @alfatarsos said:

    @Obelous said:

    @alfatarsos said:

    @barbaros said:

    @alfatarsos said:
    Okay, issue now sorted out. An API call from the WebStore actually went the wrong way on 30-09 and mistakenly eliminated a different VM on the Portal's database.

    I've not only made the service available again, but also corrected the sections of the code where the issue arose, both at the WebStore module and at the Portal, and this is not expected to happen again.

    Wrong periods described by the user aside, that was the root cause, and it's now resolved. :)

    So it's your own fuck up then, user is not at fault (like abuse) as you claimed earlier.

    An automated system's fuck up, and one that gets it right hundreds of times per week on dozens of different functions. Happens.

    I only advanced that one because the last two times someone mentioned that it was always Zeta.10 Houston, which is old news by far now. But I didn't entirely close the door to being something else, hence the use of the word "certainly" early on - which has eventually proved to be the case.

    To make it 100% clear: yes, the user was not at fault for any abuse. There was an early correlation to Zeta.10 which has proved not precise.

    Apology?

    The only one due here is due to the fact that the service had to be redeployed. That is some added work and inconvenience.

    But I already wrote earlier on that the user could request some compensation, for example, once things got sorted - that counts as an apology.

    $3.55/(365 * 3)*10?

    Thanked by 2zejjnt alfatarsos
  • @alfatarsos

    Has the price gone up for the renewal?

  • alfatarsosalfatarsos Member, Host Rep
    edited October 2

    @xieyang said:
    @alfatarsos

    Has the price gone up for the renewal?

    I'm sorry, but this is not a support center. If you have questions about renewals, send them to the company's e-mail, or do not renew in advance and wait for the subsequent invoice to arrive prior to the end date - which, mind you, is only in 2028/29.

    A 2028/29 topic will only be dealt for those users in 2028/29. Obviously. It's insane to even ask otherwise.

    That e-mail should have already been used for the request in question on this topic. LET is not a support forum.

    However, I wouldn't be surprised if pricing would go up in any shape or form for these ultra low-cost plans by that period, given the global market trend and how cheap they were and, honestly, how much hassle users like you give these and other companies with these type of topics like this is Nodeseek.

    You are on a 3.55 USD service for a 3 year plan on a 384MB RAM service. That's 1.18 USD per year. Honest advice? Don't push it.

    That seems the most sensible piece of advice I can give and will also be my final communication on this topic.

    Best regards.

  • @alfatarsos said

    However, I wouldn't be surprised if pricing would go up in any shape or form for these ultra low-cost plans by that period, given the global market trend and how cheap they were and, honestly, how much hassle users like you give these and other companies.

    You are on a 3.55 USD service for a 3 year plan. Honest advice? Don't push it.

    If questioning the price of a contract renewal is viewed as a hassle, then these plans should never have been launched in the first place.

  • forestforest Member
    edited October 2

    @alfatarsos said: I'm sorry, but this is not a support center. If you have questions about renewals, send them to the company's e-mail, or do not renew in advance and wait for the subsequent invoice to arrive prior to the end date - which, mind you, is only in 2028/29.

    I mean, this is LET. It's a place where companies and customers interact. While it's not officially support, it is pretty common that people use it that way when the topic is already up. And I don't just mean MJJs complaining and spamming their support tickets here, but people talking to staff in real-time in the DeluxHost threads, Chunkserve threads, Cloudblast thread, etc.

    Usually it's better to just send a ticket instead, but IIRC you only provide tickets for certain services, not all.

  • @xieyang said:
    @alfatarsos said

    However, I wouldn't be surprised if pricing would go up in any shape or form for these ultra low-cost plans by that period, given the global market trend and how cheap they were and, honestly, how much hassle users like you give these and other companies.

    You are on a 3.55 USD service for a 3 year plan. Honest advice? Don't push it.

    If questioning the price of a contract renewal is viewed as a hassle, then these plans should never have been launched in the first place.

    That's obvious.

  • zedzed Veteran

    over 9000 vps providers, why do you choose to eat this guys shit

  • forestforest Member

    @zed said:
    over 9000 vps providers, why do you choose to eat this guys shit

    Don't kink shame!

  • Good Heavens! It has been 1 year now and the C-servers guy hasn't improved his craft of apologizing!

    First, they suggested the user committed some sort of fraud. Next, they refuse to take responsibility of the mistake made by the automated system they deployed. Compensating the user for the mistake is a good start, but it is not a substitute for an apology. This is a good example of humans becoming Homo-Economicus and not understanding how interpersonal relationships work.

    I don't know what happened, but if my past history is any indication, they are posting here instead of writing support tickets because they were probably not nice to the user in the tickets and closed them prematurely

  • openidopenid Member

    So am I getting this right? First they smear regular users as abusers, then when they realize it’s totally their own fault they don’t even apologize publicly, and they keep sneaking in digs at customers. Can you believet that? My Jesus

Sign In or Register to comment.