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.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
How is ChunkServe
neighhouse
Member
in Providers
Hi,
I'm looking to get some VPSes from ChunkServe, how are their Poland VPSes (which I assume is default Poland because Amsterdamn ones are mentioned separately)
Comments
Oh.. okay how do I delete this thread. My dumbass just needed to dig a little deeper to find a whole box of terrible reviews. Guess that is my answer.
TLDR version: Shit. Dont host anything productive. For everything else its OK
@angstrom lol
The performance and connectivity is decent, but any response to tickets can take weeks, even if it's due to downtime.
the nam says everything.
Hey!
Indeed as some people mentioned, we have some delays with support tickets (especially for NL)., working on it. Also, any new incident (outage/major disruption) should be better communicated.
Regarding connectivity (infra), everything should be more than fine.
While I wouldn't call @Chunkserve super reliable I'm actually quite happy with my (NL) VPS. High bang per buck ratio. Just don't use it for production services requiring 24/7/365 availability.
But for anything else it's really a great deal.
I was looking at your LET VM Special (Xeon Gold NVMe Special 3 to be exact). How is the support for that and is the downtime backed for days? I mean you're being honest so I except you to continue that because honestly your last discussion thread here isn't really confidence inspiring.
Yep, totally agree on that.
With recent situations, the main problem was about DDoS attacks (carpet-bombs) targetting all of our subnets. Once the issue arised, we (and our upstream) started working on it. We did as much filtering as possible on our side - but the main problem was "leaking" traffic.
I do not want to share any attack patterns/vectors/payloads publicly due to obvious reasons.
On Saturday, upstream of our upstream mitigated the situaiton by changing the filters. One issue that arised from it, is it was too strict. This led to some blackholed traffic/timeouts to certain services. At the moment everything should be working fine. I am still going through the tickets, so if I spot any issue, will fix it asap.
The aspect that we should (and will) improve is communication about the problems - Thinking now about swapping the uptime/status page solution to one with ability to subscribe to issues by users (email). This will also lower the amount of the tickets during the incidents, as users will be better aware about the situations.
Regarding the downtime - at the moment there is nothing global and we're doing everything to avoid it. At the end of month, one, big, update is comming to the infrastructure to better handle DDoS incidents - but cannot tell the details. I can recall cuple of situations where indeed there was issue isolated to couple of vms/users, and due to delays on ticket, it remained unresolved for days, but trying to lower amount of such situations to absolute minimum.
If you haven't tried it, you'd better not start.
Chunkserve is dead, and no response to support tickets. DON'T BUY!