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
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.

chunkserve review - a pleasant surprise

2»

Comments

  • I checked on my idler I grabbed a few months ago.

    09:57:23 up 2 days, 13:02, 1 user, load average: 0.00, 0.00, 0.00

  • ElChileElChile Member
    edited April 2025

    I is the only member seeing 4-5 mb/s random Chinese IP traffic into VPS all the time?
    VPS on Amsterdam node 3 and VPS on Amsterdam node 4 both show this.
    Not too bad VPS, but extra 100s GB traffic a month not good.

  • ChunkserveChunkserve Member, Patron Provider

    @jsg said:

    @supremasi said:

    @default said:
    I am bothered by the random reboots. So far I had quite some reboots over the past few months (ever since I got the services). This is not good. Sure, for development this might be good, but I don't like it either way.

    If it was just a some random disconnection of network, that would be totally acceptable; but these are actual reboots, as in turning off the server multiple times, without notification. I don't see this as something good.

    But hey, we have an expert in security who is fine with it. I guess it mostly depends on use case for a person to embrace something like this and call it "pleasant surprise".

    __

    I got 1 random stopped vps, 1 dead vps (really dead, can not start/rescue etc), 1 eternity unsolve ticket

    btw, I have 5 vps: 1 working smooth, 2 idles (stopped), 1 dead, 1 running with random stopped

    @Chunkserve care to explain?

    @supremasi said:

    @default said:
    I am bothered by the random reboots. So far I had quite some reboots over the past few months (ever since I got the services). This is not good. Sure, for development this might be good, but I don't like it either way.

    If it was just a some random disconnection of network, that would be totally acceptable; but these are actual reboots, as in turning off the server multiple times, without notification. I don't see this as something good.

    But hey, we have an expert in security who is fine with it. I guess it mostly depends on use case for a person to embrace something like this and call it "pleasant surprise".

    __

    I got 1 random stopped vps, 1 dead vps (really dead, can not start/rescue etc), 1 eternity unsolve ticket

    btw, I have 5 vps: 1 working smooth, 2 idles (stopped), 1 dead, 1 running with random stopped

    Can You please reply to me on the ticket? Regaring the dead server - I asked You about 1 thing so I can investigate. Let me know and we're handling that.

  • @Chunkserve said:

    @jsg said:

    @supremasi said:

    @default said:
    I am bothered by the random reboots. So far I had quite some reboots over the past few months (ever since I got the services). This is not good. Sure, for development this might be good, but I don't like it either way.

    If it was just a some random disconnection of network, that would be totally acceptable; but these are actual reboots, as in turning off the server multiple times, without notification. I don't see this as something good.

    But hey, we have an expert in security who is fine with it. I guess it mostly depends on use case for a person to embrace something like this and call it "pleasant surprise".

    __

    I got 1 random stopped vps, 1 dead vps (really dead, can not start/rescue etc), 1 eternity unsolve ticket

    btw, I have 5 vps: 1 working smooth, 2 idles (stopped), 1 dead, 1 running with random stopped

    @Chunkserve care to explain?

    @supremasi said:

    @default said:
    I am bothered by the random reboots. So far I had quite some reboots over the past few months (ever since I got the services). This is not good. Sure, for development this might be good, but I don't like it either way.

    If it was just a some random disconnection of network, that would be totally acceptable; but these are actual reboots, as in turning off the server multiple times, without notification. I don't see this as something good.

    But hey, we have an expert in security who is fine with it. I guess it mostly depends on use case for a person to embrace something like this and call it "pleasant surprise".

    __

    I got 1 random stopped vps, 1 dead vps (really dead, can not start/rescue etc), 1 eternity unsolve ticket

    btw, I have 5 vps: 1 working smooth, 2 idles (stopped), 1 dead, 1 running with random stopped

    Can You please reply to me on the ticket? Regaring the dead server - I asked You about 1 thing so I can investigate. Let me know and we're handling that.

    you only responded to Ticket #GFR-322222 about my vps that just went off and can't be started.
    that previously experienced several random stops.
    the funny thing is: I already explained that the vps is off and can't be turned on, you answered by asking if I can access it via VNC

    for dead vps (can't start, reinstall, etc) is in Ticket #LSY-127522, which you last replied on March 16th, there was no response from you whatsoever after I responded back and still no solution until now,

    Thanked by 2dedimark Chunkserve
  • ChunkserveChunkserve Member, Patron Provider

    @supremasi said:

    @Chunkserve said:

    @jsg said:

    @supremasi said:

    @default said:
    I am bothered by the random reboots. So far I had quite some reboots over the past few months (ever since I got the services). This is not good. Sure, for development this might be good, but I don't like it either way.

    If it was just a some random disconnection of network, that would be totally acceptable; but these are actual reboots, as in turning off the server multiple times, without notification. I don't see this as something good.

    But hey, we have an expert in security who is fine with it. I guess it mostly depends on use case for a person to embrace something like this and call it "pleasant surprise".

    __

    I got 1 random stopped vps, 1 dead vps (really dead, can not start/rescue etc), 1 eternity unsolve ticket

    btw, I have 5 vps: 1 working smooth, 2 idles (stopped), 1 dead, 1 running with random stopped

    @Chunkserve care to explain?

    @supremasi said:

    @default said:
    I am bothered by the random reboots. So far I had quite some reboots over the past few months (ever since I got the services). This is not good. Sure, for development this might be good, but I don't like it either way.

    If it was just a some random disconnection of network, that would be totally acceptable; but these are actual reboots, as in turning off the server multiple times, without notification. I don't see this as something good.

    But hey, we have an expert in security who is fine with it. I guess it mostly depends on use case for a person to embrace something like this and call it "pleasant surprise".

    __

    I got 1 random stopped vps, 1 dead vps (really dead, can not start/rescue etc), 1 eternity unsolve ticket

    btw, I have 5 vps: 1 working smooth, 2 idles (stopped), 1 dead, 1 running with random stopped

    Can You please reply to me on the ticket? Regaring the dead server - I asked You about 1 thing so I can investigate. Let me know and we're handling that.

    you only responded to Ticket #GFR-322222 about my vps that just went off and can't be started.
    that previously experienced several random stops.
    the funny thing is: I already explained that the vps is off and can't be turned on, you answered by asking if I can access it via VNC

    for dead vps (can't start, reinstall, etc) is in Ticket #LSY-127522, which you last replied on March 16th, there was no response from you whatsoever after I responded back and still no solution until now,

    Thank You for clarificarion. If its not a problem, I’ll merge those tickets to clean this up. Will reply in 5mins.

  • twaintwain Member

    What do you guys expect for these prices? Get real guys

  • jsgjsg Member, Resident Benchmarker

    @twain said:
    What do you guys expect for these prices? Get real guys

    To be honest I expected a crappy VPS - but was positively surprised and had no downtime or reboot so far.

    But you are right insofar as of bloody course one can expect only so much for that price and it's to be expected that some corners have been cut. But still, I'm happy with that thingy so far.

  • good information

  • @Chunkserve Tickets from April 8th have not received any reply, I sent a private message on this forum and there was also no reply, VPS turns off by itself every 24 hours, and has to be started manually, I don't understand what happened, even though the usage is normal for both CPU and RAM

  • itachikonohaitachikonoha Member
    edited April 2025

    Just a disclaimer from my side:

    I did complain about the random shutdown but a little bit of fault was upon me too because I didn't raise a ticket. I believed that since these VPS were in heavy discount, so some level of annoyance was something I will have to deal with.

    Chunkserve did contact me and ask to raise ticket if I face the same. That was a very pleasant interaction and will raise a ticket if the issue arise.

    Thanked by 3JohnnySac zed jsg
  • @Calypso said:
    I'm reasonably happy. In the beginning there were quite a few issues, most of them are gone now. VPS is fairly stable and network issues are not that many anymore.

    However, if you need them, you're in for a treat. Well... a wait basically. But when your ticket or your issue is picked up he's helpfull and will go a long way to get a solution.

    I must add something to my original comments. Especially about things said here and in tickets by @Chunkserve. To be honest: I think things are growing a bit above his head; that shows in response time through tickets since the beginning, but also in how improvements are not always made even if it is seen.

    Sometimes I experience a lot (and I mean periods of over 80%) CPU steal. When I put a ticket in that some time ago it was "We've taken measures to prevent" and "we do monitor it". But then it keeps on happening and when my monitoring shows it, his (if present) should be able too. And the issue should not suddenly be limited just after a response to my ticket (after quite a long while of seeing it again) that it will be looked at - i.e. monitoring should have alterted him before so that it can be mitigated.

    The same goes with the sender e-mail address of tickets; it has been mentioned on LET before that they still have the default from-address (@example.com). It was read an reacted on that it'd be taken care of. Still is the same.

  • ChunkserveChunkserve Member, Patron Provider

    @Calypso said:

    @Calypso said:
    I'm reasonably happy. In the beginning there were quite a few issues, most of them are gone now. VPS is fairly stable and network issues are not that many anymore.

    However, if you need them, you're in for a treat. Well... a wait basically. But when your ticket or your issue is picked up he's helpfull and will go a long way to get a solution.

    I must add something to my original comments. Especially about things said here and in tickets by @Chunkserve. To be honest: I think things are growing a bit above his head; that shows in response time through tickets since the beginning, but also in how improvements are not always made even if it is seen.

    Sometimes I experience a lot (and I mean periods of over 80%) CPU steal. When I put a ticket in that some time ago it was "We've taken measures to prevent" and "we do monitor it". But then it keeps on happening and when my monitoring shows it, his (if present) should be able too. And the issue should not suddenly be limited just after a response to my ticket (after quite a long while of seeing it again) that it will be looked at - i.e. monitoring should have alterted him before so that it can be mitigated.

    The same goes with the sender e-mail address of tickets; it has been mentioned on LET before that they still have the default from-address (@example.com). It was read an reacted on that it'd be taken care of. Still is the same.

    Hey!
    I already replied to a ticket explaining the situation :) We were handing one abusive customer (CPU) - already passed the details on the ticket, why suspending abusive servers didn't fixed it instantly + compensanted for that.

  • @Chunkserve said:
    I already replied to a ticket explaining the situation :) We were handing one abusive customer (CPU) - already passed the details on the ticket, why suspending abusive servers didn't fixed it instantly + compensanted for that.

    You go by on the real points I'm making: it should have been seen through monitoring. Abusive users will always be present - esp. when you're low end. When I entered the ticket it was already going on for 12 hours.

    Also the other thing: after all this time your from mailaddress is still @example.com - so basically many filters will consider it spam. Has been pointed out several times already, but still isn't solved, and it's such an easy thing to change...

    Thanked by 2Chunkserve jsg
  • jsgjsg Member, Resident Benchmarker

    @sangatsetia said:
    ... VPS turns off by itself every 24 hours, and has to be started manually ...

    FWIW, mine has an uptime of almost 20 days that is, no reboot besides maybe during the first days.

    @Chunkserve

    You started successfully and even managed to come up in my top-3 lists. Now it basically boils down to two options: either listen to your customers, work your ass off, steadily improve things ... and grow - or - take everything lightly, don't care too much about what your customers say, and rest on what you've achieved so far ... and sooner or later loose it.

    And @Calypso is right, proper and tight monitoring is a must. Big, big Contabo for instance lost lots of customers and reputation basically IMO due to monitoring (and quickly reacting) problems. Don't repeat their mistake!

    I wish you success.

  • GerritGerrit Member
    edited July 2025

    @sangatsetia said:
    @Chunkserve Tickets from April 8th have not received any reply, I sent a private message on this forum and there was also no reply, VPS turns off by itself every 24 hours, and has to be started manually, I don't understand what happened, even though the usage is normal for both CPU and RAM

    I should have read your review before i ordered.

    Looks like it's more a rule than exception for their late responses... I have been waiting for more than 2 weeks to get a rDNS removed. And waiting for 1 1/5 week to get a refund.

    I can't do sh** with a VM where I can't trust customer services in answering tickets, resolving issues within an acceptable period of time.

    July 8th, ordered.
    July 8th, requested a rDNS to be set up.
    July 8th, minor mistake by me with wrong A-records, but resolved right away and notified them.
    July 10th, notified them again.
    July 12th, Enough bullsh** now... let's cancel, refund and move on.
    July 12th, send new ticket with cancelation and refund request.
    July 13th, CS promised a refund and removal of rDNS.
    July 25th, CS rDNS finally removed (cached for 1 1/2 week). No further information and details on the refund.

    And now... only one day left untill we're 3 weeks into the matter.

    {1 out of 5 stars} So as for Customer Experience, even 1 star is way to much.
    {4 out of 5 stars} Network... Not the best routing / path, but certainly acceptable.
    {4 out of 5 stars} VM is pretty good tbh.
    {4 out of 5 stars} Controlpanel (missing setting up a rDNS by myself and using my own .iso)

    But the most important thing (for me) is the customer experience, if something goes wrong, I can trust that it will be addressed and resolved quickly and adequately. What has not happened so far.

  • To add another personal review. I ordered it with no expectation, would be total idler. One day server went down (node I am on had issues apparently). And when it was backup, the content of the disk was gone. It was like unpartitioned empty disk. I don't have any data on it but whole disk getting wiped or whatever, gave me zero trust. Of course you have to have personal backups but just having to restore your backup just because the node failed is just a sour experience.

    I won't mention about ticket reply times. It's one man operation, so as usual LET provider, if you don't have to rely on tickets and if your VPS wouldn't get wiped for whatever reason, all is fine. If not, then good luck getting a response to your ticket.

    Anyways, won't renew, and actually was thinking at some point to give server away to someone else for free.

    Thanked by 2oloke fly056
  • ChunkserveChunkserve Member, Patron Provider

    @Gerrit said:

    @sangatsetia said:
    @Chunkserve Tickets from April 8th have not received any reply, I sent a private message on this forum and there was also no reply, VPS turns off by itself every 24 hours, and has to be started manually, I don't understand what happened, even though the usage is normal for both CPU and RAM

    I should have read your review before i ordered.

    Looks like it's more a rule than exception for their late responses... I have been waiting for more than 2 weeks to get a rDNS removed. And waiting for 1 1/5 week to get a refund.

    I can't do sh** with a VM where I can't trust customer services in answering tickets, resolving issues within an acceptable period of time.

    July 8th, ordered.
    July 8th, requested a rDNS to be set up.
    July 8th, minor mistake by me with wrong A-records, but resolved right away and notified them.
    July 10th, notified them again.
    July 12th, Enough bullsh** now... let's cancel, refund and move on.
    July 12th, send new ticket with cancelation and refund request.
    July 13th, CS promised a refund and removal of rDNS.
    July 25th, CS rDNS finally removed (cached for 1 1/2 week). No further information and details on the refund.

    And now... only one day left untill we're 3 weeks into the matter.

    {1 out of 5 stars} So as for Customer Experience, even 1 star is way to much.
    {4 out of 5 stars} Network... Not the best routing / path, but certainly acceptable.
    {4 out of 5 stars} VM is pretty good tbh.
    {4 out of 5 stars} Controlpanel (missing setting up a rDNS by myself and using my own .iso)

    But the most important thing (for me) is the customer experience, if something goes wrong, I can trust that it will be addressed and resolved quickly and adequately. What has not happened so far.

    Hey, RDNS and own iso feature is on the roadmap to add soon. Regarding routes, if You can DM me if anything is wrong, we can try checking if it can be re-routed via better path :) Sorry to hear Your experiences. The revDNS was previously created for another customer, and when the vm was terminated, IP went back to the pool - that's why there was an existing record. I don't remember what VM we suspended in the past - but there was a case with "gambling-like" site that we suspended asap after receiving abuse e-mail. Regarding the disk, we did not experienced any global issue with any array - I'm not sure if it was on Your ticket, or someone else, but I asked about any changes made in partition table. Even if something was corrupted, there are tools that may recover it (in most cases). I'm sending You a DM now regarding Your comment. Thank You for the honest words and have a great day!

    Thanked by 1JohnnySac
Sign In or Register to comment.